Blurry Images in Preview and Published
Jun 12, 2017
By
M. Bosscher
I've noticed this for awhile, all of my images I insert into this Storyline 3 course appear quite blurry everywhere - on the Storyline development screens, when previewed and when published (either as HTML5 or Flash).
The images are all smaller than the maximum size, they are at 100% scaling, have no effects applied to them. My Publish settings is set to 100% quality. I've tried bitmaps, pngs, jpgs, all identical blurry results.
I've searched these forums and seen a couple other threads on it , but never found a solution or real explanation for it. I can't send this course over to my client - it's embarrassingly bad.
190 Replies
Hi Ron,
Thanks for popping back in to share your additional findings. I've added this to the report that Crystal shared.
We do recommend using images that do not need to be scaled as you can see in this documentation.
Hi,
How come this is not higher priority? Its not fun at all to have to produce such blurry products. It's not OK at all...
Just updated to latest version (Update 6: 3.6.18134.0) in hopes this would have been fixed, but still no fix...?
It's actually gotten worse after last update. I can see that the scaling is fixed (where the course would be 10% smaller after published to LMS) but the blur is even worse now.
First image below is Preview vs Production.
Second image below is NewPublish vs OldPublish. Notice how the size is different now with the new version, but it's very blurry. Both are opened in same browser, and same LMS. Top is published with latest version SL3, bottom is published with previous version (Click to see full-size).
Hi Stian,
I know your goal is to produce high-quality work, and this bug is getting in the way of that.
This issue is high on our priority list, and we are targeting to release a fix for it in the next update of Storyline 3. While I don’t have an ETA on that release just yet, we’ll let you know as soon as it’s ready.
Thanks for the update. Glad to hear its on it's way! Looking forward to be able to deliver crisp courses again, as it does produce awefull quality as it is now unfotunately.
I'm having the same problem. The images are very blurry when previewing or publishing. This is causing a problem with the QA testing on our LMS. Can we get this fixed? Is there a workaround?
Hi Beth! So sorry the blurry images are causing a problem with your QA testing. Are you also using Storyline 3?
We've prioritized this issue, and we're targeting to release a fix for it in the next update of Storyline 3. I don't have a date for that release just yet, but we'll let you know as soon as we do!
Is there a date for this resolution yet?
Hi Beth,
I don't have a date for the next release at this point, but we'll let you know as soon as it's ready!
Any news? I dont understand why this is not pushed out quicker. Every published course looks blurry and that's not good for anyone.
I agree with the above statement. This is really disappointing and has been an issue for a while. I'm having trouble with blurriness in my previews and now i'm hesitant to publish. Scaling an image down in Storyline 3 makes it almost not even worth it to put the image in. The text is blurry too. Shouldn't it look exactly like my canvas? I can understand a tiny bit of blurriness, but this is way too much.
Hi Evan,
We recently released a fix for this in Storyline 360, and the next update of Storyline 3 will include the same fix.
I know this is impacting your work and causing a lot of frustration. I'm sorry I have to add to that by not having an update to share, but as soon as we know more the team will post in discussions like this one.
YAY!!!! thank you for making this a priority!
Hi,
I am also experiencing this same issue!
When previewing in Storyline 3 the quality is extremely blurry and same goes for when it is published and viewed in Google Chrome. However when viewing in the IE browser the quality is great. But... Google Chrome is the preferred browser for everyone in my company so having the quality of the images depreciate is extremely disappointing, especially when a lot of hard work has been put into the modules.
Since we are locked into using only IE for government contracts, at least until everything is forced into Edge, it currently looks great. I hope if this changes back to blurry again for IE that we are able to roll back to the current version of Storyline 360.
Hopefully you find a solution for both browsers.
Hi Ron,
The latest update of Storyline 360 should look great in IE, Edge, and Chrome. Are you having trouble still in the latter?
Hi, thank you for the responses! I'm looking forward to the next S3 update. I do want to clarify that this fixes the blurriness in the Preview area and also in the various browsers. Is that correct? Thank you so much for your help.
We are only using IE for our client, so I don’t know about Chrome. It’s looking great in IE now. If it were to change is there any way to roll back to the version that was working until that issue was resolved?
Hi there, Evan. You should see improvement in both Preview and the published output of Storyline 3 with the next release. We'll post here once it's ready!
Hi Ron. Here's how you can install previous versions of Storyline 360 from the desktop app!
Thank you!
Any idea as to how long the fix will be for Storyline 3? Producing courses which are blurry is not a good look
is there a way to publish the images uncompressed? i bring them in at the optimized size 100%, but even when i publish at max image quality it still comes out blurry published
Hi Yusuf,
I don't have a date yet, but as soon as we do, the team will share here. We know how important it is to produce high-quality work, so we're focused on buttoning up the rest of this update and fully testing it before it's release.
Cougar,
When you publish, there is an option to adjust the quality of videos, images and audio:
One, tip: Image compression only applies to JPG files.
i have the image quality set to 100, and it didn't make a difference. it's
more noticeable because the images are screenshots.
Hi Ashley,
Could you please prioritize this as a discussion topic with your management team? The community has been asking about this for MORE than 2 years now. Articulate fixed the problem in 360, but neglected S3. My question is how could you neglect S3 when your customers paid good money for it? How is it that 360 was updated and S3 wasn't updated simultaneously (or very shortly afterward)? How is it that we are still talking about this 2 years later? Please advise and give us a concrete timeline for the update. There shouldn't be a work around; there should be a concrete answer. If we don't receive one, who else can we contact at Articulate HQ to express these very clear inequities?
Thank you.