How to Import Passwords From Safari to Chrome
To import passwords from Safari to Chrome, export your saved logins from Safari as a CSV file, then import that file into Chrome. This is the most reliable cross-platform method and works on both macOS and Windows when Chrome can read the exported CSV. Before you begin, make sure both browsers are updated and that you have access to your macOS keychain if Safari requests it.
Export Saved Passwords From Safari
Safari stores passwords in macOS Keychain and can export them as a CSV, which Chrome can read. There is no direct one-click sync between Safari and Chrome, so an intermediate file is required. Follow these steps to export from Safari on macOS.
Step 1: Open the Keychain Access app
Open Keychain Access (located in Applications > Utilities). Search for Safari or chrome entries. Safari passwords are stored under the login keychain, typically labeled with the website or domain name.
Step 2: Export passwords from Keychain Access
Keychain Access can export keychain items, but it does not export passwords directly as a CSV. A safer and more practical method is to export passwords from within Safari using its built-in password manager, which produces a CSV that Chrome accepts.
Step 3: In Safari, open Preferences and go to Passwords
In Safari on macOS, choose Safari > Settings (or Preferences) from the menu bar, then click Passwords. You may be prompted to authenticate with your Mac login password or use Touch ID or Face ID.
Step 4: Export the list
Click the Export button and save the CSV file to a location you can find later. If the Export button is not available, use the manual method below. This CSV will include site URLs, usernames, and hidden passwords in plain text.
Manual export if Export is unavailable
Select all password rows in the list, copy them, and paste them into a CSV-formatted file with three columns: item, username, and password. Be cautious when handling this file, since it contains sensitive credentials in clear text.
Prepare Chrome for Import
Chrome organizes passwords in its own password manager and can import CSV files. Before importing, confirm that you are signed into Chrome with the profile you want to use. You can import passwords into Chrome on Windows, macOS, Linux, and ChromeOS with consistent steps.
On Windows or macOS
Open Chrome, click your profile icon, then go to Settings > Autofill > Passwords. Click Import and select the CSV you exported from Safari. Follow the prompts to complete the import. Chrome will show a summary of imported entries and flag any duplicates.
On Linux
The steps are the same: open Chrome settings, go to Passwords, and use the Import option. Ensure the file path to your CSV is correct and that Chrome has file access permissions.
On ChromeOS
In ChromeOS, open Settings > Autofill > Passwords, then choose Select file to import. Note that ChromeOS may require you to authenticate at the device level before allowing the import.
Verify the Import
After the import finishes, review your Chrome password list to confirm that entries were added correctly. Check that usernames and URLs match and that there are no duplicate entries that could cause confusion later. You can search for specific sites in Chrome’s password manager to quickly validate.
Privacy and Sync Considerations
CSV files contain plain-text passwords, so protect them just like any sensitive credential. Delete the file after import or move it to an encrypted location. If you no longer need it, securely erase it from your storage. Also consider whether you want Chrome to sync passwords to your Google account; enabling sync can make passwords available across your Chrome devices.
Alternative Cross-Browser Options
If you frequently move data between browsers, consider using a password manager that supports both Safari and Chrome. Many modern managers support import and export in standard formats and can act as a single source of truth. This avoids repeated CSV handling and reduces exposure of plain-text passwords.
| Attribute | Verified Detail | Source Type |
|---|---|---|
| Export format from Safari | CSV (comma-separated values) | Browser feature (Safari > Preferences > Passwords) |
| Chrome import location | Settings > Autofill > Passwords > Import | Chrome stable channel help documentation |
| Authentication required | Yes: macOS login password, Touch ID, or Face ID for Keychain; Chrome profile sign-in for import | Browser and OS security prompts |
| Password visibility | Plain text in the CSV; handle with care and delete after use | Security best practice guidance |
| Duplicate handling | Chrome flags duplicates during import; review and resolve conflicts manually | Chrome import workflow |
| Cross-platform support | Works on Windows, macOS, Linux, and ChromeOS when using CSV export/import | Chrome cross-platform behavior |
Common Issues and How to Resolve Them
- Missing Export button in Safari: Use the manual copy-paste into a CSV method; ensure you include the correct three columns (item, username, password).
- Import fails or shows zero passwords: Confirm the CSV header matches expected columns and that the file is saved as UTF-8 encoded text.
- URL mismatches (http vs https): Chrome may treat these as different entries; check both versions in your list after import.
- Authentication errors: Make sure you have full disk access for Chrome if prompted in macOS Security & Privacy settings.
Sync, Backups, and Future-Proofing
Once passwords are in Chrome, you can rely on Chrome Password Manager sync to keep them available across devices, provided you remain signed in and have sync enabled. For ongoing backups, export a fresh CSV periodically and store it securely, such as in an encrypted folder. If you switch primary browsers often, evaluate a dedicated password manager that supports seamless cross-platform sync and reduces manual export/import steps.
Final Notes
Importing passwords from Safari to Chrome is straightforward when you use Safari’s built-in CSV export and Chrome’s import tool. Always protect the exported CSV, review entries after import, and consider long-term solutions if you regularly move credentials between browsers. This process is reliable and repeatable, making it suitable for periodic use or migration planning.