KeePassDX

KeePassDX is a password manager for the KeePass file format, developed by Jeremy Jamet of Kunzisoft in France as a fork of the older KeePassDroid. There is no account and no cloud service behind it: your passwords live in one encrypted .kdbx file, and KeePassDX opens it, edits it and fills in logins from it. This is the Libre build, which the FAQ describes as having “no proprietary code” and not being “linked to any closed services”.

The password file

• Formats: KeePass 1 (.kdb) and KeePass 2 (.kdbx, up to version 4.1), so the same file opens in KeePassXC, KeePass and other compatible apps.
• Encryption: AES, Twofish or ChaCha20, with AES-KDF, Argon2d or Argon2id to slow down password guessing. When you create a new database, KeePassDX times the key derivation on your phone to set its strength.
• Unlocking: a master password, a key file (KeePassDX can generate one), or a hardware key such as a YubiKey through HMAC-SHA1 challenge-response. The hardware key needs Kunzisoft’s separate Key Driver app, and the wiki calls this support “only available in beta for testing”.
• Inside the entries: passkeys, file attachments with an image viewer, and one-time codes (TOTP and HOTP). Steam uses a code format of its own: entries that already have a Steam code, for example from KeePassXC, show it in every version, but choosing that format for a new code is unlocked only for contributors (see Libre, Free and Pro below). KeePassDX has no QR scanner: you share an otpauth:// link to it from a scanner app.
• Where the file is: anywhere Android’s file picker reaches, including cloud apps that support it. KeePassDX keeps no copy of its own; when the file changes elsewhere, it offers to merge or reload. Syncing is the job of your file manager or sync app (see the questions below).

Filling in passwords and passkeys

• Autofill, on Android 8.0 and later, through Android’s own autofill service. The inline suggestions shown on some keyboards are off by default.
• Magikeyboard, its own keyboard, which types an entry’s fields without the clipboard and also works on older phones.
• Passkeys, since version 4.2.0, on Android 14 and later: KeePassDX creates passkeys and keeps their private keys in your database. In this Libre build, one step is different. The Google Play build trusts a ready-made list of browsers that may ask for passkeys; the Libre build has no such list, so the first time a browser like Chrome asks, KeePassDX offers to add it to Settings › Form filling › Passkeys settings › Privileged apps. Signing in to a computer with a passkey on the phone also needs Google Play services added there.
• Earlier 4.5 versions, from August and September 2026, added the passkey PRF extension, which some apps use for encrypted backups, and the post-quantum ML-DSA passkey algorithms. 4.5.6, from October, lets autofill match web addresses that have no top-level domain, such as localhost.

Unlocking with your fingerprint

Device unlock stores your master password encrypted, with a key in the Android Keystore that only works after you authenticate, inside a dedicated security chip (StrongBox) when the phone has one. You need a screen lock set up for it. The wiki is clear that “Device unlocking does not exempt you from remembering the master password of your database.”

What goes online

Nothing. The app has no internet permission, and we found no network code: no analytics, no crash reporting, no icon downloads. Android’s own backup copies the app’s settings, but not the database or the stored unlock keys. Screenshots of the app are blocked by default.

Libre, Free and Pro

• Libre (this file, com.kunzisoft.keepass.libre): on IzzyOnDroid, F-Droid and the project’s GitHub.
• Free (com.kunzisoft.keepass.free), on Google Play. The FAQ: “All versions currently have the same usage features”, but it lists two additions to this one that it calls “not entirely consistent with the ethics of libre software”: Steam one-time codes, which don’t follow the OTP standards, and Google’s list of browsers trusted for passkeys. In the 4.5.6 code, though, choosing Steam for a new code depends on contributor status in both versions (see Pro); the browser list is what differs.
• Pro isn’t a separate password manager. “KeePro Support” is a paid app on Google Play ($10 in the US); installed next to KeePassDX, it marks you as a contributor, which unlocks extra visual themes and the manual choice of Steam codes. The FAQ: “Manual selection of this algorithm can therefore only be unlocked after a contribution.” People who contribute in other ways can ask the developer for an unlock procedure by e-mail.

Because their package names differ, Libre and Free install side by side, and neither updates the other. To switch, install the other one and open the same .kdbx file.

About this file

• This is the developer’s own build of version 4.5.8, from October 2026, via IzzyOnDroid: the same file, byte for byte, as the Libre APK on KeePassDX’s GitHub releases. Its signing certificate matches the fingerprint published in the README. F-Droid builds and signs its own Libre copy with a different key, so moving between F-Droid’s and this one means uninstalling first (see the questions below for what that removes).
• Version 4.5.7 fixed the autofill menu and the extension used when saving a new database file, but also enabled code shrinking for every build, including Libre; Libre users reported crashes, including one report of a database becoming a zero-byte file. Version 4.5.8 reverts that shrinking change. This site did not host 4.5.7.
• The 16.8 MB file runs on ARM and x86 phones and needs Android 4.4 or later; passkeys need Android 14. Our scan found no trackers.
• The screenshots are the project’s own. Apart from the first, with the passkey prompt, they date from 2023, so details of today’s screens differ.
• KeePassDX is licensed under the GPL-3.0 or later. Its built-in icon packs are based on Nuvola (LGPL-2.1) and Font Awesome (CC BY 4.0).

CPU types in this build: arm64-v8a (64-bit ARM, almost every phone since 2017); armeabi-v7a (32-bit ARM, older and budget phones); x86 (32-bit Intel, emulators); x86_64 (64-bit Intel, emulators and Chromebooks).

Versions currently kept in the IzzyOnDroid repository. We host and check only the newest one. Full changelog.