Enables translation teams to edit Scripture on any device
About this app
Bibledit: Now translation teams can edit Scripture on any device!
Here’s a quick list of capabilities that Bibledit provides for Bible translation teams today:
• Bibledit has much of the same functionality of Paratext, but it works on any smart device — including all types of computers and tablets and phones.
• A translation team can work with Bibledit via the Internet without installing anything. We call this the Cloud version. But for most translation team members, it will be better to install Bibledit locally. This is called the Client version. The Client version saves editing changes made by each team member to his/her device, and when they have an connection, their work will automatically be saved to the Cloud.
• Many excellent and scholarly translation resources available in Bibledit. And one can view translation resources while editing a translation on the same screen.
• Bibledit can port changes in a Bible text over to a local instance of Paratext. I think many translation team leaders will want to do this. But the opposite is also possible: Bibledit can receive Bible texts from Paratext.
• Bibledit has many powerful export options. These include creating web-ready HTML files, beautifully formatted OpenOffice files (which then can easily be turned into PDF files), and Sword modules for Bible-reading applications on all smart devices.
Licensed under GPL-3.0-or-later.
What's New in v5.1.046
Imported from the F-Droid repository index.
Version history
Jun 5, 2026 · 78.9 MB · Android API 23–36 · code 181
Imported from the F-Droid repository index.
SHA-256 408091917d3a6be7f0286aabcfed2251893968f580d47cb6ae0f7feeb48b65f5
Dec 22, 2025 · 57.9 MB · Android API 22–34 · code 167
Imported from the F-Droid repository index.
SHA-256 34d5d9838273d63a4d56e13018e6a75b54e35eea61c98a9c573ae7fbf5b0ca76
Jul 17, 2024 · 59.1 MB · Android API 22–33 · code 162
Imported from the F-Droid repository index.
SHA-256 d6541b89885b6803007ab114fd8966432bb431dab9aa54553040c67e4058fe2a
Will it run on your device?
92%
- Runs on a broad range of modern Android versions.
- Multiple CPU architectures are covered.
- Aligned with the latest Android target SDK expectations.
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 org.bibledit.android 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, 5.1.027 is the last build before it. Android will not install an older version code over a newer one, so you must uninstall Bibledit 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 Bibledit, and a listing is removed when the evidence for it stops holding up.
Get Bibledit
Every source we list for org.bibledit.android 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
408091917d3a6be7f0286aabcfed2251893968f580d47cb6ae0f7feeb48b65f5
Signing certificate
5248d2b75b417e75959fb7bd1056a36d6e1d2c70c51cd94520fdd059701bc82e
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.