Skip to Content
Platform.Ontology

Autoplay audio and video

Starts video or sound automatically; muted video is allowed, sound usually needs prior interaction.

Does something on your deviceThings a page can doMedia outputWeb browsersWhile you use it

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

BrowserStatusFirst versionReleasedNote
ChromeSupported32009-09-15None
EdgeSupported122015-07-29None
FirefoxSupported3.52009-06-30None
SafariSupported3.12008-03-18None
Safari on iPhoneSupported32009-06-17All iOS browsers use WebKit
Chrome on AndroidSupported182012-06-27None
Samsung InternetSupported1.02013-04-27None

How a site asks for it

API<video autoplay muted playsinline>; HTMLMediaElement.play(); allow="autoplay"; navigator.getAutoplayPolicy()
Browser compat keysapi.HTMLMediaElement.autoplay
api.HTMLMediaElement.play
How access is grantednone
What the user seesNone (no browser prompt)
Needs a secure context (HTTPS)No
Needs a user gestureYes
Activationsticky
How long it lastsChrome Media Engagement Index (MEI) score is stored per origin
How to take it backNothing to revoke (no permission is stored)
Inside an iframeTop frame must delegate with allow="autoplay" for cross-origin iframes

Typical flow

  1. Element has muted attribute or origin has activation or high MEI
  2. play() resolves or rejects with NotAllowedError
  3. 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

TypeExampleApps
videoA streaming home page plays a silent trailer behind the title, so browsing feels alive.Netflix
gamesA browser game must wait for your first click or key press before its music and sounds can play.None named
socialA social feed starts muted clips as you scroll, and you tap to hear them.Instagram, TikTok
newsA news site starts a muted video in an article, which many people watch with captions.None named
adsA video ad starts muted in the page, and counts a view after a few seconds.None named
shoppingA store plays a muted product video on the page to show the item in use.None named
liveA live stream page starts muted and asks you to unmute for sound.Twitch
musicA 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

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

ScoreValueMeaning
Sensitivity1 of 5How revealing the data is
Utility4 of 5How useful it is to honest apps
Friction0 of 5How much the user has to do
Fingerprint bitsNot ratedRough 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

Sources

How well checked: Based on official documentation.

On this page