- Starting price
- Free and open source
- Free tier
- Yes
- Platforms
- Windows · macOS · Linux · iPhone · iPad · Android · Chromebook
- Developer
- Tobias Klein
- Launched
- 2019; iOS launched 2026
- Updated
- Aug 9, 2026
The verdict
Ezra Bible App is one of the strongest no-cost choices for readers who build topical verse lists and notes across a large SWORD library. It offers real desktop software, mobile apps, export, word-study tools, commentaries and optional Dropbox sync without a subscription, and its GPL source is inspectable. It requires more stewardship than a closed consumer Bible: modules come with different rights and quality, the interface rewards learning, and the published privacy paperwork is materially inconsistent.
Try Ezra Bible App ↗Opens ezrabibleapp.net
Ezra Bible App is a cross-platform Bible study program maintained by German developer Tobias Klein. Its organizing idea is not a social feed, devotional plan or library of purchased books. The user reads a SWORD Bible module, assigns verses to topical tags arranged inside tag groups, and writes Markdown notes attached to verses or whole books. Search, Strong’s data, morphology, dictionaries, commentaries, cross-references and parallel translations remain beside that personal work. Notes and verse lists can be exported to Word; user data can be exported to CSV; optional Dropbox integration can synchronize a database across devices.
The SWORD connection determines both its breadth and its complexity. CrossWire and additional repositories distribute modular Bibles, commentaries, dictionaries and related texts across many languages. Some are public domain, some copyrighted, some geographically restricted, and some require an unlock key or separate permission. Ezra lets users configure repositories and install compatible modules, but the app’s being free does not make every text free to redistribute. Metadata, versification, Strong’s tagging and commentary quality also vary by module. A reader must evaluate the resource, not assume the application has endorsed every theological claim or text edition it can open.
Version 1.20.0, released 31 May 2026, substantially improved the word-study panel with morphological information, Vine’s Expository Dictionary, Strong’s occurrence counts and navigation, while adding configurable SWORD repositories, fuller-screen study panels and better commentary behavior beside parallel translations. That arrived only two months after the iOS edition launched on 29 March 2026. The broader project predates the mobile listing: its public repository began in 2019, and desktop packages for Windows, macOS and Linux remain central. Android and Chromebook builds are also available. The project is licensed under GNU GPL v2.0, allowing inspection, modification and redistribution under the license’s conditions.
The trust story is mixed. Apple says the iOS app may collect crash diagnostics not linked to identity. Its linked June 2022 policy is a generated template that says much more: automatic IP, device identifiers, usage data, Sentry, possible marketing, business partners, broad California identifier categories and even possible “sale” of three data categories. It also describes accounts and purchases that do not match the obvious local-first free product. Open source makes technical verification possible, but it does not reconcile legal promises automatically. This researched review uses official documentation, source metadata, the current Apple record and policy; we did not install modules, connect Dropbox, inspect every dependency, audit compiled binaries or test import and export fidelity.
✓ The good
- Genuinely free and open source - the GPL-2.0 codebase has no advertised subscription or premium lock
- Cross-platform continuity - supported builds span the three major desktop systems plus iOS, iPadOS, Android and Chromebook
- Topical study is first-class - two-level tag organization turns verse collections into a durable research system
- Notes stay beside Scripture - verse and book notes use Markdown and can be searched and exported
- Broad SWORD ecosystem - Bibles, commentaries and dictionaries in many languages are not tied to one commercial store
- Strong export options - CSV and Word reduce lock-in and let research leave the application
- Serious word study - version 1.20 adds morphology, Vine’s and occurrence navigation rather than merely keyword lookup
- Optional rather than mandatory cloud - local work does not require an Ezra account, while Dropbox is available for people who want sync
✗ Watch out
- Module quality and rights vary - compatibility does not guarantee textual accuracy, theological fit, redistribution permission or regional availability
- Privacy disclosures conflict - Apple lists only unlinked crash data while the linked policy describes identifiers, usage, marketing and possible sale
- Dropbox is the only documented synchronization route - users who avoid it must manage local exports and backups themselves
- Learning curve exceeds mainstream Bible apps - repositories, modules, tags, Markdown and study panels require deliberate setup
- Mobile localization metadata conflicts - Apple lists English only while the official project site lists eleven interface languages
- No declared Apple accessibility features - cross-platform availability does not establish screen-reader or keyboard quality
- Single-maintainer concentration - an active open project can still depend heavily on one person for releases and direction
- One store rating is not evidence - the perfect US score says nothing reliable about stability across seven platforms
Best for
- Students who organize Scripture by topics, keywords and reusable verse lists
- Open-source users who want inspectable software and portable exports
- Readers needing Bible modules outside a single commercial bookstore
- Desktop-first study with optional mobile access and Dropbox synchronization
- Teachers building sermon manuscripts or reference collections from personal notes
Avoid if
- You want a zero-configuration Bible with licensed modern translations already included
- You cannot evaluate the source, rights or theological perspective of installed modules
- You need seamless proprietary-library purchases, customer service and polished onboarding
- Your organization prohibits Dropbox or requires centrally managed team collaboration
- You need a privacy policy that already matches the exact current implementation
What Ezra Bible App is
Ezra is a personal research environment layered over the SWORD module standard. Bible browsing provides the base. Tags turn selected verses into topical lists, and tag groups create one level of hierarchy above them. Notes attach to verses or books and support Markdown. Search can work across a Bible module or the currently open browsing context, with phrase, multiword and Strong’s-aware options. Study panels expose dictionaries, morphology, commentaries, introductions, footnotes and cross-references when the installed module supplies them.
The application stores its own user data in a local SQLite database. Export routes create CSV backups or Word documents containing verse lists and notes. Dropbox synchronization can propagate changes at startup, after edits, at close and according to settings such as Wi-Fi availability. This design gives the reader ownership-like portability without pretending every installed biblical text can be freely copied. The personal data and the licensed module content are related in the interface but governed differently.
Why topical tagging is more durable than collecting highlights
Most Bible apps let users color a verse or place it in a flat list. Ezra treats a topic as a study object. A verse can receive one or more tags, tags can sit inside groups, and the resulting collection remains available beside the Bible. That supports long-running questions: every passage related to exile, wisdom and speech, covenant signs, prayer in Acts or a teaching series. Notes add interpretation and source reminders without forcing the user into a separate document. Word export can turn the curated material into a handout or manuscript.
Organization can also become a substitute for reading context. A tagged verse remains part of a paragraph, book and canon; collecting it under a topic does not settle its meaning. Use tags as indexes back to passages, name them precisely, keep notes that distinguish quotation from interpretation and periodically review whether a category imposes conclusions the text does not. Ezra’s two-level hierarchy is enough to build a useful system and simple enough that the system need not become the study itself.
SWORD repositories and modules: extraordinary breadth with user-side due diligence
Ezra can browse translations from CrossWire repositories and, since version 1.20, configure additional SWORD repositories. Modules may supply Bible text, Strong’s numbers, morphology, commentaries, dictionaries, book introductions, cross-references and footnotes. Users can place translations in parallel and open supporting resources in study panels. The official site emphasizes that this architecture enables work in many languages rather than restricting the app to a fixed English bundle.
A module is a container, not a quality seal. Check publisher, edition, revision date, language, versification system, encoding, copyright and unlock requirements. An older public-domain English text may be legally easy and linguistically unsuitable for a new reader; a community translation may be valuable and still need review; a commentary can represent a specific tradition. Do not copy protected text into exported documents beyond its permission. For a class or church, publish an approved module list so participants are comparing the same editions and know which resources are commentary rather than biblical text.
Word study in version 1.20: Strong’s, morphology and Vine’s in context
The May 2026 update adds morphological information to the word-study panel, integrates Vine’s Expository Dictionary, counts occurrences for a Strong’s number and improves navigation among those references. When a module includes the necessary tagging, a reader can move from a translated word to its indexed Greek or Hebrew entry, observe grammatical information and find other places associated with the same identifier. Fullscreen study panels make this more workable on tablets and phones.
Strong’s identifiers are lookup aids, not definitions that can simply be substituted into a verse. An English word may represent several source words; one source word can carry different senses; morphology narrows grammar but does not decide discourse; and Vine’s reflects its author, era and scope. Compare occurrences in context, consult a current lexicon when precision matters and resist the “root meaning” fallacy. Ezra gives unusually capable free access to the evidence, but the user still needs a sound method for interpreting it.
Local data, Word and CSV export, and Dropbox synchronization
Personal tags and notes live in an SQLite data layer and can be exported. CSV supports structured backup and migration; Word export produces readable verse lists, notes and sermon-oriented documents. Optional Dropbox integration links an account and can synchronize on startup, on every change, at close and over Wi-Fi according to the official feature documentation. A status indicator reports sync state. This is more portable than a closed note silo and more convenient than manually copying a database between devices.
Synchronization creates conflict and confidentiality questions. Make an export before connecting a second device, verify that both run compatible versions and test with disposable entries. A sermon note may contain private pastoral illustrations; a topical database can reveal beliefs and research interests. Dropbox then becomes a processor and security boundary even though Ezra has no account of its own. Use strong account protection, remove old linked devices, understand recovery and deletion behavior, and retain an offline export that does not depend on either service.
Pricing
Ezra Bible App
Free
All application features—topical tags, notes, search, word study, commentaries, parallel translation, exports, repository management and optional Dropbox synchronization—are available without an Ezra subscription. The program is published under GNU GPL v2.0.
SWORD modules
Varies by module
Many repository resources are free or public domain. Others can be copyrighted, restricted, locked or licensed separately. Ezra provides a module framework, not a blanket license to every Bible and commentary. Read the module metadata and publisher terms before sharing or redistributing content.
Dropbox sync
Optional external account
The official feature page documents synchronization through Dropbox. Ezra does not charge for it, but Dropbox account, storage, privacy and plan limits are external. Local-only users can avoid this connection and rely on regular exports and device backups.
Self-supported deployment
Your time
Open source permits inspection and modification under GPL-2.0, but there is no advertised enterprise support contract, managed church workspace or guaranteed response time. Organizations adopting it at scale should budget for module curation, backups, upgrades, training and internal support.
Ezra itself costs nothing on every documented platform. There is no advertised premium edition, recurring plan, in-app purchase or feature-limited free tier. GPL-2.0 means recipients can study and modify the program and redistribute qualifying versions under the license.
The surrounding costs are resource and stewardship costs. Some SWORD modules may require an unlock key or have rights that limit copying. Dropbox may have account or storage constraints. A user may also choose paid dictionaries or reference works outside Ezra to validate deeper language study.
Open source shifts support rather than eliminating it. A household can rely on documentation and community discussions. A school or church should decide who approves modules, keeps exports, tests upgrades, responds to sync conflicts and supports less technical participants. No paid service-level agreement is offered on the public site.
Portability is the strongest financial protection. Word and CSV exports let a reader leave without losing the substance of personal work. Test those exports before accumulating years of notes, and document how to restore them. A free tool is most valuable when its backup route is understood before it is needed.
Where Ezra Bible App falls behind
Privacy paperwork is irreconcilable as written. Apple’s current developer disclosure says only crash data may be collected without identity linkage. The linked policy, last updated 18 June 2022, says usage data is collected automatically, names IP addresses and unique device identifiers, identifies Sentry, describes accounts, purchases, promotions and business partners, marks California identifiers and internet activity as collected, and says those categories may be sold. A current product-specific policy should replace the generated template and explicitly reconcile each App Store answer.
The template is not merely overbroad; some clauses appear unrelated to the product. Ezra advertises no account or purchase system, while the policy discusses registrations and contracts for bought items. It says the company may send marketing by telephone or SMS and may offer partner promotions. Boilerplate this disconnected from implementation makes informed consent harder, not safer.
Consumer onboarding cannot match YouVersion, Logos or Olive Tree. New users must understand repositories and modules before the app feels complete. A curated first-run path explaining the difference between Bible, commentary and dictionary, with rights and language filters, would make the open ecosystem much more approachable.
Localization is confusing on iOS. The project site lists English, Spanish, German, Dutch, French, Slovak, Slovenian, Ukrainian, Russian, Romanian and Brazilian Portuguese. Apple’s current metadata lists English only. That may be store-localization configuration rather than the actual interface, but a mobile buyer cannot tell. Publish a platform-by-platform language table.
Collaboration is not the goal. Dropbox syncs one user’s data; it is not a class workspace with permissions, commenting, shared notebooks or version history. Teams needing governed shared research should use a system built for collaboration or exchange controlled exports.
Accessibility remains undocumented in Apple’s standardized section. Desktop keyboard use and responsive panels may work well, but no public conformance statement establishes VoiceOver, TalkBack, screen magnification, reduced motion, high contrast or full keyboard navigation. An open repository makes accessibility contributions possible; it does not make them complete.
Ezra Bible App vs. STEP Bible vs. Logos Bible Software
STEP Bible is the easiest free route to strong language-linked study in a browser. It removes installation and repository setup, offers original-language connections and works well when a reader needs a quick lookup from almost any device. Ezra is better for durable personal topical collections, local notes, offline modules and exports. STEP is a hosted research site; Ezra is a personal workspace whose data can remain local.
Logos is the commercial library and research system. It offers a vast licensed bookstore, sophisticated searches, citation-aware resources, linked datasets, courses and institutional support. It can cost substantially more and creates a proprietary library relationship. Ezra cannot match that depth, but it costs nothing, opens its source, runs on Linux and lets a reader work with SWORD resources and portable personal data without purchasing an ecosystem.
Olive Tree sits between them as a polished consumer study Bible with purchased resources and capable mobile use. It generally requires less setup and has publisher relationships for modern translations and study Bibles. Ezra wins when open standards, desktop Linux, topical tagging and no subscription matter more than storefront convenience. The right choice depends on whether the reader wants an immediately curated library or the freedom—and responsibility—of assembling one.
The bottom line
Ezra Bible App deserves attention because its freedom is substantive: open code, seven platform targets, portable notes, Word and CSV export, configurable Scripture repositories and a word-study tool that keeps improving. It can become a durable Bible research desk without requiring a recurring payment. The same openness means users choose and evaluate modules, manage backups and decide whether Dropbox belongs in their workflow. The most avoidable problem is the privacy policy, whose generated 2022 language is dramatically broader than Apple’s 2026 disclosure. Fix that documentation, strengthen onboarding and publish accessibility status, and Ezra becomes easier to recommend beyond technically confident students.
Alternatives to Ezra Bible App
STEP BibleA free browser-based study environment with excellent language connections and no local module setup, but less emphasis on personal topical databases.
Logos Bible SoftwareThe deep commercial option for licensed books, datasets and research workflows; far more powerful and expensive than Ezra’s open SWORD model.
Olive Tree Bible AppA polished mobile and desktop study app with a commercial bookstore and easier onboarding, trading openness for curated publisher access.AndBibleA mature open-source Android study app using SWORD-family modules, ideal when mobile depth matters and an iOS or desktop build does not.XiphosA veteran open-source desktop SWORD front end with broad module access, better suited to traditional pane-based study than Ezra’s topical workflow.Frequently asked questions
Is Ezra Bible App completely free?
Yes. The app has no advertised subscription, premium unlock or in-app purchase and is released under GNU GPL v2.0. Many SWORD modules are free or public domain, but individual Bible, dictionary and commentary modules can have their own copyright, regional restrictions or unlock requirements. Free software does not grant redistribution rights to every text it can display.
What are SWORD Bible modules?
SWORD is an open Scripture-software framework used to package Bibles, commentaries, dictionaries and related resources. Ezra reads modules from CrossWire and configurable additional repositories. Each module carries its own language, metadata, versification, features, quality and license. Users should check the publisher and rights rather than assuming repository availability means an official or unrestricted edition.
Where does Ezra store my notes and tags?
The project documentation describes user data in a local SQLite database. Notes and tags can be exported to CSV, and verse lists and notes can be written to Word documents. Optional Dropbox integration synchronizes data between devices. Before enabling it, export a backup, protect the Dropbox account and test conflict behavior with nonessential entries. Ezra does not advertise its own cloud account.
What can its word-study tools actually tell me?
With a suitably tagged module, version 1.20 can show Strong’s entries, morphology, occurrence counts, navigation and Vine’s Expository Dictionary. These tools help locate evidence; they do not make a user fluent in Greek or Hebrew or prove that every occurrence has the same sense. Interpret grammar and vocabulary in sentence, literary and historical context, and consult current scholarly lexicons for teaching claims.
Does Ezra Bible App collect data?
The current Apple label says crash diagnostics may be collected without identity linkage. The linked 2022 policy says far more, including IP addresses, unique identifiers, usage data, Sentry, marketing and possible sale of California identifier categories. Because those public statements conflict, users should not rely on either as a complete architectural description. Local-only use reduces cloud exposure; Dropbox and repository downloads still contact external services.
Which languages does the interface support?
The official project site lists eleven: English, Spanish, German, Dutch, French, Slovak, Slovenian, Ukrainian, Russian, Romanian and Brazilian Portuguese. Apple’s iOS metadata currently lists only English. That discrepancy may concern store localization rather than the in-app interface, but it is unresolved publicly. Bible text language is a separate matter and depends on installed modules.
Can a church collaborate inside Ezra?
Not as a governed multiuser workspace. Ezra is designed around one user’s tags, notes and local database, with Dropbox for that user’s devices and exports for sharing. It does not advertise roles, shared notebooks, comments, approval, audit logs or centrally managed module policies. A class can standardize modules and exchange Word or CSV files, but organizations needing live collaboration should choose a platform built for it.
Sources & further reading
More Bible Study Software
VerseLink BibleVerseLink Bible keeps Scripture, sermon notes, highlights and original-language helps entirely on your device with no account, tracking, ads or subscription—but local-first privacy makes manual backup your responsibility.
Rava: Discover God’s StoryA free, multilingual facilitator that lets almost anyone press play and guide a Discovery Bible Study with little preparation—excellent for reproducible group participation, but not a replacement for wise leadership, contextual interpretation or a modern privacy policy.
ARMA CoursesARMA makes serious Bible and theology teaching approachable through short, energetic courses—valuable for guided learners, but narrower and less transparent than a seminary library.
Storyverse InstituteStoryverse makes Bible, theology, soul care and ministry training approachable through 200+ videos, community and cohorts—but its age, collection and deletion disclosures conflict too sharply for informed enrollment.
The Word One to OneA polished, completely free guide for reading John and Acts with a friend—excellent for a trusted conversation, but narrow in scope and incomplete on app privacy and safeguarding.
Waha: Discovery Bible StudyA free audio facilitator that lets an ordinary person lead Scripture discussion in 63 languages—even offline or in a restricted nation—with a strong multiplication method and privacy documentation that has not kept pace with its security claims.