Move Saved Passwords Between Browsers: Chrome, Edge, Firefox, and Safari

Moving to a new browser is painless until you realize hundreds of saved logins are stranded inside the old one. I have switched browsers three times in the past two years, and the password question stops most people before they even begin.

The answer is simpler than it looks. Chrome, Edge, Firefox, and Safari all export saved passwords as a CSV file in about two minutes. The one thing you must know before you start: delete that CSV the moment your import finishes, because it stores every password in plain, readable text with zero encryption.

Quick Answer

Export your saved passwords from the old browser’s settings as a CSV file, then import that file in the new browser’s password manager. The whole process takes about five minutes. Delete the CSV immediately after — it stores every password in plain text and is a serious security risk if left on your device.

How Do I Export Passwords from My Old Browser?

Here is what each browser supports before you start:

Browser	Export to CSV	Import from CSV	Where to Find It
Google Chrome	Yes	Yes	Settings → Google Password Manager → gear icon
Microsoft Edge	Yes	Yes	edge://settings/passwords → three-dot menu
Mozilla Firefox	Yes (v79+)	Yes	Menu → Passwords → three-dot menu
Safari	No	Yes (Mac only)	File → Import From → Passwords CSV file

Export from Google Chrome

1. Click the three-dot menu → Settings → Autofill and passwords → Google Password Manager.
2. Click the Settings gear in the upper right corner.
3. Select Export passwords and confirm when prompted.
4. Enter your computer login password if asked, then save the file to your Desktop.

Export from Microsoft Edge

1. Type edge://settings/passwords in the address bar and press Enter.
2. Click the three-dot icon next to “Saved passwords” → Export passwords → Export passwords.
3. Save the file to your Desktop.

Export from Mozilla Firefox

This requires Firefox version 79 or later. Update first via Help → About Firefox if needed. If you run into trouble with an older version, Mozilla’s official export documentation covers the steps in detail.

1. Click the hamburger menu → Passwords.
2. In the Passwords window, click the three-dot menu in the upper right → Export logins.
3. Confirm the warning, then save the file to your Desktop.

Pro tip: Save the CSV to your Desktop, not your Downloads folder. It is harder to forget to delete when it is sitting right in front of you.

All three browsers bury the export option inside password manager settings — once you know where to look, the export takes under a minute.

How Do I Import Passwords Into the New Browser?

Import into Google Chrome

1. Go to Settings → Autofill and passwords → Google Password Manager → the gear icon.
2. Click Import passwords → Select file, choose the CSV, and click Open.
3. Chrome shows how many entries were added and flags any duplicates.

Import into Microsoft Edge

1. Go to edge://settings/passwords.
2. Click the three-dot icon → Import passwords → From a CSV file.
3. Select the CSV and click Import. Edge shows a summary count when finished.

Import into Mozilla Firefox

1. Open the Passwords window (menu → Passwords).
2. Click the three-dot menu → Import from a File → select the CSV.

Import into Safari (Mac only)

1. In Safari, go to File → Import From → Passwords CSV file.
2. Authenticate with your Mac password or Touch ID, select the CSV, and click Import.

After importing, test two or three logins you use every day. When I moved about 340 passwords from Chrome to Firefox, three entries had imported with an extra space appended to the password — a quirk caused by a special character in the original entry. Testing right away caught it before it turned into a lockout.

If you use multiple Chrome profiles for work and personal browsing, see my guide on setting up Chrome profiles before exporting, so you know which profile’s passwords you are moving.

Spot-checking five key logins right after import catches nearly all character-encoding issues before they become a problem.

Why Should I Delete the CSV File Right Away?

The CSV file has no password and no encryption. Any person or piece of malware that opens it can read every username and password instantly. Treat it like a sticky note with your bank PIN — use it once, then destroy it.

1. Right-click the file on your Desktop → Delete (Windows) or Move to Trash (Mac).
2. Empty the Recycle Bin or Trash immediately.
3. On Windows, open File Explorer and check Quick Access → Recent files to confirm no auto-saved copy exists elsewhere.

Troubleshooting tip: If Chrome reports “0 passwords imported,” open the CSV in Notepad and check the first row. Chrome requires the headers to read exactly name,url,username,password. Edge sometimes exports with slightly different column labels that Chrome rejects — rename the headers, save the file, and try the import again.

The unencrypted CSV is the single biggest security risk in this entire process — deleting it is not optional.

What Are the Most Common Password Migration Mistakes?

1. Leaving the CSV on your device. It is completely unencrypted. Fix: set a two-minute phone timer the moment you save the file.
2. Skipping the post-import test. Special characters in passwords can cause silent import errors. Fix: manually test five key logins right after importing.
3. Creating duplicates. Importing into a browser that already has some passwords saved adds them twice. Fix: clear the existing password list first, or use the browser’s built-in duplicate finder afterward.
4. Leaving sync on in the old browser. Chrome and Edge keep syncing passwords to your Google or Microsoft account unless you turn it off. Fix: sign out of sync in the old browser’s settings once migration is confirmed complete.
5. Doing this repeatedly when you switch browsers often. A free password manager like Bitwarden removes the migration problem permanently — credentials follow the extension, not the browser. Before switching, check my comparison of Chrome vs Edge vs Firefox privacy defaults to pick the right browser from the start.

Most migration headaches come from two sources: leaving the CSV on the device too long, and skipping the post-import test — both take under two minutes to prevent.

Frequently Asked Questions

Is it safe to export browser passwords as a CSV file?

Safe only if you delete the file immediately after importing. The CSV is unencrypted plain text — no password, no protection. I always delete it and empty the Trash within five minutes of finishing the import.

Will importing passwords overwrite what is already saved in the new browser?

No. Imports add entries rather than replace them. Browsers flag duplicates and skip them, so existing passwords stay intact. If you see duplicates afterward, use the browser’s built-in password manager to clean them up.

Can I transfer Chrome passwords to Safari on iPhone?

Not directly via CSV on mobile. The cleanest path is to import the CSV into Safari on a Mac first, then let iCloud Keychain sync those credentials to your iPhone automatically — no cable required.

Why does Firefox show no export option?

CSV export was added in Firefox version 79. Go to Help → About Firefox to check and trigger an update. Once current, the Export logins option appears in the Passwords window’s three-dot menu.

Should I use a dedicated password manager instead of browser-saved passwords?

For most people, yes. A free tool like Bitwarden stores credentials independently of any browser, eliminating migrations entirely. It also pairs naturally with two-factor authentication for a much stronger overall account security setup.

Conclusion

Moving saved passwords between browsers takes about five minutes: export a CSV from the old browser, import it in the new one, and delete the file immediately. The only real danger is leaving that unencrypted file sitting on your device.

Not sure which browser to land in? My side-by-side look at Chrome, Edge, and Firefox privacy defaults shows which one protects your data right out of the box — choose the right browser first and you may never need to migrate again.