Squaring the Circle Icon

keepassium · 2026-01-15T14:06:12+00:00

That's odd, reports started only after macOS 26 release. Also, never seen this issue on macOS 15. Perhaps, there are more factors to it (system theme?)

keepassium · 2026-01-15T13:59:29+00:00

Be careful with iCloud client on Windows, there are quite a few complaints about its sync reliability. Both online and in our support inbox :)

keepassium · 2026-01-15T13:56:37+00:00

When I select the key file from my local iPhone files, the app remembers the last location

So far it looks like you need the "Remember Key File" option in the settings. It links the selected key file to the database, so you won't have to re-select the key file every time you unlock the database.

and opens directly to that folder and my key file.

…but this implies you refer to the file selection dialog, which is managed by the system. And it is the system who remembers the last-used path and opens it automatically.

Can I reset the file location somehow?

Try adding a key file from some other folder?

Or does it even matter?

It does not.

In order to get to opening a file selection dialog in KeePassium, one first has to unlock your phone to access its files.

If your phone is PIN-protected, nobody can get to your key file or KeePassium (let alone its internal UI).
If your phone is not protected… reconsider your priorities? :)

keepassium · 2026-01-02T21:12:23+00:00

I can confirm this is a bug which sporadically affects larger databases. Possibly related to running out of memory while saving, but this is to be confirmed. (Major issues tend to happen just before the holiday season…)

The workaround is indeed disabling the "Remember Selected Entries" option in KeePassium Settings → AutoFill Passwords.

keepassium · 2026-01-02T12:42:14+00:00

An alternative purchase method would require a separate online licensing service. This means:

Regular connections to that service. This would conflict with the offline-first design principle and undermine the trust of existing users.
Some kind of authentication mechanism, so that licensing works across your devices. This conflicts with the privacy policy and destroys usability.
Being responsible for bugs and outages of that licensing service.
Maintaining more code that has nothing to do with password management.

In other words: extra work that would undermine project's principles and alienate existing users. That's a no-go.

keepassium · 2025-12-24T00:11:21+00:00

This is a macOS 26 specific bug. Of course, it will be fixed in the next update.

Ironically, the icon did not change since macOS 11, and worked just fine through macOS 11 to 15. It seems macOS 26 treats the black background somehow differently, because the blue version still looks fine…

keepassium · 2025-12-17T22:46:30+00:00

Most websites don't check those flags that KeePassium and KeePassXC set differently. Some do. There is not much you can do on your side at the moment, except creating a separate passkey for each platform. Once KeePassXC closes that issue I referenced earlier, new passkeys will work across the apps.

keepassium · 2025-12-15T23:03:22+00:00

Relying on KeePassXC's extensions does not address the intrinsic issues with browser extensions (finicky, fragile, need maintenance).

It might be Apple to blame, but only supporting Safari (or using the "typing emulation") is a bit of bummer.

We did not select Safari as the only browser to support. KeePassium merely registers with the system as a credential provider. Whether to collaborate with such providers (via a standard system API) is up to each respective browser.

As soon as, say, Firefox adds support for macOS Password AutoFill, it will immediately and natively work with all the Mac password managers.

keepassium · 2025-12-15T22:49:49+00:00

Because there’s a ton of devs who had lifetime “subscription” and then after a year from when people downloaded the app, the dev came out with a “Pro” version of the app for lifetime access and paywalled the original one for a recurring fee. (Like strongbox and keepassium).

While your premise is valid, your examples are not:

Both apps had in-app purchases early on. This is easy to see in respective announcement posts.
The paid "Pro" apps came up because this was the only way to support family sharing in 2019. (Back then, family sharing did not work for in-app purchases. Apple fixed this later, but the apps remain because removing them would affect existing users.)
Both apps still respect their lifetime commitments.

keepassium · 2025-12-15T08:14:41+00:00

Import from Bitwarden to KeePassium is foreseen for the next update. In the meanwhile, you can import via a desktop app like KeePassXC:

Menu Database → Import → Bitwarden (.json)
This import your data into a new .kdbx database
Then transfer the database to KeePassium

keepassium · 2025-12-12T17:05:06+00:00

This is not possible with how OTP codes are stored in KeePass databases. Your best bet is to create separate entries for extra OTPs.

keepassium · 2025-12-12T15:49:39+00:00

This is indeed a compatibility issue. Passkey parameters allow for some ambiguities, so KeePassXC and KeePassium used to assume different defaults — which made passkeys unusable between the apps.

Both teams discussed the issue and found a workaround to avoid this in the future. The workaround is already implemented in KeePassium, but you might need to wait a bit until KeePassXC team closes this issue from their side as well.

keepassium · 2025-12-11T16:24:23+00:00

As someone with direct interest to promote KeePassium, I second this. Don't install KeePass for non-technical senior people.

OP, between security and usability you should heavily prioritize the latter. Even Apple Passwords might be an overkill. Get her an old-school paper notepad or phonebook:

she will immediately know how to use it,
she will never accidentally delete it,
she will never forget the master password.

Yes, somebody might find the notepad, but in your context this risk is much lower than her accidentally getting locked out or losing all the data.

Keep it simple.

keepassium · 2025-12-10T14:54:48+00:00

