Most developers upload video previews that nobody watches. They record 30 seconds of scrolling through their app, add background music, and hope the algorithm rewards them. It doesn't work that way.

A video preview is not a demo. It's a conversion asset — a 15-second pitch that answers "Why should I download this?" before the user scrolls past your listing.

This guide covers how to produce video previews that actually move the needle.

What Is an App Store Video Preview?

The App Store video preview is a short video that plays inline on your listing — above your screenshots. When the page loads, it auto-plays (muted) and loops. Users can tap to unmute and expand it.

Apple's research shows that listings with a video preview see up to 40% higher conversion rates compared to those without. That's significant — but only if your video is actually good. A mediocre video performs worse than no video at all.

The preview is not indexed for search ranking. It doesn't affect discoverability. Its only job is conversion — turning visitors into installers.

Video Preview Specs and Requirements

Get these right or your video gets rejected:

Property	Requirement
Duration	15–30 seconds
Format	H.264 video, AAC audio, .mp4 container
Max resolution	1920 × 1080 px (HD)
Orientation	Portrait (for iPhone), landscape (for iPad) — match your screenshots
Max file size	500 MB
Audio	Optional. Most users watch muted. Design for silent playback.

Important constraints:

No voiceovers — Apple explicitly requires that videos contain no voiceovers or spoken narration
No text overlays — Apple does not allow burned-in text or captions within the video itself
Show actual app usage — no stock footage, no external branding, no URLs, no calls to action
Show the app running — screen recordings of your app in action. No animations, no mockups, no promotional footage

These constraints are intentionally strict. Apple wants the video to show real app functionality — not a marketing ad. Work within these rules, don't fight them.

The Three-Act Video Framework

Your 15–30 seconds need structure. Use this three-act format:

Act 1: Hook (0–3 seconds)

Show your app's strongest visual moment immediately. No intro, no logo animation, no title card. Start with the feature that looks best or solves the biggest problem.

Good opening: A workout app that starts with a timer counting down and a smooth animation showing a completed set.

Bad opening: A logo fade-in, then "Welcome to FitPro" text, then a slow pan to the home screen.

Three seconds is all you get. After that, the user scrolls.

Act 2: Flow (3–15 seconds)

Show 2–3 key actions flowing together. The goal is to demonstrate how the app works through visual storytelling, not explain every feature.

Pick a single user journey and follow it through:

A budgeting app: open dashboard → add a transaction → see the category chart update
A meditation app: select a session → start breathing exercise → see progress ring fill
A photo editor: load a photo → apply a filter → export the result

Each transition should be smooth. Cut dead air. Speed up slow interactions. The user should see cause and effect — their action, your app's response.

Act 3: Resolution (15–30 seconds)

End on a satisfying visual moment: a completed task, a beautiful result, a progress summary. This leaves a positive impression as the video loops back to the start.

Good ending: A receipt-scanning app that ends with a clean, organized expense report.

Bad ending: The video stops mid-action or on a blank loading screen.

Editing Your Preview for Maximum Impact

Raw screen recordings don't convert. Edit aggressively:

Cut dead time — loading screens, typing, waiting, empty states. Use jump cuts. If a transition takes 2 seconds, cut it to 0.5. Users don't care about realistic timing.
Speed up slow interactions — if an animation takes 5 seconds, compress to 2. Aim for at least one meaningful action per second.
Add motion graphics — since Apple forbids burned-in text, use highlight boxes, zoom-and-pan, and arrows to guide attention. These are visual cues, not text — they're allowed.
Choose background music carefully — most users watch muted, but pick a track that matches your app's mood and is royalty-free. Epidemic Sound or Artlist work well.

When to Use Video vs Screenshots

Video preview is not mandatory. It's optional. Here's when it makes sense:

Use a video preview when:

Your app has complex interactions that are hard to capture in static screenshots (animations, gestures, real-time features)
Your primary value is visual — photo editing, video creation, AR experiences
You want to show the app's "feel" — smoothness, responsiveness, polish
Your screenshots already cover the key features and the video can show the flow between them

Skip the video preview when:

Your app is simple and screenshots communicate everything clearly
You don't have the time or resources to produce a quality video
Your app's value is text-based or data-heavy (reading apps, reference tools)

A well-made video preview lifts conversion. A rushed, low-effort video hurts it. If you can't commit to quality, invest in screenshots instead.

A/B Testing Video Previews

Like promotional text, video previews can be updated without submitting a new binary. This means you can experiment.

Testing approach:

Run your current video for 2–4 weeks — establish a baseline conversion rate in App Store Connect
Create a new variant — different opening hook, different user journey, different editing style
Swap the video — upload the new version and run it for 2–4 weeks
Compare conversion rates — a 3-5% improvement justifies the effort

What to test:

Opening moment — does starting with your most visually impressive feature beat starting with your most useful one?
User journey — does a different flow (e.g., "import → edit → export" vs "browse → select → apply") perform better?
Pacing — does a faster-cut 15-second video beat a slower 30-second version?

Common Video Preview Mistakes

Starting with a logo or branding. Your brand is already visible — your app icon and name are above the video. Wasting the first 2 seconds on a logo is leaving conversion on the table.

Showing too many features. A video that tries to cover 6 different features covers none of them well. Pick one core journey and follow it.

Including text or narration. Apple will reject it. Don't risk a submission delay — design the video to communicate visually.

Ignoring silent playback. If your video requires sound to make sense, it's failing. 80%+ of users watch muted.

Uploading a raw screen recording. No editing, no pacing, no structure. It looks unprofessional and kills trust.

Forgetting to update. If your app has changed significantly, your old video shows outdated UI. An inaccurate video confuses visitors and increases bounce rate.

Production Workflow

Here's a practical workflow for creating a video preview:

Script the journey — write down the exact sequence of interactions you'll show (3-4 actions max)
Record on device — use QuickTime screen capture on macOS with a connected iPhone, or use Xcode's built-in screen recorder
Edit in a NLE — use Final Cut Pro, DaVinci Resolve, or Premiere Pro to cut, speed up, and add motion graphics
Export as H.264 .mp4 — 1920 × 1080, 30 fps, AAC audio
Upload to App Store Connect — go to your app → App Information → App Preview Videos
Verify on a real device — check how it looks on an actual iPhone in the App Store before going live

LaunchPilot's metadata editor helps you track and manage your App Store Connect metadata alongside your creative assets — explore the features if you manage multiple apps and locales.

Quick Reference Checklist

Use this before uploading your video preview:

App Store Video Previews: How to Make Them Convert (Not Just Exist)