Explaining an app feature in a vertical video

Software is hard to show in a vertical ad. There is no box to unwrap and no surface to light. What you have is a screen, a problem the screen solves, and a few seconds to make someone who was watching something else care. This article is about doing that for one feature at a time, with a presenter who says what the feature does while the screen appears alongside the words.

Pick one feature, not the product

The most common mistake in software video is trying to explain the product. A product has a dozen features and a pricing page; a 30-second vertical video has about 75 spoken words. Pick one feature that solves one recognizable problem, and make the video about that.

A good candidate feature:

• Solves a problem the viewer would describe in the same words you would.
• Has a result you can state in one sentence.
• Looks like something on a screen (a view, a button, a before and after), so there is a picture to show.

"Our platform helps teams collaborate" is a product pitch. "Turn a messy email thread into one task with a single click" is a feature. The second one makes a video.

The screenshot is your product photo

In an e-commerce ad, the product clip comes from a product photo. For software, the equivalent is a screenshot. Clipelle generates one product clip from the image you upload, with slow camera moves, and lays it over the presenter at fixed moments. So the screenshot you pick is the picture the viewer will see.

What makes a good one:

• Portrait or square if you can. The final video is 9:16. A wide desktop screenshot in a vertical frame leaves little room; a phone screen or a cropped section of the desktop view fills it better. See vertical video, explained once for the frame math.
• The feature in its finished state. Show the result, not the empty form. A completed task, a filled chart, a message that says "Done."
• Realistic but clean data. Fake names that look fake pull attention. Plausible names, no personal data, nothing you would not want a stranger to read.
• Large type. Whatever text is on the screenshot will be small on a phone. If a label matters, make it bigger in the screenshot before you upload it.
• No clutter. Hide notifications, close extra tabs, use a neutral background.

If your product is a mobile app, a screenshot from the phone itself is often already perfect. If it is a desktop tool, crop to the part of the screen where the feature happens.

Writing the spoken part

The structure that works for physical products works for software: hook, problem, product, benefits, call to action. The difference is that "the product" is one feature and the benefit is almost always time, clarity or fewer mistakes. A spoken ad script in 75 words covers the shape; here is how it bends for an app.

Hook with the moment, not the category. "Ever lose a task because it was buried in an email?" works. "Looking for a project management tool?" does not; nobody is, at least not while scrolling.

Problem in the user's language. Describe the annoying Tuesday, not the market gap. "You copy the request into your to-do list, then forget which thread it came from."

Name the feature and show it. This is where the screenshot clip appears. "With Thread to Task, one click turns the email into a task that keeps the link to the conversation."

Two benefits, concrete. "Nothing gets lost, and anyone on the team can see where it came from."

A call to action that fits software. For an app, the next step is usually "try it free" or "download." Keep it to the words; there is no button in the video, so the sentence has to say it. If you have a trial length or a deal, put it in the Offer line on the form; that is the only way it reaches the call to action.

Here is a full example, 69 words:

Ever lose a task because it was buried in an email? You copy it to your list, then forget which thread it came from. Thread to Task fixes that: one click turns the email into a task that keeps the link to the conversation. Nothing gets lost, and the whole team can see where it started. Try it free for fourteen days at the link below.

Tone and presenter for a software audience

Software buyers are often watching with the sound off at work. Two things follow.

First, the captions do most of the work. In a Clipelle video, the only text on screen is the captions of what the presenter says, with the current word highlighted in your accent colour, plus an optional small logo in the top right. There are no text cards to fall back on, so the spoken sentences must read well as captions. Short sentences help. So does avoiding jargon that reads fine but sounds odd aloud.

Second, the tone should match the product's seriousness. Clipelle offers four tones (elegant, playful, direct, warm). For most B2B features, direct is right: it keeps the sentences plain and the claims clear. Playful fits consumer apps and anything aimed at a younger audience. Pick the presenter the same way: a neutral, professional look rather than the most striking one. Standard quality is the recommended starting point; Premium adds more natural head and hand movement and the best lip-sync at a higher cost per second, which matters more in slow, close-up ads than in a quick feature explainer.

Use the Direction field (up to 200 characters) to tell the script who the viewer is and what to emphasize: "Audience: operations managers at small agencies. Emphasize: no setup, works with the inbox they already have."

A series, not a single video

One feature per video has a second advantage: you end up with a series. Five features, five 30-second videos, the same presenter, the same caption style, the same logo in the corner. Together they explain the product better than one long video would, and each one can be tested on its own.

Clipelle stores brand defaults in Settings (accent colour, caption look, font, logo) so every video in the series comes out matching without retyping. If your team would rather create these from a script or an assistant than from the form, there is an API and an MCP server that create the same projects with the same options.

A short checklist for a feature video

Before you click Generate:

1. One feature, one problem, one result.
2. A screenshot that is vertical or square, shows the finished state, has large type and no clutter.
3. A hook about the viewer's moment, not the product category.
4. Two concrete benefits, no jargon.
5. A call to action that names the next step (try, download, start) and, if you have one, a trial or offer in the Offer line.
6. Tone set to match the product; Direction filled with audience and emphasis.
7. "Review script first" on, at least for the first few, so you can pick the hook and fix any term the script got slightly wrong.

The Apps and SaaS page describes how teams use this for launches, release notes and onboarding. The pattern is the same every time: one screenshot, a few sentences, a presenter who explains it in under a minute.