This issue has been fixed in FV Player 7 at the end of 2018. If audible video autoplay is not permitted it then goes to silent autoplay. That works with Android and iOS phones as well.
Update 2023: If you are facing autoplay issues please check if your web server is not setting the
Permissions-PolicyHTTP header withautoplay=(). Changing that toautoplay=(self)orautoplay=(*)will fix the issue.
We received an increased amount of complaints about autoplay not longer working lately. That’s because of the new restrictions set in Google Chrome 66 – the most popular web browser.
I’m sure you don’t like when you visit some website and suddenly there is upbeat music playing from everywhere and you have no idea what’s going on. So companies like Apple or Google are gradually making it harder and harder for websites to play a video without user intervention.
This is how the error appears on browser console
It was working like that forever for mobile users, also saving the precious mobile internet bandwidth. Then the issue became so big that desktop browsers started to address it as well. First Safari 11 (released in September 2017) blocked any autoplay video which is not muted. Now Chrome 66 (released in April 2018) blocks autoplay video unless:
- User has interacted with the domain before by clicking or tapping on the website.
- Or the user’s Media Engagement Index (MEI) threshold has been crossed, meaning the user has previously play video with sound.
2026 update: Media Engagement Index got more complex over time. Currently it “measures an individual’s propensity to consume media on a site” using “ratio of visits to significant media playback events”.
On top of that the following conditions have to be met:
- Consumption of the media (audio/video) must be greater than seven seconds.
- Audio must be present and unmuted.
- The tab with the video is active.
- Size of the video (in px) must be greater than 200×140.
You ca read full details in this article: Autoplay policy in Chrome on developer.chrome.com
So to prevent broken playback we disabled video autoplay in FV Player 6.6.1 for Chrome 66. However it’s only a quick workaround before we get FV Player 7 our the door.
Why don’t you just fix it?
Fixing the issue for FV Player 6 is not easy, specially as the MEI score can’t be reset. That’s really bad for web developers – you simply can’t predict what the first-time visitor gets on your website. Read more in the “In Chrome 66, how do I reset the Media Engagement Index (MEI)?” topic on Google Chrome Help Forum. The answer is you can’t do that (apart from creating a new user account on your computer, or trying to access your website under new domain name, believe me – I tried).
Update for web developers:
You can start a new Chrome browser which won’t have any of the Media Engagement Index set by setting the user data directory to a non-existing folder, like this (the command is for OS X):
/Applications/Google Chrome.app/Contents/MacOS/Google Chrome --user-data-dir=fake-folder --incognito --auto-open-devtools-for-tabs http://example.com/what-you-need-to-debug
Another update for web developers:
It’s easier to just click the Avatar icon in Chrome toolbar and pick “Open Guest Window“. Then you can check chrome://media-engagement to verify no MEI scores are present.
Beside that the developers are really hating it and now Google is already reverting some of the changes:
- Game developers hated Chrome 66. Here’s how Google is making amends on Mashable.com
- Google tried to block autoplay videos on Chrome, But it broke apps and games on TheGuardian.com
Your Google Chrome remembers you interacting with your site, so it will always autoplay videos on your website, while first-time visitors would get into trouble with broken video playback.
Unfortunately the video wouldn’t play at all!
I really hope Google Chrome will allows us to edit the MEI scores using some debug tool soon.
FV Player 7
You might heard about FV Player 7 before and wonder why is it taking us so long to release it. As you might know we use Flowplayer for the core video technology. And while:
- Flowplayer 6 release took only 6 releases before becoming stable
- Flowplayer 7 already has 15 releases out and it’s not clear if 7.2.6 is really the final stable release yet! But let’s not blame the Flowplayer team for it – the evolution of technology is speeding up constantly (not sure if it’s always going the right way though)
So it’s taking a while, but we didn’t just wait, we submitted fixes and bug reports to it as well, so we are really working hard to make sure you get a reliable product.
Now it is about to be launched for beta testing for all of our FV Player Pro users and it handles this scenario well. The video simply autoplays without sound. Then if the user likes the video he might unmute it (increasing MEI score). And the Chrome browser notices that and will allow videos to autoplay on the future visits.
All of this change of how desktop browsers work has an upside as well – the behavior of mobile and desktop browsers is getting unified.
Martin Viceník
Martin graduated as an engineer in Computer Science from Slovak Technical University in Bratislava. He grew up in Liptovský Mikuláš in northern Slovakia next to the beautiful Tatra mountains. He is the developer behind our FV Player.
Leave a Reply