Password securityCOMPARISON

KeePass vs KeePassXC (2026): Same Database, Different Apps, 2.8 Update

Not the same app, same .kdbx file: KeePass 2 is the Windows original with plugins, KeePassXC a native Linux, macOS and Windows rewrite with browser fill and TOTP. What 2.8 changes and which to pick.

By Eric Gerard · Editor · PwdFortress14 min readPhoto via Pexels

If you have gone looking for an offline password manager, you have run into two programs with almost the same name, the same logo lineage and the same file extension - and very little explanation of why both exist. The confusion is understandable, and it clears up quickly once you know one thing: they are not two versions of one product. They are two independent programs that happen to read the same database.

Not sure which one fits? Our password manager comparison tool asks how many people, whether you need free only, open source or a vault kept off the vendor's cloud, then removes what does not fit and prices the rest over 1 to 3 years.

Want the open source spirit without managing a .kdbx file and your own sync? Proton Pass is open source too, imports KeePass and KeePassXC exports, and syncs end-to-end encrypted on unlimited devices on its free plan.

Short answer

KeePassXC is the better default for most people in 2026, because it runs natively on Linux, macOS and Windows and has browser integration, TOTP codes and an SSH agent built in. KeePass is the original, is Windows-first, and earns its place through a large plugin ecosystem that can do things nothing else does. Crucially, both read the same .kdbx file, so this choice is reversible at any time - you are not locked in by picking one today.

At a glance: the two KeePass programs and the synced alternatives

Most people who compare these two are really choosing between a file they sync themselves and a vault that syncs for them. Here are both answers on one table, with the step to take for each. Prices were checked on the providers' own sites on 17 and 18 October 2026.

OptionBest forSync between devicesPriceOpen sourceNext step
KeePassXCLinux, macOS, mixed desktopsYou move the .kdbx file yourselfFreeYes (GPL)Download from keepassxc.org
KeePassWindows users who rely on pluginsYou move the .kdbx file yourselfFreeYes (GPL)Download from keepass.info
Proton PassOpen source fans who want sync handledBuilt in, end-to-end encrypted, unlimited devices on the free planFree, Plus 2.99 USD/month billed yearlyYes (apps)Try Proton Pass free
BitwardenA free synced vault, or self-hostingBuilt in, unlimited devices on the free planFree, Premium 19.80 USD/yearYesSee Bitwarden
NordPassThe most polished hosted appsBuilt in (free plan: 1 active device at a time)Free, Premium from 1.99 EUR/month (1 year)NoSee NordPass plans

If you are happy managing the file, you can ignore the bottom three rows: KeePassXC or KeePass is the right tool, and the rest of this comparison helps you choose between them. If sync is the part you dread, jump to moving a KeePass database to a synced manager.

Why there are two programs at all

KeePass came first: a Windows password manager written by Dominik Reichl in C# on the .NET framework, released under an open source licence. Because the code was open and the format documented, a separate project called KeePassX appeared to give Linux users a native application rather than a .NET program running under emulation. KeePassX was later succeeded by KeePassXC - the XC stands for Cross-Compatible - maintained by a community team that picked up development when KeePassX went quiet.

So the family tree matters: KeePassXC is not a fork of today's KeePass 2.x. It descends from a separate line that started with the early KeePass and was rewritten in C++ with the Qt toolkit. That is why the two programs look different, behave differently and ship on different schedules, while still speaking the same file format.

KeePassX vs KeePassXC: the third name in search results

KeePassX is finished. Its website posted "Development stopped" on 9 December 2021: "KeePassX is no longer actively maintained. You might want to switch to KeePassXC which is based on KeePassX" (keepassx.org). The last version listed there is 2.0.3, and it gets no security fixes.

  • If you still use KeePassX, install KeePassXC and open your existing .kdbx file. There is nothing to export or convert, and your master password and key file stay the same.
  • If a guide tells you to install KeePassX, it is out of date. KeePassX predates KDBX 4, the database format KeePass introduced in version 2.35 (2017), so it cannot open a file that current KeePass or KeePassXC saved in that format.
  • KeePass vs KeePassX is therefore not a live choice in 2026: the comparison that matters is KeePass 2 against KeePassXC, which is what the rest of this page covers.

What they share: the database

This is the part worth understanding before any feature comparison, because it changes the stakes of the decision.

Both programs store your entries in a single encrypted KDBX file, unlocked by a master password, optionally combined with a key file. There is no server, no account and no sync service in either program - the file sits wherever you put it, and if you want it on several machines you put it in whatever storage you already trust.

