Where Does KeeWeb Store Vaults and Settings?
KeeWeb stores vaults as .kdbx files wherever you save them. Settings live in browser storage; self-hosted adds config.json.
Last updated
KeeWeb inverts the usual layout: there is no vault directory because the vault is a single .kdbx file wherever you put it (local disk, Dropbox, Drive, OneDrive, WebDAV, or self-hosted). Desktop apps open local files; the web app opens URLs and cloud picks. App preferences live in browser local storage, not files, so reinstalls forget settings but never passwords.
Self-hosting adds one file: config.json beside the web app pins the default database URL and options for your users. That file configures the deployment, never the vaults. The format compatibility is the safety net: any KDBX client opens the same file, so KeeWeb abandonment costs a UI switch, not data.
Where KeeWeb stores this, by platform
(your chosen .kdbx location)
The vault itself, anywhere you save it. Sync via cloud or WebDAV for multi-device. Self-hosted web adds config.json for defaults. App prefs in browser storage; back the .kdbx, nothing else.
Frequently asked questions
how do i back up my keeweb vault
Copy the .kdbx file itself; that file is the vault, readable by KeePass, KeePassXC, and every KDBX client. Cloud-synced copies merge on save. Losing password plus keyfile means no recovery exists anywhere.
is keeweb still maintained
Yes, since 2021. The original app stopped shipping while the KDBX format marches on (KDBX4, Argon2id elsewhere). Keep vaults in portable KDBX so migration to KeePassXC or forks like KeeWebX stays one file open away.
Notice an outdated path? Let us know.