Home / Knowledge / Playback

Browser Autoplay Restrictions: Why You Need to Click

You may have noticed that many videos don't start on their own — they wait for a click. That's the browser autoplay policy at work.

Why the restriction exists

Playing sound without the user's permission is disruptive. Major browsers therefore require that autoplay with sound happen only after the user has interacted with the page, or when conditions such as muting are met.

Impact on HLS players

Even when technically ready, calling play immediately after page load can be blocked. The safe approach is a clear Play button the user clicks — exactly how our player is designed.

What developers can do

  • Autoplay muted by default and enable sound on the first click;
  • Show a prominent play button to invite interaction;
  • Catch playback failures and show a hint instead of failing silently.
← Improving HLS Playback from the Production SideCopyright and Compliance Notes for Streaming Tools →