Exporting a Bitwarden vault takes about thirty seconds. What takes longer - and what almost nobody is told - is understanding what the file does not contain, and where you can safely put it afterwards.
Because an export is, by definition, your entire password collection outside its protection. Done carelessly, the backup becomes the weakest point of the whole setup.
Planning to move the export to another manager? Our free password CSV converter rewrites Bitwarden's unencrypted .csv in Chrome or KeePassXC format inside your browser and flags reused passwords before you import them anywhere.
Exporting to switch managers? Proton Pass has a dedicated Bitwarden importer that reads the plain .json export, and its free plan covers unlimited logins on unlimited devices, so the whole move can be checked before paying anything.
Black Friday 2026 (read on 17 November 2026): the Proton Pass partner page our link opens takes 60% off the first year of Pass Plus ($23.88 for the first 12 months, then $35.88 a year) and Pass Family ($33.48 for 6 accounts, then $59.88 a year), with the 30-day money-back guarantee. The order page shows the price for your country, so check it before paying. See the Proton Pass Black Friday offer
The export itself
From the web app: Tools → Export, leave Export from on My vault, pick a format, confirm with your master password (or an email verification code), and the file downloads. From the browser extension: Settings → Vault options → Export vault. The desktop app has Export in its navigation menu. Nothing is modified in your vault, so you can repeat it as often as you want.
Redesign beta (checked 21 November 2026): Bitwarden is testing a new design for the browser extension and desktop app (opt-in beta, cloud accounts only, not available on self-hosted servers). If you joined it, organisations are labelled Vaults, "Collections" become Shared folders, and a vault switcher sits in the item list, so the menu names above may differ for you. The web app is not part of the beta, so Tools → Export is unchanged there. Switch the beta off in the extension if you want the layout described in this guide.
On a phone, there is now a second route: Bitwarden can export directly to another app on iOS 26+ and Android 10+, without any file, provided the destination app supports the FIDO Credential Exchange Protocol (CXP). When both apps support it, it is the cleanest migration there is, because no plain-text file ever lands in your downloads.
Choosing the format, honestly
There are 4 formats on that menu: plain .json, .csv, .json (Encrypted) in two variants, and .zip (with attachments). According to Bitwarden's own documentation (checked on 19 October 2026), only the JSON-based exports include cards, identities, stored passkeys and SSH keys.
Encrypted JSON with a password of your choosing is what you want for a backup you keep. The file is unreadable without that passphrase, and it can be restored into any account - including a brand-new one, which matters if what you lost is the account itself.
Encrypted JSON tied to your account is offered as the safer-sounding option, and it is safe, but it can only be imported back into the same account. As a disaster-recovery backup it therefore protects you against everything except the disaster you were preparing for.
Plain JSON is readable by any text editor, which is exactly the point when you are migrating to another manager - and exactly the danger the rest of the time. Use it for the few minutes the migration lasts, then delete it properly.
.zip (with attachments) bundles a .json file and the files attached to your items. It is the only format that carries attachments, and it is limited to your individual vault. Like plain JSON, the .json inside is readable, so treat the archive with the same care.
CSV is the lowest common denominator. It carries the least structure and loses the most: cards, identities, passkeys and SSH keys are not in it at all, and custom fields and folders survive only partially. Choose it only when the destination refuses everything else.
One detail worth knowing before you pick the encrypted route: the password-protected export derives its own key from the passphrase you type, independently of your account key, which is exactly why it can be restored into a different account. The account-restricted variant is tied to your account's encryption key instead, and Bitwarden warns that rotating that key makes older account-restricted exports impossible to decrypt. Same file extension, same apparent format, two completely different recovery stories.

