BlogLocalization

App Store and Google Play preview videosevery size and language from one master

4 min read

Apple allows up to three preview videos for each device size and language (Apple). An app with iPhone and iPad previews in ten languages can therefore keep up to 60 of them, plus a Google Play video for every market. Since October 2026 there are more surfaces to fill: a 21:9 header video at the top of the product page, a silent 3:2 video in search results, and in-app event cards that take 15 to 30 seconds of video, and custom product pages, up to 70 of them, can now appear in organic search for the keywords assigned to them (MobileAction).

Made by hand, that many videos rarely stay current, and markets end up watching an old version of the app in a language they don't read. The way to keep them current is to build one master and make everything else from it. Here's how, store by store.

What each store requires

App Store previews run 15 to 30 seconds, up to three per device size and language, as H.264 or ProRes files of up to 500 MB at no more than 30 frames per second. Each device size has its own accepted resolutions, and the poster frame defaults to the frame five seconds in (Apple).

The new App Store formats, live with iOS 27, add their own shapes. The product page header video is 21:9 at 3840×1646 and runs 5 to 30 seconds. The search results video is 3:2, plays muted and can't be unmuted. Apple Ads plans search-results video ads in the same 3:2 shape, without audio. These assets can be reused across the default page, custom product pages and in-app events, and each custom page built for an audience or a keyword wants a video that speaks to it.

Guideline 2.3.4 is the rule that matters most. Previews may only use video screen captures of the app itself. Narration and text or video overlays are allowed to explain what isn't clear from the screen, but AI-generated scenes, stock footage, avatar presenters and shots of people tapping a phone get previews rejected (Flowjam).

Google Play takes one YouTube link per listing, public or unlisted, with ads turned off, in portrait or landscape. Only the first 30 seconds autoplay, muted, and the video appears before the screenshots and on some home, search and recommendation surfaces, so the opening has to work alone (AppLaunchFlow).

Making the master

Apple's rule decides how the master is made. The footage has to be screen recordings of the app, so no tool that generates scenes or presenters can make an App Store preview, however good the result looks. Generation has a place only on top of the screens: captions, callouts, motion graphics that point at what matters, transitions and music.

Choose the flow to show. For most apps that's the moment the product does its job: the result screen, the progress chart, the level clearing. Make the master in one language and one size, and get it approved. Spend the most time on the opening: the frame at five seconds is the App Store's default poster frame, the first seconds are what autoplays on Google Play, and the 3:2 search video has to sell without sound.

Making every version from it

Every surface and size. Each format, device size and orientation needs its own layout. Place the recording for the frame and lay the captions out again around it rather than scaling them down, so they stay readable on a phone and don't cover the part of the screen they explain. A 21:9 header puts the app beside its captions rather than under them; a 3:2 search video needs captions sized for a thumbnail. iPad previews need iPad recordings, since Apple wants the app as it runs on that device.

Every language. Translate the captions and let the layout reflow for longer or shorter lines. If the app is localized, record the screens in that language too, because a German caption over an English interface tells a German viewer the app isn't really in German. Run each language through the QA checklist before it goes live.

The second and third slots. They're worth using. The extra previews can open on different features or moments of the same flow, with a different first five seconds, and custom product pages can each lead with the feature their audience came for.

Updating previews when the app changes

A preview goes out of date with every release that changes a screen it shows. Record the new screens and replace them in the master, keep the approved captions, callouts, music and timing, and remake the layouts and languages from the new recordings. A new market works the same way: the master's captions translated over that language's recordings. Word and trivia games have one more layer, since the board itself is in the language (animated type for word games).

Building the master in Motn

Motn keeps the screen recordings as footage that's never generated again, so the master meets the same rule a plain screen recording does, and Claude writes the captions and callouts over it as live code. Each surface, device size and language is laid out from that master in one workflow; each language's recordings are swapped in with the master's captions, timing and motion kept; and a release means replacing the recordings, not rebuilding sixty previews. The same approach to real screens drives product demos that update with the app.

A good first test is your main iPhone preview: rebuild it from fresh recordings, make the second and third slots and the new 21:9 and 3:2 videos from the same master, and add the languages where your store page gets the most traffic. More for subscription apps is in Motn for apps.

Make yours on Motn.