Chrome Audio Fix in SL360

The release notes state: Enhanced: We added support for Google Chrome 66. If audio stopped working in your Storyline course, install the latest update and republish.

The forum Update 3 post states: Fixed: Published content stored on your local computer wouldn't play in Google Chrome 64 and later.

Which is it?  A local computer problem or a problem with every course sent to the field?


51 Replies
Justin Grenier

Good Morning, Paul!

In the scenario you described, does the first slide contain audio?

If the first slide contains audio, based on Chrome's Media Engagement rules as I understand them, I would not expect the audio to play.

If the first slide does not contain audio and the learner is interacting with the content before audio appears, I would expect Chrome to interpret the learner's interaction as explicit permission to play the audio.

If the first slide contains audio that is playing successfully in the scenario you described, I would want to check the learner's Media Engagement Index (MEI) by using Chrome on that learner's machine to visit chrome://media-engagement/.

Let us know what you find!

Paul Bailey


Thank you for the response.

What you are describing sounds like the user experience if the course had been published on 360 version 3.15.155581 or later. (perhaps I am mistaken or confused)

I am trying to confirm the NEW user experience for if our courses have NOT been re-published on the version that has the "fix."

If a ...

  • Chrome 66 user (that has not modified their settings)
  • that has NEVER used our LMS
  • engages  with a module published with a 360 version prior to 3.15.155581
  • which does contain audio
    ... would you expect anyone as described above to hear the audio?
Justin Grenier

Hi again, Paul.

My description above is what I would expect to happen in any version of Storyline 360 content prior to Update 15.

Here's what I'd expect to happen in Storyline 360 Update 15 or later:

  • If the first slide contains audio and we detect that Chrome is blocking auto-play of that audio, we place a play button on the first slide to allow the learner to initiate the audio.
  • If the first slide does not contain audio and the learner is interacting with the content before audio appears, I would expect Chrome to interpret the learner's interaction as explicit permission to play the audio.

Please let me know if I can help to clarify further!

Mark Ramsey


We're still using Storyline 2. There is a bit of a movement here to see if we can move to 3.

We are also trying to deal with the audio slider failing in a course published to HTML5, with the player set to scale. We are actually thinking about taking off the audio slider in our interface because of this issue. But I understand this has been dealt with in Storyline 3?


Ashley Schwartau

What a super fun issue we all get to deal with. *facepalm* So, here's a question that my team and I are confused about: how the heck do we test this if the MEI is going to build up and remember that we've interacted with a domain before? With all of the translated versions of our inventory of courses, we have 120+ courses to republish in order to make sure they function correctly in our demo portal. But if we upload something to our demo portal, after a while, it'll remember that we've been to that domain and just start working right? Will clearing our cache clear the MEI?

What about in the SCORM Cloud? How does that work? Does it 'reset' each time you launch/test a course?

Trying to better understand since we have a daunting task ahead of us, not only republishing everything but also testing to make sure its good to go, so any suggestions you can provide or light you can shed on this issue will be helfpul. :-/

Still curious about those two bolded questions if anyone has any answers or insight?!?!? This is a big issue for us right now and we're not sure of the best way to move forward.

Ashley Terwilliger-Pollard

Hi Ashley,

One of the ways that I've been testing is viewing content in an incognito window in Chrome. Another option is to check your MEI, and see if that's a site that's appearing for you. (You can visit this page chrome://media-engagement/ to see yours). 

As for SCORM Cloud, it won't necessarily reset just because you're launching a course again, but it may present you with the play button if Chrome detects media that is attempting to autoplay.

Justin also shared an update here regarding our plans for a content updater for Storyline 2, 3, 360 and Studio 13 and 360. We'll keep you posted about those as they become available.  

Crystal Horn

Hey everybody. I'm excited to let you know that we just released update 17 for Storyline 360! It includes new features and fixes - check them all out here.

One of the fixes addresses an issue where in HTML5, the audio on the first slide was not playing when viewed locally on Google Chrome Version 66.

Here’s how you can update Storyline 360 to take advantage of everything the latest release has to offer. Let me know how you make out!

Chidamber Pujar

I do not think this Play button/ Audio not playing on the first page has been resolved in Articulate 3 for Chrome 66 and above (having issues with HTML5 version)....I have the latest update from the site, but i am still facing the same issue.

Can someone confirm if there has been a fix?

Ashley Terwilliger-Pollard

Hi Chidamber,

It's fixed in the latest updates for Storyline 2, 3 and 360. Take a look here for more details on video playback in Chrome(link in there for the audio version as well). If you had previously published content you'll need to publish that again and re-upload to your LMS/web server. I'd also test out the newest upload in an incognito Chrome browser or clear your browser's cache to ensure you have the latest version of your course.

If you confirm the above update and the audio/video is still not working for you, can you share a copy of your .story file for us to take a look at? 

Chidamber Pujar

Thanks for the reply Ashley.

We have the latest update installed on my machine & i have tried republishing & testing it on Chrome, but the audio does not play on the initial welcome screen only on Chrome (Version 67.0.3396.99 (Official Build) (64-bit)).

Have attached a sample story file for your kind reference. 

Appreciate your help in this matter.






Crystal Horn

Hi Chidamber.  I published and uploaded your example file to web.  I also tested launching the output locally.  Your course played as I expected it to - blank on the first slide, and then the elements on the second slide working as designed.

What exactly are you seeing on your end?  There isn't any audio in that file, and I didn't see a play button appear when launching the course in either environment.

Alyssa Gomez

Hi Chidamber!

Thanks for sending over the new sample file. I published it to Web using Storyline 3. When I tested it in Chrome 67, I was able to hear audio on the first slide. Here's a screen recording of my testing. 

Could you also test this link and let me know if the audio on the first slide plays for you?

Chidamber Pujar

Hi, Thanks for trying it out...I am trying the same (have cleared cache, rebooted, tried on 5 difft machines etc) but it does not load on the first instance...
- I launch the course using the story_html5.html in chrome (Version 67.0.3396.99 (Official Build) (64-bit))
- the audio on the first page does not play on the first go.
- If i go to the next screen & come back, the audio plays properly.

Have attached the published files for your reference. What am i doing wrong? Please note that this happens ONLY if i publish it in Articulate 3...if i publish in Articulate 360, it works fine. 

Chidamber Pujar i get it...why your course is running...
I am facing this issue when i run my course from my local machine...that is my clients requirement too...a standalone course...
I am not facing this issue in Articulate 2 or 360...only in Articulate 3

That is what i am trying to say, the standalone issue has not been fixed in Articulate 3...can you please confirm?

Chidamber Pujar

I do not think this is an apt solution. When the same solution works for Articulate 2 & 360...why not for Articulate 3?
Running of EXE in many environments is not possible.

The patch for Articulate 2 & 360 made it work on Chrome, why can we not have a proper patch for Articulate 3 as well?
So as the patch is not yet ready for Articulate 3, Can you please update me as to when would this be made available? An early solution would be quite helpful...