- Starting price
- Free for listeners · church plans from $0
- Free tier
- Yes
- Platforms
- iPhone · Android · Web publisher tools
- Developer
- GETSERMONS APP LTD
- Launched
- 2024
- Updated
- Aug 9, 2026
The verdict
GetSermons combines several genuinely useful listening ideas in one free app: broad sermon discovery, offline audio, playback control, timestamped notes, playlists, short clips, and questions tied to a sermon. Its public evidence is still early—roughly 1,000-plus Android installs, no meaningful iOS rating sample, store builds unchanged since July 2025, a publisher FAQ that says the church app is still being built, a Google Play disclosure that data is not encrypted, and policies that never adequately explain sermon licenses, clip permissions, transcripts, Preachai providers, or contradictory tracking labels. Listeners can explore low-risk public sermons with minimal profile data; churches should wait for a working pilot, written rights chain, security answers, export, AI controls, and a complete contract before making it their canonical archive.
Try GetSermons ↗Opens getsermons.app
GetSermons is a sermon streaming and discovery service. The mobile app lets a listener browse thousands of messages by preacher, church, or topic, receive recommendations, change playback speed, download audio, build and share playlists, save notes at exact timestamps, and turn 30- to 45-second moments into social clips. Preachai adds a chat interface for asking questions about a sermon “as though” speaking with its preacher. Search and discovery are the front door; the promise is to make a large distributed sermon library feel more navigable and interactive than a folder of podcast episodes.
A second product is aimed at churches. GetSermons advertises sermon hosting, subscriber growth, analytics, a church website, distribution to major podcast players, unlimited storage on paid plans, marketing automation, and support. Public pricing runs from a free 10-hour and 1,000-subscriber plan to $32 and $48 monthly tiers. That is inexpensive beside many church media platforms. Yet the homepage FAQ still says the publishing app is being worked on and asks churches to check back, while the pricing and “for churches” copy present a purchasable service. Google Podcasts—discontinued in 2024—also remains in the distribution list. Treat the public church offer as a product that needs a live demonstration, not a settled feature matrix.
The listener app is real but modestly established. Apple says the iPhone app first launched May 3, 2024, is free, requires iOS 12 or later, occupies about 127 MB, and was last updated to version 0.0.21 on July 21, 2025. It has too few ratings to display an aggregate. Google Play reports 1,000-plus installs and a July 20, 2025 update. A year without a store release does not prove abandonment, but it makes current compatibility, fixes, catalog growth, and AI behavior harder to judge—especially while the website’s privacy policy was updated in April 2026.
We reviewed the live product, church, pricing, FAQ, privacy, terms, Apple, and Google Play pages on August 9, 2026. We did not create an account, listen through a complete sermon, confirm catalog counts, contact a preacher, upload a church archive, create or share a clip, inspect transcript accuracy, query Preachai, test downloads, measure streaming, confirm podcast distribution, verify recommendations, exercise deletion, inspect encryption or source code, identify every processor, request support, or perform copyright, privacy, security, accessibility, doctrinal, pastoral, or legal review. Claims about the library, distribution, support response, subscriber limits, analytics, and the 10% missions allocation come from the vendor unless explicitly attributed to a store.
✓ The good
- Free listener access - the mobile catalog, playback, notes, clips, playlists, downloads, discovery, and AI features are presented without a subscription charge
- Useful discovery structure - preacher, church, topic, search, recommendations, and curated playlists can expose listeners to more than one familiar feed
- Strong listening mechanics - speed control, offline downloads, dark mode, queues, and timestamp-linked notes address normal long-form audio needs
- Timestamped notes preserve context - returning to the exact audio moment is better than saving an isolated quotation without its surrounding argument
- Clip creation is convenient - formatted 30- to 45-second excerpts lower the work required to share a meaningful moment with a source link
- Church entry price is low - 10 hosted hours and 1,000 subscribers at $0 can support a small proof of concept before a paid commitment
- Public tier boundaries - subscriber ceilings, storage language, analytics level, support targets, and monthly prices are easier to compare than sales-only pricing
- Deletion path exists - the 2026 policy says users can delete in settings or request deletion, with active-system deletion targeted within 30 days
- Mission giving is explicit - pricing says 10% of subscriptions supports missions, although the recipient and reporting still need documentation
✗ Watch out
- Publisher availability is contradictory - pricing and church pages sell a service while the FAQ says the publishing app is still being worked on
- Google Play says data is not encrypted - that current developer disclosure is a serious concern for accounts, activity, notes, AI prompts, and church data
- Privacy labels do not reconcile - Apple lists cross-app tracking and linked contact, identifier, usage, photo/video, and diagnostic data while Google says no sharing
- Preachai governance is missing - no public model provider, prompt retention, transcript source, citation behavior, error policy, speaker approval, or safety boundary is documented
- Sermon and clip rights are unclear - the terms do not establish publisher authority, speaker consent, transcript rights, music clearance, takedown, excerpt limits, or reuse rules
- Store momentum is thin - the builds are over a year old, Android adoption is only 1,000-plus, and Apple has no useful rating sample
- Terms are unfinished - a literal privacy-policy link placeholder remains, Nigerian exclusive jurisdiction is imposed, and billing, refunds, content, AI, and church obligations are sparse
- Distribution copy is stale - Google Podcasts is still named despite its 2024 shutdown, weakening confidence in the rest of the integration list
- AI framing can imply endorsement - “chat with the preacher” may cause users to attribute generated words, advice, or doctrine to a real speaker who never said them
Best for
- Listeners exploring public sermons with a separate Bible open and enough judgment to verify quotations, context, interpretation, and AI answers
- People who value offline listening, variable speed, playlists, and timestamped notes more than a mature social or recommendation ecosystem
- Churches testing a small non-sensitive public archive after confirming speaker rights and receiving a working publisher demonstration
- Communication teams willing to approve every clip and retain the full source, title, preacher, church, date, and original link
- Small ministries that can keep an independent master archive and podcast feed while piloting a low-cost discovery channel
Avoid if
- Your church needs a proven canonical sermon host, uptime commitment, migration service, complete publishing workflow, or long operating record now
- Your security baseline requires encryption in transit and at rest, MFA, a DPA, subprocessors, incident terms, audit evidence, or formal procurement answers
- A speaker has not explicitly authorized hosting, transcription, AI use, recommendation, clipping, social distribution, and derivative formats
- You expect Preachai to represent the preacher, settle doctrine, supply counseling, or provide medical, legal, mental-health, crisis, or safeguarding advice
- You plan to save confidential pastoral notes, counseling facts, prayer details, children’s data, or sensitive disclosures in the listener or church system
What GetSermons is
GetSermons is both a consumer sermon player and an emerging distribution service. For listeners, it indexes audio around people, churches, themes, recommendations, saved collections, notes, shareable excerpts, and AI-assisted questions. For publishers, it proposes a central upload that can feed GetSermons, podcast directories, a church website, analytics, subscribers, and marketing workflows.
It is not a Bible translation, commentary, fact-checked theological database, licensed counseling service, authoritative representation of every preacher, or guaranteed archival repository. A sermon is a teacher’s interpretation addressed to a particular congregation and moment. Recommendations and generated conversation add further editorial layers. Check the biblical passage, full recording, source church, speaker, date, doctrinal context, and any corrections before relying on an excerpt or answer.
Why sermon listeners may try GetSermons: the recording remains the center of notes, clips, and questions
Podcast apps can play and download sermons, while church apps can organize one congregation’s archive. GetSermons tries to make a cross-church catalog interactive without reducing it to text. A note returns to its timestamp, a clip is cut from the audio, and Preachai is presented as a way to interrogate the sermon. That shared source can be valuable: the user can move from a remembered idea back to the speaker’s actual words rather than relying on an orphaned quotation.
The safe design standard is traceability. Every note, clip, transcript sentence, recommendation, and AI claim should retain preacher, church, sermon title, publication date, full recording, exact timestamp, transcript confidence, Bible reference, and correction state. AI answers should say “the transcript states” instead of “the preacher believes,” cite the moments used, admit when the sermon does not answer, and direct personal or high-stakes questions to Scripture and qualified humans. Without that structure, convenience can manufacture authority the source never supplied.
Discovery, playback, downloads, and playlists: a promising catalog still needs provenance
Browsing by preacher, church, and topic plus personalized recommendations can make a scattered sermon world easier to navigate. Variable speed, offline download, dark mode, saved playlists, and sharing cover the everyday mechanics people expect from mature audio apps. Curated collections can help a listener follow a biblical book, question, season, or trusted teacher across several recordings.
Catalog scale is not the same as catalog quality. GetSermons should show who supplied each file, whether the speaker and church authorized it, original publication date, denomination or ministry context where supplied, recording completeness, audio quality, transcript source, edits, reuploads, rights territory, and removal history. Churches should be able to claim profiles, correct metadata, suppress unauthorized copies, approve topics, and prevent algorithmic recommendations from implying agreement between unrelated speakers.
Notes and social clips: context must travel with the memorable moment
Timestamped notes are the strongest low-risk feature because they help a listener capture an idea without losing its location. Clip turns a short portion into a shareable video for WhatsApp, Instagram, Facebook, and similar surfaces. That can help a church distribute a concise invitation or let a listener point a friend to a meaningful section without requiring a full hour first.
Thirty seconds can also reverse the meaning of an argument, omit a qualification, expose a person mentioned from the pulpit, or pair copyrighted music and imagery with a new social use. Let publishers disable clipping by sermon, choose safe boundaries, supply branding and captions, require a canonical link, review generated transcripts, and remove a clip everywhere after a takedown. Users should preview several minutes around the excerpt and never use a provocative fragment to make a speaker appear to say what the full message rejects.
Preachai: useful sermon Q&A should never pretend to be the preacher
Preachai gives the listener a chat box connected to a sermon. The sensible use is retrieval and explanation: find where a topic appears, summarize a stated point, list Bible references, compare two sections, or ask what illustration led to a conclusion. This can lower the navigation cost of a long recording and make a transcript more accessible to someone reviewing or studying it.
The “live-chatting with the preacher” framing is the central risk. A language model can invent doctrine, motives, quotations, applications, and personal counsel. It may not know whether the transcript is correct or whether the preacher has changed or corrected a view. The interface should be visibly synthetic, use first-person language only inside verified quotation, cite timestamps for every material answer, disclose model and retention, give publishers opt-in and deletion, refuse impersonation and high-stakes advice, and provide report and correction tools. Users should never present a generated answer as the preacher’s words.
Pricing
Listener app
Free
iPhone and Android listening, browsing, recommendations, playlists, offline audio, notes, clips, and Preachai are presented as free for the foreseeable future. No paid consumer tier is published.
Small church
$0/month
Includes 10 sermon hours, up to 1,000 subscribers, basic analytics, and a stated 48-hour support target. Confirm whether storage is total or recurring and whether every publisher tool is actually live.
Medium church
$32/month
Advertises unlimited sermon hours, up to 10,000 subscribers, advanced analytics, 24-hour support, and marketing automation. Tax, currency, cancellation, refunds, overages, and annual discounts are not clearly documented.
Large church
$48/month
Advertises unlimited sermon hours and subscribers, advanced analytics, one-hour support, marketing automation, and custom integrations. A one-hour target is not a service-level remedy.
Mission allocation
10% of subscriptions
The pricing page says this share supports missions. It does not name recipients, selection criteria, restricted versus unrestricted use, timing, or a public impact report.
The listener proposition is straightforward: the iPhone and Android apps are free, and the site says they will remain so for the foreseeable future. “Foreseeable” is not a price guarantee, so keep exports of notes and playlists if they matter.
The free church plan is a practical test bed if 10 hours and 1,000 subscribers fit. Verify whether “10 hours” is cumulative hosted audio, monthly upload time, or another measure; the pricing card does not explain it.
At $32 and $48 monthly, the paid plans appear inexpensive for unlimited sermon storage. The decision should turn on the actual publisher workflow, delivery reliability, rights controls, export, podcast ownership, analytics definitions, support performance, and contract—not headline storage.
Confirm who owns the RSS feed and subscriber relationship. A church should retain a domain-controlled feed, original audio and transcripts, complete metadata, consent records, analytics exports, and the ability to leave without breaking podcast followers or embedded players.
Obtain written billing terms before paying: trial, renewal date, tax, currency, failed payment, cancellation effective date, refund, plan downgrade, subscriber overflow, storage after cancellation, export window, deletion, and future price notice.
Where GetSermons falls behind
Reconcile the church product publicly: state which publisher, website, RSS, directory, subscriber, analytics, automation, and integration features are generally available, beta, planned, limited, or retired.
Correct stale and unfinished documentation, including Google Podcasts, the privacy-link placeholder, dates, support terminology, governing entities, billing, refunds, cancellation, plan limits, and product-specific terms.
Publish a sermon-rights framework covering uploader authority, preacher and church consent, music, guest speakers, testimonies, transcripts, AI processing, clips, derivative media, distribution, territorial limits, DMCA, disputes, and takedown propagation.
Explain Preachai end to end: transcript creation, retrieval scope, model and hosting providers, prompt and output retention, training, publisher opt-in, citations, error reporting, safety, age limits, human review, deletion, and impersonation boundaries.
Resolve Google Play’s “data is not encrypted” disclosure and publish encryption in transit and at rest, MFA, access controls, security testing, vulnerability reporting, incident notice, backups, recovery, logs, and assurance evidence.
Reconcile Apple tracking with Google no-sharing disclosures and the privacy policy, naming every SDK, field, purpose, processor, linked status, retention period, advertising use, consent choice, deletion path, country, and international transfer.
Add publisher and listener portability: original audio, RSS ownership, metadata, transcripts, notes, playlists, clips, subscriber consent, suppression lists, analytics, deletion receipts, and a documented shutdown or migration procedure.
GetSermons vs. SermonAudio vs. church podcasts vs. general podcast apps
GetSermons has the most integrated idea here: a cross-preacher Christian catalog combined with timestamped notes, social clips, recommendations, and sermon-specific AI. SermonAudio has a far longer operating history, a huge church and broadcaster network, mature media distribution, and more institutional evidence, though its interface and pricing serve a different audience. A church-owned podcast keeps the canonical source and subscriber relationship clearer but offers less cross-catalog discovery. General podcast apps provide polished playback, queues, casting, downloads, and broad reviews without sermon-specific context or AI.
Choose on control and trust before novelty. A listener can use GetSermons as a discovery layer while following a church’s original feed and checking the full message. A church can syndicate selected public sermons after verifying permissions while preserving its own archive and feed. Preachai and clip creation are differentiators only when provenance, citations, consent, and corrections are stronger than the risks they introduce. Today the product looks more appropriate for cautious exploration than exclusive institutional dependence.
The bottom line
GetSermons understands that listening is more than pressing play. Discovery by teacher and topic, offline audio, speed controls, playlists, timestamped notes, clips, and sermon-aware questions form a coherent experience, and the church tiers make ambitious distribution financially accessible. The problem is not the idea; it is the evidence around it. The current apps have a small public footprint and no store update since July 2025. The church FAQ conflicts with the sales pages. Google’s developer disclosure says data is not encrypted. Apple’s tracking label, Google’s no-sharing label, and the privacy policy do not tell one story. The terms barely address the rights required to host, transcribe, transform, clip, distribute, and simulate conversation around someone else’s sermon. Try the listener app with public material, little personal data, and an open Bible. Churches should run a reversible pilot only after a live demonstration, written permission chain, security answers, AI specification, export test, and contract review—and should keep their own archive, domain, RSS feed, transcript, and subscriber consent outside the platform.
Alternatives to GetSermons
Frequently asked questions
Is GetSermons free?
The iPhone and Android listener apps are free, and the website says they should remain free for the foreseeable future. Churches can also start with a $0 plan limited to 10 sermon hours and 1,000 subscribers; paid plans are listed at $32 and $48 monthly.
What is Preachai?
It is an AI chat feature attached to a sermon. GetSermons describes it as asking questions as though chatting with the preacher, but generated replies are not the preacher’s own words unless they quote a cited timestamp. Do not use it as pastoral authority or high-stakes advice.
Can I listen offline?
Yes. Offline downloads are among the advertised listener features, alongside playback speed, playlists, notes, dark mode, recommendations, and sharing.
Can churches publish sermons through GetSermons?
The site advertises hosting, analytics, podcast distribution, a church website, subscribers, and automation, but its FAQ also says the publisher app is still being worked on. Ask for a live account demonstration and a written generally-available feature list before buying or migrating.
Does GetSermons own uploaded sermons?
The public terms do not provide the detailed chain of permission this product needs. A church should retain ownership and obtain explicit speaker, guest, music, transcript, AI, clip, social, and distribution rights in writing before upload.
Is GetSermons private and secure?
The disclosures are not strong enough to say so. Apple lists tracking and linked data, Google says no sharing but also says data is not encrypted, and the policy does not reconcile the SDKs or explain Preachai data. Use minimal data and do not store confidential pastoral material.
How current is the app?
Apple and Google both show the most recent mobile update in July 2025. Apple version 0.0.21 has too few ratings for a summary, while Google Play reports 1,000-plus installs. Check compatibility and support before depending on it.
