Home › Converters › Bitwarden to Google Chrome

Bitwarden to Google Chrome converter

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

Convert your Bitwarden export

Drop your Bitwarden 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 Bitwarden 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 1 of 11 column names match (name), and they're in a different order — enough for Chrome to accept the file and then put your passwords in the wrong fields.

Bitwarden column	Google Chrome column	What happens
`name`	`name`	Same name, position adjusted
`login_username`	`username`	Renamed and repositioned
`login_password`	`password`	Renamed and repositioned
`login_uri`	`url`	Renamed and repositioned
`login_totp`	`— none —`	Chrome has no 2fa secret field. Written into notes instead of dropped.
`notes`	`note`	Renamed and repositioned
`folder`	`— none —`	Chrome has no folder field. Written into notes instead of dropped.
`favorite`	`— none —`	Chrome has no favorite field. Written into notes instead of dropped.

What carries over

Field	Bitwarden	Chrome	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	Yes	No	Written into the notes field as "Folder: …" so you can re-sort later.
Two-factor (TOTP) secrets	Yes	No	Written into notes. Re-add them by hand, or keep them in a separate authenticator.
Favorites	Yes	No	Dropped — re-star your important entries after importing.
Custom fields	Yes	No	Flattened into notes as name: value pairs.
Multiple URLs per entry	Yes	No	First URL kept; the rest appended to notes.
File attachments	Yes	No	No CSV export includes attachments. Download them out of Bitwarden separately before you close the account — this is the one thing people lose permanently.

Step 1 — Export from Bitwarden

Open the Bitwarden web vault at vault.bitwarden.com and sign in.
Go to Tools → Export vault.
Choose .csv as the file format (or .json to keep custom fields and multiple URIs).
Enter your master password and select Export vault.

Official instructions: Bitwarden export documentation

Watch out for

Bitwarden prefixes bare domains with http:// on import. If you care about https, put the full URL in the login_uri column.
The free plan allows only two collections in an organization vault — import to your personal vault if your folder count is higher.

Step 2 — Convert it

Drop the file onto the converter above. It parses Bitwarden's layout, maps each field onto the universal record, then writes Google Chrome'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 Chrome 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 Google Chrome

Go to chrome://password-manager/settings in Chrome.
Select "Select file" next to Import passwords.
Choose the converted CSV and confirm.

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 4 — Verify and clean up

Open ten entries in Google Chrome at random and check them against Bitwarden.
Your folder names were written into each entry's note. Re-sort them however Chrome organizes items.
Sign in to one real site using Google Chrome 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 Bitwarden account — and change any password you suspect was exposed while the plaintext file existed.

Questions

Why won't Google Chrome import my Bitwarden file directly?

Only 1 of 11 column names match (name), and they're in a different order — enough for Chrome to accept the file and then put your passwords in the wrong fields. The converter rewrites the file into Google Chrome'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.

What gets lost moving from Bitwarden to Google Chrome?

Google Chrome can't natively store: folders / groups, two-factor (totp) secrets, favorites, custom fields, multiple urls per entry, file attachments. Rather than drop that data, the converter writes it into the notes field where Chrome has one, so you can move it back by hand. Keep your Bitwarden account active until you've confirmed everything you need made it across.

Can I keep my 2FA codes in Google Chrome?

No — Google Chrome has no field for TOTP secrets at all. The converter puts each secret into the entry's note so it isn't lost, but Chrome won't generate codes from it. Move those to a dedicated authenticator app before you shut down Bitwarden, or pick a target that supports them.

Is the export file from Bitwarden encrypted?

No. A Bitwarden 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 Bitwarden's export?

Bitwarden prefixes bare domains with http:// on import. If you care about https, put the full URL in the login_uri column.

Anything unusual about importing into Google Chrome?

Chrome stores no TOTP secrets, no folders and no favorites. Anything in those fields has to go into the note column or be lost.

Related converters

Other routes out of Bitwarden

Other ways into Google Chrome

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