Home › Converters › Google Chrome to Proton Pass
Google Chrome to Proton Pass converter
Google Chrome and Proton Pass both use CSV, but Google Chrome writes 5 columns; Proton Pass expects 11 in a different order — so Proton Pass rejects a raw Chrome export or silently files everything into the wrong fields. Drop your export below and get back a file Proton Pass accepts.
Convert your Google Chrome 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
Every column Chrome exports has a counterpart in Proton Pass, but they come out in a different order, and Proton Pass expects 6 more columns that Chrome never writes. A CSV importer reads by position as much as by name, so the file still needs rebuilding.
| Google Chrome column | Proton Pass column | What happens |
|---|---|---|
name | name | Same name, position adjusted |
username | username | Same name, position adjusted |
password | password | Same name, position adjusted |
url | url | Same name, position adjusted |
— none — | totp | Left empty — Chrome exports nothing for this. |
note | note | Same name, position adjusted |
— none — | vault | Left empty — Chrome exports nothing for this. |
What carries over
| Field | Chrome | 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 | No | Yes | Not in the source file |
| 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 Google Chrome
- Open Chrome and go to chrome://password-manager/settings.
- Select "Download file" next to Export passwords.
- Confirm with your operating system password or PIN.
- Save the Chrome Passwords.csv file.
Watch out for
- Chrome stores no TOTP secrets, no folders and no favorites. Anything in those fields has to go into the note column or be lost.
- The exported file is plaintext on disk with no protection at all — delete it as soon as the import finishes and empty your trash.
Step 2 — Convert it
Drop the file onto the converter above. It parses Google Chrome'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 Google Chrome.
- 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 Google Chrome account — and change any password you suspect was exposed while the plaintext file existed.
Questions
Why won't Proton Pass import my Google Chrome file directly?
Every column Chrome exports has a counterpart in Proton Pass, but they come out in a different order, and Proton Pass expects 6 more columns that Chrome never writes. A CSV importer reads by position as much as by name, so the file still needs rebuilding. 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 Google Chrome to Proton Pass?
Proton Pass supports every field Google Chrome 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 Google Chrome account.
Is the export file from Google Chrome encrypted?
No. A Google Chrome 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 Google Chrome's export?
Chrome stores no TOTP secrets, no folders and no favorites. Anything in those fields has to go into the note column or be lost.
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 Google Chrome
- Google Chrome → 1Password
- Google Chrome → Apple Passwords
- Google Chrome → Bitwarden
- Google Chrome → Dashlane
- Google Chrome → Enpass
- Google Chrome → KeePassXC
- Google Chrome → Keeper
- Google Chrome → LastPass
- Google Chrome → Microsoft Edge
- Google Chrome → Mozilla Firefox
- Google Chrome → NordPass
- Google Chrome → RoboForm
- Google Chrome → Safari
Other ways into Proton Pass
- 1Password → Proton Pass
- Apple Passwords → Proton Pass
- Bitwarden → Proton Pass
- Dashlane → Proton Pass
- Enpass → 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
- Safari → Proton Pass
Moving the other way? Proton Pass → Google Chrome · All 210 converters