What the file leaves behind
This is the part worth reading twice, because it is where backups quietly fail.
Attachments are missing unless you chose .zip. The JSON and CSV exports carry your items but not the files attached to them. If you store recovery codes, certificates or scanned documents as attachments, pick .zip (with attachments); for files attached to organisation items, which the .zip does not cover, download them one by one. A backup you believe complete and that is not is more dangerous than no backup at all, because you stop worrying.
Organisation items are not included. A personal export covers your personal vault only. Anything shared through an organisation, such as a family collection or a team vault, needs its own export, run by an owner, an admin or a member with the Manage collection permission. People typically discover this after leaving a team.
The trash and your Sends are never exported, whatever the format. If you were counting on retrieving a deleted item from an export, it will not be there.
Where to put the file
An unencrypted export sitting in Downloads is a plain-text list of every account you own. Two rules make the difference:
- If it is plain JSON or CSV, it is temporary. Import it, verify the import, then delete it - and empty the trash. On an SSD, ordinary deletion is usually enough given the file's short life; what matters more is not letting it linger for months.
- If it is an encrypted backup, treat the passphrase as the real secret. Storing it inside the vault the backup protects is a circular dependency: the day you need the file, you will not be able to open it. Write it down physically, or keep it with your other recovery material.
Cloud sync is not automatically wrong for an encrypted export - but be aware that you are handing an encrypted archive of your entire credential set to a third party, and that its safety now rests entirely on that one passphrase.
Verify the export, once
An untested backup is a hope, not a backup. Do this once, right after your first export:
- Open the file. A plain JSON should show your items; an encrypted one should be unreadable noise. If an "encrypted" export is readable, you exported the wrong format.
- Count the items and compare with your vault's item count. A large gap usually means organisation items you did not export.
- If it is your disaster-recovery copy, try importing it into a fresh test account. It is the only way to learn now, rather than on the day it matters, that the account-tied format cannot be restored elsewhere.
If you are exporting to leave Bitwarden
A good share of exports are not backups at all: they are the first step of a move. If that is your case, the format question answers itself, because the destination decides it.
Proton Pass has a dedicated Bitwarden importer (checked on proton.me on 18 October 2026). Export from Bitwarden as plain .json, then open the Proton Pass browser extension, go to Settings, Import, pick Bitwarden in the provider list and drop the file in. Proton documents the import as covering your logins and notes, so check cards and identities by hand afterwards, and move attachments by hand: the importer takes the plain .json, which never contains them, so keep a .zip export alongside if those files matter. The free plan covers unlimited logins on unlimited devices, so you can run the whole migration and compare item counts before paying anything; Pass Plus (2.99 USD/month billed yearly) adds unlimited email aliases, a built-in authenticator and more vaults.
The rule from earlier applies with full force here: that plain JSON is your entire vault in readable form. Import it the same session, compare the counts, then delete it and empty the trash. Keep your Bitwarden account open for a week or two, untouched, as a fallback while you confirm nothing went missing.
Which file each destination reads
The destination, not Bitwarden, decides the format. Here is what each importer accepts, read on the official help pages on 21 November 2026:
| Moving to | Bitwarden export to pick | Where to import it | What does not come across |
|---|---|---|---|
| Proton Pass | .json (plain) | Browser extension: menu, Settings, Import, provider Bitwarden | Proton documents logins and notes only: check cards, identities and attachments by hand |
| 1Password | .json (Encrypted), option Password protected | Desktop app: File, Import, Bitwarden. Website: your name, Import data | Passkeys and items in shared collections. Plain JSON and the account-restricted export are refused |
| Chrome, Firefox, Safari, KeePassXC or any manager that reads CSV | .csv, run through our CSV converter for the target's column names | The target's CSV import | Cards, identities, passkeys and SSH keys are not in a CSV at all |
The 1Password trap: 1Password's import guide (published 17 August 2026) says the import fails with an error if your Bitwarden account uses Argon2id, and the fix it gives is to switch the key derivation function to PBKDF2 before exporting again. Our Bitwarden Argon2 settings guide shows where that setting lives. Since you are leaving the account, the weaker setting only matters for the few minutes the export exists.
Moving your vault? Proton Pass imports a Bitwarden export directlyBitwarden .json importer · Unlimited devices on the free plan · Plus 2.99 USD/month billed yearly · Black Friday: 60% off Pass Plus the first year→If the next manager does not read Bitwarden's CSV columns, our password CSV converter rewrites the unencrypted .csv export in Chrome or KeePassXC format inside the browser, and counts the passwords reused across sites before you move them.
The short version
Export via Tools → Export. Choose encrypted JSON with your own passphrase for a backup, .zip if you need your attachments, plain JSON only for a migration you finish the same day, and never CSV if you have passkeys. Remember that organisation items are not in a personal export. Store the passphrase outside the vault it protects, and test a restore once - before you need it.
Disclosure: the Proton Pass link goes through our /go/ redirect. Proton Pass is an affiliate partner and may pay us a commission if you subscribe, at no extra cost to you. Bitwarden pays us nothing.
★ Cure53 audit · ✓ Free plan · Cross-platform
Get NordPass30-day money-back guarantee · Free plan available→Frequently asked questions
How do I export my Bitwarden vault?
In the web app, go to Tools, then Export, choose the format, confirm with your master password (or an email verification code), and the file downloads immediately. In the browser extension the option sits under Settings, Vault options, Export vault; the desktop app has Export in its navigation menu. The operation is read-only: nothing in your vault is modified, and you can export as often as you like.
Which export format should I choose?
Encrypted JSON if the file is a backup you intend to keep, because it stays unreadable without your password. The .zip format if your attachments matter, since it is the only one that carries them. Plain JSON if you are migrating to another password manager that needs to read it, and only for the few minutes the migration takes. CSV only when the destination refuses everything else: it is the poorest format and drops cards, identities, passkeys and SSH keys.
Does the export contain my file attachments?
Only if you pick the .zip (with attachments) format, which packs a .json file and your attachments together. Bitwarden's documentation (checked on 19 October 2026) says this format is only available for individual vault data, so files attached to organisation items still have to be downloaded separately. Every other format leaves attachments out entirely, which is the trap people discover on the day they need the backup.
Does a Bitwarden export include my passkeys?
Yes, but only the .json formats (plain, encrypted or inside the .zip). CSV drops stored passkeys, along with cards, identities and SSH keys. Bitwarden also warns that passkeys created before version 2024.3.1 carry a usage counter that a website may reject after a restore, so exports of passkeys that old should not be your long-term backup.
Does the export include items from an organisation I belong to?
Not by default. A personal export only covers your individual vault. Items shared through an organisation, such as a family or team collection, require a separate export from the organisation, which owners, admins and members with the Manage collection permission can run for the collections they can access. Many people discover this after leaving a team, when the shared items are gone.
Is an encrypted export tied to my account?
It depends on the option you pick. The account-restricted encrypted export can only be imported back into the same account, which is safe but useless if the account itself is what you lost. The password-protected export uses a passphrase you choose and can be restored anywhere - it is the right choice for a real backup, provided you store that passphrase somewhere other than the vault it protects.
