Home › Converters › Google Chrome to Enpass

Google Chrome to Enpass converter

Google Chrome and Enpass both use CSV, but Google Chrome writes 5 columns; Enpass expects 6 in a different order — so Enpass rejects a raw Chrome export or silently files everything into the wrong fields. Drop your export below and get back a file Enpass accepts.

Convert your Google Chrome export

Drop your Google Chrome CSV here or click to choose a file — nothing is uploaded

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.

Your export file is plaintext. Both the file Google Chrome gives you and the one you download here contain every password in readable form. Delete them as soon as the import is verified, and empty your trash.

What's actually different between the two formats

Only 3 of 5 column names match (url, username, password), and they're in a different order — enough for Enpass to accept the file and then put your passwords in the wrong fields.

Google Chrome column	Enpass column	What happens
`name`	`Title`	Renamed and repositioned
`username`	`Username`	Renamed and repositioned
`password`	`Password`	Renamed and repositioned
`url`	`URL`	Renamed and repositioned
`— none —`	`TOTP`	Left empty — Chrome exports nothing for this.
`note`	`Notes`	Renamed and repositioned

What carries over

Field	Chrome	Enpass	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 Enpass'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 Enpass 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 Enpass

Open Enpass → Menu → File → Import.
Choose "Other" → CSV.
Select the converted file and map the columns.

Watch out for

Enpass CSV export flattens custom item templates. Anything beyond title/username/password/URL/notes arrives as note text.
Enpass exports per-vault. If you use more than one vault, export each separately and convert each file.

Step 4 — Verify and clean up

Open ten entries in Enpass at random and check them against Google Chrome.
Sign in to one real site using Enpass 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 Enpass import my Google Chrome file directly?

Only 3 of 5 column names match (url, username, password), and they're in a different order — enough for Enpass to accept the file and then put your passwords in the wrong fields. The converter rewrites the file into Enpass'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 Enpass?

Enpass 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 Enpass?

Enpass CSV export flattens custom item templates. Anything beyond title/username/password/URL/notes arrives as note text.

Related converters

Other routes out of Google Chrome

Other ways into Enpass

Moving the other way? Enpass → Google Chrome · All 210 converters