Text verification
How you can check this Bible hasn't been changed
ScriptureLeaf does not ask you to trust a copyright notice or a promise. It publishes the evidence needed to check the text.
The ScriptureLeaf reader build matches the frozen official BSB source for 3rd Printing, retrieved on 6 September 2026.
- Books
- 66
- Chapters
- 1,189
- Verse-number slots
- 31,102
- Reader differences
- 0
4d4b312e8e24691f749584c77e75c6a5070056144add3adde8f727a1cfa212c81. A fingerprint for text
SHA-256 is a standard mathematical process that turns text into a 64-character fingerprint. The same input always gives the same fingerprint. Change even one character and the result changes dramatically.
There is no feasible known way to deliberately change the text and make it keep the same SHA-256 fingerprint. That makes the fingerprint useful as a tamper check.
2. A named source and date
“The BSB” is not specific enough for verification. ScriptureLeaf records the exact official files, their addresses, their byte sizes, the date they were frozen and the fingerprint of each raw download.
The reader's canonical text is built from bsb_tables.tsv from the official BSB downloads, labelled 3rd Printing.
- bsb.txt4,331,393 bytes
2ac3af1de52d4e68261cba91d85c320b7eadc6560e830d99e591767b8ff5ca96 - bsb.xlsx2,395,629 bytes
6152506a21bc3dd637248474254cc19cc58841de98f98137eec68cea6a9b38a2 - bsb_usfm.zip1,598,046 bytes
a91f7b674487981410a9235d8ca8702507b3e1ec39c1f143a0952fde675eed0a - bsb_tables.tsv85,525,373 bytes
09bbee6f9fe4fa22b5df28e8a9ffa99bf9c33435f4eb8c47c2dc221d855d35cb
Different official file formats have different raw-file fingerprints because a spreadsheet, a text file and a USFM archive are different byte sequences. A raw-file mismatch is not, by itself, evidence that Bible wording differs.
3. Separate copies, with their family tree shown
We also compare the text with copies published elsewhere. We do not call every mirror “independent”. The witness report records where each copy came from, whether its lineage is known, and every difference the code finds.
2 configured copies were compared in this release. 0 currently have lineage strong enough to be labelled independently derived. Unknown does not mean bad; it means we will not claim more than the evidence shows.
And you can check us
Drop an official BSB download into the checker. Your browser calculates its fingerprint on your device. The file itself is not uploaded to ScriptureLeaf.
What exactly is being claimed?
This release proves that the generated ScriptureLeaf reader corpus matches the frozen official source used by the build. It does not claim that SHA-256 proves which translation is theologically best, or that every third-party copy has independent origins. Those are different questions.
Older Bibles were kept honest by copying and comparing. This is the same instinct with reproducible arithmetic.