Home › Converters › Safari to Proton Pass
Safari to Proton Pass converter
Safari and Proton Pass both use CSV, but Safari writes 6 columns; Proton Pass expects 11 in a different order — so Proton Pass rejects a raw Safari export or silently files everything into the wrong fields. Drop your export below and get back a file Proton Pass accepts.
Convert your Safari export
The conversion runs entirely in this tab using JavaScript. Your file is never sent to a server — you can confirm it by opening your browser's Network tab, or by turning off Wi-Fi before you drop the file in. Prefer not to do this in a browser tab at all? Download the converter and run it from your own disk.
What's actually different between the two formats
Only 3 of 6 column names match (url, username, password), and they're in a different order — enough for Proton Pass to accept the file and then put your passwords in the wrong fields.
| Safari column | Proton Pass column | What happens |
|---|---|---|
Title | name | Renamed and repositioned |
Username | username | Renamed and repositioned |
Password | password | Renamed and repositioned |
URL | url | Renamed and repositioned |
OTPAuth | totp | Renamed and repositioned |
Notes | note | Renamed and repositioned |
— none — | vault | Left empty — Safari exports nothing for this. |
What carries over
| Field | Safari | Proton Pass | Result |
|---|---|---|---|
| Item name / title | Yes | Yes | Carried over |
| Username and password | Yes | Yes | Carried over |
| Website URL | Yes | Yes | Carried over |
| Notes | Yes | Yes | Carried over |
| Folders / groups | No | Yes | Not in the source file |
| Two-factor (TOTP) secrets | Yes | Yes | Carried over |
| Favorites | No | No | Not in the source file |
| Custom fields | No | No | Not in the source file |
| Multiple URLs per entry | No | No | Not in the source file |
| File attachments | No | No | Not in the source file |
Step 1 — Export from Safari
- On macOS Sequoia or later, passwords moved to the Passwords app — open that instead of Safari.
- On earlier macOS: Safari → Settings → Passwords, then the ••• button → Export All Passwords.
- Confirm with Touch ID or your Mac login password.
- Save the CSV.
Watch out for
- Safari and the Passwords app share one iCloud Keychain store and one CSV layout — importing to either lands in the same place.
- There is no folder structure in iCloud Keychain, so groups from the source have to go into notes.
Step 2 — Convert it
Drop the file onto the converter above. It parses Safari's layout, maps each field onto the universal record, then writes Proton Pass's exact expected columns — including the empty ones its importer requires and, where the two differ, the right shape for 2FA secrets. You'll see a preview and a list of anything Proton Pass can't hold before you download.
Rather not put this file in a browser tab connected to the internet? The same converter is available as a single HTML file you can download and open with your network switched off.
Step 3 — Import into Proton Pass
- Open Proton Pass → Settings → Import.
- Choose the matching source, or "Generic CSV" if the source is not listed.
- Upload the converted file and pick a destination vault.
Watch out for
- Proton Pass splits identity between email and username. If your source only has one login field, the converter puts an address that looks like an email in the email column and everything else in username.
- The vault column controls which Proton vault an item lands in. Folders from the source map onto it.
Step 4 — Verify and clean up
- Open ten entries in Proton Pass at random and check them against Safari.
- Generate a 2FA code for one account in Proton Pass and confirm it matches Safari. A TOTP secret that imported wrong fails silently until you're locked out.
- Sign in to one real site using Proton Pass to confirm autofill works.
- Delete both CSV files and empty your trash. If your Downloads folder syncs to iCloud, OneDrive or Dropbox, confirm the deletion propagated there too.
- Only then close your Safari account — and change any password you suspect was exposed while the plaintext file existed.
Questions
Why won't Proton Pass import my Safari file directly?
Only 3 of 6 column names match (url, username, password), and they're in a different order — enough for Proton Pass to accept the file and then put your passwords in the wrong fields. The converter rewrites the file into Proton Pass's exact expected layout, including the column order and any empty columns its importer requires.
Do my passwords get uploaded anywhere?
No. The conversion is JavaScript running in your own browser tab — the file is read with the FileReader API, transformed in memory, and handed back to you as a download. There is no upload, no server-side processing and no analytics attached to the file. You can verify this by disconnecting from the internet before you drop the file in: the conversion still works.
Does anything get lost moving from Safari to Proton Pass?
Proton Pass supports every field Safari exports, so a standard login entry survives intact — name, username, password, URL, notes, folder and 2FA secret. File attachments are the exception: no CSV export from any manager includes them, so download those separately before you close your Safari account.
Will my two-factor codes still work after the move?
Yes, as long as Safari exported the secrets. Safari and Proton Pass store them in different shapes — one uses a bare Base32 secret, the other a full otpauth:// URI — and the converter translates between them, which is the step most manual migrations get wrong. Check a couple of codes against your old vault before you delete it, since a TOTP secret that fails to import is silent until you're locked out.
Is the export file from Safari encrypted?
No. A Safari CSV export is plaintext — every password in it is readable by anything that can open the file, including other apps on your machine and anything that syncs your Downloads folder to the cloud. Convert it, import it, then delete both files and empty your trash. If your Downloads folder syncs to iCloud, OneDrive or Dropbox, check that the deletion propagated.
Anything unusual about Safari's export?
Safari and the Passwords app share one iCloud Keychain store and one CSV layout — importing to either lands in the same place.
Anything unusual about importing into Proton Pass?
Proton Pass splits identity between email and username. If your source only has one login field, the converter puts an address that looks like an email in the email column and everything else in username.
Related converters
Other routes out of Safari
- Safari → 1Password
- Safari → Apple Passwords
- Safari → Bitwarden
- Safari → Dashlane
- Safari → Enpass
- Safari → Google Chrome
- Safari → KeePassXC
- Safari → Keeper
- Safari → LastPass
- Safari → Microsoft Edge
- Safari → Mozilla Firefox
- Safari → NordPass
- Safari → RoboForm
Other ways into Proton Pass
- 1Password → Proton Pass
- Apple Passwords → Proton Pass
- Bitwarden → Proton Pass
- Dashlane → Proton Pass
- Enpass → Proton Pass
- Google Chrome → Proton Pass
- KeePassXC → Proton Pass
- Keeper → Proton Pass
- LastPass → Proton Pass
- Microsoft Edge → Proton Pass
- Mozilla Firefox → Proton Pass
- NordPass → Proton Pass
- RoboForm → Proton Pass
Moving the other way? Proton Pass → Safari · All 210 converters