In a recent blog post, Google Chrome product manager John Pallett wrote that “a significant number” of autoplay videos are axed by users who don’t want them - either by muting, pausing, or closing out of the tabs altogether - within only six seconds of the videos’ start. In its most recent update (which brings us to Google Chrome 66), Google Chrome had begun to automatically block autoplay videos based on your preferences, which could cut down on the number of times you have to frantically mute your computer while trying to determine where that infernal noise is coming from. Your days of being startled by a video that seems to begin playing out of nowhere on your browser were about to come to an end, until the Chrome team realized that this update impinged upon users’ abilities to play games and build art projects. (Also, there is a Paypal donation option for this work. Def a lifesaver for me and will be throwing some cash this dev's way, perhaps consider doing the same) Also, maybe Unity should take a look at what this guy has done and roll in his solutions into the official WebGL export template. Not too much though, so maybe playing around with what is there could help people with their issues. But the template has some fun javascript happening. I don't know what specific kind of sorcery is going on under the hood to produce such auto-magical results. I'm building with Unity 2019.4.1f1, and I used the 2019 option in the template downloads. Pretty nice template, does what it says and has some nice options. I had been looking for good WebGL export templates and found this one: The offered jslib solution didn't work for me, nor did the silent mp3 method. I wasn't trying to autoplay, and by the time the user would have encountered the video, they will have had clicked the WebGL canvas element plenty of times. Just to clarify, even just having a video was broken in WebGL MacOS Safari. I was having the same issues as everyone else.

Chrome autoplay video 2019