Skip to content

KeePassDX: An Offline Vault With Working Autofill

KeePassDX: An Offline Vault With Working Autofill

KeePassDX review tests KDBX conflict handling via Syncthing/Nextcloud, Chrome/Firefox/Samsung autofill modes, and shared-device offline-vault safety.

App summary

App
KeePassDX
Developer
Kunzisoft
License
GPL-3.0-only
Version
unknown
Size
unknown
Price
Free (open-source); exact pricing for any paid/donation variants unknown

The Local-First Model and What It Costs You

KeePassDX is an Android app from the developer Kunzisoft, published under GPL-3.0-only and offered as free open-source software. The fact data does not specify pricing for any paid or donation variants, so “free” is the confirmed baseline and nothing beyond it should be assumed. What the listed functions do establish is a local-first posture: the app is described in terms of a local-first model and KDBX compatibility, not in terms of accounts, servers, or a hosted vault.

That distinction carries real weight. A local-first password manager leaves the database file in your hands. You decide where the KDBX file lives, which app or service touches it, and how copies move between devices. Nothing in the fact data describes an account system, a sync backend, or a vendor-held copy of your vault. The trade is straightforward: you get a file you control, and in exchange you inherit the jobs that a hosted service would normally do for you — storage, backup, transfer, and the messy business of reconciling two copies that drifted apart.

This is where a specific kind of reader should stop and think. If you want built-in cloud sync without managing files yourself, KeePassDX as described here is not aimed at you. The same goes for anyone expecting a polished browser extension and desktop app bundle, teams needing shared vaults with people who do not use KeePass-format tools, and users who would rather not think about KDBX file storage at all. The app’s listed scope is Android plus local-first handling plus KDBX compatibility. Everything past that is your responsibility or someone else’s software.

The open-source license is worth naming precisely because it is one of the few trust signals the fact data actually provides. GPL-3.0-only means the source is available under a copyleft license, which is a different proposition from a closed app that asks you to take its word. It does not, by itself, tell you anything about how the app behaves in edge cases. For that you still have to reason from documented functions — and where the documentation stops, say so plainly rather than filling the gap with a guess.

KeePassDX + Syncthing/Nextcloud: What Happens When Two KDBX Copies Conflict

Start with what the fact data supports. KeePassDX is listed as an Android app with a local-first model and KeePass KDBX compatibility. There is no built-in cloud-sync feature anywhere in the listed functions. So when people ask how to sync KeePassDX with Nextcloud or Syncthing on Android, the honest answer is that the syncing is done by Nextcloud or Syncthing, not by KeePassDX. Those are external file-sync tools you choose and configure, and their behavior — versioning, conflict copies, rename policies — belongs to them, not to this app.

Now the uncomfortable part. The fact data does not document merge-conflict handling for two synced copies of the same KDBX database. It does not describe a merge algorithm, a conflict-resolution screen, a “keep newest” rule, or any automatic reconciliation of divergent entries. That exact behavior should be marked unknown. Anyone who tells you KeePassDX will cleanly merge two edited copies is describing something the fact data does not establish. The KDBX compatibility listing tells you the app can work with the database format; it says nothing about what happens when two versions of that database meet.

Because of that, treat Nextcloud and Syncthing as choices you must evaluate on their own terms. A file-sync service that produces conflict copies is doing you a favor, because it preserves both files instead of silently picking one. A service that overwrites without warning is a different risk profile entirely. Neither behavior is KeePassDX’s decision to make, and the app’s listed functions give you no lever to change it.

A verification checklist helps here, and it stays inside what can be defended. First, identify which copy is newer by checking file timestamps and, if your sync tool exposes it, version history. Second, preserve both files before you touch anything — copy them somewhere outside the sync folder so a later sync pass cannot clobber your only remaining copy. Third, open each file in KeePassDX separately and confirm what each one actually contains, because the newer timestamp does not guarantee the more complete vault. Only after that should you resolve the situation, and you resolve it as a file-management decision, not as an app feature. Do not assume an undocumented merge will sort it out for you.

