App Store preview videos in more than one language: what to localize and what to leave alone

What the stores actually let you do

Apple's App Previews page states the limit directly: "You can have up to three app previews for each language your app supports." Previews are attached to a localization in App Store Connect, the same way screenshots are, so a German listing can carry a German preview while the English listing keeps the English one. Nothing forces you to fill every slot; a localization with no preview simply shows the screenshots.

Google Play describes the promo video in its store listing asset guidance as a YouTube URL and asks developers to "provide a localized video tailored for users in different markets". Because the video is a YouTube link on each language's listing, a localized version is a separate upload to YouTube and a separate link in the Console. The other differences between the two stores are in Google Play promo video vs App Store preview.

Both stores autoplay the video with sound off. Apple: "By default, app previews play with the sound muted." Google: "only the first 30 seconds autoplays", muted, on the surfaces that autoplay at all. That single fact settles the localization question for most apps. A voiceover you paid to translate will not be heard by the majority of people who see the preview. The text on screen will. (We wrote a separate piece on making a video work with the sound off.)

What changes per language, and what does not

Split a preview into its layers and the answer becomes obvious.

The screen recording is the base. If your app is localized, record it in each language you plan to publish, because a German preview showing an English interface looks like a mistake. If the app is English only, the same recording serves every listing, and the localization lives entirely in the layers above it.

The on-screen text layer is the part that always changes. Titles, feature callouts, the closing line with the app name: every word of it. Short text is the rule here, since a caption that fits in two seconds in English tends to grow by a third in German or Finnish. Write the English version with room to grow, or plan a slightly longer hold on each card.

The narration layer is optional. Because autoplay is muted, we only localize a voiceover when the video also runs somewhere with sound on, such as a paid ad or a landing page. For the stores alone it is money spent on something few people hear.

Music does not change. Neither do the transitions, the zooms, the background colours or the pacing. That is why a properly built master file makes the second language almost free.

One master, many exports

The workflow we use, and the one we would suggest to anyone editing in-house:

1. Cut the master in the primary language, with every piece of text on its own layer or track, never baked into the footage.
2. Export a text sheet from the timeline: card number, time in, time out, English text, character count.
3. Have the sheet translated by a person who knows the app. Machine output is fine for a first pass, but "Sync" and "Share" are exactly the words that come back wrong.
4. Duplicate the text layers per language, paste the translations, and check every card at its actual on-screen size. Long strings get a smaller size or a longer hold, never a smaller safe area.
5. Swap in the localized screen recording if the app is localized.
6. Export one file per language to the store's spec, and pick the poster frame for each.

The whole second-language pass usually takes less time than the first review of the English cut, because every creative decision has already been made.

Which languages deserve their own preview

Not all of them, at least not on day one. A quick way to decide:

App Store Connect's analytics show impressions and downloads per territory, and Google Play Console shows them per country, so the numbers for that first row are already in your dashboards. Territory is not language, but it is close enough to rank the work.

There is one more reason to localize the preview that has nothing to do with numbers. A listing where the screenshots speak German and the preview speaks English tells a German user the video was an afterthought. Half-localized listings read as less trustworthy than fully English ones.

Details that trip people up

The poster frame is chosen per preview, which means per language. It should show the same screen in the same language as the video, and Apple's page warns that changing it later requires a new submission of that preview. Choose it when you export, not after launch.

Right-to-left languages mirror the interface, and a preview that pans left to right through an Arabic or Hebrew app feels backwards. Record the app in that language and let the motion follow the layout.

Numbers, dates and currency formats live inside your app's screens. A preview recorded with an English build might show "9/30/2026" to a French listing, which is a small thing that a careful reviewer or a picky user will notice. Recording in the target language fixes it automatically.

Prices are not allowed in previews in any language, so a paywall screen has to be cut or blurred in every version, not only the English one.

Google Play's rule about the first 30 seconds applies to each localized YouTube video separately, so a longer localized cut needs its in-app content up front just like the original.