Support
Start with the frequently asked questions. If they do not answer your question, report it on GitHub.
Frequently asked questions
How do I use KeyDBX to AutoFill passwords?
Open Settings > General > AutoFill & Passwords on your iPhone and select KeyDBX. Then tap a password suggestion in a sign-in field, or pick an account from the suggestions above the keyboard.
How do I open a database on Dropbox?
- On the KeyDBX unlock screen, tap Choose, then Choose from Dropbox.
- Sign in to Dropbox and allow KeyDBX to access it.
- Put the
.kdbxfile in the KeyDBX folder inside theAppsfolder in your Dropbox. - Select the file in the KeyDBX Dropbox list.
KeyDBX can access only its own app folder. For files in other locations, use Choose from Files and open them through the Dropbox app.
There is a conflicted copy in my Dropbox. What do I do?
When the same database changes in two places, KeyDBX does not overwrite the version on Dropbox. Dropbox saves the KeyDBX version under another file name. Open both files in KeePass or KeePassXC on your computer and merge them, then tap Got It in KeyDBX Settings.
Can I use KeyDBX offline?
Yes. A Dropbox database unlocks with the version this device last synced, and you can edit and save it. KeyDBX uploads the changes when you return to the app or tap Sync Now in Settings.
KeyDBX cannot open my database.
KeyDBX supports KDBX 4.0 and 4.1. Convert KDBX 3.1 and KeePass 1.x databases to the KDBX 4 format with KeePass or KeePassXC on your computer first. The error message names the stage that failed. Include the full error message when you report a bug.
Can I recover a forgotten master password?
No. Your database is encrypted with your master password. The developer has none of your data and no recovery mechanism.
Face ID unlock suddenly asks for my master password.
When the Face ID data on your device changes (for example, you reset Face ID or add an appearance), the master password KeyDBX stored becomes invalid. Enter the master password once, and Face ID unlock works again.
AutoFill shows "Using AutoFill Copy".
When the original file is temporarily unreadable (for example, when you are offline), AutoFill uses the encrypted copy on your device and shows when the copy was updated. The copy is updated each time you unlock or save. Open KeyDBX and unlock once to update it.
A password I saved with AutoFill is not in the database.
When AutoFill cannot write to the original file right away (for example, when you are offline), new passwords and passkeys are kept on your device. The next time you unlock the database in KeyDBX, the app writes the pending changes to the database. Pending changes are listed under Sync & Pending Changes in KeyDBX Settings.
Where did the password I copied go?
Copied content stays on this device, is cleared automatically after 60 seconds, and does not sync to your other devices.
Passwords are hidden during screen recording.
During screen recording, mirroring, or AirPlay, KeyDBX hides passwords and verification codes. They appear again after recording or mirroring stops.
How do I change the interface language?
Choose it in KeyDBX under Settings › Language. By default, KeyDBX follows the system language.
Report a bug
Issues are public. Do not paste passwords, database files, master passwords, key files, or TOTP secrets. Check screenshots for this information before you post them.
Include:
- The KeyDBX version, iOS version, and device model.
- Where the database is: Files, iCloud Drive, Dropbox signed in within KeyDBX, or Dropbox opened through the Files app.
- Steps to reproduce, the expected result, and the actual result.
- The full text of the error message. Error messages contain only information such as the stage, the position, and error codes. They never contain passwords.
Security issues
If you find a security vulnerability, do not open a public issue. Use GitHub private vulnerability reporting. Only the developer can see the report.
- Open private vulnerability reporting (Security → Report a vulnerability in the repository).
- Describe the impact, the steps to reproduce, and the affected versions.
- If a database is needed to reproduce the issue, create one with test data only. Do not attach a real database.