KeePassDX Autofill in Chrome, Firefox, and Samsung Internet: Accessibility Mode vs Keyboard Mode

The only confirmed capability in the fact data is that KeePassDX lists Autofill and Keyboard Integration among its functions. That is the whole of it. The fact data does not enumerate which browsers are supported, does not describe per-browser behavior, and does not specify how the two integration paths differ in practice. If you are searching for why autofill does not work in Chrome on Android, the fact data will not hand you a browser-specific fix, and this article will not invent one.

The accessibility-mode versus keyboard-mode contrast is a genuine information gap. Both phrases describe approaches Android password managers commonly take, but the fact data names integration without specifying behavioral differences between the two modes. It does not say which mode covers which input fields, whether one requires enabling an Android accessibility service, whether the other depends on a custom keyboard being active, or how either behaves inside a WebView or a browser’s own autofill pipeline. Those details are unknown until verified on your device with your apps.

Browser quirks deserve the same treatment. Chrome, Firefox, and Samsung Internet each handle autofill differently on Android, and the fact data says nothing about any of them specifically. It would be easy to promise that switching to keyboard mode fixes every browser. That promise is not supported. The realistic framing is that you have two integration paths listed, the differences between them are undocumented here, and one mode fixing all browsers is not something the fact data can back up.

One related misconception is worth clearing up because it shapes expectations. KeePassDX does not include a dedicated browser extension like Bitwarden’s, at least not among the listed functions. There is no extension in the fact data. What you have is Android-level autofill and keyboard integration, which means the mechanism lives in the operating system’s input layer rather than inside the browser. That is a different architecture with different failure modes, and it explains why browser-specific troubleshooting advice written for extension-based managers often does not transfer.

KeePassDX on a Shared Android Device: Offline-Only KDBX Storage Is Not the Same as Shared-Device Safety

Define the threat boundary using what is actually listed. KeePassDX runs on Android, follows a local-first model, and works with KDBX databases. No automatic cloud sync is documented in the fact data. That combination means the vault’s exposure is tied to the device and to wherever you chose to store the file — not to a vendor’s servers. It does not mean the vault is safe on a phone other people use.

Consider what “offline-only” does and does not buy you. It removes a class of risk that comes from a hosted copy of your database. It does nothing about someone picking up the unlocked phone, about a second user profile with access to shared storage, about an app that can read the folder your KDBX file sits in, or about a backup process that copies the file somewhere you did not intend. Offline is a statement about network paths. Shared-device safety is a statement about who and what can reach the file locally, and the fact data does not address that second question.

Biometric unlock is listed as a function, and that is where a lot of assumptions creep in. The fact data lists Biometric Unlock but does not establish whether biometrics can replace the master password after a reboot. Mark that as unknown. Readers ask why biometric unlock stops working after a reboot, and the honest answer from this fact set is that the app’s post-reboot behavior is not documented here. Do not build a mental model in which your fingerprint is a permanent substitute for the master password; the fact data supports biometric unlock as a listed capability and nothing more specific.

Several shared-device concerns are simply uncovered. App cloning — the Android feature that duplicates an app into a separate profile with its own data — is not mentioned in the fact data. Android backup behavior for the app’s data is not mentioned. Work profiles, which create a managed space on the same physical phone, are not mentioned. None of these are documented, which means none of them can be ruled out or ruled in from this fact set. If you share a phone, the responsible move is to reason about the file’s location and the device’s user model yourself, rather than assuming that “offline” implies “private to me.”

KeePassDX Is Not a KeePassXC Fork: Reading KDBX Compatibility Correctly

The misconception is common enough to state plainly: KeePassDX is not described in the fact data as a KeePassXC fork, and no fork relationship is stated anywhere. What the fact data does say is that KeePassDX is developed by Kunzisoft, licensed GPL-3.0-only, built for Android, and lists KeePass KDBX Compatibility among its functions. That is a compatibility claim about a file format, not a claim about shared code with a desktop application.

