Description

AI voiceover for app store previews is a 15-30 second TTS track mixed into App Store and Google Play listing videos. This guide covers muted autoplay, Apple and Play specs, locale takes, and a production loop so you ship listing audio instead of a studio recast every release.

AI Voiceover for App Store Previews in 2026

#TLDR

AI voiceover for app store previews is text-to-speech for listing clips: 15-30 seconds on Apple, muted autoplay on both stores, stereo export, and the same narrator across locales. Write for spoken time. Put the story on screen. Validate brand names before you upload to App Store Connect or paste a YouTube URL into Play Console.

What is AI voiceover for app store previews?

AI voiceover for app store previews is a short narration track generated from a listing script, then mixed into the video that plays on your product page. Apple defines app previews as device-captured clips of your iOS, iPadOS, macOS, tvOS, or visionOS app. You can ship up to three previews per language, and each clip can run up to 30 seconds. They autoplay on the product page and in search, and Apple Ads can reuse them.

Onepin is a voice workflow platform that orchestrates, validates, and ships production-ready audio across 100+ TTS models. Engines such as ElevenLabs and Google Cloud Text-to-Speech stay engines. You still own duration, stereo mix, locale, and the file that App Store Connect or Play Console will accept.

GM Insights values the global TTS market at USD 4.8 billion in 2025 and USD 5.7 billion in 2026. Store listings are a 15-30 second slice of that market. A cinematic 90-second brand film does not fit the slot.

Why do App Store preview videos play muted?

App Store preview videos play muted because Apple designed autoplay for a public store, not a theater. Apple’s own preview guide says previews play with the sound muted by default, so you should add copy on screen and keep text on long enough to read. If you add voiceover, Apple still wants high-quality capture with no background noise, because unmuted playback is the voice of the app.

Google Play may autoplay preview video with muted audio for up to 30 seconds, depending on device, settings, network, and surface. Play also tells you to put the core experience in the first 10 seconds and to keep at least 80% of the video representative of the actual app. Voiceover that only works if someone unmutes fails both stores.

That is why AI voiceover for app store previews is a dual-track job: on-screen copy for mute, narration for unmute, ads, and localized listings.

How long can an App Store preview voiceover be?

An App Store preview voiceover can last only as long as the video: 15 seconds minimum, 30 seconds maximum. App Store Connect also caps the file at 500MB, sets a default poster frame at 5 seconds, and requires stereo audio: 256kbps AAC at 44.1kHz or 48kHz for H.264, or PCM/AAC for ProRes 422 HQ. Frame rate maxes at 30 fps.

Write the script to spoken time. A 90-word English take at a natural rate already crowds 30 seconds. Cut features instead of speeding the file to 1.3x. Apple also bars seasonal copy and prices in the video, because pricing changes by region.

On Play, you paste a YouTube URL. Ads must be off, privacy public or unlisted, and the video embeddable. Only the first 30 seconds autoplay, so a 3-minute trailer wastes the listing.

How should I write a 30-second listing script for TTS?

You write a 30-second listing script for TTS as spoken time, then generate and measure.

1. One benefit per sentence. Nested clauses are where engines skip a “not.”
2. Speak the app name the way you want it heard. Test it on two engines.
3. Put feature labels on their own breath so they match the on-screen super.
4. Keep the same greeting and close across locales so the voice ID is obvious.
5. Time the take. If duration overshoots 28 seconds, cut words. Do not stretch.

Apple requires footage captured inside the app, not over-the-shoulder hands. Voiceover cannot paper over a clip that shows the wrong UI. Disclose IAP or login if the footage shows paid features.

ElevenLabs lists 70+ languages on its text-to-speech product. Google Cloud TTS currently lists 380+ voices across 75+ languages and variants. Coverage is not quality. A language list does not prove your app name is spoken correctly in Japanese.

For the model map, see the TTS leaderboard guide. For the production layer, see what TTS orchestration is. Adjacent use cases: AI voiceover for ads and AI voiceover for product demos.

Why does using Onepin mean you are not locked into one model?

Using Onepin means the listing pipeline talks to a production layer, not a single vendor SDK. Onepin is a voice workflow platform that orchestrates, validates, and ships production-ready audio across 100+ TTS models. You keep ElevenLabs for English previews, Google for a locale pack, and you change a route when a checkpoint drifts.

The job for store previews:

1. Script and glossary live next to the listing version.
2. Surface rules: 15-30 seconds, stereo container, loudness, captions for Play.
3. Generate on the routed model. Lock voice ID and model version for the catalog.
4. Validate pronunciation, duration, and format. Word error rate from ASR is the wrong metric for TTS.
5. Retry or fall back on the failed line only.
6. Ship a versioned mix. Yesterday’s iOS 26 UI clip does not mix with today’s copy.
7. Store model name, voice ID, and generation date with the App Store Connect asset.

That loop is what “AI voiceover for app store previews” should mean in production.

Ship the listing, then the locale pack

Pick one English 20-second take. Freeze a voice. Run the brand-name glossary. Caption the Play cut. Then put a production layer above the engine so a silent model update cannot rewrite every locale you certified last quarter.

Try Onepin if you already generate listing VO on ElevenLabs or Google and still recut after every App Store screenshot pass.