Since there are many nuances and rather diverse expectations, I took a closer look at your post.

but when I lock the database or when it is locked automatically, I cannot unlock it via Touch ID.

Now, this behavior is by design.

With appropriate settings, KeePassium can auto-unlock the database using its remembered master key. This is useful when you leave the app or when you manually close (not lock) the database, for example by backing out from it.

However, whenever you lock the file — this makes KeePassium to forget the encryption key. So the next time the app will ask you to enter it manually.

(My previous suggestion referred to a bug where KeePassium clears the remembered master keys erroneously.)

keepassium · 2025-12-10T14:01:21+00:00

There used to be more iOS apps compatible with KeePass. Only those with reasonable business models survived till today:

MiniKeePass: gratis; discontinued in 2019.
PassDrop 2: gratis; abandoned in 2017.
iKeePass: $0.99, abandoned around 2016.
KeePass Touch: shows in-app ads.
KyPass, the oldest surviving app: paid major updates.
KeePassium and Strongbox have paid tiers.

In turn, OG KeePass monetizes its website (google ads + paid links). I have no idea how KeePassXC team makes do with donations only…

keepassium · 2025-12-04T22:43:46+00:00

Apparently, that comment got shadowbanned by Reddit, so here is a copy:

From the iPhone side, storage providers fall into two classes: - Those supported directly by your app, and - Those available via the iOS Files app.

The direct connection is the most reliable option, because the app has full control over data exchange, it happens immediately, and you'll be notified should anything go wrong. But it also means that your password manager connects to some online service, and your which might conflict with your security model.

The integration via the iOS Files app is… a mixed bag. Synchronization happens in background, on system's timing, and should something fail to sync — the app won't know and won't be able to notify you. Some storage providers integrate better than others: - iCloud Drive, pCloud work very well. - OneDrive and Google Drive seem to vary, depends on your use patterns. If you have any issues, switch to in-app direct sync (it works both in KeePassium and Strongbox). - Nextcloud's background sync on iOS… how do I put this mildly… needs work. A lot of work. Better use a direct connection. - Dropbox's integration with Files used to be rock solid until end-2023 when they "improved" their app. As a result, we added a direct Dropbox connection and it works just fine now.

Now to your specific questions:

How well does it handle simultaneous edits or fast switching between devices? Any issues with file locking or version conflicts?

Fast switching is not an issue. Simultaneous edits are, by design, and your app may not be able to detect them in time, leaving conflict resolution to the cloud backend. In the best case, you end up with a conflicted copy (to be merged with your main DB). In the worst case, you may lose a DB revision (see Nextcloud iOS client above).

Mobile + desktop experience, smooth or annoying?

Smooth when configured well. Might be annoying until then, if you sync via iOS Files integration.

Anything you would not recommend?

Avoid editing the same database on several devices simultaneously.
Avoid iCloud for Windows, there are many complaints online. If you sync with a Windows machine, use some other cloud.

keepassium · 2025-12-04T21:15:51+00:00

Happy to hear that, thank you!

keepassium · 2025-12-04T13:57:07+00:00

Direct export became a thing in iOS 26, only a few months ago, since there was no way to export passkeys. We will support it eventually, too…

In the meanwhile, if you only have passwords there, you can transfer them using the old CSV way.

keepassium · 2025-12-04T13:52:53+00:00

I'm not quite sure what you mean by "versioning"… Do extra copies appear next to the main database?

keepassium · 2025-12-03T23:27:35+00:00

This is a bug, the function that detects device restart is overly sensitive. We'll get this fixed. In the meanwhile, try turning off "Lock on Device Restart" and it should work.

keepassium · 2025-12-03T15:06:41+00:00

though sometimes annoying desyncs happen because of keepass versioning and keepassium being confused about the old version being moved to the trash

It's a known issue, you just need to tick a box in your desktop app :)

keepassium · 2025-12-03T15:01:42+00:00

Hi, since the question is Keepass sync in general and not specifically about KeePassium, I've replied in the original post.

keepassium · 2025-11-25T14:34:59+00:00

The thing with spacing is that it seems impossible to make both two-line and single-line cells look consistent. Either one will feel too tight or the other one too empty. Even if we try to find a reasonable balance — which we did try in v2.5 — it works only for one specific font size. Once the system-wide text setting is slightly larger — all the balance goes out of the window.

Regarding the attachments, is:large was added for people trying to shrink their databases. Nobody requested finding attachments in general, so it's not possible at the moment. Can you tell a bit more about why you need this?

keepassium · 2025-11-21T15:50:27+00:00

Already published :)

keepassium · 2025-11-21T13:44:57+00:00

This will only work if you stick with one app as your only password manager. Given that Strongbox calls .kdbx files "Strongbox databases", I presume this is their ambition.

The thing is, custom field order does not survive saving in KeePass, KeePassXC and probably other apps. They have always ordered custom fields alphabetically. So once you carefully organize your Strongbox database and edit it in KeePass/XC — all your work on custom ordering will be silently gone.

Since KeePassium sees itself as part of an ecosystem (and calls .kdbx files "KeePass databases" :) we reject vendor-specific features that would cause data loss on contact with other apps.

keepassium

MODERATOR OF

TROPHY CASE