Compatibility and forking are different things, and conflating them leads people to expect feature parity that was never promised. A fork implies a shared codebase and a shared lineage, with features inherited and diverged over time. A compatibility claim implies that the app can read and write a database format. The fact data gives you the second and not the first. KeePassDX is best understood as an Android client for KDBX databases, full stop.

That framing answers the practical question — can I open the same database in KeePassXC and KeePassDX? — only as far as the documentation goes. KDBX compatibility is listed for KeePassDX, so the format is the intended common ground. Whether a specific database written by one client opens without friction in the other depends on details the fact data does not cover: which KDBX version the file uses, which key derivation settings it carries, and how each client handles them. Those cross-client behavior details are unknown here and should be verified with your own file, keeping a backup before you try.

Keep this separate from the usual Android-vs-Android comparisons. The question of whether KeePassDX is a fork of a desktop app has nothing to do with how it stacks up against other Android KeePass clients, and dragging those comparisons in muddies the point. The correction stands on its own: different developer, different license listing, different platform, and a compatibility claim rather than a lineage claim.

KeePass KDBX Compatibility: What the Label Actually Promises

KDBX Compatibility appears in the fact data as a listed function, and it is the single most load-bearing phrase in the app’s description. It tells you the app is built around the KeePass database format rather than a proprietary store. That is the promise: your vault is a KDBX file, a format with a life outside this one app, which is exactly why the local-first model is viable in the first place.

What the label does not promise is a version matrix. Readers ask whether KeePassDX supports KDBX4 and Argon2 databases. The fact data lists KDBX compatibility generally and does not enumerate format versions or key-derivation algorithms. That means the specific answer is unknown from this fact set. If your database uses a particular KDBX generation or a particular derivation setting, verify it against the app’s own documentation and test with a copy of your file rather than assuming blanket support.

The same caution applies to moving in from another Android KeePass client. People ask how to import from Keepass2Android without losing entries. The fact data does not document an import path, a migration wizard, or any inter-app transfer mechanism. What it does establish is KDBX compatibility, which suggests a shared container format is the natural bridge — but “suggests” is doing real work in that sentence. Export from the old app, keep the exported file untouched, and open a duplicate in KeePassDX so the original remains intact if something goes wrong.

There is a broader point buried in this. A compatibility label is a claim about the container, and containers are only half of a password manager’s behavior. How entries are grouped, how attachments are handled, how history is stored — none of that is specified in the fact data. Treat KDBX compatibility as a green light for the file format and a yellow light for everything layered on top of it.

Biometric Unlock and the Password Generator: Two Different Trust Decisions

Biometric Unlock and the Password Generator are listed as functions, and they tend to get bundled together in people’s heads as “convenience features.” They are not the same kind of thing. Biometrics is a question about how you get into the vault. The generator is a question about what goes into the vault. Mixing them up leads to bad assumptions about both.

On biometrics, the fact data confirms the capability exists and stops there. It does not say whether biometric unlock can stand in for the master password after a reboot, does not describe a fallback flow, and does not specify what happens when the fingerprint sensor fails repeatedly. The misconception that biometric unlock means you never need the master password again is exactly that — a misconception the fact data cannot support. Treat the master password as the thing that matters and biometrics as a listed convenience whose boundaries are undocumented.

The password generator is easier to reason about because it is a narrower claim. It is listed as a function, which means the app can produce passwords for you. The fact data does not describe configurable character sets, length defaults, passphrase modes, or whether generated settings persist between sessions. Those are unknowns. What you can say is that having generation inside the same app that stores the result removes the step of moving a password between tools, which is a genuine practical benefit and also the entire extent of what the listing supports.

Both features sit inside the local-first frame, and that is the thread worth pulling. A generator running on your device and a biometric check running on your device keep the workflow local. Neither one changes the fact that the KDBX file is yours to store and protect. Convenience features reduce friction at the edges; they do not relocate the security boundary.

