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.
Hi everyone!
Do you have an image that looks blurry in Rise 360? We've designed a workaround to keep your images looking crystal clear.
If you'd like an image to keep its specific file format and not undergo compression, you can opt-out of image optimization on a case-by-case basis. Add _NOPROCESS_ to the name of your image file. It'll upload and display exactly as you saved it. Keep in mind that the 5GB file size limit still applies, and you could see an increase in your output file size.
Wonderful, thank you! :)
Hello, I am trying this when saving a PNG file and it does not seem to work. Is this still supposed to be a work around or is there something else to try?
Hello, Sara. You should be able to add _NOPROCESS_ to the file name, at the beginning or end, right in your file explorer:
When you add that file anywhere images are supported, you'll see better quality. If that isn't working, would you please share your image file with us here? We keep everything private and delete your files when we're done troubleshooting!
Hey Crystal
I have been going some grief trying to get my images which look sharp in Photoshop to remain that way once in Rise. Does the info you gave out here still stand?
So a file format might look like this: great_image_NOPROCESS_.jpg
Would that be the correct way to do it?Many thanks
FrazerI've been using this fix and it does still work! So long as you have _NOPROCESS_ anywhere in the file name it should work.
Hi Michele,
I have images under 5 MB - pngs and jpgs and everything I upload looks very poor. I have tried everything I know along with the recommendation from Rise and the results are unacceptable. The images themselves when view on my mac is crisp. This issue really needs to be worked on!
I don't think Rise should be doing the work for optimizing images, since it clearly is not working. Rise users should take that task on and upload the proper image size theirselves - maybe that'd work better.
I agree. 2 years is a long time to figure out a compression algorithm, and for the response to remain "we are working on it". I imagine it just hasn't been a priority, and it won't be until the community vocalizes the need. So I just wanted to add another voice here. This needs to be prioritized and a ballpark time frame would be appropriate, if only to maintain credibility in the forum.
It's now been six years since this post and it's still a problem. I'm bringing it up again in the hopes it'll become a priority.
Seriously!
Yep. Good call Matt! Agreed.
Hi everyone,
The only way I can get around this problem is to upload high quality, 300 dpi images to Rise. They have to be under 5 MB though, or they won't upload. If you use a graphic already sized for the web, the end result is unacceptable. Here's the article that finally helped me figure out what to do:
Kayla, I'm only guessing, but I think screenshots taken with iPhones and iPads may be larger files sizes than you can get from a Mac or PC desktop computer. It would probably be a pain to experiment with it, but it might be possible to get a more useable file by collecting your screen shots that way. That's my best guess, anyway. Good luck! :D
Hi everyone! I've noticed that images appear to get cut down to as much as 30% of their original image size, visibly impacting quality. Also, sometimes exported images are saved as JPG and others are PNG - is there a reason for this?
I'm using a fairly time-consuming workaround:
- Export the Rise course
- Open the assets folder (content > assets)
- Open the folder of the original images (the largest original image is 3.3MB)
- Rename each original image to match the name in the assets folder (these names appear to change with each time you export FYI)
- Re-save as JPG as necessary
Does anyone know of a faster workaround?
I've noticed this issue has been happening for quite some time now, based on what I'm seeing in forums. Is there an ETA when this will be resolved?
Surprisingly this issue is still the same in Rise 360. Adding _NOPROCESS_ doesn't do the trick for me. I would like to add my vote. Thanks.
Hi Kayla and Andrew,
Thanks for your posts!
I don’t currently have any updates, but you are now subscribed to this conversation which means as we share updates here, you’ll automatically be notified.
Hi All! We are having this problem as well- particularly with screenshots for software training that we are working on. They look great in their original format but then when we put them in Rise they are fuzzy and hard to read. The workaround that I found was that if I save the image as a .GIF it will pull in with less loss/compression issues. It's still not 100% ideal, but it's good enough that we are ok to use the images in our course. Hope that helps!
Currently on a trial period as 2 colleagues are already Articulate customers.
I'm trying to develop an e-learning presentation for our different softwares but I'm quite disappointed by the quality of screenshots considering that my presentation needs a lot of it... I've been looking through the different guide and best practices but it looks like I reached a wall with this topic and the two years issue. Guess I'll stick with ppt for now...Hi everyone. For those of you continuing to see issues with images you use in Rise 360, we'd like to help. Matt, Jason and Anthony, please watch for an email from us. With your permission, we can test the image files you're using to see if we can make further recommendations while we work on this issue. We'll delete your files when we're done troubleshooting.
Thank you for sharing the impact this issue has on your work.
Tracey Flanders mentioned above that using gifs rather than jpgs or pngs saves a significant amount of quality. For anyone who hasn't tried this yet and who might still be looking for an immediate solution, this has been our workaround, too. I can confirm that gifs make a noticeable difference.
