# Import & export passwords — CSV/JSON ↔ KeePass, no upload

> Import Chrome, Firefox, Bitwarden, 1Password, or LastPass exports (CSV/JSON) into an encrypted KeePass .kdbx vault, or export a .kdbx back to CSV/JSON — locally, no upload.

Import password exports from Chrome, Firefox, Bitwarden, 1Password, or LastPass (CSV/JSON) and turn them into an encrypted KeePass .kdbx vault, or export an existing .kdbx back to CSV/JSON. All conversion happens in your browser, so your plaintext credentials never touch a server.

Switching password managers is where credentials are most exposed: the export step dumps everything to a plaintext CSV or JSON. Converting that into an encrypted KeePass vault locally closes the window fast — the sensitive file is read in the browser and the output is a properly encrypted .kdbx, with nothing uploaded in between.

It reads the common export shapes from Chrome, Firefox, Bitwarden, 1Password, and LastPass, and can also export a .kdbx back out when you're migrating the other way.

After importing, open the new vault in the Vault Manager, run the Vault Health Check to catch weak carry-overs, and replace them with the Password Generator.

## How to

1. **Choose a direction.** Import a CSV/JSON export, or export a .kdbx to CSV/JSON.
2. **Add the file.** Drop the export from your old manager, or your .kdbx vault.
3. **Map & confirm.** Check fields map correctly to entries.
4. **Save.** Download an encrypted .kdbx (or the CSV/JSON) to your device.

## FAQ

### How do I move from Chrome or LastPass to KeePass?

Export your passwords from the old manager as CSV/JSON, drop that file here, and save the result as an encrypted .kdbx you can then open in the Vault Manager.

### Why is a password-export CSV so risky to handle?

It's your entire credential set in plaintext. Doing the conversion locally means that file is read in your browser and never uploaded, so you're not scattering copies through a web service.

### Can I go the other way, from .kdbx to CSV?

Yes. You can export a KeePass vault back to CSV or JSON for migrating into another tool — just delete the plaintext export once you're done.

### Are my credentials uploaded during conversion?

No. Parsing the export and building the encrypted vault both run in this tab, so the credentials stay on your machine throughout.


## Related tools

- [Vault Manager](https://www.safepaper.app/passwords/password-manager)
- [Vault Health Check](https://www.safepaper.app/passwords/password-audit)
- [Password Generator](https://www.safepaper.app/passwords/password-generator)
- [AES file encrypt](https://www.safepaper.app/security/file-encrypt)

---

Canonical HTML: https://www.safepaper.app/passwords/import-export
Markdown: https://www.safepaper.app/passwords/import-export.md

There is no upload endpoint — your files are processed in this browser tab. Open your network tab and check.