What we’re doing to help you update your courses for browser auto-play settings (updated 12/06/2018)

May 15, 2018

Recently some common browsers, including Chrome and Safari, have started blocking auto-play of audio and video content on the sites you visit. That includes audio and video in e-learning courses that are hosted online.

That means that audio or video on the first slide of a course will not automatically play. It also means that videos and audio won’t work when learners suspend a course and restart on a slide that contains audio or video. Your content won’t be affected by this issue unless videos and audio are set to play automatically.

Unfortunately there’s nothing you can do to override the browser’s settings. That’s why we released updates for Storyline 360, Studio 360, Storyline 3, and Storyline 2 to automatically detect when this occurs and present the learner with a play button overlay. That user interaction is what the browser needs in order to play the audio or video. If your courses have a required user interaction on the first slide and no media, you may not need to republish to have the media autoplay.

We’re working on a content updater for Storyline 360, Studio 360, Storyline 3, Storyline 2 and Studio '13 that’ll let you mass update all your courses. In the meantime, you’ll need to republish your courses one at a time to fix this issue.

We know this is super frustrating, and we’re so sorry for the trouble. We’ll keep you posted on our progress.

UPDATE (12/06/2018): We've now created a tool that lets you mass update existing courses without republishing them. Currently, the updater works on Storyline 360, Storyline 3, Studio 360, Storyline 2, and Studio '13 courses. See this article for details!

159 Replies
Justin Grenier

A quick update:  Since the original release of Chrome 66 effectively broke a lot of web content, (such as e-learning courses with audio introductions), Google responded to the cries for help and rolled back their audio policy in an update to Chrome 66 on May 15, 2018.  We recommend updating Chrome to the latest version, which allows audio to autoplay as expected.

But this reprieve is temporary.  Google will stop autoplaying audio again in October 2018 when Chrome 70 is released. And with the software updates and content updaters mentioned above, you’ll be ready.

Will Findlay

Unfortunately as most of our content is in an LMS where we have no FTP access (it allows course content modifications, but only through a web interface), updating is going to be a major issue for us. Any chance Google would be open to some enhancements like 1) telling the user sound has been blocked and 2) providing the user a way to turn sound on?

Ashley Terwilliger-Pollard

Hi Cassie, 

Did you confirm you're also using the latest update of Storyline 360? The 3.15.15581.0 update included the fix for Chrome autoplay, and we also have a new update available today of 3.16.15842.0 which fixes the issues here.  

The changes Chrome made will only impact Audio, the Video items will still not autoplay and you'll see that play button to start. 

Leslie McKerchie

Hi David, 

Great questions.

1. We do not have an ETA on the updater, but we will be sure to update you here when we can.

2. The updater will be individual to the products/version the content was created on.

I wanted to be sure that you saw Justin's update here regarding the Chrome auto-play that was originally posted as well.

Paula DeYoung

Hi Justin.  I apologize in advance if I'm being slow, but does issue affect all slides where video is set to auto play or just when it's on the 1st/opening slide (or resume slide with video)?  In other words, do I need to add launch buttons to each slide with video for it to work properly?

Thanks in advance,


sebastjan f

problem occurs if you have audio on the first (starting) slide. All other slides work fine.

My solution:

- add a blank dummy first page and add "Jump to #your original first slide# when timeline starts" trigger.

Probably causing some delay and influencing user experience.. but at least it is working.

To the Storyline team:

- we need some sort of "batch update" .. just checked - we have over 1100 *.story files.. republishing is not my favorite option :(


This discussion is closed. You can start a new discussion or contact Articulate Support.