Courses published for the web no longer loading in Chrome


I am no longer able to launch Storyline 2 files published for the web in my Chrome browser (v.53). They work fine in other browsers, AND for other Chrome users (though I don't know their versions). Is anyone else experiencing this? It's a problem I've only experience over the last week or so. 


ETA: The HTML5 version published at the same time plays in Chrome with no problems.

Thanks in advance,


27 Replies
Ali Goulet

Hi Rachel,

Welcome to heroes, thanks for taking the time to reach out to us here! How are you viewing the course when you're testing the published output? If you open an Articulate Storyline course from your local hard drive, you'll encounter security restrictions from the computer, web browser, Flash Player, and network that'll cause various features of your content to fail. To properly test your published content and share it with others, you'll want to make sure to upload it to the environment for which it was published.

Since you're publishing for the web, you'll want to upload the published output to a web environment, such as tempshare, to properly test it. 

If you're seeing this behavior after uploading it to the web, would you mind sharing your .story project file here? You can add it as an attachment right to a comment in this thread. Thanks! :)

Sara Lulloff

We just started experiencing this issue with SL2 files on our LMS running on Chrome. These files all used to launch and work correctly, and have now stopped working. They launch but only show a blank player. The audio still plays, but nothing appears on the screen. Is this caused by a recent upgrade to Flash? Has anyone else been experiencing this issue in the past few weeks?

Alyssa Gomez

Hi Sara!

Have you recently upgraded Google Chrome? Google introduced a new security feature in Chrome 56 that blocks Flash content unless you give it permission to play.

You can get around this by including the HTML5 output when you publish. Then, bypass the Flash output and launch the HTML5 course directly. Just link to the story_html5.html file in your published output.

If you try that and you're still having trouble, we can help you test the file to nail down whether your LMS is the culprit. Simply send us the original unpublished file using this link, and we'll take care of the rest. 

Alyssa Gomez

Hi Sara,

That's right--if learners are using another browser like Internet Explorer, they'll need a link to the Flash output. It sounds like linking directly to the story_html5.html file isn't a viable workaround for you. 

I'm curious to test your file in another environment like SCORM Cloud to see how it behaves there. Would you mind sharing a copy of it with me? You can attach it in a new thread comment using the Add Attachment button. 

Sara Lulloff

Hi Alyssa,

I attached the original SCORM 1.2 zip file and the SL2 file. I did republish the file out of SL2 and uploaded the new SCORM 1.2 zip file to our LMS, and for the people I've talked to who were having the issue, the file is now working. Do you have any idea why that would be? Thank you, Sara

Indrani Sen

Hello Alyssa,

We are having this same problem elsewhere where the connections are dated and spotty not in our office.  Would you recommend using the html 5 link too?  A

For example:


lso we are accessing this link via a vimeo page as shown in the screenshot.  Many thanks,



Indrani Sen

Hello Alyssa,

All is fine.  It is working well.  Please could you let me know why I am getting a huge white arrow over a black circle before a course opens up. Please see the attached file. It is a flimsy request in comparison to the whole course working.  But thought of asking.  Many thanks


Ashley Terwilliger

Hi Indrani,

That play button is much larger than I'd expect, but it's added in the latest updates to Storyline to account for the changes browsers such as Chrome and Safari have made to the way they handle the autoplay of media items. You can read a bit more about that here. 

It sounds like you were able to resolve the other issue you were having with your video playback though?