Forum Discussion
Poor image quality in Storyline 360
Hey guys,
I have found a few threads on poor image quality of previous versions of Storyline, however the new 360 version has also very poor image quality when piblishing. Please see attached screenshot: original image in high resolution saved in png format, imported via Insert Image into Storyline (smaller size! should work fine!) and when published in HTML5 - you can see this low-quality soapy artifacts.
Please let me know where I can adjust image quality settings to avoid that. It seems not to matter how carefully original images are selected with a good quality -if the end result is poor. Please help!
Thank you!
- SytaFokkema-cddCommunity Member
Hello Leslie (and other heroes),
Has there been a solution to this issue yet? I am still experiencing the same problem with images and video, and am not always able to ask for 96dpi imagery as I use existing content.
Also, my record-screen of a movie within Articulate is incredibly poor quality which makes it hard to make a demo. Is that to do with the same issue?
Love to hear an update!
ps. cant share confidential client file, sorry
Hi there Syta. The issue with blurry images in Chrome is still open with our team. It has a high priority and is being addressed, and I apologize for the issues you're seeing in your current courses.
These are our best practices for recording high quality screencasts in Storyline. We'd be happy to help you one-on-one to make sure your recordings are coming out the way you'd like!
- SytaFokkema-cddCommunity Member
Thanks so much Crystal for the quick reply and tips with regards to screencasts, I can definitely use that.
I've come accoss a number of ways to retain image quality in this thread and am trying to find a summary/overview of best practises (for the time being). Is the below article the most up to date one to go to for best practices on image quality? If so, maybe pin that to the top of the thread?
Thanks again.
- IrinaPoloubessoCommunity Member
Dear Leslie,
When I do the same steps to insert an image in microsoft PPT (be it a copy-paste from a screenshot, or inserting from the file) - I do not experience any problem with the image quality. However the same steps in SL make an image look as a disaster :(
I attach again the fragments, could you please escalate it with your development team for more urgent care? We cannot show our materials like that to our customers :(
I am aware of not resizing the image in SL, but it happens before I touch it even - merely by any insertion method. - IrinaPoloubessoCommunity Member
And yes, I checked out the article with best practices - it does not resolve the issue.
- IrinaPoloubessoCommunity Member
Hi Irina,
Thanks for sharing all those images. It looks like in your comparison files even, one is sized slightly larger than the other? I also saw that you're having a similar discussion here with Alyssa and I'd agree with her ideas to test the Classic player. It looks like the scaling that's occurring within the modern player to fit your browser/screen size may be impacting the overall quality.
Let's keep the discussion going in that forum page, or if you'd prefer to take it out of ELH our Support Team is standing by!
- IrinaPoloubessoCommunity Member
Dear Ashley,
I do use classic player, and unfortunately support says they cannot replicate the issue, leaving me with evidences on my hands quite helpless.
Inspite of the 100% image qualit y setting, chosen for publishing in SL, you can see the low-quality JPEG artifacts on the SL fragment, compared with PPT (which , though not perfectly-crisp, at least does not insert the artifacts)
Hi Yoann,
I'm sorry to hear your experience with images in Storyline has been less than stellar. I know your goal is to produce high-quality work, and this bug is standing in the way of that. I don't have an update to share at this point, but we promise to share any new information we can, as soon as we can.
- ChristaReich178Community Member
Status update please? We are holding off sharing our courses with our project leads as we know they will not find the image quality acceptable.
Hello, Christa!
We released a fix for the issue where text and images could be blurry when viewing a course in Chrome or Safari in Storyline 360 Update 26.
What version and update of Storyline are you using? You can find this detail by going to Help >> About Storyline.
Hi Benoit,
Thanks for reaching out and letting us know that your client is running into some blurriness despite being on the latest update to Storyline 360.
We have some guidelines for high-quality images and videos that can be found here.
I'm curious if the image was scaling up or down as that may be the cause of the blurriness.
With your permission, I'd like to take a look at your project file to investigate what's happening. You can share it publicly here, or send it to me privately by uploading it here. I'll delete it when I'm done troubleshooting.
- PatrickSchmidCommunity Member
If you come to any solution it would be great if you posted that publicly, so everyone here can profit.
I pretty much agree with Benoit that the automatic resizing of images when importing them to Storyline is the main problem here, not a bug that might or might not cause images to appear blurry in chrome.
- BENOITGUILLOCommunity Member
Hello Patrick,
Sure, and whatever we will conclude, we will share. But first we have to check precisely what's wrong because I could also have made a mistake. We are now comparing original screenshot VS released integrated screenshot seen by users VS screenshot stored in the mobile folder's SL release.
- LuisLastraCommunity Member
¡Hello there!
Same issue here: Every single image are getting in lower resolution in preview and HTML5 exported files.
¿Any clues?
Thanks in advance.
Hi Luis! I opened a priority support case for you since you are an Articulate 360 Teams member. You should receive a confirmation email that includes an upload link. Feel free to share your .story file and any image source files as examples so we can test. We'll delete your files when we're done troubleshooting. Thanks!