How to make a video play automatically

The short version: a video can start on its own, but only with the sound off. That is not a setting on YouTube, on your site builder, or in any tool. It is a rule the browser enforces, and nothing you can install will get around it.

Once you know that, autoplay becomes a straightforward decision rather than a thing that mysteriously does not work.

Why browsers stopped allowing it

Around 2017 and 2018, Safari and then Chrome both changed the rule. Before that, any page could start playing sound the moment you opened it, and enough sites did that people were opening ten tabs and hunting for which one was shouting at them. Firefox and Edge followed. Every current browser now refuses to start an audible video unless a person has interacted with the page first.

There is one exception, and it is not one you can rely on. Chrome keeps a score of how often you personally have watched video on a given site, and once that score is high enough it allows audible autoplay there. So a video that autoplays with sound on your own site, on your own computer, will very often stay silent for a first-time visitor. This is the single most common reason someone believes their autoplay works when it does not.

If you are testing autoplay, use a private browsing window. It is the only way to see what a new visitor sees.

How to turn it on

In the builder, open Playback and switch on Autoplay. Mute switches on with it, because that is the only combination a browser will honour. Switch Mute back off and Autoplay switches off too, for the same reason: leaving both on would hand you code that silently does nothing.

If you are writing the embed URL by hand, both parameters have to be there:autoplay=1 on its own is ignored, and autoplay=1with mute=1 works.

When muted autoplay is the right choice

Silent, moving video as part of the design of a page is a real and common use, and it is what the rule leaves room for:

• A background or hero video. A short loop behind a headline, with no sound to lose.
• A product in motion. Ten seconds of something being used, where seeing it is the whole point.
• An animation or demo that would otherwise be a GIF, at a fraction of the file size.

All three usually want looping as well, and often want the control bar hidden, so the video reads as part of the page rather than as something to watch.

When it is the wrong choice

If the audio carries the message, autoplay is working against you. A muted autoplaying interview starts without the viewer, plays past the part that would have hooked them, and by the time anyone unmutes they have missed the opening. A thumbnail with a clear play button does better, because the person watching chose to start it and starts at the beginning.

There is also a cost you do not see. Autoplay downloads the video for everyone who opens the page, including people who were never going to watch and people on a phone paying for data. On a page where a small share of visitors watch, that is most of your bandwidth spent on nobody.

The rule people forget

Accessibility guidelines treat anything that moves automatically for more than five seconds as content that needs a way to stop it. That means a visible pause control, on the page, without hunting. It matters for people with vestibular conditions, for whom unexpected motion is genuinely unpleasant, and for anyone using a screen reader who now has moving content competing with what they are trying to read.

In practice: if you autoplay something longer than a few seconds, leave the control bar visible. A looping three second background clip is fine. A three minute video playing itself behind your text is not.

Browsers also respect a system setting called reduced motion, which some people turn on for exactly this reason. It is worth honouring.

Phones behave differently

On iPhones, a video that starts on its own will sometimes take over the whole screen rather than playing in place, which is jarring and is almost never what you wanted. Avoiding that needs a specific instruction in the embed code, and generated code here includes it already.

Low Power Mode on iOS blocks autoplay outright, muted or not. Android's data saver settings can do the same. So even a correctly muted autoplay will not start for some people, which is another reason the video should still look inviting when it is sitting still.

The middle option

There is a version of this that most people actually want: the video does not download or start on its own, but it looks like a video and takes one click. A thumbnail with a play button over it, and the real player arriving only when somebody asks for it.

It is the default in the builder, it starts from the beginning with sound, it costs your visitors almost nothing until they choose to watch, and it sidesteps every rule on this page. If autoplay was an attempt to make the video feel present rather than to literally start it without asking, this is the thing to try first.