- Starting price
- Free
- Free tier
- Yes
- Platforms
- Web · Progressive web app · Offline-capable browser install
- Developer
- Bible in One Scroll / jungrok5
- Launched
- 2026
- Updated
- Aug 9, 2026
The verdict
Bible in One Scroll is an unusually ambitious free outreach page: thirteen memorable scenes, strong mobile design, hundreds of localized editions, transparent source code, offline support, maps, QR sharing and a clear invitation to continue reading. It is not “the Bible in five minutes.” It is an evangelical redemptive-historical summary that selects, compresses and interprets the Bible, followed by apologetics and an invitation to faith. Share it when that framing fits, verify every localized edition, and pair it with complete Scripture and human conversation.
Try Bible in One Scroll ↗Opens one-scroll-bible.com
Bible in One Scroll is a free mobile-first website that condenses the Bible’s storyline into one continuous page. Thirteen scenes move from Creation, the Fall, the Patriarchs, Exodus, Conquest and Judges, the United Kingdom, the Divided Kingdom, Exile, Return, the Silent Years, Jesus, the Church and final Restoration. Each scene uses a repeated visual pattern: principal people, key events, a selected verse, a “Christ thread,” a short “Love that won’t quit” theme and a misconception to correct. The English page then presents themes such as sin, law, grace, justification by faith, kingdom and gospel, answers common objections, offers a prayer to receive Christ and proposes next steps.
The project calls this an approximately five-minute overview and publishes versions in more than 210 languages. The live English page declared 215 language alternatives when reviewed. Language auto-detection, a visible switcher, right-to-left handling, theme controls, offline-capable service-worker files, a web-app manifest, QR sharing and lightweight static files make the resource easy to open on a phone and send to someone else. Companion material includes overview maps and timelines for the Old Testament story, Jesus and Paul. No registration or email address is required to read.
The “one scroll” is an editorial work, not a newly translated miniature Bible. It uses selected Scripture quotations alongside original connective prose, summaries, theological claims, apologetics, questions, illustrations and application. Its structure is intentionally evangelical and redemptive-historical, with Reformed vocabulary especially visible in the English gospel explanation. It follows a 66-book Protestant canon and reads the whole story toward Christ. That may be exactly the lens a church or evangelist wants to share; it should be named rather than mistaken for a tradition-neutral synopsis or an academic consensus about every passage.
The source repository is unusually open for a new outreach site. Code is published under MIT, most project-authored content under Creative Commons Attribution 4.0, and English prose is excluded from that content grant where ESV quotation rights require separate treatment. Scripture quotations retain the rights and notices of their publishers. The README documents a multilingual production workflow involving AI-generated prose translation, back-translation, automated checks, review and several Scripture-source tiers. Those are project claims and process descriptions, not independent certification that every sentence in every language has been reviewed by a qualified native speaker and theologian.
Our 4.3 score is an editorial researched rating. We inspected the public English edition, source repository, licensing and shipped page behavior; we did not commission native review of 215 editions, validate every Scripture license, reproduce the complete generation pipeline, assess every theological assertion or conduct an accessibility and security audit. Repository metadata showed a remarkably active young project—hundreds of commits within weeks—but activity is not the same as durable governance. The page also loads Google Analytics 4 before offering a visible consent choice and has no working public privacy or terms route, a significant trust gap for a site deliberately distributed across jurisdictions.
✓ The good
- Clear narrative architecture - thirteen repeated scenes make a long and complex biblical timeline easier to remember
- Extraordinary language reach - more than 210 localized routes pursue access far beyond a typical English-first microsite
- No account or paywall - readers can open, scroll, install and share without registering
- Mobile and low-friction delivery - static files, progressive-web-app support, offline caching and QR links suit field sharing
- Open development - source, issues, commit history, contribution guidance and multi-part licensing are publicly inspectable
- Visible bridge to complete reading - the project presents next steps instead of claiming the summary is sufficient
- Consistent teaching aids - people, events, verses, maps, misconceptions and recurring themes give every scene a familiar shape
- Translation workflow is documented - the project discloses its use of AI, back-translation, checks and source tiers instead of hiding automation
✗ Watch out
- The title can overpromise - a short Christian summary is not the Bible and cannot preserve its full books, genres, voices or tensions
- One strong theological lens - evangelical and Reformed redemptive-historical conclusions are woven into the overview and invitation
- AI-scaled localization is difficult to verify - language count does not establish native, biblical or theological accuracy
- Apologetics claims are compressed - manuscript, authorship, archaeology and unity arguments need sources and careful qualification
- No privacy notice - Google Analytics loads on the site without a functioning public explanation of data, retention or user rights
- No visible consent before analytics - cross-jurisdiction sharing creates privacy obligations a static outreach page cannot ignore
- Very young project - rapid commits show energy but not long-term maintenance, independent review or institutional continuity
- Licensing is layered - code, original content, English material, Bible quotations and third-party media cannot all be reused under one license
Best for
- Churches and individuals sharing a concise evangelical overview in a recipient’s preferred language
- First-time readers who need a chronological scaffold before opening complete biblical books
- Mobile outreach where a no-account, lightweight and offline-capable page is helpful
- Teachers who will identify its framework and use each scene as a doorway into the whole passage
- Translators and developers willing to inspect, improve and document an open multilingual project
Avoid if
- You need a complete Bible, formal translation, academic introduction or tradition-neutral survey
- You cannot have Google Analytics load before an informed regional consent decision
- You need independently certified native and theological review for a particular language today
- Your audience would reasonably mistake selected quotations and commentary for a complete biblical text
- You need a mature organization with published safeguarding, accessibility, privacy and editorial governance
What Bible in One Scroll is
The main page is a guided theological narrative. It selects an arc, assigns each era one compact scene, connects people and promises, identifies recurring love and rebellion, points each scene toward Christ, corrects a selected misconception and ends with a gospel presentation and response. That makes it closer to a multilingual evangelistic tract, illustrated biblical-theology outline and mobile lesson combined than to a Bible-reading application.
Technically, it is a static, dependency-light website designed to be cloned, translated and hosted easily. Language files, SEO metadata, alternate-language links, structured data, a language selector, theme state, local browser storage, maps, QR sharing and a service worker are handled without an account backend. The approach is fast and resilient, though Google Analytics introduces a third-party network and privacy dependency.
Why thirteen scenes can unlock the story—and rewrite it by compression
A new reader often knows isolated names without knowing where they belong. Repeating the same visual questions across Creation, Patriarchs, Exodus, Kingdom, Exile, Jesus and Church creates a mental timeline. The transitions help explain why later biblical authors refer back to creation, covenant, deliverance, David, exile and promise. A five-minute scaffold can reduce intimidation and make a first complete book easier to locate.
Compression is interpretation. Choosing one verse, one misconception and one Christ connection for an era pushes other themes out of view. Wisdom literature, lament, law, prophetic dispute, poetry, women’s narratives, contested chronologies and the distinct arguments of New Testament writers cannot fit comfortably into thirteen cards. The page should be introduced as this project’s guided summary. After every scene, open the named books and ask what the short arc omitted, simplified or connected by theological inference.
The thirteen-scene scroll: memorable chronology with a declared gospel destination
The scroll moves from creation through Israel’s ancestors, exodus, land, judges, monarchy, division, exile, return and the intertestamental interval into Jesus, the early Church and promised restoration. People, events and selected verses anchor each period. The “Christ thread” and recurring love theme make the project’s interpretive center explicit, while misconception boxes challenge simplified popular ideas. Maps and timelines add geographic and chronological orientation.
This structure is strongest when the teacher says where observation ends and synthesis begins. “Jesus was present in all 39 Old Testament books,” “Israel equals me,” a particular law-and-grace formulation or a scene’s chosen fulfillment can carry meanings beyond a quoted verse. Some readers will share the framework; others will parse those relationships differently. Linking each claim to full passages, commentary and an editorial note would let learners examine the reasoning rather than receiving a smooth story as self-evident.
More than 210 languages: transparent automation needs visible human status
The repository documents an ambitious localization system. It distinguishes Scripture sources by availability and licensing, drawing where possible on published translations and resources such as YouVersion-linked editions, eBible, Digital Bible Library or API.Bible materials, unfoldingWord resources and Open Bible Stories, with bridge-language handling where a complete local source is unavailable. Project-authored prose is translated with AI assistance, back-translated, checked and reviewed according to the published workflow. The live site exposes 215 language alternatives.
At this scale, every locale needs a public status card: language and script, Bible edition and rights holder, machine-translation involvement, native reviewer name or organization, theological reviewer, review date, completeness, unresolved issues and correction history. Character-by-character Scripture checks can detect drift from a selected digital source; they cannot prove that the source is appropriate, the surrounding prose is idiomatic or a theological term communicates locally. Defer a language rather than presenting unreviewed confidence merely to preserve a count.
PWA, maps and open source: excellent distribution with unfinished trust infrastructure
A small static package can load quickly, cache for later reading, install from the browser, switch language and theme, and share through a link or QR code. The project avoids account friction and exposes its implementation on GitHub, where contributors can inspect changes or report a correction. MIT code and CC BY content terms encourage adaptation, while the custom license text appropriately separates Scripture and English ESV constraints from the project’s own work.
The browser experience still creates data. The live page loads Google Analytics 4 through Google Tag Manager infrastructure and records language or interaction events, while local storage retains language and theme and the service worker stores files on the device. The expected privacy and terms pages returned no useful notice during research, and no consent choice appeared before analytics. A no-account product can be privacy-respecting, but it must disclose the remaining processing, honor regional consent requirements and provide deletion or opt-out instructions.
Pricing
Bible in One Scroll
Free
Every public language route, the main thirteen-scene scroll, maps and installable progressive-web-app experience are available without an account, subscription or donation gate. The project does not publish a premium tier, advertising upgrade or institutional license. Normal internet and device costs remain the user’s responsibility.
Offline and sharing use
Free after access
The static site includes service-worker and manifest support intended to cache content and behave like an installed web app. QR and ordinary links make distribution simple. Test the exact route and all required media on the target browser before relying on it without a connection; cached behavior can vary after updates or storage clearing.
Reuse and adaptation
Open licenses with important exceptions
Code is MIT licensed and most original non-English project content is offered under CC BY 4.0. English content containing ESV material is excluded from that broad content license, and every Bible quotation remains subject to its publisher’s permission and notice. Images, fonts, maps and other third-party assets may carry separate terms. Review the repository license before republishing.
There is no financial barrier. A recipient can follow a link, switch language and read without creating an account. That makes Bible in One Scroll materially easier to distribute than a course platform, subscription app or printed shipment. It also means the project has no obvious paid support contract or institutional guarantee.
Offline support can reduce data cost after the first visit. A ministry planning field use should preload and test the exact language on the exact browser, then confirm that quotations, images, maps, navigation and update behavior work in airplane mode. Progressive web apps depend on browser storage, and an operating system may evict cached files.
Open licensing lowers development cost but does not mean “anything on the page is free to copy.” MIT applies to software. CC BY 4.0 applies to the project’s eligible original content with attribution. English content is carved out where necessary, and Bible translations are governed by their publishers. Anyone printing, remixing or bundling an edition must audit every content layer and preserve required notices.
The hidden institutional cost is review. A church distributing ten languages needs ten competent reviewers, not merely one person who likes the English version. Reviewers should compare Scripture quotations to the named edition, read the prose naturally, identify doctrinal assumptions, test links and check cultural illustrations. Publish their names and dates so recipients can assess the edition.
Long-term continuity also has a cost. The repository was created in June 2026 and accumulated hundreds of commits rapidly. That pace is impressive, but a project should document maintainers, release cadence, backups, domain succession, security contact and the process for urgent translation corrections. A static fork can preserve access if the main site ends, provided licenses and update responsibility are understood.
Where Bible in One Scroll falls behind
The project needs a durable privacy notice before broad international promotion. It should name Google Analytics and any tag-management or hosting processors, explain event fields, IP handling, legal basis, retention, international transfer, cookies or storage, regional consent, opt-out and contact rights. A dead privacy route is not adequate for 200-plus localized entry pages.
The consent experience does not match the site’s reach. Google Analytics was requested without a visible choice before loading. Requirements differ by jurisdiction and configuration, but the conservative approach is to keep nonessential analytics off until the visitor has an informed option where consent is required. The project can also use aggregate privacy-preserving metrics or no analytics.
The title and five-minute promise need a constant qualification. A person has not read “the Bible” after reading the scroll; the person has read selected verses and a theological summary. Label every component as Scripture quotation, project summary, interpretation, apologetics or invitation and place a direct full-chapter link beside each selected verse.
The apologetics section compresses evidence too aggressively. “Sixty-six books,” “about forty authors” and “1,500 years” are common Protestant overview formulas rather than precision measures accepted without qualification. Saying writers worked separately and were unaware of one another overstates the evidence because later authors knowingly engage earlier Scripture and some texts have complex compositional histories.
The Dead Sea Scrolls do not establish that the entire Bible remained “almost letter for letter” unchanged for a thousand years. The manuscript evidence includes substantial agreement and meaningful variants across textual traditions. Archaeology can illuminate or corroborate people, places and practices; examples do not by themselves prove every historical or theological claim. Link scholarly sources and match wording to the actual evidential scope.
Language quality is asserted more readily than demonstrated. A documented AI, back-translation and native-review workflow is a strong start, but the public page needs edition-level badges and reviewer records. “AI translated and native reviewed” should never be copied to every locale unless that exact edition completed the defined stage.
Accessibility evidence is missing. A long decorative scroll, small mobile controls, maps, animated transitions, color themes and hundreds of language scripts require keyboard, screen-reader, zoom, contrast, reduced-motion, font fallback and right-to-left testing. Publish a statement, known limitations and a simple text-only alternative.
Governance is young and person-dependent. GitHub provides transparency, but readers need named editorial, translation, privacy and safeguarding contacts; a correction policy; release notes; conflict resolution; and a plan if the primary maintainer leaves. High commit count cannot substitute for accountability across hundreds of languages.
Bible in One Scroll vs. BibleProject vs. Open Bible Stories
BibleProject explains biblical books and themes through polished videos, podcasts, classes and articles. It offers far more literary and historical context, although its own biblical-theology perspective also shapes the narrative. Bible in One Scroll is dramatically faster and available in more language routes; BibleProject is the richer next step when a reader can access a supported language and has time to learn.
Open Bible Stories is a fifty-story visual overview created for open translation and reuse. Its CC-licensed structure and mature translation ecosystem are especially valuable where local teams need adaptable story material. Bible in One Scroll uses only thirteen scenes, adds a compact evangelistic and apologetic close, and provides a slick single-page PWA. Open Bible Stories offers finer narrative granularity and an established open-source translation foundation.
GodTools and the JESUS Film app are mature evangelism resources with multiple presentations, languages, media and organizational support. Their message structures are also editorial and should be matched to the audience. Bible in One Scroll offers a wider whole-story scaffold and transparent code; the larger ministries offer longer operational history, training and distribution systems.
A complete Bible in a reader’s language remains the destination. A full translation preserves books, sequence and genres and gives the reader more than the editor’s selected route. Bible in One Scroll can answer “Where does this story fit?” It should immediately answer the next question—“Where can I read the whole thing?”—with a lawful, reviewed complete edition and local people who can listen.
The bottom line
Bible in One Scroll gets many difficult product choices right. It is free, fast, accountless, mobile-first, shareable, installable, open source and explicit about its translation automation and licenses. Thirteen repeated scenes can give a first-time reader a usable timeline, and the project repeatedly points beyond itself. Producing hundreds of language routes in weeks is technically remarkable. The same scale magnifies editorial responsibility. This is selected Scripture inside an evangelical redemptive-historical argument, not a five-minute Bible. Its apologetics sometimes turns common summaries into claims stronger than the evidence warrants; its localization quality needs edition-specific human provenance; and its Google Analytics deployment lacks the privacy notice and consent structure an international outreach project should consider foundational. Use it as a conversation-opening tract when its theological frame fits the sender and recipient. Name that frame, check the exact language, distinguish Bible quotation from project prose, qualify historical evidence and link every scene to complete books. If the team adds fixed privacy and terms pages, consent-aware analytics, reviewer badges, accessibility testing, sourced apologetics and a public correction ledger, this could become an exemplary open multilingual first-step resource.
Alternatives to Bible in One Scroll
BibleProjectA deeper visual and audio introduction to biblical books, themes, literary design and the unified story.Open Bible StoriesFifty openly licensed Bible stories built for community translation, teaching and visual distribution.
GodToolsA mature multilingual evangelism app with several guided conversation tools and organizational support.JESUS Film ProjectA large multilingual video library centered on Jesus, with stronger media and distribution infrastructure.
YouVersionA free destination for complete Bible reading, audio, plans and lawful translations in many languages.Frequently asked questions
Is Bible in One Scroll the full Bible?
No. It is a five-minute-claim overview made from thirteen editorial scenes, selected Bible quotations, connective prose, theological interpretation, apologetics and an invitation to faith. It can provide a timeline, but readers should continue into complete biblical books in a named translation.
What theological perspective does Bible in One Scroll use?
The English edition uses an evangelical redemptive-historical framework with recognizable Reformed language, a 66-book Protestant canon, recurring Christ-centered connections and a direct conversion invitation. That is a legitimate declared ministry perspective, not a neutral summary of every Christian or academic interpretation.
How many languages does Bible in One Scroll support?
The project advertises more than 210 languages, and the live page exposed 215 alternate-language declarations during research. Availability is not proof of equal review. For any specific edition, ask which Bible translation it quotes, whether AI translated the prose, who reviewed it, when, and what unresolved issues remain.
Does Bible in One Scroll use artificial intelligence?
Its repository documents AI-assisted translation of project-authored prose, back-translation, automated checks and human review. Scripture quotation sources are handled separately. The site should publish the completed review status per locale; a documented general workflow does not prove that every language passed every step.
Is Bible in One Scroll free and open source?
Reading is free and the code repository uses the MIT license. Most eligible original content is offered under CC BY 4.0, but English ESV-related content is excluded from that broad grant and Scripture translations retain publisher rights. Third-party images, maps or fonts can also have separate terms. Check the repository license before reuse.
Does Bible in One Scroll work offline?
The site includes a web-app manifest and service worker intended to support browser installation and cached reading. Offline results depend on browser, storage and whether the needed route and assets were previously loaded. Test the exact language in airplane mode before depending on it in the field.
What information does Bible in One Scroll collect?
No account is required, but the live site loads Google Analytics 4 and uses local browser storage for settings plus a service worker for cached files. A working public privacy notice and visible pre-analytics consent choice were not available during research. Avoid assuming “no account” means “no data,” and the publisher should document and minimize the analytics flow.
Sources & further reading
More Teaching & Theology Websites
BibleProjectA nonprofit studio that turned the entire Bible into animated explainers, free seminary-grade courses, and a deep-dive theology podcast - and somehow gave it all away.
Christian Classics Ethereal LibraryThe Christian Classics Ethereal Library is possibly the oldest Christian site on the internet, and it is still the single best free source for the public-domain canon - from Augustine to Spurgeon, with the entire 38-volume Ante-Nicene and Nicene-and-Post-Nicene Fathers in the middle.
Christian History InstituteThe quiet workhorse of popular church history publishing for forty years - and almost everything they have ever printed is sitting online for free.
Faith Comes By HearingA 50-year-old mission organization that has recorded the Scriptures in more languages than any other group on earth - and the parent ministry behind Bible.is.
Renewing Your MindLigonier Ministries’ flagship daily teaching broadcast, anchored in R.C. Sproul’s decades-deep archive and continued by today’s teaching fellows - the closest thing Reformed listeners have to a daily seminary classroom on the radio.
Desiring GodJohn Piper's ministry, four decades deep, with every book free as a PDF and a podcast archive nobody else can match - and a Reformed Baptist lens you should know going in.