How to Move Your Passwords from Google Password Manager to KeePassDX

Short answer: export your passwords from Google Password Manager as a CSV file, import that file into KeePassXC on a computer to make an encrypted KeePass database (.kdbx), copy the .kdbx to your phone and open it in KeePassDX. Then set KeePassDX as Android’s autofill service and delete the CSV. Your passkeys can’t come along yet; see the next section.

What moves, and what doesn’t

• Passwords move. Google Password Manager exports them as a CSV file. According to Chrome’s source code, it has five columns: name, url, username, password and note.
• Passkeys don’t, for now. Google’s help page is precise: “You can download your passwords to a .csv file. You can also export your passwords and passkeys into another password management app.” The second route uses the Credential Exchange standard, which Google Play services supports since version 26.21 (June 2026), but the receiving app has to support it, and KeePassDX doesn’t yet: its developer opened an issue for it in September 2026, calling it “a must-have feature”, with no date. Until then, you can keep Google Password Manager for your existing passkeys alongside KeePassDX, or create new passkeys in KeePassDX site by site (it handles passkeys on Android 14 and later).
• KeePassDX can’t read the CSV itself. Its wiki: “KeePassDX does not and will not offer this plaintext import feature.” It recommends doing the conversion on a computer, with KeePassXC or KeePass 2, which is what Step 2 does. You need a Windows, macOS or Linux computer for that step.
• The CSV is not encrypted. Anyone who gets the file can read every password in it. Keep it on as few devices as possible and delete it at the end (Step 5).

Step 1: Export your passwords

The simplest way is to export on the computer you’ll use for Step 2, so the unencrypted file never touches your phone. In Chrome on a computer, Google’s steps: select More › Passwords and autofill › Google Password Manager › Settings, scroll to “Export passwords” and select Download file.

On Android, in Chrome: More › Settings › Autofill and passwords › Google Password Manager, then at the bottom Settings › Export passwords & passkeys › Download file. Some of Google’s pages call the option simply “Export passwords”. You need a screen lock on the phone to export; if you don’t have one, Android asks you to set one up. Despite the name of the option, the file contains passwords only.

Step 2: Turn the CSV into a KeePass file with KeePassXC

1. Install KeePassXC (keepassxc.org) on your computer and start it.
2. Click Import File on the welcome screen, or use Database › Import…. Choose Comma Separated Values (.csv), select the file from Step 1 and import it into a New Database.
3. In the CSV import screen, keep the option that says the first line has field names, and look at the preview. KeePassXC matches columns by name, so Username, Password and URL fill themselves in, but Chrome’s other two columns have different names: set Title to name and Notes to note yourself. Without a title, KeePassXC warns that “entries will be hard to tell apart”.
4. Click Done. The New Database dialog opens.
5. On the Encryption Settings screen, KeePassXC’s guide says: “we don’t recommend making any changes besides increasing or decreasing the decryption time using the slider”. Leave the slider low rather than high: the same guide warns that a phone “will likely take two to four times longer to access and save your database than on your home computer”. The defaults (KDBX 4, AES-256, Argon2d) all work in KeePassDX.
6. Set the database password. KeePassXC recommends “a long, randomized password”, and warns that losing it “might result in permanent locking of your database”: there is no reset.
7. Save the .kdbx file.

On Windows, KeePass 2 works too: it has imported Google Chrome’s password CSV files since version 2.39, from 2018.

Step 3: Open the file in KeePassDX

1. Copy the .kdbx to your phone. Over a USB cable, Android’s help says to tap the “Charging this device via USB” notification and choose File Transfer. Unlike the CSV, the .kdbx is encrypted, so you can also use LocalSend or KDE Connect on your own network, or put it in a cloud or sync folder if you plan to keep it in sync with the computer.
2. In KeePassDX, tap Open existing vault and pick the file. The wiki recommends a short tap, which keeps a lasting link to the file; a long press opens it in a way that is “less” persistent.
3. Enter the database password. If you like, set up fingerprint or face unlock afterwards; it stores your password encrypted with a key in Android’s Keystore, but, in the wiki’s words, “Device unlocking does not exempt you from remembering the master password”.

If you keep the file in a cloud folder, read KeePassDX’s notes on syncing first: Google Drive works only “Partially”, and some users saw corrupted files when Syncthing synced while KeePassDX was saving.

Step 4: Make KeePassDX fill in your passwords

1. Android’s autofill service. In KeePassDX, open Settings › Form filling › Credential provider service. Android opens its own screen for the preferred service (on Android 14 and later, “Passwords, passkeys and autofill”; names vary by manufacturer); choose KeePassDX. Autofill needs Android 8.0 or later.
2. Chrome, which otherwise fills in from Google: More › Settings › Autofill and passwords › Autofill settings › Autofill using another service, then Restart Chrome. Google: “To use another autofill service, you must first add the service in Android settings”, which is step 1.
3. Stop Google offering to save new passwords, so new ones don’t end up in the old place: in Android’s Settings app, search for Password Manager, tap Settings and turn off Offer to save passwords. Chrome’s Google Password Manager settings have the same switch.
4. The first time in each app, expect to pick the entry by hand. In Google’s export, logins for Android apps carry an android:// address. In our reading of KeePassDX’s source code, it recognises apps by a field of its own, not by the URL, so it won’t suggest those entries automatically at first. Choose the entry from the list; KeePassDX remembers the app for next time (the “Save search info” option, on by default). Websites match by their address straight away.

Step 5: Clean up

• Delete the CSV everywhere it went: the computer’s Downloads folder and its recycle bin, the phone’s Downloads folder, and any folder that syncs it to the cloud. Files by Google keeps deleted files in its Trash for 30 days; to remove them at once, open Menu › Trash, select the file and tap Delete.
• Delete your passwords from Google, if you want to, once you have checked a few logins in KeePassDX. Individual passwords can be deleted in Google Password Manager. There is also Settings › Delete all data, but Google says this removes your Google Password Manager data, “which include passwords and passkeys”, so only use it after you have dealt with your passkeys (see the first section).

Keeping your passwords safe from now on

There is no account behind KeePassDX and nothing to recover from. The .kdbx file is your password store, so keep a copy somewhere other than your phone, for example on the computer you used for Step 2, and update it from time to time. KeePassDX itself has no internet permission: it doesn’t upload anything, and backing up and syncing the file is up to you.