THE FILE FIELD GUIDE
.kdbx

KeePass Encrypted Database

Disk & Database

KDBX is a KeePass-style encrypted credential database. Unlocking requires the configured master-password/key-file or other factors. Neither the database nor a password alone is always sufficient; inspect key composition and version support.

Main use
Store credentials in an encrypted database
Data type
Binary data
All sections, questions and sources

Content reviewed: · Editor:Kai

Opening steps

Choose your environment or purpose to see its steps.

KeePass / compatible KDBX client

Preserve the original and inspect a working copy in a compatible application.

  1. Select a copy in a trusted compatible client.
  2. Supply the key factors configured at creation.
  3. Inspect entries, attachments and modification state; separate originals and backups.
Inspect the received file and its requirements

Establish dependencies and settings before proceeding.

  1. Check KDBX version, cipher/KDF and client support.
  2. Identify key files, account-dependent factors or other configured components.
  3. Distinguish synchronization-conflict copies from the intended master.

Menu labels and support vary by app, OS and version. Preserve the original before making changes.

Troubleshooting by symptom

  • Password rejected: inspect the complete key-factor combination.
  • Another device fails: inspect additional factors and cipher/KDF support.
  • Data stale: compare sync location, conflict copies and update times.
  • Key lost: inspect legitimate key backups; guaranteed unlocking is not available.

KDBX → compatible database / selected export

  1. Use an environment that can unlock the database and perform a recipient-compatible migration/export.
  2. Verify entry counts, attachments, history and whether the output remains encrypted.

CSV/XML may be plaintext; inspect preservation of attachments, history and added features.

Understand the composite master key

A composite setup requires all configured factors. Replacing a key file with another similarly named file does not recreate the key; preserve the original securely.

Source for these steps:KeePass · KDBX File Format Specification / KeePass · Master Key

Worked example: checks before handoff

Example: before mobile migration, verify client support/factors and test unlocking plus representative entries/attachments on a copy.

Source for these steps:KeePass · KDBX File Format Specification / KeePass · Master Key

Related-format differences

Related-format differences
Format / methodPurpose and preserved information
.kdbxStore credentials in an encrypted database
KDB / CSVKDB is a legacy format; CSV can be plaintext, with different compatibility/confidentiality.
KDBX → compatible database / selected exportCSV/XML may be plaintext; inspect preservation of attachments, history and added features.

Handling and security

Do not share master credentials/key files or leave plaintext exports in ordinary shared storage.

Questions and answers

Will Excel read KDBX?

It is encrypted; use a compatible client and correct key factors.

Can I recreate a lost key file?

A new key file normally differs from the lost one; inspect legitimate backups.

Does CSV retain database encryption?

CSV can be plaintext; review destination/fields and treat it separately from encrypted database storage.

Format facts: name, steward and MIME type
Formal name
KeePass Encrypted Database
Steward / specification
KeePass
MIME type
Consult the producer or delivery system. The extension alone does not establish a MIME type.

Primary and official sources

  • Software documentationKDBX File Format Specification

    Encrypted database versions, structure and key derivation.

    KeePass · Link checked:
  • Software documentationMaster Key

    Master passwords, key files and recovery limitations.

    KeePass · Link checked: