You’re welcome to add our Bible text to your website or app.
However, we’re currently in the middle of a massive upgrade and proofread of our text. This includes updating most of the Christian books to conform to the Aramaic manuscripts. So our translation will be quite different in places in a few years. You may wish to wait a while before adding it to your website or app.
Our Bible text is public domain. These files are supplied with no warranty.
Our Bible text includes hyperlinks to other websites (e.g. Wikipedia), and to our translator notes and commentaries; you may remove these links if you wish, but we would prefer that you leave them intact if at all possible. Also, a link to 2001translation.org would be very much appreciated.
Download it as a plain HTML file:
We will eventualy like to have the text in a format compatible with Paratext format but it currently is not. You will have to alter it yourself into a format suitable for you.
Points to keep in mind
The 2001 Translation crosses-out fake words and passages from the Bible text using the <del> HTML tag. These must still appear crossed-out in your app or website, otherwise the reader may be misled.
We refuse to dishonestly translate passages that nobody can actually translate. For example, we leave out much of Ezekiel chapters 40-42 because translators only pretend to know what the measurement descriptions mean. So it will seem that some verse are ‘missing’ from the 2001 Translation; your app must take this into account and not crash (or whatever) when trying to load a verse that is not present.
Checking for updates
These files are automatically updated with the latest corrections to the 2001 Translation whenever our Bible text is updated. Your software can also check for updates and automatically download the latest version, if you want.
This can be done via an If-Modified-Since HTTP request to our server. If the text has been updated after the date you provided in your HTTP request (which should be the date it was last downloaded), the server will return the newly updated text; otherwise, it will return a standard “304 Not Modified” status.
Don’t crash on changes
If your application downloads a new copy of our Bible text, it must be prepared for the text being different. String lengths will change, and this might cause problems if you don’t anticipate it.
For example, let’s say that Super-Duper Bible Reader App assumes that a verse will always exist and be the same length. Now Joe Bloggs loads up the app, and highlights some words in Psalm 10:10. The app records the start and end locations of his highlight so it can display it again later...
Now, let’s say that our volunteers determine that the verse is a fake, and we remove it from the 2001 Translation. The application on Joe’s phone then downloads the latest version of the 2001, and attempts to display that verse. But it’s gone. So what will happen when the app tries to re-draw Joe’s highlight into a verse that no longer exists? Nothing? Or will the app crash?
So please make sure that future changes to the 2001 Translation text (if you choose to download updates for it) won’t cause problems in your application.
The Bible text is provided as-is, for free, with NO WARRANTY. Ensuring that it works well in your app or website and does not conflict with other scripts or systems is your responsibility. We do not and cannot accept any liability for any negative effects the text will have on your app, users, website, business, or anything else. You use the text at your own risk.