The practical consequence: switching is not a migration. You do not export, convert and re-import. You install the other program and open the file you already have. If you try one for a week and dislike it, you have lost nothing but the download. Two habits are still worth keeping - back the file up before opening it in a new program, and if one program has written a newer KDBX version than the other supports, update the older program first.

KeePassXC 2.8 (October 2026): does the new version affect your database?

KeePassXC 2.8.0 was released on 21 October 2026 (release notes). It is the biggest release in years: the move to Qt 6, native Arm64 builds for Windows, an AArch64 AppImage for Linux, Wayland Auto-Type through desktop portals, configurable keyboard shortcuts, and synchronisation with a remote copy of the database through external tools you configure yourself (it does not add a KeePassXC cloud service).

Does upgrading touch your .kdbx file? The release notes announce no change to the KDBX format, so a database saved by 2.8 still opens in KeePass 2 and in the mobile apps. One documented side effect: on Linux, the new Polkit Quick Unlock adds a UUID to the database's public metadata, so the file is marked as modified on first launch. If you sync the file between machines, expect one extra save, and copy the .kdbx somewhere safe before the first launch, as with any upgrade.

Should you update? Yes. The release fixes a use-after-free when importing crafted KDB files (CVE-2026-69150), an entry reference injection through the browser extension and out-of-bounds writes in browser messaging. If you use KeePassXC with its browser extension, those fixes alone justify updating every machine.

Keeping the app patched and the file in step on each device is the part of the KeePass model you do yourself. If that is the chore you want gone, Proton Pass imports a KeePassXC export and syncs end-to-end encrypted on unlimited devices on its free plan. The door stays open both ways: 2.8 also improves KeePassXC's own Proton Pass importer.

Black Friday 2026 (read on 17 November 2026): the Proton Pass partner page our link opens takes 60% off the first year of Pass Plus ($23.88 for the first 12 months, then $35.88 a year) and Pass Family ($33.48 for 6 accounts, then $59.88 a year), with the 30-day money-back guarantee. The order page shows the price for your country, so check it before paying. See the Proton Pass Black Friday offer

Close-up of a black laptop keyboard photographed at a very low angle, with the background dissolving into blur under a purple-grey tint
Close-up of a black laptop keyboard photographed at a very low angle, with the background dissolving into blur under a purple-grey tint

Where they genuinely differ

Platform and technology

KeePass is a C#/.NET application designed for Windows, where it is entirely at home. It can run on Linux and macOS through Mono, but that route means extra setup and an interface that never quite belongs on those desktops.

KeePassXC is C++ with Qt, with native builds for Windows, macOS and Linux. If you move between operating systems - or if you are not on Windows at all - this difference alone usually settles the question.

PlatformKeePassKeePassXC
WindowsNative (.NET)Native (Qt)
macOSVia Mono (non-native UI)Native (Qt)
LinuxVia Mono (non-native UI)Native (Qt)
iOSThird-party apps (Strongbox, KeePassium)Same third-party apps
AndroidThird-party apps (KeePassDX, Keepass2Android)Same third-party apps

On mobile the two are indistinguishable: neither project ships a phone app, and the third-party apps (Strongbox and KeePassium on iOS, KeePassDX and Keepass2Android on Android) open a .kdbx file created by either program. The Mono route for KeePass on macOS and Linux works, but expect non-native file dialogs, slower startup and no keychain integration.

Built in versus bolted on

The clearest philosophical split is what belongs inside the program.

KeePassXC builds the capabilities most people want directly into the application: integration with browsers via the official KeePassXC-Browser extension, generation of TOTP two-factor codes, and an SSH agent that can hold your keys. You install one program and those features are there.

KeePass keeps the core smaller and delegates to plugins. Browser integration, in particular, comes from third-party plugins rather than the program itself. This is not a shortcoming so much as a different bargain: you assemble the setup you want, and you maintain the pieces you assembled.

One capability both share is auto-type: the program types your username and password into the active window by simulating keystrokes. KeePass has the more elaborate sequence syntax, with per-entry patterns such as {USERNAME}{TAB}{PASSWORD}{ENTER}, delays and window-title matching, and two decades of edge cases covered. KeePassXC supports the same core syntax natively on all three desktops, and on Linux it handles both X11 and Wayland, where KeePass under Mono is limited. For most people both are fine; power users with unusual window-matching needs will find KeePass more flexible.

