What Is Autoplay?
A player setting that starts a video automatically when the page loads, instead of waiting for a visitor to press play.
Autoplay makes an embedded video start playing as soon as its player loads, without a visitor clicking play. In a YouTube embed it is controlled by adding autoplay=1 to the embed URL.
Browser restrictions
Most modern browsers block autoplaying video with sound unless the visitor has already interacted with the site, or unless the video is also muted. That is why autoplay is almost always paired with mute=1 in practice: muted autoplay is widely allowed, sound-on autoplay usually is not.
When to use it
Autoplay can suit a hero banner or a background-style video, but it adds friction for visitors on slow connections and can conflict with cookie-consent requirements if it starts before consent is given. The embed code generator leaves autoplay off by default for this reason and lets you switch it on deliberately.
Why browsers restrict autoplay so heavily
Autoplaying video, especially with sound, was widely disliked by web users, unexpected noise, wasted bandwidth on mobile data plans, and videos playing that a visitor never asked for. Browser makers responded over the past several years by progressively restricting autoplay, generally requiring that video be muted unless the visitor has already shown some engagement with the site, such as a previous click. This shift happened gradually across Chrome, Safari and Firefox, which is why older tutorials describing unrestricted autoplay with sound no longer reflect how browsers actually behave.
A practical example
An embed configured as autoplay=1 alone will typically fail silently in most modern browsers, simply not starting, because sound-on autoplay is blocked by default. Adding mute=1 alongside it, autoplay=1&mute=1, is what actually works reliably, since muted autoplay remains broadly permitted. This is precisely why our embed code generator enables mute automatically whenever autoplay is switched on.
Autoplay vs. click-to-play
The alternative to autoplay is simply waiting for a visitor to click the player’s own play button, which is the default behaviour of any embed without the autoplay parameter set. Click-to-play respects visitor intent and avoids unnecessary bandwidth use for people who scroll past without watching, while autoplay can increase watch time on content specifically designed to be consumed passively, such as background-style video. Most general content benefits from click-to-play as the safer default, with autoplay reserved for specific, deliberate use cases like a hero banner.
When in doubt, defaulting to click-to-play rather than autoplay is the safer choice for both visitor experience and privacy-conscious page design.
It is also worth testing autoplay behaviour across a few different browsers before relying on it for something important, since the exact threshold for what counts as sufficient prior visitor engagement can vary slightly between Chrome, Safari and Firefox.
Autoplay settings also interact with a visitor’s own device-level preferences on some platforms, meaning a visitor who has globally disabled autoplay in their browser or operating system may not see it trigger even when your embed code requests it, regardless of your own configuration.
Frequently asked questions
Why doesn't autoplay work with sound?
Most browsers block autoplaying video with sound unless the visitor already interacted with the page, so autoplay is usually paired with mute.
How do I enable autoplay on a YouTube embed?
Check the Autoplay option in our embed code generator; it will automatically enable mute alongside it for reliability.
Build your embed code
Our generator writes a privacy friendly embed code you can paste straight into your page.