Autoplay
Autoplay is a video player setting that starts playback automatically when a page or screen loads, without the viewer pressing play. Most browsers block autoplay with sound and only allow it when the video is muted or the user has interacted with the site. Autoplay is common for background videos, previews and social feeds.
Why it matters
Autoplay can raise engagement on feeds and landing pages, since viewers see motion instantly. Done badly, it annoys users, wastes mobile data and gets blocked by browsers. Teams that expect sound often find their videos silently fail to start, losing views they never notice. Whether muted autoplay is really starting shows up in FastPix Video Data, which records startup failures and exits before start for every view.
How it works
- The page or app marks a video to start on its own when it loads or comes into view.
- The browser checks its autoplay policy, such as whether the video is muted or the user has interacted.
- If allowed, playback starts; if not, the play request fails and the video waits for a tap.
- Good players detect that failure and show a play button or start muted instead.
Why won't my video autoplay?
Usually because the video has sound. Chrome, Safari and Firefox block sound-on autoplay until a visitor clicks or taps something on the page. Start the video muted, and on iPhone add playsinline too, and autoplay normally works. Low power mode and browser settings can still stop it, so always show a visible play button as a fallback.
Is autoplay bad for user experience?
Autoplay is fine when muted and expected, such as in a short video feed or a product hero. It hurts experience when it plays sound unexpectedly, uses mobile data on long videos, or distracts from reading. Offer clear pause controls and consider starting only when the video is visible on screen.
Where it's used
Short video apps, ecommerce brands and news publishers use muted autoplay in feeds, product pages and article headers to show motion immediately and lift engagement.
Where it usually goes wrong, and how FastPix handles it
When browsers block autoplay, the failure is silent. Teams see fewer views but cannot tell whether viewers chose not to watch or the video never started.
Breakdowns by browser, device and operating system in FastPix Video Data separate a browser blocking autoplay from a slow start. Your team can tell a blocked autoplay from a viewer who chose not to watch, and fix the right problem.
By the numbers
- Chrome changed its autoplay policy in April 2018 with Chrome 66, and muted autoplay is always allowed. (Autoplay policy in Chrome, Chrome for Developers)
