serving html5 as a default

May 05, 2015


I would like html5 to be served as a default, not flash.

The current detection in the story.html file is filtering by browser not by html5 capability in the browser, and the check for html5 is only done for mobile devices. All others get flash???

Is it possible to add/change the launch page to check for html5 capability first and launch html5 if it is available, and check for flash only if the browser in not html5 capable? I can write it myself however I will then have to maintain my changes whenever I publish. This is not ideal.


11 Replies
Leslie McKerchie

Hi All!

Articulate Storyline lets you publish courses for Flash, HTML5, and the Articulate Mobile Player app. To distribute your published content, upload it to your web server or LMS, then link to the story.html file in the published output. Here’s how Storyline determines which version of your content to display when learners view it.

So, when learners launch your published Articulate Storyline course, they'll automatically see the best version for their device and browser. If you'd prefer to bypass the Flash and Articulate Mobile Player output altogether and only launch the HTML5 version of your course, see this article for instructions.

Modifying the published output is not something we support.

Robert Grimes

Thank you for your response, however, the information in your response does not reflect the facts, 

Looking at the code in story.html we can see that:

1)  Safari and mobile browsers are served html5 by default.

2) All other browsers are served flash.  For non mobile browsers the code in story.html makes no attempt to link to the content which is best suited to the browser (as you stated),, unless you consider flash to be the best content suited for html5 capable browsers.  The code in story.html tests for flash and if flash is available it serves flash. For non mobile browser, it does not test for html5. NOT AT ALL. 

Today the majority of browsers support html5. Users and content providers want html5.  Your lazy approach addressing this issue leaves you on the tail end of the curve. Why do you bury one of your best features?

Also note . I followed the link you provided but unfortunately my German is rusty.

Direkte Verlinkung zu Ihrer veröffentlichten HTML5-Ausgabe






Mark Freeman

I hope your development team reviews how the Flash Default is more problem than solution. Example: There is an unscheduled browser security update which doesn't automatically update Flash Player. The user may not be aware that Flash needs to be updated, so when they access the course in the LMS (ie Moodle) the course is just blank. And since the course thinks the browser is flash-based, it will not go to the alternative start-ups. This is a major problem with my government clients as they just cant update the Flash Player on their own , an IT support request is required even though I have given them the solution to update.

This is real world Issue!!! I hope development is listening. There may be other government clients with the same problem.

If there is not going to be an update to allow setting the default at the time of publishing, my clients may insist on me developing courses in Captivate.

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