A webpage is not always broken because of a large mistake. Small details can produce exactly this problem: debugging: video fails to autoplay. This guide shows you what to look for, a concrete fix, and how to check that it worked.
The Idea in Plain English
Browsers commonly block autoplay with sound. For inline mobile autoplay, muted and playsinline are often needed, and playback is never guaranteed.
You can test this using a small local HTML file. Change one part at a time and check the result in the browser before adding more code.
A Working Example
The first part shows a problem. The second part shows a safer or more accurate version. Compare them before reading the explanation.
<!-- Problem -->
<video src="intro.mp4" autoplay></video>
<!-- Corrected example -->
<video src="intro.mp4" autoplay muted playsinline loop width="640" height="360"></video>What Each Part Does
- The video element provides a video player when a compatible source exists.
- src points to the asset the browser should load.
- width reserves the image or embedded resource’s intended horizontal dimension.
- height reserves the image or embedded resource’s intended vertical dimension.
Before the fix, the browser can behave incorrectly or report a warning. After the change, test the exact failure rather than assuming the page is fixed.
Try It Yourself
Test browser autoplay policy and provide controls where the visitor needs to play or pause.
Common Beginner Mistakes
- Check the underlying cause before changing unrelated tags.
- Changing several parts of the example at once, making it difficult to see which part caused a different result.
- Choosing a tag only because its default appearance looks right, without checking whether it describes the content correctly.
Key Takeaways
- Browsers commonly block autoplay with sound. For inline mobile autoplay, muted and playsinline are often needed, and playback is never guaranteed.
- Before the fix, the browser can behave incorrectly or report a warning. After the change, test the exact failure rather than assuming the page is fixed.
- Test the markup in a browser, and check accessibility and real-world behavior where relevant.