Mobile app preview video resolutions
Choose the upload family in App Store Connect. These are accepted video export sizes, which can differ from the device's screen pixels. This table covers the listed iPhone and iPad families; check Apple's full reference for other platforms and future upload support.
| Upload family | Portrait pixels | Landscape pixels |
|---|---|---|
| iPhone 6.9 / 6.5 / 6.3 / 6.1-inch | 886 × 1920 | 1920 × 886 |
| iPhone 5.5 / 4-inch | 1080 × 1920 | 1920 × 1080 |
| iPhone 4.7-inch | 750 × 1334 | 1334 × 750 |
| iPad 13 / 11 / 10.5-inch | 1200 × 1600 | 1600 × 1200 |
| iPad 12.9-inch (2nd generation) | 1200 × 1600 900 × 1200 | 1600 × 1200 1200 × 900 |
| iPad 9.7-inch | 900 × 1200 | 1200 × 900 |
Choose the upload family before setting the canvas
Keep the intended App Store Connect slot beside the export settings. A native device recording can have a different pixel size from the accepted preview asset. Selecting a similarly shaped canvas is not enough; compare the exact width and height. The table groups mobile families that share accepted export sizes. Its scope excludes other platforms, future upload availability and the store's scaling decisions. Consult the linked reference and your console when the intended family is not listed.
For a fictional notebook, give each export a destination such as portrait phone preview or landscape tablet preview. Keep a separate source recording and rendered output instead of overwriting the captured footage. If a designer sends the raw recording, the dimensions may explain why it is not ready for the selected slot. Return to the editor and render an appropriate output. Do not stretch the UI merely to make the numeric check pass; inspect the resulting view for distorted text and controls.
Use exact file properties, not the export preset's name
Read the finished file's properties after rendering. The manual form compares entered dimensions, duration, frame rate, size and a selected format combination. The size field uses decimal megabytes and states that interpretation in the report. If a properties window rounds the display, find the exact byte count and divide it by one million before entering the size. A preset label or an estimated export size is not evidence of the resulting file's properties.
The encoding and extension fields describe different parts of the export. Apple's listed combinations include H.264 with the listed movie extensions and ProRes 422 HQ with MOV. A filename alone cannot identify its encoding, and renaming an extension is not conversion. A matching manual result still leaves encoding profile, progressive scan, bitrate, audio configuration and enabled tracks to inspect against the source reference. Record which settings were observed and which checks remain pending. The form never turns an assumption about the codec into a detected property.
Tell one product story that survives muted playback
Apple describes app previews as footage of the app and notes that playback is muted by default. Start your production brief with one supported journey: the starting screen, action, visible response and outcome. A fictional walking notebook could show saving a route note and finding it in the journal. Keep captions readable and leave enough time for someone unfamiliar with the product to understand each step. Review the clip without audio before relying on narration to explain a transition.
Use an original comprehension exercise before the store submission. Show the clip to a fresh reader, then ask what they expect to do after installing. Write down their words before supplying the intended answer. If they expect navigation while the app only stores notes, inspect the caption and scene sequence. Include the actual login or purchase boundary when it affects the shown task. This informal exercise tests understanding; it does not predict conversion, prove search demand or replace a store experiment. Review authorization for footage and other displayed content separately.
Preserve the export, poster frame and review record
Give the rendered file a versioned name and record the build, locale, destination, observed properties and source capture. Keep the original when testing a new edit. The poster frame is another decision: inspect the selected still as an explanation of the app when the video does not play. A frame in the middle of a transition may satisfy a timestamp choice while communicating little. Review the still and the clip as separate views of the same supported task.
After uploading, inspect the console's processing and validation feedback rather than interpreting this form as approval. Confirm the intended destination and localized presentation, and leave failed or unanswered checks in the handoff. A useful record might say entered dimensions matched; audio configuration verified in editor; console processing pending. If you later change the poster frame or edit the sequence, update the record so the next reviewer knows which file was examined. Keep any later traffic or conversion report's source and filters separate from these technical and comprehension observations.
Working example
Fictional export handoff: a small note-app team sends a native phone recording with a duration just above the listed maximum. The designer checks the intended mobile upload family, revisits the edit and renders a new file. The owner enters the finished file's exact properties in the form; the covered checks now match. Someone independently checks encoding and audio settings, reviews the clip muted and chooses a poster frame showing the saved note. The team uploads that version and records console feedback. This example has no measured download, ranking or conversion result; it illustrates a traceable handoff rather than a universal export preset.
Your next steps
- Record the mobile upload family and accepted preview resolution.
- Read exact properties from the finished file before entering the form.
- Review encoding, audio, footage, muted understanding and poster frame separately.
- Preserve the rendered version and inspect console processing and validation.
Questions about this guide
Can I upload my native screen recording as an App Store preview?
Compare it with the accepted preview size for the intended upload family. Native screen pixels can differ. The table covers listed mobile families; validate the actual export and console feedback.
Does this form inspect or upload my video?
No. It checks numbers and format choices you enter. No video is uploaded. The private result is not cached or saved as an export record.
Does a matching export check mean Apple will accept it?
No. The result covers entered values only. Encoding details, audio, file integrity, footage, poster frame and store validation still need review.
Can I fix the format by renaming a file extension?
No. A filename change does not alter encoding. Render a new export using the intended settings and inspect its actual properties.
Official sources
Sources checked October 5, 2026. Review the current provider documentation before acting on requirements.
Turn the next test into something useful.
Publish a focused brief on RateMyApp. Credits fund approved private reports; public store reviews are voluntary and unrewarded.
List your app for feedback