KeePassXC review — offline password manager without cloud
KeePassXC is an open-source password manager that keeps your passwords in an encrypted file on your own device: no cloud, no account, and you handle syncing yourself.

KeePassXC review
KeePassXC is an open-source password manager that keeps your passwords in an encrypted file on your own device: no cloud, no account, and you handle syncing yourself.
Who is this for? Anyone who wants no cloud-based password manager and prefers to handle synchronisation themselves. For most users, Bitwarden is the simpler choice.
KeePassXC is an open-source password manager that stores an encrypted database file locally. No cloud, no account, no synchronisation service. You manage everything — and that is exactly why some privacy-minded users prefer this over Bitwarden.
How KeePassXC differs from Bitwarden
Bitwarden synchronises your vault to the Bitwarden cloud (or your own server). KeePassXC doesn’t. The database file (.kdbx) sits on your device. You decide where it lives, how it’s synchronised and who has access to it.
Advantage: No dependency on an external service. Even if KeePassXC stops existing tomorrow, your database still works — any compatible KeePass programme can open the file. A hardware key is the exception to check first: KeePassXC’s FAQ says YubiKey databases from KeePass2 (KeeChallenge) and KeePassXC can’t open each other.

Older version: KeePassXC 2.7.10 (2025). Groups on the left, entries on the right, all stored in one local .kdbx file. Screenshot: VulcanSphere, Wikimedia Commons (GPL).
Disadvantage: Synchronisation across multiple devices must be arranged yourself — via Syncthing, an encrypted cloud folder, or a USB drive.
Specifications
| Property | Value |
|---|---|
| Platform | Windows 10/11, macOS 12 or later, Linux |
| Database format | KDBX 3.1 / 4 (.kdbx) |
| Encryption | AES-256, ChaCha20 or Twofish |
| Open-source | Yes (GPL-2 or GPL-3) |
| Cloud sync | No built-in cloud — local file; since 2.8.0, Remote Sync can run your own download/upload commands (e.g. scp) |
| Browser extension | Yes (KeePassXC-Browser for Firefox, Chrome, Edge, Brave, Chromium, Vivaldi and Tor Browser) |
| YubiKey / hardware key | Yes: HMAC-SHA1 challenge-response with YubiKey or OnlyKey, not FIDO U2F; for a Nitrokey, the FAQ points to Nitrokey’s own documentation |
| Quick Unlock | Windows Hello; Touch ID or Apple Watch on macOS (since 2.8.0 also the Mac’s password when Touch ID is unavailable); on Linux since 2.8.0 via Polkit, your system’s own authentication prompt |
| Mobile | No official app — use KeePassDX or KeePass2Android (Android), Strongbox or KeePassium (iOS) |
| Price | Free |
Database security
KeePassXC encrypts the database with AES-256 by default, or with ChaCha20 or Twofish. You protect access with a combination of:
- Master password — always use one: KeePassXC warns strongly if you skip it, and its FAQ says never to use a key file without a password
- Key file — optional extra file stored separately (on USB drive). The file must never change, and if you lose it you lose the database, so keep a backup
- Hardware key (YubiKey/OnlyKey) — optional, as extra challenge-response protection. Set a slot to HMAC-SHA1 first and keep a copy of its secret (or program a second key with it): without either, a lost key means a lost database
The combination of master password, key file and optional challenge-response through a hardware key makes offline attacks much harder. Important detail: this is not classic online 2FA, but additional protection for the database key itself.
Update to 2.8.0 or later. Version 2.8.0 (21 October 2026) fixes a use-after-free when importing crafted KDB files (CVE-2026-69150), out-of-bounds writes in the browser-extension messaging, and entry-reference injection through the browser extension, according to its release notes. The project rates its CVEs low to moderate and says none concern the core functionality or cryptography. It also moves the app to Qt 6.
Independent reviews. France’s cybersecurity agency ANSSI awarded version 2.7.9 on Windows 10 a first-level security certification (CSPN) in November 2025, valid until November 2028; ANSSI adds that this is no recommendation and no guarantee against exploitable flaws. The evaluating lab, Synacktiv, reported one issue, outside the evaluated threat model: an attacker with administrator rights may find master passwords in a memory dump. A 2023 review of 2.7.4 by consultant Zaur Molotnikov found no major problems in the core, and left out parts such as browser communication and auto-type. Neither covers 2.8.0.
Synchronisation across devices
KeePassXC doesn’t synchronise automatically. Since version 2.8.0 (21 October 2026) it can run a download and an upload command you set yourself, for example scp to your own server (Database → Remote Sync… → Setup Remote Sync…); KeePassXC runs those commands but provides no server. Options for using the database across multiple devices:
Syncthing: Peer-to-peer synchronisation without cloud. The database is synchronised encrypted between your devices. Most privacy-friendly option. See the Syncthing review.
Encrypted cloud folder (Proton Drive, Cryptomator + Dropbox): Store the .kdbx in an encrypted cloud folder. KeePassXC opens it locally — the cloud only sees an encrypted file.
USB drive: Copy the database manually. Simple, no automation, suitable for minimal use.
Browser extension
KeePassXC-Browser connects the extension to the desktop app via a local socket. The extension recognises login fields and offers your saved logins — comparable to Bitwarden’s extension. Filling in without a click is an option that is off by default, and the extension itself warns it isn’t safe. Works on Firefox, Chrome, Edge, Brave, Chromium, Vivaldi and Tor Browser.
Requirement: KeePassXC desktop must be running for the extension to work. No browser-only use like Bitwarden.
Mobile use
KeePassXC itself has no mobile app. The official FAQ points to these compatible alternatives:
- Android: KeePassDX or KeePass2Android — both open
.kdbxfiles, from local storage or through your own sync setup - iOS: Strongbox or KeePassium — both support KeePass databases; Strongbox has a free version for non-commercial use with a paid Pro version, KeePassium is free with an optional premium subscription. If you want a first-party mobile app without extra setup, consider Bitwarden.
KeePassXC vs Bitwarden
| KeePassXC | Bitwarden | |
|---|---|---|
| Cloud dependency | No | Optional (cloud or self-hosted) |
| Automatic sync | No — arrange yourself | Yes |
| Open-source | Fully | Code public; official apps commercially licensed builds since October 2026 |
| Mobile app | Via third parties | Own app |
| Hardware key | Yes (YubiKey/OnlyKey challenge-response) | Yes, for logging in to your account: FIDO2 security key free, YubiKey OTP with premium |
| Difficulty | Higher | Lower |
| Price | Free | Free + premium subscription available |
Choose KeePassXC if:
- You don’t want data in a cloud, even encrypted
- You want complete control over the database file
- You already have a synchronisation solution (Syncthing, NAS)
- You want a YubiKey or OnlyKey as extra database protection
Choose Bitwarden if:
- You want easy synchronisation across multiple devices
- You want a mobile app without extra configuration
- You prioritise ease of use
Caveats
Control comes with operational burden: KeePassXC is excellent when you actually want to own the file, the sync method, and the backup process. If you do not want to think about those things, the same control becomes friction rather than an advantage.
Mobile is still an ecosystem workaround: The database format is portable, but the experience is not as unified as with Bitwarden. That matters if you expect a seamless first-party app stack across laptop and phone.
A bad DIY sync setup can be worse than a good hosted service: KeePassXC is not automatically safer just because it is local-first. If you handle backups or synchronisation badly, you can end up with more failure modes and less reliability than a well-run cloud option.
Pros and cons
Pros
- No cloud dependency — the .kdbx file lives entirely on your device and works even if KeePassXC stops existing
- Supports master password + key file + optional hardware-key challenge-response, which makes offline attacks much harder
- Fully open-source (GPL-2 or GPL-3) and free
- Browser extension works with Firefox, Chrome, Brave, Edge and other supported browsers via local socket
- Uses the KeePass file format, shared with other apps — any compatible KeePass programme can open the file
Cons
- No official mobile app — requires a separate KeePass app such as KeePassDX, KeePass2Android, Strongbox or KeePassium
- Synchronisation across devices must be arranged manually via Syncthing, encrypted cloud, or USB
- Desktop app must be running for the browser extension to work — no browser-only access
- Higher learning curve than Bitwarden for new users
Conclusion
In our view KeePassXC is one of the most privacy-friendly password managers for users willing to manage a bit more themselves. No cloud, fully open-source, optional hardware-key protection. The price for that control is that you need to arrange synchronisation and mobile access yourself.
Beginners choose Bitwarden. Advanced users who prefer control over convenience choose KeePassXC.
Getting started
1. Download and install KeePassXC
Download KeePassXC from keepassxc.org/download/. Available for Windows, macOS, and Linux; on Linux the download page recommends the Flatpak package. No account required.
2. Create a new database
This assumes a new database. Already have one? Click Open Database and go on to step 3; from another password manager, Import File brings your data in.
Open KeePassXC and click Create Database (or Database → New Database…). The wizard has three screens: General Database Information (a name), Encryption Settings (the defaults are fine for most people) and Database Credentials. There, choose a strong master password you do not use anywhere else. Write it down and store it somewhere safe and separate from your devices — there is no recovery option.
Optional: on the same screen, Add additional protection… → Add Key File → Generate. Store the key file on a separate USB drive, not on the same device as the database, and keep a backup copy: without it the database won’t open.
After the wizard, save the database (Database → Save Database) and choose where the database file goes.
3. Set up the browser extension
Install KeePassXC-Browser for your browser (linked on the download page). On Linux, browsers installed as Flatpak or Snap are generally not supported; Ubuntu’s Firefox Snap is the known exception. In KeePassXC go to Tools → Settings → Browser Integration (on macOS, Settings is in the KeePassXC app menu instead of Tools), tick Enable browser integration, and under Enable integration for these browsers: tick yours, then click OK.
With your database unlocked, open or restart your browser, click the extension icon and click Connect. Give this connection a unique name (e.g. firefox-laptop) and click Save and allow access. The extension connects via a local socket — KeePassXC must be running for autofill to work.
4. Set up synchronisation
Choose a sync method that fits your setup:
- Syncthing: store the
.kdbxin a shared Syncthing folder for peer-to-peer sync without any cloud. Edit on one device at a time: after changes on two devices, Syncthing keeps the older one as a.sync-conflictcopy, which you can bring back in with Database → Merge From Database… - Proton Drive or Cryptomator + your own cloud: store the
.kdbxin an encrypted folder — the cloud only sees an encrypted file. Proton Drive has desktop apps for Windows and Mac; on Linux only a command-line tool - USB drive: copy manually if you only have a small number of devices
5. Add a mobile app
Use KeePassDX or KeePass2Android on Android, Strongbox or KeePassium on iOS. Point them at the same .kdbx database via your chosen sync method. Syncthing on a phone means a third-party app (see the Syncthing review). Using a hardware key? Check first that the app supports it: KeePassium and Strongbox list YubiKey support.
Next step
Choose this if…
KeePassXC is the right choice if you deliberately want no cloud vault and are willing to own your sync and backup process. If you just want it to work across all your devices without thinking about it, this is usually not the first pick.
- Bitwarden review — the simpler, mostly open-source choice with built-in sync
- YubiKey vs Nitrokey review — hardware keys as extra database protection
Already have this?
If you already use KeePassXC, make sure your auto-lock, backup routine, and key file storage actually work before adding more features.
- Two-factor authentication guide — 2FA for the accounts in your vault, not as a substitute for your vault
Want to go further?
If the main question is control versus convenience, compare KeePassXC only against the few logical alternatives rather than a long list.
- Bitwarden review
- Password manager guide — migration, backup, and recovery planning