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. 

20 Replies
Michele Schuck

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:

https://articulate.com/support/article/Best-Practices-for-Images-Videos-and-Audio-in-Rise-Courses#images

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

CT  Learning

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.

Tracy Flanders

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! 

Ryan Niehoff

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? 

Relton McBurrows

As I'm reading similar threads on this issue, this has been an issue for over 2 years.  2 years ago, some on staff was saying they're working on a fix.  Is there really no fix yet?  I'm hoping to use Rise, but I can't embarrass my department with really bad images.  Can I use whatever method your developers are using to embed the default images?

Ryan Niehoff

Two years is quite a long time to be "working on a solution". My concern is that there's any image compression happening at all. Most stock images or screen shots are captured with appropriate image sizes as well as the proper formats. 

Also, why are some of my original PNG images being converted to JPG? It's very random and I can't make sense of why this happens.

We need an ETA - two years is more than enough time for analysis and determining how long it will take to fix. This tells me Articulate has not prioritized this. The workaround takes HOURS of replacing images because the images are always named differently with each export, and some of those images are flipped to JPG (so I have to re-save my original image as JPG before overwriting the output image file). This compression workaround exponentially increases development time for a tool that's supposed to be quick and easy.

This now needs to be a priority. I have to make my team and VP aware as it may impact our future relationship with Articulate if they cannot pivot quickly to address big problems like this. 

Please let the community know asap of the ETA.

Matt Bassuk

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.   

Anthony Smadja

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...

Crystal Horn

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.