Why we built Auto vertical 9:16 first

The format problem nobody talks about

When we started Clipr, the obvious problem was clear: long-form sermons and podcasts sit unused on a hard drive while TikTok, Reels, and YouTube Shorts are where actual reach lives. Every creator we spoke to knew this. But we kept hearing the same friction point, buried in every conversation. It wasn't 'I can't find the good moments.' It was 'even when I find them, turning them vertical is annoying.'

Desktop video editors make you juggle timeline layers, aspect ratios, and canvas resizing. Mobile editing apps are fiddly. And if you're a pastor or church social media manager, you've probably got thirty other things on your plate. The vertical reformat wasn't the headline problem, but it was the one that killed momentum. People would find a clip, see it was 16:9, and just... not bother.

We could have made finding moments the star feature. Let the AI identify the best 90 seconds, export an MP4, and call it done. But that export would still be landscape. It would still need work. It would still sit in a folder, unused.

Why 9:16 became the first brick

Here's what changed our thinking: a vertical clip ready to post is not the same thing as a vertical clip that needs finishing. One is friction. One is ready. We decided that every single clip Clipr exports should land in your phone's photo library already cropped, already pillar-boxed if needed, already in the exact format you upload to TikTok. No extra step. No fiddling.

That meant Auto vertical 9:16 couldn't be a bonus feature. It had to be foundational. The moment our scoring service identified a great clip, it had to reformat it in the same breath. If you export a clip, you get vertical. If you batch five sermons (that's a Pro feature), you get five vertical clips, ready to queue up and post.

Some of our early testers asked if we'd keep landscape as an option. We said no. We meant it. Adding landscape mode would make the feature optional, and optional means creators forget about it, which means they edit manually somewhere else, which means Clipr becomes one step in a longer workflow instead of the whole thing.

The cost of getting it right

Building Auto vertical 9:16 was harder than it sounds. A sermon recorded on a camera uses the full frame. Chopping it to 9:16 either crops your speaker's head off, or it pillar-boxes and leaves black bars on either side. We tested both approaches. The pillar-boxes won. They're honest. They say 'this is the moment that matters' instead of pretending the whole frame is interesting.

We also had to think about captions. A vertical clip with captions needs font sizes and positioning that work on a 390-pixel-wide phone screen, not a 1920-pixel monitor. So we baked the captions in, auto-sized and placed them intelligently. That feature sits in Creator tier and above. The free version still gets vertical reformatting, just without burned-in text.

And watermarks. The free tier includes a small Clipr watermark; Creator and Pro don't. Why? Because if your first experience with Clipr is posting five free clips to your church's Instagram with a watermark on them, you might not feel like it's yours. Watermark-free export, even on free tier eventually, respects that these are your sermons, your content, your ministry.

The broader choice

Building Auto vertical 9:16 as the core feature said something about what Clipr is. We're not trying to be a general-purpose video editor or a TikTok automation tool. We're saying: if you have a sermon, a podcast, a long talk, we will find the moments and hand them back to you in the exact format you need, right now, ready to share.

That's a specific promise. It means we're not trying to do everything. We're doing one thing well. We're not adding desktop exporting or social platform connectors or trending sound matching, because none of that helps if the clip isn't already vertical and in your hands.

It also meant betting early on Apple's on-device speech transcription. We could have used cloud transcription, which might be marginally more accurate, but then every file would need to leave your phone and hit our servers. On-device transcription keeps your sermons on your device. We rank them server-side for engagement only, which is different.

What we learned from launch

The first week Clipr went live, we watched people use it. The pattern was consistent. Someone would open a sermon file, wait for transcription, see the moments flagged, and then immediately look at the preview. The moment they saw it was already vertical, already framed, already ready, something shifted. The app went from 'let me try this' to 'I can use this right now.'

We also saw what we didn't expect: people batch processing. Pro users uploading five sermons at once, getting back five vertical clips, queuing them to post over a week. That became a real workflow. It only works because vertical formatting is automatic, not optional.

The faith score explanation feature in Pro tier, the batch processing, the unlimited clips on Pro, the iCloud-safe free tier counter - those all came from watching real use. But they sat on top of the foundation we'd already laid. Auto vertical 9:16 is why those features matter, because they're all built for people who don't have time to format videos manually.

The question we still ask

We built Clipr for creators who have sermons but no edit time. Auto vertical 9:16 was the feature that made that possible, because it removed the one format problem that kept people from shipping. But it also raised a question we think about a lot: what other friction points are hiding in your workflow? What feature isn't optional but feels optional because we haven't made it mandatory and automatic yet?

That's how we build. Not with checkboxes. With moments. With the pastor who found a great clip and then gave up because reformatting felt like work.