Understanding autoplay behavior for web players
Overview
This article explains how autoplay and sound may behave for Lightcast web players, including why some players may start muted when autoplay is enabled.
When to use this article
Use this article when a web player is configured to start playback automatically but does not automatically play with sound.
This can happen when:
Autostart is selected in the embeddable web player settings before the player is added to your website
Autoplay has been enabled for supported web players by Lightcast
Autoplay behavior can vary depending on the viewer’s browser, device, player type, Channel type, and how the viewer accesses the player.
How it works
Modern web browsers restrict autoplay with sound in many situations. As a result, a web player may be allowed to start automatically only when the audio is muted.
The browser—not the Lightcast player alone—ultimately determines whether autoplay with sound is permitted.
A browser may allow audio to play automatically after the viewer has interacted with the website, Web App, or player. For this reason, autoplay behavior may differ depending on how the viewer accesses the content.
For example, a player opened through a direct player link may behave differently from the same player viewed after the viewer has already interacted with a website or Web App.
What to expect
Depending on the browser, device, and viewing experience:
The player may start automatically with sound.
The player may start automatically with the sound muted.
The viewer may need to interact with the website or player before sound can play.
Autoplay may be restricted entirely in some circumstances.
If a player starts muted when autoplay is enabled, this does not necessarily indicate a problem with the player. The viewer’s browser may be enforcing its autoplay policy.
Autoplay with sound may be available for some supported player and Channel configurations when browser requirements are met, but it cannot be guaranteed across all browsers, devices, player types, Channel types, or viewing methods.
Need autoplay with sound for a specific setup?
If autoplay with sound is required for a specific Channel, player, or publishing workflow, Contact Customer Support. Our team can review your configuration and help determine what options are available for your setup.
FAQs
Why does a web player autoplay without sound?
A web player may autoplay without sound because the viewer’s browser restricts autoplay with audio. In these cases, the player may begin playback muted until the viewer interacts with the website or player.
Is autoplay without sound a player issue?
Not necessarily. A player starting muted may be the result of the viewer’s browser enforcing its autoplay policy rather than an issue with the Lightcast web player.
How is autoplay enabled for a web player?
Some web player autoplay options may be available from the player’s EMBED settings, such as Autostart. Other autoplay behavior may require Lightcast configuration, depending on the player type, Channel type, and publishing setup.
Contact Customer Support if you need autoplay reviewed for a specific web player.
Can autoplay with sound be enabled for every Channel?
Not necessarily. Autoplay with sound depends on the player setup, Channel type, browser behavior, device, and how the viewer accesses the player. It cannot be guaranteed for every viewing experience.
Does autoplay with sound work the same from a direct player link?
Not always. A direct player link may start muted because the viewer has not interacted with the website or domain before the player loads.
Can viewer interaction affect autoplay with sound?
Yes. In some cases, a browser may allow sound to play automatically after the viewer has interacted with the website, Web App, or player.
Can autoplay behavior vary by browser or device?
Yes. Autoplay behavior can vary by browser, device, operating system, and viewing method.
