Can You Use Voiceover in an Apple App Store Preview?

The short answer

Yes. Apple's App Store preview guidelines explicitly permit voiceover audio. There is no rule against narration, speech, or spoken content in app previews.

The more useful question is not "can you?" but "when should you?" — because whether voiceover helps or hurts depends on the app, the audience, and how the audio is produced.

How voiceover works in App Store previews

In search results, App Store previews autoplay silently. A user will not hear voiceover unless they have their device's ringer switch on, or unless they tap the preview to play it with sound on the full product page.

That means voiceover should never be the only carrier of information. If a user watches your preview muted — which many do — the footage and text overlays need to tell the complete story on their own. Voiceover should add to that, not replace it.

When voiceover helps conversion

When the benefit needs explanation. Some apps have a value proposition that is not obvious from watching the UI. A budgeting app, a meditation tool, a habit tracker — the what is visible in the footage, but the why often benefits from a voice that names it clearly and personally.

When the app has a strong brand voice. For consumer apps with a clear personality, voiceover can carry that tone in a way that text cannot. A friendly, warm narration feels different from the same words on screen.

When the audience skews toward audio-on consumption. Gaming apps, audio apps, and social apps often have audiences comfortable with audio-forward experiences. In those categories, voiceover feels natural.

When text overlays work better

When the outcome is visually obvious. If watching the footage already communicates the value clearly, voiceover adds noise rather than signal. A clean UI that tells its own story rarely needs narration.

When most users browse muted. In quiet environments — commuting, office, library — users keep devices muted. Text overlays work in every context; voiceover only works when audio is on.

When you need multiple language versions. Text overlays are straightforward to localize — swap the overlay text. Voiceover requires re-recording in each language, which adds cost and time.

AI voiceover

AI voiceover has improved dramatically. For most app preview use cases, a well-selected AI voice sounds natural and professional at a fraction of the cost of a studio recording. Tools like ElevenLabs, Play.ht, and WellSaid Labs produce voices that consistently pass the "is this AI?" test for casual listeners.

Cost comparison:

• Professional human voiceover: €150–400 per take, often with additional fees for buyout rights or multiple takes
• Premium AI voiceover: €20–40 using a service like ElevenLabs with a commercial-tier subscription
• Generic TTS (text-to-speech): Free to cheap, but sounds obviously robotic and hurts perception

When AI wins: speed, cost, and language coverage (one subscription covers 30+ languages). When human wins: unique voice personalities, complex emotional range, and brand-voice matching for established consumer apps.

Localizing voiceover

Apple allows localized previews per App Store region. If you ship to multiple regions, each locale typically needs its own voiceover. Options:

• Skip voiceover in localized versions and rely on translated text overlays. Simplest and cheapest.
• AI voiceover per locale. Low cost, fast, quality is consistent across languages. Most localized preview work lands here.
• Human voiceover per locale. Premium feel but €200–400 per language. Usually reserved for flagship markets.

Voiceover scripting best practices

• Keep it short. A 30-second preview can comfortably hold 40–60 words of voiceover. More than that feels rushed.
• Don't describe what viewers already see. "This is the home screen" when the home screen is on screen is dead weight. Use voiceover to add context, name benefits, or express emotion the visuals can't.
• Open with intent, not logistics. "Plan your week in three minutes" beats "Introducing Taskflow, a new productivity app."
• Write for the ear, not the page. Short sentences. No subclauses. Words you'd say naturally.
• End with a light CTA. "Try it free" or "Start today" framed as invitation, not command. Or no CTA at all — the install button is right there.

The combined approach

Many of the most effective previews use both: light voiceover narration that names the core benefit, combined with on-screen text that reinforces key moments. This redundancy means the video communicates fully whether the user is watching muted or with sound — and that is usually the right goal.

Template that works well:

• Voiceover gives one primary line per benefit (3 lines across 30 seconds)
• Text overlays give 2–3 word labels per key moment (4–5 overlays total)
• Music bed supports pacing without competing with voice
• Everything still makes sense if audio is muted

Audio technical requirements

Apple does not enforce a loudness standard, but reasonable practice:

• Audio codec: AAC (required)
• Sample rate: 44.1 or 48 kHz
• Loudness target: around -16 LUFS integrated (typical mobile video level)
• Voice peak: around -3dB, no clipping
• Music duck under voice: -6 to -9 dB when voice is speaking

FAQ

Does Apple reject previews for voiceover content?

Only if the content itself violates other rules — misleading claims, competitor mentions, unverifiable superlatives. The existence of voiceover is not an issue.

Can I use AI voices trained on a real person's voice?

Only if you have explicit consent or licensing. Cloning a celebrity or public figure without permission is legally risky and can trigger takedowns.

Is voiceover better than a good music track?

Neither beats the other in isolation. A strong visual story with great music and no voiceover frequently outperforms a weak visual story with narration. Voiceover adds a layer; it doesn't rescue a broken structure.

How much does it matter if audio is off by default?

A lot. Most users watching on a commute, at work, or in a quiet space will never hear the voiceover. If the video depends on the narration to make sense, you lose most of the audience.

Do I need to disclose AI voiceover?

Not to Apple. No guideline requires disclosure. Some apps voluntarily disclose for transparency with their audience, but it's not a common practice.