VSL autoplay: muted autoplay, the unmute prompt and restarting the hook

Yes, a VSL can autoplay, but only muted. Chrome, Safari and Firefox block autoplay with sound for a first-time visitor who hasn't interacted with your site, so the pattern that works is: start muted the moment the page loads, show a large "Tap for sound" prompt, and restart the video at 0:00 when the visitor unmutes, so they hear the hook from the first word.

Here is that pattern from the visitor's side, from page load to sound:

Muted autoplay, step by step

What a first-time visitor sees, from page load to sound

1. 1Muted startThe video starts muted the moment the page loads. On-screen text or captions carry the opening line.
2. 2"Tap for sound"A large, plain prompt sits over the video, clear of the presenter's face, and the whole frame is tappable.
3. 3The visitor tapsSound comes on, and the prompt is gone the same instant.
4. 4Restart at 0:00A first-time viewer is rewound to the start, so they hear the hook from the first word.

Can a VSL autoplay with sound?

Not reliably, and on cold traffic almost never. Chrome, Safari and Firefox all separate muted autoplay, which they allow, from autoplay with sound, which needs something the visitor has done on your site first. Here is where each one draws the line:

Chrome. Chrome's autoplay policy launched for audio and video in Chrome 66, in April 2018. Muted autoplay is always allowed. Sound is allowed only if the visitor has interacted with your domain (a click or a tap), has crossed Chrome's Media Engagement Index threshold on desktop, or has added your site to their home screen or installed it. The index is built from past visits where the visitor played media with sound for more than seven seconds in an active tab, so a first-time visitor from an ad hasn't built one on your site.

If your player sits in an iframe served from another domain, add allow="autoplay" to the iframe so the page can delegate its autoplay permission to it. Chrome allows autoplay in same-origin iframes by default.

Safari. WebKit's video policy for iOS, introduced with iOS 10, lets a muted video autoplay without a tap. On iPhone the video also needs the playsinline attribute, or playback requires fullscreen. If a video becomes unmuted without a user gesture, it pauses, and an autoplaying video pauses when it's scrolled out of view. On the Mac, Safari 11 began blocking media with sound from autoplaying on most websites, and visitors can change that per site.

Firefox. Firefox blocks media with sound from playing automatically by default. Visitors can also pick a setting that blocks all media from autoplaying, even when it's muted.

The practical rule: design for a muted start, and make sure the page still works when nothing autoplays at all. MDN's autoplay guide explains the fallback: the play() call returns a promise that's rejected when autoplay is denied, and the page should then offer a way to start playback manually. Chrome's own advice is blunter: never assume a video will play.

Why muted autoplay beats click-to-play on cold traffic

A click-to-play VSL asks a cold visitor for a commitment before they've seen anything: press play on a long video from someone they don't know. A muted autoplay VSL asks a smaller question. The video is already moving, the presenter is already talking, and the only decision left is whether to turn on sound.

Here is what changes when you switch, and when click-to-play still wins:

Muted autoplay or click-to-play

The default for cold trafficMuted autoplay

Three things change when you switch:

• The first impression is motion, not a still frame. A face mid-sentence gives the visitor a reason to look at the video instead of scrolling past it.
• The opening can work on silent viewers. On-screen text or captions in the first seconds carry the hook's promise before anyone taps.
• Your key metric moves. Play rate jumps toward 100%, because the browser "plays" for everyone it allows. The real question becomes how many visitors choose sound.

Click-to-play

Click-to-play can still be the better choice in two situations:

• Warm audiences who already know the presenter, such as an email list, and already have a reason to press play.
• Pages where the video is secondary, such as an advertorial with an embedded clip, where motion competes with copy the visitor came to read.

Don't settle it by opinion. Split-test muted autoplay against click-to-play on the same traffic and judge by revenue per visitor, not by plays. Autoplay is one of the core VSL player features, but it's still a variable you can test.

Why restart the VSL at 0:00 on unmute

The hook does its work in the first seconds of the video, and on a muted start nobody hears those seconds. By the time a visitor reads the prompt, decides and taps, the presenter is several sentences in.

Say your hook runs from 0:00 to 0:20 and a typical visitor taps for sound at 0:08. Without a restart, they hear 0:08 onward: the end of the promise, without the setup that made it interesting. With a restart, playback jumps back to 0:00 the moment they tap, and every sound-on viewer hears the whole hook.

The muted seconds weren't wasted either. They were the teaser that earned the tap.

Two refinements make it work:

• Restart first-time viewers only. A returning viewer who was 14 minutes in yesterday should resume where they left off, not get thrown back to the start.
• Make the muted seconds stand on their own. Put the opening line on screen as text or captions, and keep the presenter's face in frame. A silent viewer should understand the promise and want to hear the rest.

