Detecting html5 compatible browser on desktop and playing html5


I understand that using Articulate Storyline you can publish to:



iOS by the articulate player

I also understand that if the browser doesn't support Flash, and you select the right options when publishing, it will open an HTML5 version eg Safari on an iPad

My client has asked who has a mix of Chrome browsers and IE8 browsers on desktops - is it possible to set it up on launch it detects if the desktop has an HTML5 compatible browser, eg Chrome, and then plays the HTML5 version, but if the desktop computer has a non HTML5 compatible browser, eg IE8, it then plays the FLASH version?

Thanks heaps


7 Replies
Peter Anderson

Welcome to Heroes, Kate

Great question. Here’s how Storyline determines which version of your content to display when users view it:

  • Users will first see the Flash version of your content if their browser supports it.
  • If they're using an iPad and if you chose the Articulate Mobile Player option when you published, they'll see a launch page that allows them to view the course in the iPad app. (And if they don't have the app installed on their iPad yet, they'll see an option to install it.)
  • If they're using an iPad and you didn't choose the Articulate Mobile Player option when you published, but you did choose HTML5, they'll see the HTML5 output in mobile Safari.
  • If they're using some other non-Flash compatible browser and you chose to publish for HTML5, they'll see the HTML5 output. (For a list of supported browsers, click here.)

There's more information here. Hope that's helpful, and welcome again!

Jeff Forrer

Question.  So when you get this message, for instance on an HTML 5 course produced by Storyline (running in IE).

"Unsupported Browser
The HTML5 player does not currently support this web browser.

Click here to view this project using the standard Flash player. "

Is there a way to make it so that it is seemless to the user to run the Flash version instead vs. showing the message?  If so, how would you adjust the HTML or whichever files need to be to rid of that message for the end user?  Thanks!!

Jeff Forrer

Sorry, I probably wasn't very clear on my note.

If I have a course published to HTML 5 and provide a link and we don't know what browser our end user will use, (i.e. Chrome vs. IE), and they click on our link to our HTML 5 course, in IE is gives the unsupported browser message to the user, in Chrome the course plays.

So, if for the IE situation, instead of giving the Unsupported browser message, can we just have it show the Flash version vs bringing up the message and needing our users to have to click the link to the swf version?

Thanks again!

Peter Anderson

Hi Jeff, 

Are you able to attach the link to your course here, or PM it to me? If you're linking directly to the HTML5 file, I'm not sure there's a way to alter the version that launches depending on the browser. However, if you're linking to the story.html file, it should default to the Flash version. Out of curiosity, is there a reason you'd like the default launch to be the HTML5 version? 

Simon Perkins

Hi Peter

Are you saying that it's best to have an LMS call the standard story.html file instead of story_html5.html?  In which case Flash will remain the preferred experience by default, but SL will know that the html5 version is present (if it is) and use that if browser permits.  But what happens if the LMS calls story_html5.html?  Does it not fall back to Flash?

I've also noticed that I don't see HTML5-specific animations unless I run the story_html5.html.  I thought a PC should behave the same locally as an LMS, i.e. if I call the normal story.html file then surely it should play the html5 anims because my browser is ready for them?