Five at once: why we built batch processing into Clipr
Last month, a church social media manager emailed me in mild panic. She had filmed four Sunday sermons while the pastor was away, recorded a guest speaker on Wednesday, and faced the prospect of processing each video individually. She had perhaps ninety minutes to spare before the week got away from her. That email changed how we thought about Clipr for busy creators.
The reality of sermon capture
Most of the feedback we get from churches and podcasters comes wrapped in the same constraint: time. A pastor records a fifty-minute sermon. A podcast host publishes weekly episodes that run an hour or more. A church communications officer juggles Sunday services, midweek teachings, and special events. All of them know their content could reach more people as short clips on Reels, Shorts, and TikTok. But the practical barrier is always the same. Processing videos one at a time, waiting for transcription and scoring to finish, exporting, then moving to the next file, is a rhythm that doesn't fit the real pace of ministry work.
When we first launched Clipr, the Pro tier was there for creators who wanted unlimited clips and access to the faith score explanation for each moment (so you can see why the algorithm flagged a particular section as engaging). But we kept hearing the same refrain in conversations with users: "Can I just submit five or six at once and come back when they're done?" That wasn't laziness. It was reality.
Batch processing changes the workflow
Batch processing in Clipr works straightforwardly. If you're on the Pro plan, you can select up to five videos at once, submit them, and the system works through them in parallel. Your Apple Speech transcription happens on-device, as it always does. The AI moment scoring runs server-side, ranking the moments in each video for engagement. Captions get baked in, the vertical 9:16 format is applied, and you get back five complete sets of clips ready to export.
The actual time saved is harder to quantify than it sounds, but consider the math. Processing one forty-minute sermon might take three to four minutes of actual interaction with the app, plus some waiting time. Five sermons, done one after another, is fifteen to twenty minutes of interaction time. Done in batch, you load them all, hit process, and your time drops to maybe four or five minutes of setup. More important than the minutes saved, though, is the mental relief. You're not switching contexts five times. You're not wondering which video you processed last. You submit a week's worth of content and trust the system to work through it while you're doing something else.
Why batch only works at Pro
We made a deliberate choice to reserve batch processing for the Pro tier, and I want to be honest about the reasoning. The Creator plan gives you unlimited clips per month, auto-captions, vertical reformatting, and watermark-free export. That covers most creators' needs. But the infrastructure cost of processing five videos in parallel, especially when they're long-form content, is higher than processing one at a time. We needed the Pro tier to carry that cost. It's not arbitrary gatekeeping; it's the actual weight of the compute.
The faith score explanation, which also ships with Pro, sits alongside batch processing as a feature that justifies the tier. When you're processing five sermons at once, you likely want to understand why the algorithm flagged a particular moment as engaging. "This scored high for faith relevance" or "This moment resonates emotionally" gives you the confidence that the clips are landing in the right places, not just anywhere the audio got louder.
A decision that came from listening
What strikes me, looking back, is that batch processing wasn't on our initial roadmap. We built Clipr's core features around the assumption that creators would process one sermon or episode at a time, maybe two or three a week. But the moment we put the app in users' hands, we learned that assumption was wrong. Churches don't release one sermon a week in a vacuum. They record multiple services. Podcasters have backlogs. Guest speakers visit and get recorded. The actual rhythm of creation in these communities is messier and faster than our initial design accounted for.
So we listened. We added batch processing. It's a small feature on the surface, but it's the kind of small feature that changes how people actually use an app, because it fits their real life instead of an imagined version of it.
What happens next
If you're a pastor or church communicator with a pile of videos waiting to be clipped, Pro is worth the upgrade just for this. Load five sermons or episodes, walk away, and come back to a week's worth of short-form content ready to export and share. You don't need to download a desktop editor, figure out aspect ratios, or spend three hours manually hunting for good moments. You get back clips with captions baked in, vertical formatting locked, and the system's judgement of which moments matter.
That said, batch processing isn't magic. You still export clips locally and upload them yourself to TikTok, Reels, and YouTube. Clipr does the hard part of finding the moments and formatting them; you do the final step of sharing them where they land. It's a partnership between tool and creator, not a handoff to a black box.
When you're holding five weeks of sermons waiting to become clips, does batch processing feel like a nice-to-have, or like the difference between a manageable workflow and an impossible one?