RevvyScales handles the mechanics on every plan: smart muted autoplay starts the video as a muted teaser, a first-time viewer who taps for sound is rewound to 0:00, and returning viewers resume from the deepest point they watched (player conversion features).

How to design an unmute prompt people tap

With muted autoplay, the unmute prompt is the most important control on the page until the buy button appears. Design it like one:

• Big. Readable at a glance on a phone and easy to hit with a thumb. Make the whole video area tappable, not just a small icon.
• Plain words. "Tap for sound" on phones, "Click for sound" on desktop. A speaker icon helps; words mean nobody has to guess.
• High contrast. Light text on a solid dark panel, or the reverse. No thin text over a busy frame.
• Over the video, clear of the face. Center or lower third, leaving the presenter's eyes and mouth visible, because a face mid-sentence signals there's something worth hearing.
• Honest. Never style the prompt as a system dialog, an error or a fake "video paused" message. A trick may win a tap, but it spends trust at the exact moment you're asking for attention.
• Gone after the tap. Remove it the instant sound is on.

A before-and-after:

Two unmute prompts

BeforeA silent corner icon

A small gray speaker icon in a corner, with no words.

It hopes the visitor notices.

AfterA centered panel

A centered panel that reads "Your video has started. Tap for sound." with the presenter visible behind it.

It asks one clear question.

Your poster matters here too. It's what visitors see while the video loads and whenever it's paused, so it should carry the same promise. See how to choose a VSL thumbnail.

How to measure VSL autoplay: unmute rate, not play rate

Once a video autoplays, "plays" mostly measures how often the browser allowed it. Track three numbers instead:

Three numbers to track on an autoplay VSL

Autoplay start rate=Visitors whose video started ÷ unique visitors. How often browsers, settings or slow loads stopped the start.

Unmute rate=Visitors who turned on sound ÷ unique visitors. The real "play rate" of an autoplay VSL.

Pitch reach=Visitors who reached the pitch second ÷ unique visitors. How many visitors stayed long enough to see the offer.

A worked example: you split 4,000 visitors from one ad set between your current prompt and a bigger, centered one that says "Tap for sound". With the old prompt, the video starts for 1,940 of 2,000 visitors (97%), and 1,085 unmute: an unmute rate of 54%. With the new prompt, 1,220 of 2,000 unmute (61%). That's 135 more people hearing the hook, and a gap that size on 2,000 visitors per side is far beyond chance.

Then check the step that pays. If pitch reach and revenue per visitor rise too, keep the new prompt. If unmutes rise but pitch reach doesn't, the prompt is pulling in curious tappers the hook doesn't hold, so work on the opening next.

Segment before you conclude:

• By device. iPhone, Android and desktop follow different autoplay rules and have different screen sizes.
• By traffic source. Visitors from a feed, a story placement or a search ad arrive in different contexts.
• New versus returning. Returning viewers resume instead of restarting, so mixing them in flatters the numbers.

For baselining and diagnosing a weak start, see the play rate guide.

When autoplay is the wrong choice

Muted autoplay is the right default for cold traffic, not a rule for every page. Hold back, or add safeguards, in these cases:

• Accessibility. WCAG success criterion 2.2.2 (Level A) requires a way to pause, stop or hide moving content that starts automatically, lasts more than five seconds and runs alongside other content, and the W3C lists synchronized media among its examples (Understanding 2.2.2). Keep a visible pause control. If audio ever plays automatically for more than three seconds, success criterion 1.4.2 requires a way to pause it or control its volume (Understanding 1.4.2), one more reason the autoplay should stay muted.
• Data costs. A muted teaser still streams video. Adaptive streaming keeps the bitrate within what the connection can carry, but a visitor on a capped plan pays for the data, so keep pause one tap away.
• Returning viewers. Someone coming back to finish should resume, not restart. See the pause and resume guide.
• Secondary video. On a presell or advertorial where the text does the selling, an autoplaying clip competes with the copy.
• Sound-off audiences. If many visitors never unmute, captions have to carry the message. Show them during the muted opening and test captions on by default; the VSL captions guide covers the options.

A VSL autoplay setup checklist

Run through this before you send traffic; the ticks stay in this browser:

A VSL autoplay setup checklist

• The video autoplays muted, with playsinline set for iPhone.
• If the play() promise is rejected, a clear play button appears over the poster.
• A large, plain, high-contrast unmute prompt sits over the video, and the whole frame is tappable.
• Unmuting restarts first-time viewers at 0:00; returning viewers resume.
• On-screen text or captions carry the hook while the video is muted.
• A pause control is visible at all times.
• If the player sits in a cross-origin iframe, the iframe has allow="autoplay".
• You've tested on iPhone Safari, Android Chrome, and desktop Chrome, Safari and Firefox, including Firefox with all autoplay blocked.
• Unmute rate is tracked by device and source for a full week before you change anything.
• You test one prompt change at a time and judge it by pitch reach and revenue per visitor.

0 of 10 done