Features
Everything a sermon recording turns into
Upload Sunday’s sermon and it comes back as a transcript tied to the audio, the passages it preached, a page your congregation can find, and a copy of all of it that stays yours.
Every recording, every plan
The same pipeline on every plan
- A transcript
- The whole sermon as text, with a time on every paragraph and sentence, so the words and the audio stay tied together.
- A summary
- A short paragraph written from the transcript, for a visitor deciding whether to listen.
- Topic tags
- Chosen from your church’s own list wherever one fits. A new tag is made only when none does, and it’s added to your list marked as not yet approved.
- Scripture passages
- The references the preacher named, found in the transcript’s own words, plus anything a person already entered, plus suggestions you approve or reject.
- Pull quotes
- Lines worth repeating, each one checked against the transcript before it’s kept, so no preacher is quoted saying something they didn’t say.
- Clarifications
- Words the transcription misheard, from a biblical name to the old wording of a passage read aloud, restored automatically and only where the engine can confirm what was said. The review screen lists every one.
- A printable transcript
- A PDF on your church’s letterhead, for the member who wants the sermon on paper.
Ready for review
- Transcript
- 41 paragraphs, 38 min 12 sec
- Summary
- One paragraph
- Topics
- Grace, Prayer
- Passages
- Luke 18:9–14, Psalm 51
- Quotes
- 2 lines, both found in the transcript
- Clarified
- 1 misheard name
- On the church’s letterhead
An example sermon, as the review screen lists it before anyone publishes.
None of it’s public until somebody at your church publishes the sermon. The plan decides how many recordings a month you send and how hard your own website may call the API; every recording gets the same treatment.
In detail
Each part on its own page
- Interactive transcripts. The whole sermon as text, tied to the audio sentence by sentence. Click a line and the recording moves there; a link carries the minute with it.
- Scripture citations. The passages a sermon preaches, found in the preacher’s own words and stored as verse ranges, so asking for a chapter finds every sermon that touches it.
- Your hosted library. A public, searchable sermon site with your church’s name on it: the archive, series, speakers, a scripture index, and a page per sermon that a search engine can read.
- Sermon graphics. A card for each published sermon and for each pull quote, in three sizes and three looks, and a short clip of a quote in the preacher’s own voice, on the Platform and Pro plans.
- The API, webhooks, and the embed. Everything you publish, available to read back out: a documented public API for your own website, a signed callback when a sermon goes live, and two elements you can paste into a page.
- Bringing your archive over. Twenty years of recordings, from a spreadsheet, a manifest, or the podcast feed you already publish. Imports draw on their own pool of credits.
- Taking everything with you. One file with your whole archive in it, whenever you want it, whether you’re leaving or not. It’s a single .tar.gz with a README inside.
Tell us about your church
Tell us how many sermons you preach a month and how far back the archive goes, and we’ll say which plan fits.