Main features
- Opens and creates .kdb and .kdbx files, versions 1 to 4
- AES, Twofish, ChaCha20 and Argon2
- Passkeys with private keys stored in the database
- Android autofill for apps and websites
- Magikeyboard to fill any text field
- Biometric unlock
- HOTP and TOTP codes
- Entry templates, group trees and entry history
- File attachments with an image viewer
What KeePassDX does
KeePassDX is an Android app for KeePass password databases. It opens and edits the same encrypted file that KeePassXC, KeePass and KeeWeb use, so it is a common choice for the phone side of a KeePass setup. You can also start a new database on the phone. Everything stays in that one file, unlocked with a master password, a key file or both, and after that with biometrics if you enable it.
Filling works through Android’s autofill service, and for apps where autofill fails there is the Magikeyboard, a separate keyboard that types the selected entry’s fields. KeePassDX can store passkeys, keeping their private keys inside the database, and generates HOTP and TOTP codes for two-factor logins. Entries can use templates for different kinds of data, keep a history, and carry attachments.
Security and encryption
KeePassDX supports KeePass databases from version 1 to 4 with AES, Twofish or ChaCha20 encryption and Argon2 key derivation. The FAQ notes that a key derivation tuned for one second on a PC can take much longer on a phone, and suggests lowering it in the database settings if unlocking is slow.
The app deliberately leaves networking to other apps. Instead of a built-in Dropbox or WebDAV client, it opens the file through Android’s file managers and storage providers, which the developers see as cleaner from a security point of view. The project does not document an external security audit.
Self-hosting KeePassDX
There is no server. The app is published in two builds. The Libre build on F-Droid, which the project recommends, contains only free software. The Free build on Google Play includes a few extras, such as Steam one-time passwords, that do not fully meet libre software standards. Both are also available through IzzyOnDroid and GitHub releases, and the README explains how to verify the APK signature.
For use on several devices, put the database in a cloud folder that your file manager can reach. The FAQ recommends a cloud on your own server under an AGPL license, for example Nextcloud, but any provider works because the file is already encrypted.
Hosted version
None. KeePassDX has no account or cloud service.
Limitations
KeePassDX is Android only. Sync depends on the file manager or cloud app holding a lasting link to the file; when a provider breaks the link, you have to reopen the database from it. There are no shared vaults with separate permissions for different people, and no way to recover a lost master password. Large attachments are better kept elsewhere, the FAQ says.
Who it suits
KeePassDX fits Android users who keep a KeePass file on the desktop and want a free, ad-free app with passkeys and autofill, and people who prefer software installed from F-Droid. If you want similar KDBX apps for other platforms, look at Keepass2Android, which has built-in cloud connectors, and KeePassium for iPhone, iPad and Mac.
License details
GPL-3.0. A donation-based Pro build only adds visual styles. The Google Play build includes a few non-libre extras such as Steam OTP; the F-Droid build does not.
Technical details
Built with
- Kotlin
- Java
- C
GitHub topics
- android
- android-application
- autofill
- credential-manager
- fingerprint
- keepass
- keepass-dx
- keepassdx
- material
- material-design
- passkey
- passkeys
- password-manager
- prf
Reviewed by the OpenSourcePicks editors from the project's repository and documentation. Something out of date? Tell us.