Importing passwords into Google Chrome is commonly done to migrate logins from another browser or password manager, consolidate credentials, or restore saved sign-ins after reinstalling Chrome. This evergreen explainer describes secure, supported methods using Chrome’s built-in importer, CSV and JSON file handling, and critical precautions to keep credentials safe. Topics include source formats, what to expect during import, how to verify success, and how to maintain strong post-import hygiene. The instructions apply to current stable versions of Chrome on Windows, macOS, Linux, and ChromeOS-like channels where available.
How the Chrome password importer works
Chrome’s native importer reads widely supported file formats and maps entries into the saved-passwords store accessible at chrome://settings/passwords. It does not overwrite existing passwords for sites already in Chrome unless you confirm replacement; duplicates may be created if the same site appears with different usernames. The tool supports major sources, including browsers (such as Edge, Firefox, and Safari) and CSV files exported from other password managers. Note that encrypted formats like browser-specific JSON databases typically require an intermediate CSV export rather than direct import. Understand these behaviors to avoid surprises during migration.
Prepare before you import
Before importing, decide whether you want all entries or only specific ones, and confirm the source format. If you are moving from another browser, export or back up that data first. Save CSV exports to a known location, verify column headers match expectations (typically domain, username, password), and avoid storing the import file on insecure or shared devices. If you use a third‑party password manager, consult its export documentation to ensure compatibility with Chrome’s username and password fields. These precautions reduce the risk of mistakes or exposure.
Supported sources and formats
Common import sources and formats include:
- Browsers: Edge, Firefox, Safari, and other Chromium-based browsers via Chrome’s import UI.
- CSV files: Must contain at least domain, username, and password columns; additional columns such as signon realm and notes are allowed and handled gracefully.
- JSON files: Generally not accepted directly; export to CSV first if your source uses encrypted stores.
- Browser-specific backups: May require export to CSV before importing into Chrome.
Step-by-step: Import from another browser
To import passwords from another browser into Chrome:
- Open Chrome and go to
chrome://settings/importData. - Select the source browser or file, then choose what to import (bookmarks, history, passwords, settings).
- If importing passwords only, deselect other items to limit scope.
- Confirm the import and wait for completion; review the password list at
chrome://settings/passwords. - Use Chrome’s built-in leak check and update any weak or reused passwords.
Step-by-step: Import from a CSV file
To import passwords from a CSV file:
- Ensure the CSV includes headers such as
origin(domain URL),username, andpassword; match Chrome’s expected column names when possible. - Open Chrome Settings > Autofill > Passwords, then choose Import.
- Select your CSV file and map columns if prompted; confirm replacement behavior for duplicates.
- After import, verify a sample of entries in
chrome://settings/passwordsand sign in to a few sites to confirm functionality. - Shred or securely delete the local CSV file if it contains sensitive credentials.
Verify and manage imported passwords
After import, visit chrome://settings/passwords to confirm that entries appear correctly, check for duplicates, and edit or remove any incorrect items. Use Chrome’s password health features to identify weak, reused, or compromised logins. If you rely on Chrome as your primary vault, enable Sync and 2SV to protect the stored data. Periodically audit large imports to remove obsolete or risky credentials.
Security best practices and limitations
Keep these security considerations in mind when importing passwords:
- Transport security: Imports from browsers usually occur over local channels; CSV transfers should be done over secure, private networks.
- Encryption at rest: Chrome encrypts saved passwords with your OS profile or account key; it is not a substitute for a dedicated, encrypted password manager for high-risk users.
- Duplicates and conflicts: Chrome does not automatically merge identical domains with different usernames; manually consolidate entries when needed.
- Backup: Export a backup of important passwords before large imports or browser changes.
- Updates: Chrome’s import behavior may change slightly across major versions; check release notes if workflows change unexpectedly.
Import source comparison at a glance
| Import source | Direct support | Typical format | Notes |
|---|---|---|---|
| Edge, Firefox, Safari | Yes | Internal browser export | Works via Chrome UI; may require temporary profile or CSV fallback. |
| Other password managers | Usually via CSV | CSV (domain, username, password) | Export from source first; verify column names and encoding. |
| CSV file | Yes | CSV with correct headers | Good for one-time migrations; securely delete file after import. |
| JSON database | No | Browser-specific encrypted JSON | Export to CSV externally before importing into Chrome. |
Troubleshooting and aftercare
If some logins do not appear, check column headers, verify the domain URL format (use the exact hostname as in the address bar), and ensure entries are not blocked by Chrome policies (e.g., enterprise-managed imports). For repeated issues, export a small test CSV (three to five rows) to validate the workflow before scaling up. After import, run Chrome’s password check, update any weak credentials, and consider using a dedicated password manager if you need advanced auditing, alerts, or cross-platform encrypted sharing.