Carry every message beyond Sunday.

Yes. Upload the recording, or paste a link from YouTube, Twitch, X, or Vimeo, and reap works as an AI sermon clip generator: it returns candidate sermon video clips you review before anything is exported. Paid plans take sources up to 180 minutes, with uploads up to 5 GB on Free and 10 GB on paid plans, so a full service recording usually goes in whole. reap works from a finished recording: it does not run your livestream, capture the broadcast, or clip a service while it is happening.

For most churches the practical starting point is the sermon. reap is AI for church media teams: it transcribes the message, suggests sermon clips, captions them in 100+ languages, and schedules them to your church social media accounts. It does not write sermons, check scripture, or make theological judgments, and every clip is reviewed by your team before it goes out.

Yes, from video. Sermon transcription comes with every upload: timed text in 100+ languages that you can correct and use to edit clips, with TXT, SRT, VTT, and CSV exports. Audio-only files such as MP3 are not accepted, so upload the video recording of the service.

Yes. Prompt-first clipping is available on paid plans, so you can ask for the clearest explanation of the main point, the section covering this week's passage, the story that supports the teaching, or the closing application, and reap returns moments from the recording that match. The clipping setup also has a genre selector, and sermons and teaching sessions sit with the Talking Head and Presentation options. Treat what comes back as a shortlist to watch, not a decision about what the message was about.

Yes, and this is the part that matters most for teaching content. Every clip a sermon clip maker suggests is a draft: it opens in reap's editor with the transcript beside it, so you can move the in and out points until the clip starts and ends on the right words, watch the surrounding context, correct the transcript, restyle or reposition the captions, and preview the finished clip. Nothing leaves reap until someone on your team exports or schedules it.

That stays with your team, and reap gives you the tools to do it rather than doing it for you. Because trimming is transcript-based, you can read what comes immediately before and after a suggested clip and widen the boundaries when a qualification or a scripture reference sits just outside them. A practical habit: watch the clip against the surrounding minute, confirm the point is complete, check that any passage cited is quoted correctly, and have the speaker or a ministry leader approve the excerpt before it is published.

Captions are generated automatically in 100+ languages and are editable, and sermon transcription needs a review pass on this kind of source. Book names, personal and place names from scripture, Hebrew and Greek terms, denominational and theological vocabulary, and quoted passages are the usual places transcription slips, along with overlapping speech and congregational response. Fixing a word in the transcript carries through to the burned-in captions, and you can export SRT or VTT files as well.

Yes, through brand templates. A template saves a caption preset, uploaded fonts, a logo overlay, and intro and outro cards, and applies them as new clips are created. Templates and custom fonts are plan-based: 3 on Creator, 6 on Studio, unlimited on Enterprise. Two limits worth knowing: a template applies to clips created after it is saved rather than restyling clips you already exported, and reap does not generate sermon-series artwork or import anything from your presentation software.

Yes. Paid plans output 9:16, 16:9, and 1:1 from one recording, with 9:16 on Free. Auto reframe gives you a starting crop with speaker detection and tracking, and a dynamic layout switch between single-crop, zoom-out, and split framing. Check the framing before export: reap does not know whether your clip depends on a scripture slide, a presentation screen, a sign-language interpreter, or a second person on the platform, and a crop tuned to the speaker can lose any of them. Framing is adjustable by hand.

Both, and they are different things. Subtitle translation covers 100+ languages and changes the written text while the original audio stays; reap can also output Roman script for languages your community reads that way. AI dubbing changes the spoken audio and covers 80+ languages on a monthly allowance of 2 hours on Creator and 5 on Studio. For teaching content, have someone fluent in the target language review the result before it goes out, and check quoted scripture against an approved translation in that language rather than letting it be machine-translated.

Yes. Approved clips can be scheduled from reap's content calendar to connected accounts: TikTok, Instagram Reels, YouTube Shorts, and LinkedIn on Creator, adding X and Facebook on Studio. You pick the clip and account, write the post copy, and set the date and time, and there is a bulk scheduler for queueing several at once. reap does not publish to every platform, does not post anything you have not approved, and does not provide engagement analytics or attendance reporting.

On the Studio plan, yes. A Team Studio workspace gives you up to 3 member seats, Admin and Member roles, and shared projects, templates, and assets, so the recording, its clips, and the publishing calendar sit in one place rather than in someone's downloads folder. Be clear about what is not there: reap has no formal approval stages, no timestamped review comments, and no pastoral sign-off tooling, so who checks a clip before it is published is a process your team defines.

Not natively. reap has no integration with Planning Center, ProPresenter, Church Online Platform, or church management systems, and it does not capture or record a livestream. What it does have is direct import from YouTube, Twitch, X, and Vimeo, plus a REST API, CLI, webhooks, an MCP server, and a Zapier integration on paid plans, which is how teams connect it to the tools they already run. Anything built that way is your own automation rather than a native integration.

No, and it is worth being direct about it. reap does not verify scripture references, select or compare Bible translations, fact-check a sermon, interpret doctrine, or understand the pastoral intent behind a message. It works from what was said in the recording. Theological accuracy, the meaning of a passage, and whether an excerpt fairly represents the teaching are judgments your team makes, and the review step exists so that they can.

That depends on rights you hold rather than on anything reap provides. Recorded worship, licensed songs, and performance footage carry their own copyright and licensing terms, and reap does not grant, check, or clear any of them. reap has no worship lyric import and no music licensing. Follow your church's existing licences and policies, and when a clip's rights are unclear, teaching content you recorded yourself is the safer source.

No. reap removes the repetitive production work sermon repurposing puts between a service recording and a finished clip: locating moments, cutting each one, typing captions, restyling every export, and re-cropping for each format. It does not decide what is worth sharing, whether a clip represents the message fairly, or how your church should sound. Those are the parts your media team, your communications lead, and the speaker keep, and the workflow is built to hand them back a starting point rather than a finished decision.