Autoplay audio and video
Starts video or sound automatically; muted video is allowed, sound usually needs prior interaction.
In one line
Can start muted video on its own, and sound only after you have interacted
Starts video or sound automatically; muted video is allowed, sound usually needs prior interaction.
A site can start media without a click. Browsers allow silent autoplay but block surprise sound unless the person has engaged with the site, which shapes ad video and background audio.
What it can and can't do
What the user does: Nothing for muted video. For sound, you tap, click or press a key on the site first
It can
- Start a silent video without a click
- Start sound after you have clicked, tapped or watched on the site
- Start a clip after you tap Play
It cannot
- Play sound on a first visit without any interaction
- Keep a sound ad alive in a tab you muted
- Override your browser's autoplay setting
- Play a video in the background once the page is hidden on most phones
How it differs between platforms: Safari and iPhone are strict about sound. Chrome and Edge allow sound for sites you used often. Firefox lets you block it.
Browser support
| Browser | Status | First version | Released | Note |
|---|---|---|---|---|
| Chrome | Supported | 3 | 2009-09-15 | None |
| Edge | Supported | 12 | 2015-07-29 | None |
| Firefox | Supported | 3.5 | 2009-06-30 | None |
| Safari | Supported | 3.1 | 2008-03-18 | None |
| Safari on iPhone | Supported | 3 | 2009-06-17 | All iOS browsers use WebKit |
| Chrome on Android | Supported | 18 | 2012-06-27 | None |
| Samsung Internet | Supported | 1.0 | 2013-04-27 | None |
How a site asks for it
| API | <video autoplay muted playsinline>; HTMLMediaElement.play(); allow="autoplay"; navigator.getAutoplayPolicy() |
| Browser compat keys | api.HTMLMediaElement.autoplayapi.HTMLMediaElement.play |
| How access is granted | none |
| What the user sees | None (no browser prompt) |
| Needs a secure context (HTTPS) | No |
| Needs a user gesture | Yes |
| Activation | sticky |
| How long it lasts | Chrome Media Engagement Index (MEI) score is stored per origin |
| How to take it back | Nothing to revoke (no permission is stored) |
| Inside an iframe | Top frame must delegate with allow="autoplay" for cross-origin iframes |
Typical flow
- Element has muted attribute or origin has activation or high MEI
- play() resolves or rejects with NotAllowedError
- Handle the rejection and show a play button
Data you get
Shape: none
No individual data fields. The signal is the access itself.
Technical limits
- Muted autoplay is allowed everywhere (iOS also needs playsinline)
- Chrome 66: audible autoplay needs user activation on the origin, a high MEI score, or an installed PWA; MEI needs roughly 20 visits and a score of about 0.2 to 0.3 (Chromium source)
- MEI counts a play as significant when media plays 7 s or more, is audible, tab active, and video at least 200 by 140 px
- Firefox 66 blocks audible autoplay by default (site exceptions allowed); Safari 11 on macOS and iOS 10 block audible autoplay by default
- Chrome mutes autoplay in cross-origin iframes unless allow="autoplay" is set
The story
What it is
A page can start video or sound by itself. Muted video is usually fine, sound needs your action first.
For you
A video on a page may start playing silently as you scroll. Sound normally starts only after you click or tap. Browsers keep this rule to avoid surprise noise.
For makers
Makers use muted autoplay to show previews and grab attention, which raises views and ad time. They ask for a tap before sound. Games need one click before audio. Ads that autoplay can annoy users.
Where you see it
| Type | Example | Apps |
|---|---|---|
| video | A streaming home page plays a silent trailer behind the title, so browsing feels alive. | Netflix |
| games | A browser game must wait for your first click or key press before its music and sounds can play. | None named |
| social | A social feed starts muted clips as you scroll, and you tap to hear them. | Instagram, TikTok |
| news | A news site starts a muted video in an article, which many people watch with captions. | None named |
| ads | A video ad starts muted in the page, and counts a view after a few seconds. | None named |
| shopping | A store plays a muted product video on the page to show the item in use. | None named |
| live | A live stream page starts muted and asks you to unmute for sound. | Twitch |
| music | A music site shows a play button, because the browser blocks sound until you tap. | None named |
Risks
- Annoying sound
- Data use
What the platform says
- Google Chrome: Autoplay policy. Chrome allows muted autoplay, and lets sound autoplay only after you have interacted with the site.
- WebKit: New video policies for iOS. Safari lets muted videos play inline automatically, and requires a tap for videos with sound.
Good uses and abuse
Legitimate uses
- Background hero video (muted)
- Short clips in feeds
- Podcast players after a tap
Known abuse
- Auto-playing ads with sound
- Hidden audio tracking pixels
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 1 of 5 | How revealing the data is |
| Utility | 4 of 5 | How useful it is to honest apps |
| Friction | 0 of 5 | How much the user has to do |
| Fingerprint bits | Not rated | Rough identifying entropy, when known |
History
- 2017-10, Safari 11: Block audible autoplay by default on macOS
- 2018-04, Chrome 66: Autoplay policy: muted allowed; audible needs activation, MEI or PWA
- 2019-03, Firefox 66: Block audible autoplay by default
- 2020-07, Chrome 86: Autoplay policy for media in background tabs unchanged; play() promise rejection documented widely
Related capabilities
Related
- Web Audio playback. Can play and mix sound inside the page, after you have tapped
- Speech synthesis (text to speech). Can speak text out loud, after you have tapped on the page
Sources
- MDN Autoplay guide
- Chrome autoplay policy
- WebKit new video policies for iOS
- Firefox autoplay blocking
How well checked: Based on official documentation.