Video not playing on iOS10 Chrome

Google Chrome currently has a bug in which it will not autoplay a .webm video if it comes after anything else. Try to use a code published here.

Build an HTML5 video as usual:

<video playsinline autoplay muted loop poster="aurora.jpg" id="bgvid">    <source src="aurora.webm" type="video/webm"> </source>    <source src="aurora.mp4" type="video/mp4"> </source></video>

If previous advise does not help, try to use scripted playback examples video.js and simpl on Github.

Also, read this post dedicated to muted autoplay in mobile browsers. And it must be useful to read Stack Overflow post as well – Efficiently detect if a device will play silent videos.

I just can't seem to locate what's wrong with this video snippet.

<video poster="sample.jpg" loop autoplay controls muted playsinline>    <source type="video/webm" src="sample.webm"></source>    <source type="video/mp4" src="sample.mp4"></source></video>

...Update: It seems there's an issue with playing Webm files with iOS Chrome.

The simplest and best fix is to make sure you declare the mp4 file first and then declare webm in second place (the reverse of your shown order). I believe iOS expects an mp4 as first file in HTML5 video tags. All iOS sees is src="sample.webm" which is not a valid expected MPEG codec so leads to your "...play button that doesn't trigger anything". You got a silent error somewhere.

Try :

<video poster="sample.jpg" loop autoplay controls muted playsinline>    <source type="video/mp4" src="sample.mp4"></source>    <source type="video/webm" src="sample.webm"></source></video>

Side note: Just my opinion but, I think having webm here is redundant since the main supporting system (Google-based tech) can already handle mp4 anyways.

Better to offer those video decoders in browsers [of end-users] a choice of mp4 or ogv (just in case of Firefox).

PS: Auto-play is disabled on most mobile systems due to SIM data allowances. The end-user must choose to play that video. Likely there are clever workarounds on the net, just remember though, this is expected behaviour so is not an issue with your current code.