Why Making a Good App Store Preview Video Is So Hard
App Store preview videos are one of the highest-impact conversion tools available. Apps with preview videos convert better than those with only screenshots. Yet most indie developers either skip the video entirely or produce something that hurts more than it helps.
The problem isn't that developers don't care. It's that making a good preview video is genuinely, surprisingly difficult.
The Resolution Nightmare
Apple requires preview videos to match the exact native resolution of each device. Not approximately. Exactly.
| Device | Resolution |
|---|---|
| iPhone 16 Pro Max (6.9") | 1320 × 2868 |
| iPhone 16 Pro (6.3") | 1206 × 2622 |
| iPad Pro 13" (M4) | 2064 × 2752 |
One pixel off — rejected. No helpful error, no automatic scaling. Most screen recording tools don't default to these resolutions, so you're fighting your tools from step one.
And you need separate uploads for each device size — at minimum 2 for iPhone, plus iPad if you support it. Three preview videos across 3 device sizes means 9 individual video files.
The Localization Multiplier
Now multiply by languages. If your video has text overlays and your app supports 10 languages:
3 preview videos × 3 device sizes × 10 languages = 90 video files
Most indie developers look at this math and upload English-only videos for two device sizes. Rational, but it means losing conversion in every non-English market.
Apple's Content Restrictions
Apple has strict rules about what can appear in a preview video:
- Only footage captured from within the app — no live-action, no external cameras
- No pricing information in the video
- Device frames must be accurate — current Apple devices only
- No misleading content — must represent the actual app experience
- 15–30 seconds only — every frame has to justify its existence
These restrictions eliminate many common video shortcuts. You can't splice in lifestyle shots or add a dramatic logo intro. Every frame must come from the running app.
Why Your App Looks Worse on Video
Some apps look great in use but terrible on recording:
- Interaction-driven apps: the satisfaction of a swipe or gesture doesn't translate to video
- Subtle animations: 120fps scrolling on device becomes jerky 30fps in a compressed video
- Text-heavy apps: a video of someone reading isn't compelling, fast scrolling makes text unreadable
- Dark mode: often results in crushed blacks and banding after compression
Text Overlays: Simple in Theory, Brutal in Practice
Short phrases like "Track your habits" seem simple but create real problems:
- Timing: at 30 seconds total, your margin is fractions of a second
- Readability: text must be large enough to read on a phone screen inside the App Store
- Localization: "Track your habits" fits one line in English — the German translation might be twice as long
- Background music adds another layer: licensing, mixing, mood matching, clean start/end within your timeline
Tools That Solve Most of These Problems
If you don't want to fight resolution requirements, text overlay timing, and localization manually, App Preview Studio is a macOS app built specifically for this workflow. It handles export validation for every device size, lets you add text overlays and background music, and supports localization — so you produce one project and export all the variants you need.
What Most Indie Developers Actually Do
Given all these challenges, most solo developers produce:
- Screen recording from the simulator at the required resolution
- One take, minimal editing — tap through the main flow, trim dead space
- No text overlays, no music — just the raw app
- English only, 2 device sizes
This takes 2–4 hours instead of 2–4 days. Functional but rarely compelling.
Quick Tips If You're Doing It Manually
- Record from a physical device — real scrolling physics look more natural than simulator
- Plan your shots before recording — write down exactly which 4–5 screens to show, in what order
- Use simple text overlays — even static white text on a dark semi-transparent background dramatically improves a video
- One message per scene — "175+ countries" on a map, "Instant alerts" on a notification. Don't explain everything
- Add device frames — makes it look intentional. App Preview Studio applies these automatically
- Skip localization initially — add localized videos later if conversion data justifies it
Monitor What Users Think After They Download
A great preview video gets downloads. But if users feel the preview oversold the experience, they'll say so in reviews. AppStoreReview monitors reviews across 175+ countries and alerts you instantly — so you catch "not what I expected" feedback early.
Frequently Asked Questions
What resolution does an App Store preview video need to be?
Apple requires preview videos to match the exact display resolution of the target device. For iPhone 16 Pro Max that's 1320×2868, for iPhone 16 Pro it's 1206×2622. Videos must be H.264 or HEVC, 30 fps, and 15–30 seconds long. One pixel off and the upload is rejected.
Can I use one preview video for all device sizes?
No. Apple requires separate videos for each display size category. At minimum you need videos for the 6.9-inch and 6.3-inch iPhone displays. If you support iPad, that's additional sizes. Most developers need 2–4 versions of every preview video.
Do I need to localize my preview video for every language?
Apple allows different preview videos per localization. If your video has text overlays or voiceover and you support 10 languages, you technically need 10 versions per device size. Most indie developers skip this and upload English only.
Are there tools that make App Store preview videos easier?
Purpose-built tools like App Preview Studio handle resolution matching, device frames, text overlays, background music, and localization in a single workflow. The alternative is professional video editors like After Effects or Final Cut Pro, which give full control but require significant video editing skills.