Flash Player 23 and Later in Google Chrome - Local Playback of Published Content

Sep 13, 2016

Hi all, 

Our team recently discovered an issue with Google Chrome and Flash player 23 (and later) that is causing some issues with the local playback of published Storyline and Studio content. This is a new security feature of Flash player 23, and if you attempt to launch content locally you may see just a spinning circle or Flash player notification.

Our recommendation at Articulate is to always test the content in the intended publish environment by uploading to your web server, LMS, Articulate Online, etc. You can see a few options detailed here for locations to test your content. 

If you need to view e-learning projects on your local computer, your best option is to publish for CD, then double-click the launch file in your published output.

Another option for local playback is to add one or more trusted locations to your local Flash Player settings. For example, you could add folders where you commonly publish content, such as your desktop or the My Articulate Projects folder in your documents.

Please feel free to let us know if you have any questions about this! 

146 Replies
Ashley Terwilliger-Pollard

Hi Eric,

Since we don't recommend local playback of the published content ever based on previous security and browser restrictions, I would say so. We did update Storyline to give a prompt about the issue if folks are trying to play the Flash content locally as well. So that will at least help them know why it's not working. Also you'll always want to look at uploading the final content to your intended publish destination. 

Ashley Terwilliger-Pollard

Hi Nancy,

Are you unable to upload it to an intended web or LMS Environment? That is our overall recommendation to prevent this behavior, as the local playback could run into other security/browser restrictions? 

You'll also want to confirm you've set the top most location within your local directory, not just that one particular file or folder. 

Susana Olivares


I develop e-learning courses for participants in developing countries with often very slow Internet connections. Therefore, providing the course on CD/DVD is a must.

The disc has an index page with links to each video's story.html. However, none of these have worked since the Flash update.

The only thing we could do is to ask users to open each folder themselves and double click on the Launch_Story.exe file.

But this is not an acceptable solution. Although we created "how-to-play-the-videos" step-by-step instructions, requests for technical assistance, as well as negative feedback from users, have increased dramatically.

When can we expect a solution?


Susana Olivares

Hi, Asheley,

Thank you for your reply. I am aware of the problem and have tried all the workarounds provided. I even came up with my own, as I mentioned in my post, but the process is clunky, and requires that my users tinker with their browser settings and/or computer.

I am confident that Articulate developers can find a way to circumvent the Flash security settings, or investigate the possibility of configuring the Storyline output to something other than Flash, or bundling your own player in such as way that it can be accessed directly from a simple html link. Who knows? You guys are the experts.

Thanks again. Look forward to hearing more.

Justin Grenier

Hey, Susana.

We've heard the cry for HTML5-only output that avoids the security restrictions of Flash.  It was a herculean effort so we couldn't fix it in Storyline 2, but in case you haven't heard, we completely overhauled the publishing options for Storyline 360:

Publish Formats

You can read more about that here.  Hope its helpful!

Steve Yurkiw

Seems I'm late to this party. Just created a story in Storyline 3. Published it and tried to view it through our LMS (Desire2Learn). The file displays but the circular loading pattern never goes away - it continues to display in the background regardless of where I navigate to in the story.  Using FireFox 53.0. Have tried to publish without Flash, just HTML5 but the results are the same. Any ideas why this is happening?

Ashley Terwilliger-Pollard

Hi Steve,

I can't imagine why Desire2Learn wouldn't support Storyline 3 - but if the file works fine in SCORM Cloud and a Storyline 2 file works at D2L - that's what it's starting to sound like. 

Both versions - are you using the same publishing options?

  • LMS vs. web
  • SCORM 1.2, 2004, AICC, or Tin Can
  • Flash first with the HTML5 fallback ( Storyline 2's main option) 

Do you know if D2L has certain supported browsers too? Here are the supported browsers for Storyline 3. 

Steve Yurkiw

It will be interesting to see, Ashley. I work at a university and our students use a wide variety of devices, I haven't heard any feedback yet, but if something isn't working properly, our students definitely let us know. This is wonderful as it shows they value the resources being created and that they see them as helpful in their learning. Will be back if we run into challenges we cannot solve. Thanks for all your help with this one!

Alex G

Hello there,


I have a published scorm 1.2 package. I don't have access to .story files. Content works with Firefox and IE but not with Chrome. I have tried it with SCORM Cloud and the LMS we use at my job, Cornerstone LMS, and the output is the same. Only the external player is visible, with a link to the menu for navigating through the slides. The slide content is empty. Changing slide this way won't help.


I have checked meta.xml and it was published with Storyline 2.4.1501.717.


Originally, this SCORM was unplayable on Cornerstone LMS using Firefox, IE and Chrome, but I modified the manifest and told it to load index_lms_html5.html instead of index_lms.html. It worked for IE and Firefox, but not with Chrome.


Chrome version is 58 and I had the IT department install me the Chrome specific PPAPI Flash plugin (v25). Chrome is unable to read the SCORM package neither on SCORM Cloud nor Cornerstone. I have allowed Flash under chrome://settings/content.


Edit: I have discovered an issue with Chrome v44 and on that was solved with update 6 of SL2. I have asked for confirmation if they had this update installed when they published.

I'll edit again if the provider tells me anything!








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