How to export Chrome passwords to KeePassXC safely

Chrome passwords can be moved into KeePassXC by exporting them to a CSV file and importing that file into a KeePassXC database. The key is to prepare the destination first, check the imported entries, and remove the temporary CSV only after the transfer succeeds. The CSV is unencrypted, so treat it like a file containing readable passwords.

The safe order for moving Chrome passwords

Before you export anything, decide whether to use a new KeePassXC database or an existing one. If you already have a database, unlock it and choose the group where the imported entries should go. KeePassXC’s version 2.8.0 User Guide says its Import Wizard can send a CSV to a new database or an existing unlocked one; entries added to an existing database are placed under the selected group.

1. Prepare the KeePassXC database. Create a database or unlock the one you plan to use. This gives the import a ready destination before you create a file containing readable credentials.
2. Export the saved passwords from Chrome to CSV. Keep the temporary file somewhere you can control, rather than leaving it in a location that automatically syncs or is shared. The CSV contains unencrypted data.
3. Import the CSV into KeePassXC. Open the Import Wizard and choose the CSV file. Review its preview before completing the import. If fields do not line up, adjust the column associations in the wizard instead of assuming the columns match.
4. Check the imported entries. Confirm that the expected logins appear, then open a few entries to check that their usernames, passwords, URLs, and notes are in the right fields. Keep the CSV until these checks are complete.
5. Remove the temporary CSV after a successful import. KeePassXC recommends securely deleting the unencrypted file after importing it. Avoid treating ordinary deletion as a guarantee that every trace has been erased; the exact result depends on the storage system.

If you intend to remove the passwords from Chrome as well, do that only after you have confirmed the KeePassXC entries you need. That keeps the browser copies available while you check the transfer.

The CSV and the KeePassXC database are different kinds of files

The CSV is a temporary transfer file; KeePassXC’s .kdbx file is the database. KeePassXC says CSV files are unencrypted, while the database file is encrypted at rest, including when stored with a cloud-storage service.

Cloud storage does not remove the database’s encryption at rest, but encryption and synchronization are separate issues. KeePassXC says its database merge compares matching entries by UUID and modification time, keeping the previous version in entry history when an entry is updated. Its remote download-and-upload synchronization is non-atomic: a change made by another process after download but before upload can be overwritten. Keep the database credentials protected and maintain a recoverable backup when storing the file remotely.