How to Install KeePassDX From the Official Source

The fact data lists “How to install” among the app’s functions but does not spell out a procedure, a distribution channel, or a set of steps. That absence is worth respecting. What can be said with confidence is the identity of the publisher: Kunzisoft. When you go looking for the app, match that name and the GPL-3.0-only license listing, and get it from the developer’s official source rather than a mirror or a repackaged build.

A persistent misconception is that KeePassDX is only distributed through F-Droid and not through Google Play, or the reverse. The fact data names neither store. It lists Android as the platform and Kunzisoft as the developer, and that is all. Rather than arguing about which storefront carries it, check the developer’s official page and follow the distribution link published there. That approach survives whatever the current channel situation happens to be.

Before you install anything, decide where your KDBX file will live. This is the step people skip, and it is the one that determines how the rest of the experience goes. Installing the app is quick; untangling a database that got duplicated across three folders is not. Pick a location, keep a backup outside it, and only then start opening files.

One more note on price and licensing, since both appear in the fact data and both get distorted. The app is free and open-source under GPL-3.0-only. The fact data does not specify pricing for any paid or donation variants, so if you encounter a paid tier somewhere, its terms are not established here. Do not assume a paid version exists, and do not assume one does not.

Verdict

KeePassDX is a credible local-first Android client for KDBX databases, and the fact data supports that much without strain: Kunzisoft as developer, GPL-3.0-only as license, Android as platform, KDBX compatibility plus autofill, keyboard integration, biometric unlock, and a password generator as the listed functions. If you already keep your passwords in a KDBX file and you want an Android app that works with that file rather than against it, this is a reasonable thing to look at.

It is not for everyone, and the gaps are the reason. Users who want built-in cloud sync without managing files themselves will find the local-first model to be work, not a feature. Users who expect a polished browser extension and desktop app bundle are looking at the wrong shape of product — no extension appears in the listed functions. Teams needing shared vaults with non-KeePass users are outside the scope entirely. Anyone unwilling to manage KDBX file storage and sync conflicts should pick something with a hosted backend and let it do that job. iOS users looking for a cross-platform KeePass app should look elsewhere, since the platform listed here is Android.

The thesis holds: the app’s real value depends on accepting undocumented limits rather than expecting cloud-sync polish. Merge-conflict behavior for two synced copies is not documented. The behavioral difference between accessibility-mode and keyboard-mode autofill is not documented, and no browser-specific support is claimed. Whether biometrics can replace the master password after a reboot is not documented, and shared-device concerns like app cloning, Android backup, and work profiles are not addressed at all. Cross-client behavior with KeePassXC is covered only to the extent that KDBX compatibility is listed.

None of that makes KeePassDX a bad choice. It makes it a choice you have to make with your eyes open. The app gives you a local vault in a portable format and a set of integration features that the fact data names but does not detail. If you are comfortable owning the file, testing your own setup, and keeping backups before you resolve anything, that trade is fair. If you want the gaps filled in for you by a vendor, this is not that product.

Pros

  • Open source and GPL-licensed
  • Works with KeePass KDBX databases, avoiding proprietary lock-in
  • Offline-first design using local database files
  • Integrates with Android Autofill and biometric unlock

Cons

  • No first-party cloud sync service; users must arrange sync and backup themselves
  • Requires users to understand KeePass database files and manage sync conflicts
  • Some advanced KeePass features may depend on database format and client support
Download from the official source

The link goes straight to Kunzisoft. We do not host app files.

Open official page →

Frequently asked questions

Is KeePassDX free?

The recorded pricing model is Free (open-source); exact pricing for any paid/donation variants unknown.

What license does it use?

It is listed under GPL-3.0-only.

Where can I download the official version?

The official link points to https://www.keepassdx.com/.

This article was drafted with AI assistance using official developer documentation, release notes, privacy policies, and public data, then reviewed by an editor. We do not claim lab testing. The full method is on our Review Method page.