TL;DR. Apple auto-plays your preview video, muted, in App Store search results before the user taps into your listing. The first three seconds run in a loop on the results page. Most indie iOS apps ship with no video at all, which means screenshot statics compete against animated previews from well-resourced competitors. A short, hook-first preview video is one of the highest-leverage ASO moves available to an indie developer and requires no production budget to make.

What a preview video actually is

An App Store preview is a short video (up to 30 seconds) that Apple shows in your app’s screenshot gallery on the product page and, more importantly, in search results.

In search results, the video auto-plays muted and loops. The user sees it before they tap. Before they read a word of your subtitle. Before they look at a screenshot. The video is running.

This is a different format from a marketing video or a demo. It is not about storytelling or brand. It is about converting a search impression into a tap, in the three seconds the user’s eye crosses your listing while scrolling.

Why most indie apps skip it

Three reasons come up consistently when you talk to solo developers about preview videos.

“It takes too long to make.” This is true if you approach it as a production video. It is not true if you approach it as a 15-second screen recording with a text overlay.

“I don’t have the design skills.” A screen recording of your app in use, captured on a real device, with a short caption in the first three seconds, performs better than a polished motion graphic that shows the app in action too late. Execution quality helps, but it is not the gate.

“I’m not sure it matters.” This is the one worth correcting. Animated content in a list of static screenshots draws attention. That is not an opinion; it is how the visual system works. The auto-play format exists because Apple knows it drives taps.

What happens in the first three seconds

Search results play your video in a cropped, small format. The first three seconds is what most users see before they scroll past.

That means the first three seconds must do one thing: communicate what the app does and why it is worth a tap. Not your logo. Not a loading animation. Not a generic “welcome” screen.

Examples of strong openings:

  • The app’s core interface showing the primary action (e.g., a timer running, a word count climbing, a habit being checked off)
  • A one-line text overlay stating the core value proposition
  • A before/after if your app produces a visible transformation

Examples of what to avoid:

  • App icon zooming in from black
  • Splash screen or loading indicator
  • Feature tour that starts with settings or onboarding

The rule is simple: if a user who knows nothing about your app would understand what it does from the first three seconds alone, the opening works. If they would not, it does not.

Technical requirements from Apple

Apple has specific requirements for preview videos that differ from screenshots:

  • Format: H.264 or HEVC, .mov or .mp4
  • Resolution: Match your device’s native resolution. For iPhone 15 Pro: 1290 x 2796 pixels portrait, or 2796 x 1290 landscape.
  • Frame rate: 30 fps
  • Maximum length: 30 seconds
  • File size: Up to 500 MB, though typical optimized videos run under 50 MB
  • Audio: Optional. The video plays muted in search results regardless of whether audio is present. Audio only activates on the product page when the user taps the video.

You can upload up to three preview videos per locale. The first video in your gallery order is the one that auto-plays in search results. Position it first.

The screen recording workflow

You do not need a motion design tool to make an effective preview. The workflow for a solo developer:

  1. Record on device. Use the built-in screen recording in iOS Control Center. Record yourself using the app’s core flow, the thing you would show a friend to explain what it does.

  2. Trim to 15 seconds. Shorter is better. The 30-second limit is a ceiling, not a target. A focused 12-second video outperforms a padded 28-second one.

  3. Add one text overlay. Use any video editor (iMovie is free, CapCut is free). A single line of text in the first three seconds stating the value proposition. “Track every workout in under 10 seconds.” “Write one sentence every day.” “Never forget a bill.”

  4. Export at device resolution. Match the resolution Apple requires for your target device. The first device in your screenshots list determines which resolution Apple uses in search results.

  5. Upload via App Store Connect. Under your version’s screenshots section, there is a slot for the preview video at the top. Drag in the file.

The whole workflow takes two to four hours the first time. Subsequent iterations take 45 minutes.

The locale angle

Like every other metadata field in App Store Connect, preview videos are per-locale. The English video will not auto-play for German users unless you upload a German version.

For most indie apps, the highest-leverage move is to get an English (U.S.) preview live first, then add German and French if those are meaningful markets for your app. Japanese requires a separate resolution upload if you are targeting Japanese devices specifically.

The absence of a preview video in a locale is not a neutral state. It means static screenshots compete against animated previews from other apps in that market. Any locale where you have active installs is worth a preview video.

How to measure whether it is working

After uploading a preview video and releasing the version, the signal to watch is impression-to-tap-through rate (what App Store Connect labels as “impressions” versus “product page views” in your analytics dashboard).

If your preview video is working, you will see that rate improve within two to three weeks of the release. The ranking for your core keywords may not change immediately, but the percentage of search impressions converting into product page visits should tick up.

A meaningful improvement is two to five percentage points on impression-to-product-page conversion. For an app getting 10,000 monthly search impressions, that is 200 to 500 additional product page visits per month without any change in keyword rankings or ad spend.

The compounding effect with screenshots

Preview video and screenshots are not separate decisions. The video plays first, and if the user continues to scroll, they land on your screenshots.

This means the screenshots should continue the story the video started, not repeat it. If the video shows the core interaction, the first screenshot can show a specific result or feature detail. The gallery functions as a single narrative arc, not a collection of independent slides.

Apps that optimize the video and screenshot sequence together consistently outperform apps that treat them as separate assets.