The stance on plugins

That bargain deserves to be stated plainly, because it is the real trade-off.

KeePass has a large plugin ecosystem covering import and export formats, synchronisation schemes, interface changes and integrations of every kind. If you have a specific requirement, there is a reasonable chance someone has already written the plugin.

KeePassXC does not support plugins at all, deliberately. The reasoning is that third-party code executing inside a password manager, with access to the decrypted database in memory, is a large attack surface to accept in exchange for convenience. Reasonable people weigh that differently - but it is a considered position, not an unfinished feature.

If your requirement is met by KeePassXC's built-in features, its approach gives you less to maintain and less to trust. If your requirement is met only by a plugin, KeePass is the program that can do it.

Security posture

Both are open source, so the code of either can be inspected. The honest comparison is about upkeep rather than a winner.

A vulnerability disclosed in 2023 and tracked as CVE-2023-32784 (NVD entry) made it possible to recover most of a master password from the memory of a running KeePass 2.x process - a consequence of how the managed .NET runtime handled text in memory. It was fixed in KeePass 2.54, as the NVD entry and the KeePass changelog record.

The useful lesson is not that one program is unsafe. It is that the version you are actually running matters more than which project you chose. An outdated KeePassXC is no better than an outdated KeePass. Whichever you pick, keep it updated, and get it from the project's own site or your distribution's repositories rather than from a mirror.

How to choose

Choose KeePassXC if you use Linux or macOS, or move between operating systems; you want browser integration and TOTP codes without assembling them yourself; or you would rather not run third-party code inside your password manager.

Choose KeePass if you are on Windows and need a capability that only its plugin ecosystem provides, or you already run a plugin-based workflow that works well for you.

Choose neither if you want a vault that syncs across your devices with no effort on your part. Both of these programs are file-based by design and leave sync to you. That is a feature if you want control, and an obstacle if you do not - in which case a hosted or self-hosted manager is the honest recommendation. The migration steps below show how to move your existing database in a few minutes. If you want sync handled for you, our NordPass review covers a hosted manager with a free tier, passkey support and XChaCha20 encryption. See our comparison of open source password managers for options that keep the code auditable, or the guide to self-hosting your own vault if you want sync without handing your data to a provider.

Moving a KeePass database to a synced manager

The most common reason people leave KeePass or KeePassXC is not security. It is the phone: keeping one .kdbx file in step across a laptop, a desktop and a mobile app through Dropbox, Syncthing or a USB stick works until two devices edit it on the same day and you have to reconcile the copies. If that is where you are, moving takes about ten minutes, and both open source options below import a KeePass database directly.

Proton Pass has a dedicated importer for KeePass and KeePassXC (checked on proton.me on 18 October 2026). In KeePass, use File, Export and pick KeePass XML (2.x); in KeePassXC, use Database, Export, XML File. Then open the Proton Pass browser extension, go to Settings, Import, and choose KeePass (xml). The free plan already covers unlimited logins on unlimited devices, so you can test the whole move before paying anything; Pass Plus (2.99 USD/month billed yearly) adds unlimited email aliases, a built-in authenticator and more vaults.

Bitwarden imports a KeePass database as an encrypted .kdbx file, an .xml export, or a .csv export from KeePassXC, according to its own help centre. File attachments do not come across: you upload them again in the new vault.

If you exported KeePassXC to CSV rather than XML, our password CSV converter reads that file in the browser, flags the passwords shared between entries, and rewrites it with the exact Bitwarden header or in the Chrome format that most other managers import.

Two precautions whichever you pick. An XML or CSV export is your entire vault in plain text, so export it to a local folder, import it straight away, then delete it and empty the trash. And keep the original .kdbx file as an offline backup: it costs nothing, and KeePassXC will still open it if you ever want to go back.

Keep it open source, let sync take care of itself: try Proton Pass freeImports KeePass and KeePassXC XML · Unlimited devices on the free plan · Plus 2.99 USD/month billed yearly · Black Friday: 60% off Pass Plus the first year→

Side by side

