For Apple developers
Prepare better App Preview assets.
Choose clear source material before editing so the finished App Preview feels polished and easy to follow.
Native qualityRecord at the best available resolution
Clean stateUse a prepared, repeatable app setup
Muted firstAudio should never carry the story alone
Rehearse firstPractice before capturing the final take
Good edits start with good source material.
Asset Recommendations help you prepare the recordings, screenshots, audio, and app state that make an App Preview easier to edit and more accurate to watch.
Use captured app experience, not live-action or promotional footage. For AR or visionOS, follow Apple's platform-specific guidance when environmental context is necessary to show a feature accurately.
Screen recordings
- Capture the real app at native UI resolution for the target device and orientation.
- Record one feature or task per clip.
- Move slowly and deliberately.
- Avoid accidental taps, gestures, and visible hesitation.
- Start before the interaction begins and stop a few seconds after it ends.
Short, focused clips give you more control during editing. They are easier to trim, reorder, and replace when the app changes. Use touch indicators only when they clarify a real interaction.
Screenshots
- Use screenshots that accurately match the submitted build and show real in-app UI.
- Keep text large and readable.
- Avoid outdated UI, placeholder content, unfinished states, marketing art, and device mockups.
- Use screenshots to introduce a feature or create a deliberate pause between recordings.
Recordings should remain the main source for an App Preview. Use still app captures sparingly and validate the final preview before submission.
Audio and voice over
Music
Music is optional. Choose something subtle that supports the experience rather than competing with it. Keep the volume low, and use only audio you have the right to include in every territory.
A good starting point with a large library of royalte free assets is pixabay.com
Sound effects
Use sound effects sparingly to reinforce an important action or transition. Keep them short, subtle, and consistent. Effects and transitions must not imply functionality or performance the app does not provide.
Voice over
Voice over is optional. Explain the benefit, not every tap. Speak naturally, keep the pace conversational, and leave short pauses between ideas. Do not make claims the footage does not prove.
The App Preview must still make sense muted. Support important audio with the right visual context or a short caption. Localize voice over and on-screen copy for each preview locale, avoid prices, dates, and seasonal claims, and disclose any login, subscription, or in-app purchase requirement for a feature you show.
App content and device state
App content
- Use fictional, believable data whenever possible.
- Remove personal information, notifications, permission prompts, debug content, and unfinished UI.
- Record from a stable, release-quality build with a repeatable starting state.
- Show only licensed content that is appropriate for all ages.
Device appearance
- Record on a clean device with Do Not Disturb enabled.
- Use a charged device so low-battery warnings do not interrupt a take.
- Keep the status bar consistent across recordings when it is visible.
Before you start recording
- Plan the story first.
- Plan the target device, locale, and orientation before capture.
- Record more clips than you think you need.
- Re-record a clip when the interaction is not clean. It is usually faster than fixing it later.
Remember
It is easier to make a clear App Preview when every recording begins with a prepared app, a practiced interaction, and a clean final state.
Create your App Preview