KeePass (KDBX)
Keyguard can work with KeePass (KDBX) databases: all your passwords live in a single, highly-encrypted file stored directly on your device. You have complete control over your data — keep the file on your computer or a USB drive, or sync it yourself with a service like Syncthing, Google Drive, or Dropbox.
Beta. The KeePass implementation is in beta and is not yet fully compatible with standard KeePass clients. Make sure you have a verified backup of your database before using it.
Opening and creating databases
When adding an account, choose KeePass and either open an existing database or create a new one. Keyguard supports these file providers:
- file system;
- WebDAV.
New databases are created in the KDBX 4.x format.
To unlock a database, enter its master password, select its key file, or provide both depending on how the database was configured.
Editing
KeePass support is read-write: you can add, edit, and delete items and
folders, and Keyguard saves the changes back into the .kdbx file. Because
changes are written directly to a local file without server mediation, let
external sync tools finish before editing the database on another device,
and keep backups.
How KDBX maps to Keyguard
Keyguard presents KeePass data through the same model it uses for Bitwarden:
| KDBX | Keyguard |
|---|---|
| Groups | Folders |
| Entries | Items (logins, and other types) |
| Tags | Item tags; a Favorite tag marks a favorite |
What does not apply
Some of Keyguard’s features are built on Bitwarden’s server platform and have no KeePass equivalent:
- Organizations and collections — KDBX has no concept of them;
- Sends — a Bitwarden platform feature.
On Wear OS, the watch receives a one-time copy of the database — see Keyguard on Wear OS.