- Starting price
- Free
- Free tier
- Yes
- Platforms
- Web browser
- Developer
- Jon Winsley
- Launched
- 2023
- Updated
- Aug 9, 2026
The verdict
Armorer is excellent at one deliberately narrow job: open the KJV, move through it continuously, search the text and share a precise verse without an account, feed or commercial overlay. Its static architecture and public source are meaningful trust advantages. It is not a complete study platform, and the lack of alternate translations, notes, audio, saved state, documented accessibility and a standard open-source license keeps it from replacing a mature Bible app.
Try Armorer ↗Opens armorer.io
Armorer is a free minimalist web reader for the King James Version of the Bible, created by independent developer Jon Winsley. Open a passage and the page behaves more like a continuous book than a sequence of separate chapter screens: reaching an edge loads the preceding or following chapter, and the browser address changes with the reading position. A table of contents moves among the 66 books and chapters, reference links can point to individual verses, and full-text keyword search runs in the browser.
The site is deliberately small. There is no account, devotional plan, highlight collection, social feed, audio player, commentary layer, subscription, advertising pitch or translation selector. The project is generated with Eleventy and uses Alpine.js for interactive behavior, then is hosted as a static site on GitHub Pages. The KJV data is credited to the SWORD Project. Search is handled in a web worker after its index loads, which keeps query processing on the device and helps the reading page remain responsive.
Winsley introduced the reader in January 2023 as a personal effort to make Scripture pleasant to read online. The public repository remains available and showed 112 commits at the time of research, with recent activity in 2026. That history is encouraging for a one-person project, but stars, forks and repository activity are not the same as a service guarantee. The code is distributed under the Common Grace License 1.0. Its terms broadly allow copying, modification, distribution and incorporation while requiring the license to accompany copies, but it is categorized by GitHub as “Other” rather than carrying a familiar SPDX or OSI-approved identifier.
The 4.4 score is our editorial judgment based on the live reader, creator note, repository and license; websites do not have an App Store rating to import. We did not conduct a formal accessibility audit, inspect every network request over time, verify the entire biblical text against another KJV edition or test every browser. A static architecture with client-side search appears privacy-friendlier than an account-based service, but it is not accurate to promise zero collection: GitHub Pages and network infrastructure can retain ordinary request information, and Armorer does not publish a standalone privacy notice explaining logs or third-party processing.
✓ The good
- Immediate reading - no account, onboarding, payment prompt or app installation stands between a visitor and the text
- Continuous chapter loading - scrolling can preserve narrative momentum while the URL follows the current location
- Stable reference links - individual verse anchors make precise sharing and citation practical
- On-device full-text search - a browser worker searches the downloaded index without sending each query to a search server
- Publicly inspectable code - readers and developers can examine how the site is built and report problems
- Static hosting reduces complexity - there is no visible account database, recommendation profile or personalized ad system
- Focused typography and dark design - the interface gives the biblical text visual priority
- Free without an upsell - Armorer does not use the reader as a funnel into a paid study library
✗ Watch out
- KJV only - readers cannot compare a modern translation or switch to a different canon or language
- No study layer - there are no notes, cross-references, dictionaries, maps, original-language tools or reading context
- No saved reader state - highlights, notes, bookmarks, plans and cross-device progress are outside the product
- Search has an initial payload - the roughly 4.5 MB uncompressed index still costs data and time on a slow connection
- Accessibility is undocumented - infinite scroll, dynamic URL changes and dark presentation need formal assistive-technology testing
- No standalone privacy or terms page - static design is reassuring but hosting logs and responsibilities remain unexplained
- One-maintainer continuity - a personal project can change or disappear without a commercial support commitment
- Nonstandard source license - the Common Grace License is permissive in practical language but not a familiar OSI license
Best for
- KJV readers who want the quickest possible route to a clean passage
- Writers and teachers sharing stable links to individual verses
- Privacy-conscious visitors who prefer no account and local keyword search
- Developers studying a compact static Bible-reader implementation
- People who already have separate tools for notes, audio and detailed study
Avoid if
- You need NIV, ESV, NRSV, NLT, a Catholic canon or another language
- You want commentary, interlinear tools, cross-references, maps or study notes
- You rely on synchronized highlights, reading plans, bookmarks or listening progress
- You need documented WCAG conformance or institutional technical support
- You require software under a standard OSI-approved open-source license
What Armorer is
Armorer is a statically generated KJV Bible website. Each book and chapter has an address, each verse has an anchor, and JavaScript adds continuous loading, navigation and search. As the reader moves across chapter boundaries, the adjacent chapter is inserted and the URL updates. A table of contents offers direct navigation. The full-text index downloads after the initial page and runs in a separate browser worker so search does not require a server query for every term.
It is intentionally not a complete Bible-study account. There is no profile, library, plan, community or content recommendation system. That constraint gives the site its speed and calm, while leaving interpretation, comparison and long-term organization to other tools. The KJV source comes through the SWORD Project, and the application code is public on GitHub under the project’s own Common Grace License.
Why a reader may prefer Armorer to a feature-heavy Bible portal
Large Bible sites solve many jobs at once: translation licensing, audio, commentary, devotionals, advertisements, accounts and recommendations. Their reading screen often inherits that complexity. Armorer treats uncomplicated reading as a complete job. A person follows a link, sees the text, scrolls through the next chapter and shares the exact location. There is no login modal asking the visitor to build a library before reading one verse.
The static, inspectable design also narrows data exposure. Search terms are processed locally after the index arrives, and no user profile is required to remember preferences. That does not make the site invisible to hosting infrastructure, and privacy should still be documented. The tradeoff is explicit: the product knows less about the reader because it does less for the reader. For someone who wants focused KJV reading, that is an advantage. For someone building a study archive, it is a reason to choose another tool.
Infinite chapter scrolling: a continuous book with addressable locations
Armorer loads the next or previous chapter as the reader approaches the boundary, reducing the repeated tap-and-wait rhythm of page-by-page sites. The browser URL updates to reflect the current passage, so continuous movement does not discard a shareable address. A book-and-chapter contents control provides the deliberate alternative to scrolling. Individual verse anchors support precise deep links, useful for a handout, message or personal bookmark.
Continuous reading can help narrative and argument remain connected across a chapter division, which was added long after the biblical texts were composed. It can also disorient keyboard and screen-reader users if focus, headings, announcements and browser history are not managed carefully. Dynamic address changes may fill history unexpectedly or make the Back button surprising. Readers should verify their preferred navigation behavior, and the project would benefit from publishing tests for focus restoration, landmarks, skip links and reduced-motion settings.
Reference and keyword search: simple discovery that stays in the browser
A visitor can move directly by book and chapter, link to a verse or search the KJV for a word or phrase. The search index is loaded after the main page and queried in a web worker, separating computation from the visible interface. The creator reported an index around 4.5 MB uncompressed and about 1.4 MB compressed. Once present, the browser can search without transmitting every spiritual or pastoral query to an application search endpoint.
Keyword search is a locator, not an interpretation engine. KJV spelling and vocabulary can hide a concept expressed with a different term, and a result list can detach a sentence from genre, speaker and argument. Search several related forms, open surrounding chapters and compare context in an appropriate study tool. On metered or low-bandwidth service, the one-time index download is material; a server search might transfer less data per visit but disclose each query. Armorer chooses local privacy and responsiveness after download over the smallest initial payload.
Static architecture and public source: low complexity with real boundaries
The site is built with Eleventy, enhanced with Alpine.js and served through GitHub Pages. Its repository exposes templates, content-processing code, styles and history for review. Static delivery removes entire categories of account and database failure and makes the reader inexpensive to host. The SWORD Project is credited as the KJV data source, connecting the text to a long-running Bible-software ecosystem rather than an unexplained copy.
Public source does not automatically establish security, accessibility or licensing compatibility. The Common Grace License grants broad practical permissions and includes a warranty disclaimer, but GitHub identifies it as an “Other” license and it is not a standard OSI choice. External contributors and institutional adopters may prefer MIT, Apache-2.0 or another familiar license with established tooling and interpretation. Static hosting also produces network requests and may keep logs. A brief privacy notice, dependency policy and documented release process would make the project’s trust model much easier to evaluate.
Pricing
Armorer web reader
Free
Every visible reading and search feature is available without payment, registration or a trial. The site does not advertise a premium tier, donation gate, storage allowance or commercial upgrade. A visitor needs only a current browser and a connection to load the pages and search index.
Account and synchronization
Not offered
There is no paid cloud account because there is no user account system in the product. That avoids a recurring fee and identity profile, but it also means Armorer cannot synchronize highlights, notes, bookmarks or reading progress. Browser history and ordinary bookmarks can preserve links, subject to the user’s own device and browser settings.
Source reuse
License terms apply
The repository can be inspected and the Common Grace License 1.0 grants broad rights to publish, distribute, copy, modify and incorporate the software while requiring inclusion of the license. The license is not presented with a standard OSI or SPDX identifier, and Bible text rights may be a separate layer. Organizations should have counsel interpret both code and content permissions before redistribution.
Armorer is free in the uncomplicated sense: there is no checkout, account tier or feature lock. Hosting a public static reader is inexpensive compared with operating profiles, synchronization and licensed content services, and the project passes that simplicity to the reader.
The absent subscription comes with absent cloud features. Someone who wants notes, highlights, bookmarks and cross-device progress will need a browser, a separate notes system or a different Bible app. Those alternatives can cost money or require an account. Do not evaluate Armorer against a paid study suite as if both promise the same job.
Data cost is small for most broadband users but relevant in low-connectivity settings. Reading pages and the compressed search index must still be downloaded. Repeated visits may benefit from browser caching, which depends on site and browser behavior. There is no documented offline installation or downloadable application bundle.
Developers considering reuse should treat license review as part of the cost. The project license is generous in ordinary language but nonstandard, and the KJV dataset’s provenance and redistribution conditions should be checked separately. Public availability is not a substitute for confirming every component’s terms.
Where Armorer falls behind
The single-translation boundary is the largest functional limit. The King James Version is historically important and preferred by many readers, but its early modern English can be difficult, and textual or translation questions often benefit from comparison. Armorer offers no alternate English edition, source language, translation notes or canon choice. Adding copyrighted translations would also change the project’s licensing and economics substantially.
Study features are absent by design. There are no cross-references, introductions, footnotes, dictionaries, maps, commentaries, original-language links or parallel panes. A reader can search the exact KJV vocabulary but cannot easily explore the historical setting or see why translations differ. That keeps the interface clean while limiting the page’s usefulness for preparation and close study.
Personal organization is also outside scope. The service does not store highlights, notes, bookmarks, prayer reflections, plan completion or audio position. Browser bookmarks can preserve a verse URL and a separate note app can hold observations, but the workflow is manual. Users should not expect a future account simply because most Bible platforms include one.
Accessibility is plausible but not demonstrated. Semantic static HTML can form a strong base, yet infinite insertion, current-position detection, dynamically updated URLs, dark contrast, small anchor targets and a large results interface all deserve assistive-technology review. There is no published accessibility statement, conformance report or documented list of keyboard, screen-reader and text-zoom behavior.
Privacy and service expectations are informal. No standalone notice explains GitHub Pages logs, cookies, analytics, retention, jurisdiction, takedowns or contact rights. We found no reason to think Armorer builds a behavioral profile, but absence of an account is not a complete privacy policy. A personal project also offers no uptime, backup, vulnerability-response or notice-of-closure commitment.
The license may discourage collaboration despite its permissive intent. Common Grace License 1.0 asks recipients to retain a distinctive text and includes theological framing. Some contributors will appreciate it; corporate and nonprofit policies often whitelist standard OSI licenses and automated scanners may report NOASSERTION. A dual license or a standard identifier would reduce uncertainty without changing the project’s stated gratitude.
Armorer vs. Bible Gateway vs. YouVersion and Bible Hub
Bible Gateway provides a vast translation catalog, passage comparison, audio, search, reading plans and a paid Plus study layer. It is much better for switching versions and consulting publisher material. Its pages also belong to a larger commercial content and advertising environment and can feel busy. Armorer wins when the requirement is simply “open the KJV and read continuously,” especially if an account and recommendation system are unwanted.
YouVersion offers hundreds of translations and languages, audio, plans, highlights, notes, images, social connections and synchronization through highly polished mobile and web products. It is the easier choice for a multilingual household or a person carrying a reading history across devices. Armorer cannot match that breadth and does not try. Its benefit is less identity, less navigation and a source repository a technical reader can inspect.
Bible Hub layers parallel translations, interlinear material, lexicons, commentaries, cross-references, sermons and topical tools around verses. It is exceptionally useful for discovery and can be visually overwhelming. Armorer is the better reading surface; Bible Hub is the more powerful lookup desk. Many people can use Armorer for sustained text and open a study site only when a question arises.
ESV.org and similar publisher sites offer refined typography, audio and authorized notes around one principal modern translation, often with account and subscription layers. Armorer’s KJV is public-domain-friendly and the reader remains free. Choose based on the text required, not the surrounding polish. For teaching or quotation, verify the edition and rights rules your organization follows.
The bottom line
Armorer is a small tool with unusually good restraint. It makes the KJV fast to open, comfortable to continue, easy to search locally and precise to link. The public repository and static delivery are genuine virtues, especially for readers tired of accounts and commercial clutter. Its limits are equally honest: one translation, no saved study life, no audio or notes, no institutional support and no published privacy or accessibility assurance. Keep it as a focused reader or teaching-link destination, not as the only Bible available. If the project adds a concise privacy notice, accessibility testing, explicit text provenance and a standard license option, its trust story could become as clean as its interface.
Alternatives to Armorer
Frequently asked questions
What is Armorer?
Armorer is a free minimalist website for reading and searching the King James Version. It loads adjacent chapters as a reader scrolls, updates the URL with the current location, provides book and chapter navigation, supports verse-level links and performs keyword search in the browser. Jon Winsley created it as a statically generated personal project.
Which Bible translations does Armorer include?
Armorer currently presents the King James Version across the 66-book Protestant ordering. It does not provide modern English translations, original-language texts, another language or an expanded canon. If a passage is difficult or a translation issue matters, compare it in a multi-version service and read the surrounding literary context.
Is Armorer free and does it require an account?
It is free and requires no account. There is no advertised subscription, premium feature or checkout. The tradeoff is that there is also no cloud synchronization for notes, highlights, bookmarks or progress. A browser bookmark can preserve a stable verse or chapter URL, while personal study records need another tool.
Does Armorer track Bible searches?
Its search index is downloaded and queried in a browser web worker, so individual search terms do not need to be sent to an application search server. However, the site does not publish a privacy notice, and normal page requests go through GitHub Pages and network infrastructure that can retain technical logs. Local search is a meaningful privacy advantage, not a guarantee of total anonymity.
Can I use Armorer offline?
The public project does not document a supported offline app or installable PWA. Pages and the search index are delivered from the web and may remain temporarily in a browser cache, but cached availability should not be treated as a reliable offline Bible. Keep a dedicated offline Bible app or downloaded text for travel, emergencies and unreliable connectivity.
Is Armorer open source?
Its source is publicly available and the Common Grace License 1.0 grants broad rights to copy, modify, distribute and incorporate it while requiring the license to remain. GitHub categorizes the license as “Other,” and it is not a familiar OSI-approved or standard SPDX license. “Source-available with broad permissions” is the clearest description; seek legal review before organizational redistribution.
Is Armorer accessible?
The static text-first design is a promising foundation, but no public accessibility statement or conformance report documents screen-reader, keyboard, zoom, contrast and reduced-motion testing. Infinite chapter insertion and changing URLs can create special navigation issues. Test the live site with the assistive technology and browser you use before depending on it.
