Store & access your files securely
About this app
DroidFS is an alternative way to use encrypted overlay file-systems on Android that uses its own internal file explorer instead of mounting volumes. This allows you to store files in encrypted vaults that other apps can't decrypt. Currently, DroidFS supports the following encrypted containers: - gocryptfs (https://github.com/rfjakob/gocryptfs): encrypts file contents and file names but doesn't hide directory structure or file sizes. - CryFS (https://github.com/cryfs/cryfs): slower, but encrypts everything and obfuscates file sizes.
Features: - Compatible with original encrypted volume implementations - Internal support for video, audio, images, text and PDF files - Built-in camera to take on-the-fly encrypted photos and videos - Ability to expose volumes to other applications - Unlocking volumes using fingerprint authentication - Volume auto-locking when the app goes in background
Permissions: Read & write access to shared storage: required to access volumes located on shared storage. Biometric/Fingerprint hardware: needed to encrypt/decrypt password hashes using a fingerprint protected key. Camera: required to take encrypted photos or videos directly from the app. Record audio: required if you want sound on videos recorded with DroidFS. Notifications: used to report file operations progress and notify about volumes kept open
All of these permissions can be denied if you don't want to use the corresponding feature.
DroidFS is free, open-source, and you can find the project's repository: - on GitHub: https://github.com/hardcore-sushi/DroidFS - on the Gitea instance of the Chapril project: https://forge.chapril.org/hardcoresushi/DroidFS
Warning ! Security is neither absolute nor definitive. DroidFS does not come with any warranty and should not be considered as an absolute safe way to store files.
Licensed under AGPL-3.0-only, by Hardcore Sushi.
What's New in v2.2.0
Imported from the F-Droid repository index.
- - Reworked UI for adding volumes
- - New unsafe feature to keep the app running as a foreground service
- - Allow choosing file export method
- - Logcat viewer (for easier debugging)
- - New turkish, chinese-simplified, and hebrew translations
- - UX improvements
Version history
Jul 30, 2024 · 9.5 MB · Android API 21–34 · code 374
Imported from the F-Droid repository index.
- - Reworked UI for adding volumes
- - New unsafe feature to keep the app running as a foreground service
- - Allow choosing file export method
- - Logcat viewer (for easier debugging)
- - New turkish, chinese-simplified, and hebrew translations
- - UX improvements
SHA-256 d5f08dd612decfd0c99f2f33640cd029dd6cf892be065ff8950b91a339db7a59
Jul 30, 2024 · 8.8 MB · Android API 21–34 · code 373
Imported from the F-Droid repository index.
SHA-256 fa5288df576b406be05a96c038422f320af6490cde00af3b1dd96bd67b8c7313
Jul 30, 2024 · 9.5 MB · Android API 21–34 · code 372
Imported from the F-Droid repository index.
SHA-256 fac8c4e94eaa1cc8ef8a7a6e799106e52d1666c74363d0039c49ca0c5b99c20e
Will it run on your device?
73%
- Runs on a broad range of modern Android versions.
- ABI coverage is focused on newer 64-bit devices.
Installation Guide
Open Settings on your Android device
Go to Security → Unknown sources (or Install unknown apps)
Enable "Allow from this source" for your browser or file manager
Open the downloaded APK file from your Downloads folder
Tap "Install" and wait for installation to complete
Launch the app from your home screen
Make sure to re-enable Unknown Sources restrictions after installation for security.
How to install this safely
How to verify the file you downloaded
Before you install anything, confirm the file is the one described here. On a computer, run shasum -a 256 your-download.apk (macOS or Linux) or certutil -hashfile your-download.apk SHA256 (Windows), then compare the output character-for-character with the SHA-256 on this page. If a single character differs, the file is not the build we recorded — delete it.
What the signing certificate proves
Every Android app is signed with a private key that only its developer holds. The fingerprint on this page is a hash of the matching public certificate, and it proves continuity rather than identity: it tells you a build came from whoever signed the earlier ones. Android enforces this at install time — if a package claiming to be sushi.hardcore.droidfs is signed with a different key, the system will refuse to install it over your existing copy. A fingerprint that changes between releases is worth pausing on, because a repackaged app that has been modified by someone else cannot keep the original signature.
How to roll back to an earlier version
If the current release misbehaves, 2.2.0 is the last build before it. Android will not install an older version code over a newer one, so you must uninstall DroidFS first — which clears its local data unless you have a backup. Reinstall the older APK only if its signing fingerprint matches the build you already trust, and check the API range: an older release may target an Android version your device has moved past.
Why we list sources instead of hosting everything
The official store channel is almost always the right choice: it updates automatically and carries the publisher's own distribution guarantees. A direct APK is useful when a device has no store access, when a rollout has not reached your region, or when you need a specific version — and only when the publisher has authorized that copy. APKBrowse does not list pirated, cracked, or unauthorized rebuilds of DroidFS, and a listing is removed when the evidence for it stops holding up.
Get DroidFS
Every source we list for sushi.hardcore.droidfs is legality-reviewed. Pirated or cracked builds are never offered.
Other sources
F-Droid listing
officialF-Droid builds this app from source and signs it. This is its official listing, with older builds and full release notes.
Source code
verified publisherThe upstream repository this build is compiled from.
We check legality and signature continuity, but device behaviour still varies. Install at your own discretion.
App Information
Security Verification
We record provenance; we do not run malware scans. Verify the hash yourself before installing.
SHA-256 Hash
d5f08dd612decfd0c99f2f33640cd029dd6cf892be065ff8950b91a339db7a59
Signing certificate
1b8934d493310a342b29bbe03bc205e0d3d58659d1abaf179577d947452499d6
Permissions Required
Previous Versions
The signing certificate fingerprint for this release is on record, so a build that does not match it did not come from this publisher.
Report a problem with this listing
A listing is only as good as its corrections. If a source is broken, a signature looks wrong, or this app should not be here, tell the moderation team.