Which Bible translations can you put in your app?
4 min read · last updated 2026-11-18
Most people who start building a Bible app run into the same wall pretty quickly. You want to use the translation you read every day. Then you find out it’s copyrighted, and the rules about what you can do with it are confusing.
This guide is my attempt to make that less confusing. It’s not legal advice. If you’re building something big or commercial, talk to the publisher. But for most projects, you can figure out where you stand in about five minutes.
The short version
If you want the easy road, use a public domain translation. The Berean Standard Bible (BSB) is the one I’d point most people to. It’s a modern, readable English translation, and as of April 30, 2023, it’s been dedicated to the public domain. You can download it, change how it’s displayed, ship it in a paid app, whatever. No permission needed.
If you need a specific copyrighted translation like the ESV or NIV, you will have to go through the publisher or an API they’ve approved. Keep reading for what that means.
Public domain translations
These have no copyright restrictions at all (with one exception for the KJV, below). You can include the full text in your app.
-
The Berean Standard Bible (BSB). Modern English, public domain since 2023. Their downloads page has it in USFM, USX, plain text, spreadsheets and more.
-
The World English Bible (WEB). Also modern English and public domain. One catch: “World English Bible” is a trademark, so if you change the text you shouldn’t keep calling it that. Details are on eBible.org.
-
The King James Version (KJV). Public domain in most of the world. In the United Kingdom, though, it’s still under the Crown’s letters patent, and the rights are held by Cambridge University Press. If your app is published in the UK, read up on that before shipping the full text.
-
Older translations like the American Standard Version (1901), Young’s Literal Translation, Darby, and the Douay-Rheims. Fine to use, but they read like what they are: translations from over a hundred years ago.
Openly licensed translations
Some newer translations aren’t public domain but use open licenses like Creative Commons. These are usually fine for apps too, as long as you follow the license. That normally means giving credit, and with “ShareAlike” licenses, releasing your changes to the text under the same license.
unfoldingWord’s literal and simplified translations (the ULT and UST) are good examples. eBible.org lists the license for each translation it hosts, which is a good place to check.
Copyrighted translations
The ESV, NIV, NLT, CSB, NASB and NKJV are all copyrighted. Most of the big publishers have a rule that lets you quote a certain number of verses without asking. It’s easy to read that rule and think it covers your app. It usually doesn’t.
Take the ESV as an example, since Crossway’s terms are clear. Their permissions page lets you quote up to 500 verses without written permission, as long as you don’t quote more than half of any book, the quotes aren’t 25% or more of your whole work, and it isn’t a commentary or reference work. You also have to include their copyright notice.
That works for a blog, a sermon handout, or a devotional book. A Bible app needs the whole text, so it’s a different situation. For the ESV, that’s what the ESV API is for. It’s free for non-commercial use, which Crossway defines as no charge for access and no ads or sponsorships. It also comes with limits: no more than 500 verses (or half a book, whichever is less) per request, displayed on a page, or stored locally. There are request limits too (5,000 a day, 1,000 an hour, 60 a minute). Access is meant for people and ministries that agree with Crossway’s statement of faith.
Two more things about the ESV that catch people off guard:
-
Crossway does not allow the ESV text to be used or processed by AI systems, including for training models. If you’re building an AI Bible tool, that rules the ESV out.
-
Using the names “ESV” and “English Standard Version” beyond normal attribution needs permission, because they’re registered trademarks.
Other publishers have similar rules with their own numbers, and those numbers change sometimes. Don’t trust a blog post (including this one) for the exact limits on the NIV or NLT. Go read the publisher’s current permissions page.
What about API.Bible?
API.Bible, from the American Bible Society, is how a lot of apps get copyrighted translations legally. Public domain and openly licensed Bibles are available on every plan. The free plan also lets you use a few copyrighted translations for non-commercial projects. If your app makes money through ads, subscriptions or in-app purchases, you’ll need a paid license for each copyrighted translation you use.
There’s a more detailed comparison in the guide to Bible APIs.
A quick way to decide
Ask yourself three questions.
-
Does my app need one specific translation? If not, use the BSB or WEB and stop worrying.
-
Will my app make money in any way, including ads? If yes, copyrighted translations will cost you something, so budget for it or skip them.
-
Will the text be fed to an AI model? If yes, read each publisher’s terms carefully. The ESV says no outright.
One more thought
It’s easy to get frustrated with copyright on the Bible. Shouldn’t the Word of God be free? Most translations took years of work by a lot of scholars, though, and the fees help pay for that work and for new translations in languages that still don’t have one. You can respect that and still be glad that good public domain translations exist.
If you’re not sure about your situation, ask in the forum. Someone has probably dealt with it before.