Forum Discussion
Horrible quality when uploading images
I don't understand why the quality of images I upload is so bad in Rise. They look fine in browser, but when I upload (and Rise compresses/crunches them) they get fuzzy, pixly and unprofessional.
I upload i png, have also tried jpg - with much worse results. Any ideas? Attached an image showing what I see in Rise v. local browser.
122 Replies
I would also like to be added to any emails about fixes. I'm having this same problem, particularly using Rise in Chrome. When I use Firefox, the images don't look as bad/unprofessional.
Thanks, Julie. We'll post here if we build anything in Rise to help. For now, the workaround is to add _NOPROCESS_ to the file name of the image to prevent compression. You'll only do this for images that appear blurry.
Thanks!
To follow-up on Alyssa's question above. I get blurry images (images of system screen shots) in Storyline 360. They look fine as originals, but compress when publish for review. The same happens if I copy images from power-point. Is the _NOPROCESS_ implemented in Storyline 360 as well?
Hi Charlotte! Thanks for your question. The _NOPROCESS_ workaround is for Rise 360 only, so it won't work in Storyline 360.
Would you mind sharing your .story file and the Review 360 link with our team? We'd like to compare how the images appear in the file to how they appear in Review 360. You can share those assets privately by opening a case here.
Hi Alyssa & Crystal,
The _NOPROCESS_ workaround worked once and then stopped. I've tried re-uploading the image, but I'm not having any luck. I've tried Chrome & Safari - any idea how I can sort it out?Hi D du Bois,
if you're using a labeled graphic with a small image, in which case, Rise will scale the image up to at least 760 px wide so it will blur. If you try to use_noprocess_for that, it won’t work.
I can suggest clearing your browser cache, then save the file as a different name + the_noprocess_Please let me know if that worked for you!
Hi there Renz,
Thank you - after I sent this I discovered the live chat feature on the support page and Hazel managed to get me sorted.
Looks like the _NOPROCESS_ tag needs to be duplicated at times for it to work, in case anyone else is struggling with this:
ImageName_NOPROCESS_NOPROCESS_.png
I really hope the dev team can get this sorted out soon.Is there an update to this problem, because the _NOPROCESS_ trick still works, but there's still some weird anti-aliasing going on without the workaround of my PNGs. Find attached a screen grab of one with the _NOPROCESS_ tag and one without side-by-side literally in the same editor.
Hello, Windesheim Flevoland.
Adding _NOPROCESS_ to the file name of your images will keep the image exactly as you saved it. What you're seeing on the right in your screenshot is your image file after Rise 360 compression. When you run into an image that loses quality as a result of that compression, using _NOPROCESS_ in the file name is the fix.
I don't have an update about other ways to opt out of image compression for your images at this time. We'll let you know if that changes.
I have a proposed solution - get rid of your image compression entirely. I think most designers are aware of image types to use, how to keep the file size small, etc.
This image compression seems to be an ongoing issue that Articulate can't seem to figure out. This indicates to me that they are playing a space they should probably stay out of if 2 years later, the best solution is to bypass it with _NOPROCESS_.
I would rather just manage my image sizes (which I do anyway), than put _NOPROCESS_ in front of all of my file names.
People here have expressed the importance of image quality, and that expectation has only increased over the past year with so much more learning happening online.
Not a significant improvement even after adding the _NOPROCESS_ for me. Does anyone else face the same?
Images are still pixelated, was this solved? Is there a compression issue?
Hi Angela!
You can opt-out of image optimization on a case-by-case basis by adding _NOPROCESS_ to the name of your image file. For example, office.png would become office_NOPROCESS_.png. The image upload and display exactly as you saved it.
If that doesn't work, please send your file our way! We'd be happy to take a closer look.
Hello! Is there an improvement for the poor quality images that result after being uploaded in Rise 360? Any images I've included in the interaction feature Tabs and Accordion using tip mentioned above (_NOPORCESS_) to the file name, the screenshots that are still unclear and blurred, significantly lowering the quality of the experience. Before uploading the screenshots into Rise 360, the images are clear. Please assist!
Hi Taryn! Thanks for reaching out!
The word you need to add is "_NOPROCESS_", please make sure this is spelled correctly and that there are no special characters in the file name.
Next, please make sure the image you are using is not smaller than the image is in Rise. It could be the image is too small and is being stretched out. Please use an appropriately sized image. If you still have trouble, please let us know and send a copy of the files here.
