Move Chrome passwords to KeePassXC without leaving a CSV behind

Share
Overhead view of a laptop and headphones on a desk
Contents

At a glance

Export Chrome passwords, map the CSV columns in KeePassXC, test the new database and remove the temporary export without deleting your only working copy.

What you will transfer

This procedure moves saved website passwords from Chrome into an encrypted KeePassXC database. It is for a desktop computer you control, with a working Chrome profile and a supported KeePassXC installation. The expected result is a database that opens with your chosen credentials, contains usable login records and has a recovery copy. The temporary CSV should then be removed from the places where you saved or copied it.

Treat this as a password transfer, not a migration of your entire Google account. Separately inventory passkeys, two-factor authenticators, recovery codes and any credentials held in another browser profile. A password CSV is not evidence that these other sign-in methods have moved. Keep your existing access available until the checks below succeed. The menu paths follow Google's desktop help and the KeePassXC 2.8.0 documentation checked on 16 November 2026; translated labels can differ. [1][2]

Prepare a private working folder

Choose a folder on your own computer that is outside automatic cloud synchronisation and shared folders. Check the actual path rather than assuming Desktop or Documents is local: either can be managed by a sync service. Close screen-sharing sessions and avoid a shared or publicly accessible computer. Do not email the export to yourself or upload it to an online converter.

The CSV contains readable password data. Encryption of the eventual KeePassXC database does not protect that separate file. For a simple migration, keep it on the same computer and import it promptly. If you already have a KeePassXC database, make a separate recovery copy before adding records. Decide which database is the destination, so you do not accidentally populate a test file and later delete it. Our KeePassXC review explains the application's broader storage and browser-integration options. [2]

Export from the correct Chrome profile

Open the Chrome profile whose passwords you intend to move. In the main menu, choose Passwords and autofill, then Google Password Manager. Open Settings and use Download file beside Export passwords. Complete any authentication requested by the operating system and save the file in the private working folder. Note the filename and location.

If you have several profiles, handle them one at a time and name exports distinctly. A profile containing work accounts may be subject to organisational restrictions; use the approved migration process for those accounts. Do not open the CSV in a spreadsheet merely to count entries. That introduces another application and may create recovery or recent-file copies. Use the importer's preview for the initial inspection. If the downloaded file is empty or belongs to the wrong profile, correct that before proceeding. [1]

Map the CSV fields before importing

In KeePassXC, open Database, then Import, and select the CSV file. The documented import wizard supports a new database or an existing unlocked database. Choose the intended destination. Read the preview before confirming: column positions are not a reliable substitute for checking their contents.

Map the website address to URL, the account identifier to Username, and the secret to Password. Map a descriptive name to Title where present; check whether any notes need their own mapping. If the first row contains column names, ensure it is handled as a header rather than becoming a login record. Confirm that commas inside values and non-English characters are displayed correctly. If several fields appear combined in one column, adjust the CSV parsing settings and recheck the preview. Do not edit or shorten a password to make the display look tidier. [2]

Checks at each transfer stage

StageContinue whenPause when
ExportThe intended Chrome profile produced the fileThe profile or storage location is uncertain
ImportURL, username and password fields line upColumns are combined or characters are damaged
VerificationThe saved database and recovery copy reopenYou cannot unlock the saved file
CleanupThe imported logins work and temporary copies are locatedThe only usable copy is still the CSV

Save and test the encrypted database

Complete the import and, for a new database, follow the database-creation dialog. Choose a unique database password that you can reliably recover. If you choose an additional key file, include its separate recovery arrangements in your plan; possession of the database alone will not replace a required key file. Save the resulting KDBX file at a location you can identify.

Now lock or close the database and reopen that exact file. This tests the credentials and the saved result, rather than just the import dialog's success message. A failed reopen is a reason to pause while the original Chrome records still exist. Make a copy of the saved database to your chosen backup location and test opening the copy as well. Label it clearly so that later password changes go into the working database, not an unnoticed older backup. [2]

Check entries before switching autofill

Check several different entries: an ordinary account, one with a long password, one with punctuation, and any record containing non-Latin text. Compare the website, username and notes with the original. Search for a known important account and inspect duplicates deliberately. Two usernames for one website can be legitimate; identical titles do not automatically mean an entry should be deleted.

Test a normal sign-in on a low-impact account at its known address. Use a fresh session or another appropriate browser context so an existing logged-in session does not disguise a bad password. Keep recovery access available and avoid repeated attempts if the site rejects the credentials. Browser autofill is a separate setup task: importing the database does not by itself connect KeePassXC-Browser. Follow the official browser-integration instructions when you are ready, then test filling on the intended domain. [2]

Remove the temporary export

Once the saved database and its recovery copy work, remove the CSV from the working folder and from the operating system's trash or recycle bin. Look for extra downloads with suffixes such as a second copy's number. If you intentionally copied it elsewhere during the transfer, include those locations in the cleanup. Removing Chrome's download-history entry alone does not remove the file stored on disk.

Ordinary deletion should not be described as proof that every historical copy has been erased. A sync service or backup may have captured the export while it existed. Check those systems' retention and deletion controls if the file entered them. If you sent the CSV to somebody or exposed it in a shared location, treat the contained passwords as exposed and change them at the relevant services from a trusted device. Deleting your local copy does not revoke a password another person already obtained. [2]

Keep a recovery copy and finish the move

Decide which password manager will be your everyday source. If Chrome and KeePassXC both keep changing copies, an old credential can look current in one of them. After successful migration, you can turn off Chrome's offer to save passwords and passkeys in its password-manager settings if that suits your chosen setup. This preference is different from deleting saved account data.

Do not use Delete all Google Password Manager data as a CSV-cleanup shortcut: Google's documentation says that action includes passwords and passkeys. Review what remains dependent on Google before removing individual records or account-wide data. Keep the encrypted database backup and its unlock requirements accessible under your recovery plan. The move is complete when you can reopen the working file, use representative logins, recover from the copy and account for the temporary export. Schedule a separate review of reused or compromised passwords; relocating them does not change their values. [3]

Frequently asked questions

Does the CSV move my passkeys?

Use this procedure for passwords. Inventory passkeys and their recovery separately before deleting anything from Google Password Manager. [3]

Can I keep the CSV as a backup?

Keep an encrypted KDBX recovery copy instead. The CSV remains a separate readable copy of its password data. [2]

Should I import again if an entry looks wrong?

First check the column mapping and destination database. Repeating an import without investigating can add duplicates rather than correct the original problem. [2]

Evidence & sources

Source record: · Checked:

Record limits · Desktop password transfer using Google help and KeePassXC 2.8.0 documentation; practical checks are editorial guidance.

  1. [1]Source reported

    Google documents exporting saved passwords from the password-manager settings.

    Supporting excerpt: Chrome password export settings

    Original quotation

    Download file
    Chrome password export settings ↗

    Source language: EN · Captured Nov 16, 2026

  2. [2]Source reported

    KeePassXC documents unencrypted CSV import with column mapping.

    Supporting excerpt: KeePassXC CSV import and database operations

    Original quotation

    A CSV file is unencrypted
    KeePassXC CSV import and database operations ↗

    Source language: EN · Captured Nov 16, 2026

  3. [3]Source reported

    Google says deleting all password-manager data includes passwords and passkeys.

    Supporting excerpt: Chrome password export settings

    Original quotation

    passwords and passkeys
    Chrome password export settings ↗

    Source language: EN · Captured Nov 16, 2026