Localize Your App Store Preview Video
App store preview videos are often the first thing a potential user sees. They drive installs more than screenshots or written copy, yet many creators ship them in English only. Each app store has strict rules about what you can upload, and each market has different expectations for what a preview should show.
Localizing your preview video unlocks installs in every market at once, but the process is more technical than localizing a YouTube video. Store-specific requirements and locale-specific uploads mean you need a clear workflow before you start. The task involves understanding technical constraints, planning audio and text strategy, then executing a repeatable workflow across your target languages.
Store Requirements and Technical Constraints
Each app store enforces strict limits on video dimensions, duration, codec, and file size. These constraints are non-negotiable, so you must work backward from them when planning your preview video localization.
iOS App Store allows 15 to 30 seconds per preview video, up to 5 videos per app. Apple requires H.264 video codec with AAC audio at 48 kHz sample rate. The maximum file size is 500 MB per video. Aspect ratio should be 9:16 (vertical, portrait) for optimal mobile display, though 16:9 (landscape) or 1:1 (square) videos are accepted.
Google Play Store allows 15 to 30 seconds per video with up to 8 videos per app. Android is more flexible on codec: accepts mp4 or webm formats. Maximum file size is 200 MB per video, which is stricter than iOS. Google also prefers vertical aspect ratio but accepts landscape.
Text overlays add a critical consideration: any on-screen text smaller than 32 points will be illegible when thumbnails render in app store listings. iOS and Android both compress preview videos to small thumbnails during browsing, so small text vanishes entirely to the user.
File Size and Bitrate Planning
If you export from your editing software at high bitrate and then layer dubbed audio on top, you can easily exceed store limits. The calculation is straightforward: video bitrate plus audio bitrate equals total file bitrate. A 25-second video at 8 Mbps video bitrate plus 192 kbps audio bitrate yields a 25.6 MB file, well within limits. But at 20 Mbps video, you are at 62.5 MB, still safe. At 30 Mbps, a 25-second video alone hits 93.75 MB.
Plan your bitrate before you export. For 30-second previews on iOS, aim for 10 to 15 Mbps video bitrate. For Google Play (stricter file size limits), aim for 6 to 8 Mbps. Test your first export: if it exceeds 180 MB on Android or 450 MB on iOS, either lower bitrate by 2 Mbps or trim 1-2 seconds from the video.
Audio should be 128-192 kbps stereo AAC for Apple and 128-160 kbps for Android. Higher audio bitrate adds little perceptual quality in a preview but increases file size. Keep audio conservative unless your app relies heavily on sound (a music player, a podcast app, a voice assistant).
Per Locale Upload Mechanics
Both stores require you to upload separate videos for each language, not a single master video. The store displays the localized version based on the user's device language setting.
iOS workflow: Log into App Store Connect, select your app, then click Localization. Choose a language from the list. Each language section has its own preview video slots (up to 5). Upload your localized video file under each language. The metadata (app name, subtitle, description, keywords) are edited in the same Localization view, in separate fields.
Android workflow: In Google Play Console, go to your app listing, then Store Listing. Scroll to "Language." Each language has its own set of preview videos (up to 8). Upload your localized video for each language. Again, short description and other text are in the same view.
Key mechanics to remember
You upload one video per language per store. If you plan to ship 8 languages on iOS and 8 on Android, you will produce and upload 16 video files total (8 versions, uploaded twice to different stores).
Do not edit multiple language versions in parallel; this creates version-control chaos. Instead, edit a single master video once, then create language variants from that master by swapping audio and text overlays.
Plan file naming carefully. Use ISO language codes: preview-en.mp4, preview-es.mp4, preview-ja.mp4, preview-zh.mp4. This prevents confusion when uploading and makes it obvious which video corresponds to which language in your file system.
Upload in batches, not all at once. Start with your top 3-5 languages (usually English, Spanish, French, German, and one Asian language), let the store cache them overnight, then verify they display correctly on actual devices. Only after that batch is live should you upload your next batch. This limits the blast radius if a video has an audio sync issue or text readability problem.
Choosing Your Text Overlay Strategy
Preview videos almost always include on-screen text: app name, tagline, key features, and call-to-action button. How you localize this text determines whether you need to re-render the video per language or can swap components faster.
Burned-in text vs. native text layers
If you burn text directly into the video file (common in YouTube video editors or basic tools), you must re-render the entire video per language. This is slow: render English, render Spanish, render German. But it is safe, because the text travels with the video file and cannot be edited accidentally in the store.
If you use native text layers in your editing software (Premiere Pro, Final Cut, DaVinci), you can adjust text per language export without re-rendering the entire video. You unlock the text layer, change "Download Now" to "Descargar Ahora," export a new variant, and move on. This approach is 5-10x faster but requires your editing software to support layer-based export.
Decision framework: Which approach to use
Ask yourself these questions in order:
-
Does your editing tool support layer-based export (most professional tools do)? If no, burn text in once and live with the slower workflow. If yes, continue.
-
Is your overlay text language-specific (tagline, CTA, feature list)? If mostly brand elements only (logo, app name), burning in is safer. If most text changes per language, native layers win.
-
Do you plan to update the video frequently (new features, messaging changes)? If yes, native layers save time on every update. If this is a one-shot preview, burning in is fine.
For most creators, the compromise works best: burn in branding (logo, app name as a watermark) once, then use native text layers for language-specific content (tagline, CTA). This gives you safety and speed.
Text sizing and safe areas
Any on-screen text must be at least 32 points to remain readable in app store thumbnails. This is a hard rule, not a suggestion. Test by looking at your text at thumbnail size on an actual phone.
Always export with a visible safe area border, about 10% margin from all edges. App store preview videos sometimes get pillarboxed on older devices or displayed in different aspect ratios. Safe area keeps critical text and visuals visible everywhere.
Localization Workflow: Step by Step
Follow this workflow for each language. Treat it as a checklist to avoid mistakes.
Step 1: Create your master skeleton
Export a single master video with no text overlays and no dialogue. This is your visual template. Include all pacing cuts, transitions, UI screenshots, and visual effects. Save this as master-preview.mp4 in a dedicated project folder.
Step 2: Create language-specific projects
For each language, duplicate your editing project. Name it clearly: preview-es, preview-ja, etc. Import the master video into each project.
Step 3: Add localized text overlays and audio
In each language project:
- Add your language-specific text layers (tagline, feature callouts, CTA button text)
- Import the dubbed audio for that language (more on dubbing below)
- Sync the audio to the video cuts. This is critical: if the dubbed audio is longer than English (common for German, French, Spanish), the audio will bleed into the next cut if you do not trim or add pauses
Step 4: Check timing and sync
Play through the video at normal speed. Verify that:
- No audio cuts off mid-sentence
- No audio bleeds into visual transitions
- Dubbed dialogue should match the timing of the speaker's pauses and gestures; exact synchronization is not required for preview videos, but close enough matters
- Text appears and disappears at the right moments
If audio is mismatched, either trim the dubbed audio slightly, extend a visual beat, or ask for a re-dub at a slightly slower pace.
Step 5: Test file size
Export once per language. After export, check the file size. If it exceeds 450 MB (iOS) or 180 MB (Android), lower bitrate by 2 Mbps and re-export. Do this before uploading to the store, not after.
Step 6: Test on an actual mobile device
Download each exported video to your phone. Play it on the actual device in portrait mode, with sound on, in a dim and bright light condition. Small screens reveal text readability issues and audio level problems that desktop playback masks.
Look for:
- Is text legible? (If it looks small on a 6-inch screen, it is too small)
- Does audio sound clear, or is dialogue muffled?
- Do cuts feel natural, or does audio bleed?
- Does the video play smoothly, or do you see stuttering?
Do not assume export preview matches phone reality. Playback is different.
Step 7: Upload to the store in batches
Do not upload all 20 languages at once. Upload your top 3-5 languages first (usually English, Spanish, French, German, and one Asian language). Let the store process them overnight.
The next day, install your app on a phone with each of those languages set as the device language. Verify that the correct video displays for each language. Only after that check is complete should you upload the next batch.
This staged approach limits the blast radius if a video has a critical problem (low volume, text cutoff, wrong language).
Common Failure Modes and How to Fix Them
Audio runs long and overlaps the next cut
Symptom: The dubbed audio plays correctly on your editing timeline, but when you export, the next visual cut starts before the audio finishes.
Cause: Dubbed languages often expand the source text. Some languages like German tend to require more time to speak the same content than English. If you dubbed at the same pace as English, the audio will run long.
Fix: Ask for a re-dub at a slightly faster pace, or trim the dubbed audio by 0.2-0.5 seconds if the content is not crucial. Do this before exporting the video.
Prevention: When recording your English preview, speak slightly slower than you normally would. This leaves room for longer dubs without overrunning your cuts.
Text is illegible on phone
Symptom: Text looks readable on your computer but blurry and small on a phone.
Cause: You set text size at 16-24 points instead of 32+.
Fix: Increase text size to 32 points or larger. Re-export.
Prevention: Always set text size to 32 points minimum at the design stage. Test on an actual phone before export.
Audio is muffled or distorted
Symptom: Dialogue is hard to hear or sounds tinny in the app store preview.
Cause: Audio bitrate set too low (96 kbps or less), or audio was clipped during dubbing (levels hit 0 dB).
Fix: Re-export with audio bitrate of 160-192 kbps. If the dubbed audio itself is distorted, request a re-dub from your voice provider.
Prevention: Spot-check audio levels during dubbing. Ask your voice provider to deliver audio at -3 to -6 dB peak, with headroom to spare.
Video file exceeds store limits
Symptom: Upload fails with a "file too large" error.
Cause: Bitrate too high (often 25+ Mbps) or video duration is too long (over 30 seconds).
Fix: Lower video bitrate to 8-12 Mbps, or trim the video by 1-2 seconds. Re-export and check file size before uploading.
Prevention: Calculate expected file size before export. Use this formula: (video bitrate in Mbps + audio bitrate in kbps / 1000) * duration in seconds / 8 = file size in MB.
Wrong language appears in the app store
Symptom: A French-speaking user opens your app, and an English preview displays.
Cause: You uploaded the video to the wrong language slot in App Store Connect or Google Play Console.
Fix: Log back into the store, navigate to the language section, and verify each video is under the correct language.
Prevention: Use file naming and checklists. Create a simple spreadsheet: Language, Video File, iOS Upload Status, Android Upload Status. Check each off as you upload. This takes 5 extra minutes but prevents mistakes.
Common Mistakes to Avoid
Over-stuffing text: A 30-second preview should have 3-4 key messages, not 10. Each second of screen time should have one clear purpose. Too much text distracts from the app itself.
Skipping the phone test: Always play each video on an actual device before uploading. Desktop preview is not reality.
Uploading all languages at once: If one video has a critical problem, you have to fix and re-upload all of them. Staged uploads (batch 1, then batch 2) let you catch problems early.
Not confirming dubbing quality: Low-quality or mismatched dubs damage your app's credibility. Spend an extra day testing dubs with native speakers before upload.
Ignoring safe area margins: Text that extends into the edges gets cut off on some devices. Always leave a 10% margin on all sides.
What to Do Next
-
Create your master preview skeleton (no text, no dialogue) in your editing software. Export it in the exact codec, bitrate, and aspect ratio your target store requires.
-
Dub that skeleton into your top language market (usually Spanish or French after English) as a test run. This reveals any issues with audio length or timing before you commit to full localization.
-
Create a checklist spreadsheet (Language, Video File, Bitrate, File Size, Phone Test, iOS Upload, Android Upload). Use it for every language to prevent mistakes.
-
Upload your first batch of 3-5 languages to the store. Wait 24 hours, then install your app on devices set to each of those languages to verify the correct video displays.
-
Only after that batch is confirmed should you produce and upload the remaining languages. This approach saves you from having to fix and re-upload a large batch if something goes wrong.
🚀 Start Dubbing Your Videos Today
DubLab uses AI to translate your videos into 92+ languages in minutes.