Main features
- Opens KeePass 2.x and KeePassXC databases
- Built-in sync over WebDAV, SFTP and FTPS
- Connectors for Google Drive, OneDrive, Dropbox, pCloud and Nextcloud
- Offline flavor without the internet permission
- Local cache for opening cloud databases offline
- Dedicated keyboard that fills fields without the clipboard
- Android autofill service
- TOTP codes and YubiKey support
- Create an entry straight from a URL shared by the browser
What Keepass2Android does
Keepass2Android is an Android app for KeePass databases, written as a companion to KeePass 2 or KeePassXC on a computer. Its author’s priority is keeping one .kdbx file reliably in sync between the phone and the PC, and that is the main difference from KeePassDX. Instead of relying only on Android’s file picker, the regular version can read and write the file itself over WebDAV, SFTP and FTPS, and through Google Drive, OneDrive, Dropbox, pCloud, Nextcloud and other services. Files opened from a server are cached on the phone, so the database still opens without a connection.
For entering passwords, the wiki recommends the Keepass2Android keyboard. When you pick an entry, a notification lets you switch to this keyboard and type the username or password into any field, which keeps the data off the clipboard. An Android autofill service, clipboard copying and a “share URL from the browser” workflow are also available. The app generates TOTP codes and supports YubiKey as a second factor.
Security and encryption
The database is an encrypted KeePass file protected by a master password, optionally combined with a second factor. The documentation is direct about what that means: nobody, the author included, can open the file without the master key, and if you forget it the data is lost.
Network access is the main security trade-off, and the project addresses it with two editions. The regular app needs the internet permission for its built-in connectors. Keepass2Android Offline has no internet permission and can only reach files through the Android file browser, so even a compromised build could not send data anywhere by itself. No external security audit is documented.
Self-hosting Keepass2Android
There is no server to run. Both editions are on Google Play, and signed APKs for several architectures are attached to the GitHub releases. Where you keep the file is up to you. The wiki compares three setups: a cloud drive (simplest, but on servers you do not control), a personal SFTP or file server on your home network (private, but only reachable at home unless you expose it), and a phone-only database (simple, but hard to back up). It also warns that a synced copy is not a backup, since a damaged file syncs to every device.
Hosted version
None. Keepass2Android uses the storage you choose.
Limitations
The app is Android only, and the author describes the wiki documentation as incomplete. Some cloud apps reached through Android’s Storage Access Framework break the link to the file or create “conflicted” copies, which is why the wiki prefers the built-in connectors. Sharing passwords with other people means sharing a whole database file; there are no per-user permissions.
Who it suits
Keepass2Android suits Android users who keep a KeePass database on a PC and want the phone to sync with it directly, especially over WebDAV or SFTP to their own server. Users who want a password app with no network access at all can install the Offline edition. On iPhone, the closest equivalent in this directory is KeePassium.
Technical details
Built with
- C#
- .NET
- Java
GitHub topics
- android
- keepass
- keepass2
- keepass2android
- password-manager
Reviewed by the OpenSourcePicks editors from the project's repository and documentation. Something out of date? Tell us.