Blurry Images in Preview and Published

Hi M., 

It sounds like you may be running into a similar issue as described here, although you also mentioned blurry in publish?

The blurriness while editing or previewing it may be connected to the changes we put in place for high resolution monitors. You can modify the DPI setting to display at 100% and that should change what you're seeing. 

We are also aware of an issue with the published output appearing blurry in Google Chrome while viewing the HTML5 output - but it appears normally in IE11 and Firefox for both Flash and HTML5. 

Some general best practices for working with images (and any media) are described here, and it does sound like you're following along with those but worth a double check. 🙂

If any of the above ideas don't help, I'd love to take a look at one of your files with a few sample images. You can share it here using the "add attachment" button at the bottom of the Reply window. 

Scaling DOWN an image will cause blurriness? That's awful/bizarre/unfortunate news but thanks for pointing that out to me. 

Sorry M - any scaling can cause issues with how a picture is displayed. If you need us to take a look at any examples or want to share thoughts on what you'd like to see us do differently, we're always happy to have that conversation here in ELH or as a Feature requests here. 

Sorry - it's just odd to hear about image degradation coming from scaling an image down in size (assuming you maintain exact aspect ratios). AFAIK it has always been best practice when dealing with images to scale down but NEVER up or you will greatly impact the images quality - so i was shocked to hear that scaling an image down in Storyline results in blurry images.  

Why would Storyline allow for the scaling of images within Storyline if this is the case?  Honest question.

Hi M., 

Storyline won't stop you from scaling an image - we want you to be able to insert and modify content as needed. Some instances the blurriness may not be noticeable or as large a concern depending on your course needs and users. 

The best practice is to insert the image at the size you need - that allows you to edit, modify, and create images in a specific editing tool and then use those in Storyline. The best of both worlds. 

Hi Ashley,

I'm running into this issue as well. And as you said it only seems to be affecting Chrome. Is Articulate working on a fix for the Chrome issue or is that something Google needs to fix?

Hey there, Adam and Natalie.  We've documented an issue where the HTML5 output appears slightly less crisp in Chrome than in Firefox or IE, for example, and we've given it priority.

In our research, we discovered that Chrome has this issue documented.  We're waiting on some movement from them, since at least part of the problem is outside of our control.

I'm sorry that your courses are impacted, and Natalie, I know you mentioned that you primarily rely on Chrome.

The current workaround is to use Flash first publishing to improve the Chrome blurriness.  Your course can still fallback to HTML5 output if Flash Player is not enabled or supported in the learners' browsers.

Hi Charlotte and welcome to E-Learning Heroes :)

I do not have an update at this time, but our team is investigating this issue as well internally to see if there is anything we can do.

It seems to be related to Chrome and HTML5 output.

I will add this thread to the report as we track user impact and so that we can update here when we can as well.

Having the same issues and with many of our users using Chromebooks it is causing many problems. We try to use Flash as suggested but it seems everytime Chrome runs an update they make more hoops you must jump through in order to enable to flash. We are an online k12 school and it very difficult to get the information to all of our users. Please make this fix a priority. 

One thing I don't understand. This is not an issue in Storyline 2 as far as html5. I love the new updates as far as allowing shortcut keys and the player updates with Storyline 3 and html5, but I feel this is a big problem. Why the change from no problem (SL2) to a problem (SL3)?

Hi Amy,

With Storyline 3 and Storyline 360, we rewrote our HTML5 publishing engine to provide broader support for HTML5 browsers and other features. Although that may not be the cause of the issue, it does make for a different set up in Storyline 3 than what was originally in Storyline 2. 

The issue is one our team is still working on and checking varying Chrome versions and how those compare to other browsers such as IE, Edge, Firefox, etc. Once we have any additional information to share we'll be certain to update the discussion here.