FeatureKeePassKeePassXC
LanguageC# (.NET)C++ (Qt)
Native onWindowsWindows, macOS, Linux
Browser integrationPlugin (KeePassRPC with Kee)Built in (KeePassXC-Browser)
PluginsYes (.NET ecosystem)No, by design
TOTP codesPluginBuilt in
YubiKey challenge-responsePluginBuilt in
SSH agentPluginBuilt in
Auto-typeYes, most flexible syntaxYes, native on X11 and Wayland
Database formatKDBX 3.x / 4.xKDBX 3.x / 4.x
EncryptionAES-256 or ChaCha20AES-256 or ChaCha20
Key derivationArgon2d / Argon2id (AES-KDF on KDBX 3)Argon2d / Argon2id (AES-KDF on KDBX 3)
Open sourceYes (GPL)Yes (GPL)
MaintainerDominik Reichl, since 2003Community team, since 2017

The bottom line

The question "KeePass or KeePassXC" carries less weight than it appears to, and that is good news. They read the same database, so no answer traps you. For most people in 2026 the sensible default is KeePassXC - genuinely cross-platform, with the features you would otherwise have to bolt on already inside. KeePass remains the right answer for Windows users whose needs are met specifically by its plugins.

Pick one, keep it updated, and remember that the strength of either comes down to the same thing: a long, unique master password that exists nowhere else.

Disclosure: links to Proton Pass, Bitwarden and NordPass go through our /go/ redirect. Proton Pass and NordPass are affiliate partners and may pay us a commission if you subscribe, at no extra cost to you; Bitwarden pays us nothing. KeePass and KeePassXC are free and linked directly to their official sites.

Frequently asked questions

Does KeePassXC 2.8 change my database?

No format change is announced in the 2.8.0 release notes (21 October 2026), so a database saved by 2.8 still opens in KeePass 2. On Linux, the new Polkit Quick Unlock adds a UUID to the database's public metadata, so the file shows as modified on first launch. Back the file up before upgrading, then update: 2.8 fixes several security bugs, including CVE-2026-69150.

Are KeePass and KeePassXC the same program?

No. They are two separate programs that read and write the same database format. KeePass is the original Windows project by Dominik Reichl, written in C# on .NET. KeePassXC is an independent community project written in C++ with Qt, descended from KeePassX, which was itself a Linux port of the early KeePass. They share a file format and a name, not a codebase.

KeePassX vs KeePassXC: what is the difference?

KeePassX is the older Linux program that KeePassXC grew out of. Its own website announced on 9 December 2021 that KeePassX is no longer actively maintained and points users to KeePassXC; its last release is 2.0.3. KeePassX predates the KDBX 4 format, so it cannot open databases saved in KDBX 4 by current KeePass or KeePassXC. If you still run KeePassX, install KeePassXC and open the same .kdbx file: no export is needed.

Can I open the same .kdbx file in both?

Yes, and this is the single most useful fact about the pair. Both support the KDBX format, so the same database opens in either program with the same master password or key file. Switching is not a migration - you point the other program at the file you already have. Back it up first as a matter of habit, and if one program has written a newer format version than the other supports, update the older program before opening it.

Which one is better for Linux or macOS?

KeePassXC. It is written in C++ with Qt and ships native builds for Linux, macOS and Windows, so it looks and behaves like a normal application on each. KeePass is a .NET application built for Windows; it can run on Linux and macOS through Mono, but that path involves extra setup and a less native experience.

Does KeePassXC support plugins like KeePass does?

No, and that is a deliberate design decision rather than a missing feature. KeePass has a large third-party plugin ecosystem that extends it in almost every direction. KeePassXC does not load plugins at all, on the grounds that arbitrary third-party code running inside a password manager enlarges the attack surface. Instead it builds the most-wanted capabilities - browser integration, TOTP codes, an SSH agent - directly into the program.

Do I still need a browser extension plugin?

With KeePassXC, no separate plugin is needed on the application side: browser integration is built in and pairs with the official KeePassXC-Browser extension. With KeePass, browser integration is provided by third-party plugins, so you choose one, install it, and keep it updated alongside the program itself.

Is KeePass less secure than KeePassXC?

Neither is unsafe, and both are open source, so the honest answer is about maintenance rather than a verdict. A vulnerability disclosed in 2023 (CVE-2023-32784) allowed much of the master password to be recovered from the memory of a running KeePass 2.x process; it was fixed in KeePass 2.54. What that episode illustrates applies to both programs equally: the version you actually run matters more than the badge on the box. Keep whichever you choose up to date.

Which should I choose in 2026?

If you want an offline password manager that works the same on Linux, macOS and Windows with browser integration and TOTP already included, choose KeePassXC - it is the better default for most people today. Choose KeePass if you are on Windows and want a specific capability that only its plugin ecosystem provides. Because the database format is shared, this decision is reversible at any time.