12 Replies
Ashley Terwilliger

Hi Katelin,

I see you also reached out to our Support team, and were able to talk through this with my colleague Vic. 

He shared the following: 

Our team just completed our review. We've observed that the resolution of your video file is around 1920x1080 while the project's Slide size is 1024x576. Although both files have the same aspect ratio of 16:9, Storyline will resize the video down to fit its Slide and the disparity between their sizes is what causes the video quality to drop.

For reference, 1024x576 is around 589,824 pixels and 1920x1080 is around 2,073,600 - which means that the video file has 3.5 times more pixels than the Slide. When the video is scaled down to fit the Slide, it loses around 1,483,776 pixels from its original size.
I understand that adjusting the Slide size of your project to match the video may not be a suitable solution for you. Since you've created the video through an Adobe application, would you be able to republish your video file at around the same size as your Storyline project?

That seems to have done the trick for you, so I wanted to share that update here with others. Also, here's a handy reference on best practices for working with high-quality images and videoes.

Leslie McKerchie

Hello Jamie and welcome to E-Learning Heroes :)

Rise courses are fully responsive, and they will adapt to screens and orientation.

We recommend using high-quality videos with a 16:9 aspect ratio for the best results in your published courses. You can read more about that here and here.

If you need us to take a look at a video file, please feel free to share.

The original issue here was for Storyline.

David Price

I realise this thread is a bit old but I am experiencing exactly the same issues.  Video produced at 1024x620 (my project size) looks blurry when inserted into Storyline 360.

I have reduced the size of the video to fit onto one of my layers but whether it is at full size or reduced, its still the same poor quality.  I have changed the compression option to 'None' and it made no difference at all.

My output video settings are set to maximum (9) and still no improvement.  It looks blurry in both preview and published.

My customer is complaining that the video quality is really poor which means I can't deliver it to them like this.  Is there any update on this?

I have attached a screenshot below of a video playing in Windows media player on top of the video playing in Storyline.  You may not be able to notice it on this screenshot, but there is a clear difference between the 2.


Leslie McKerchie

Hi David,

Thanks for reaching out and sharing what you are experiencing in your project file as well as the troubleshooting you've already done.

It looks like you're going through our best practices documentation here, but I did not see you mention locking the player. Are you doing that as well?

With your permission, I'd like you to share your project file with our support engineers to investigate what's happening. You can share it privately by uploading it here. It will be deleted when troubleshooting is complete.

Irina Poloubessov

Dear Leslie,

Following the advices in this article

I first published my video for Review using this settings:
your setting

And then I published my video as an .mp4 with highest settings (it has no sound)
what i see

 The result is that video published as a Story in Review has a way better quality than published as .mp4! Please see ,PNG attached to see the differences.

It is inconvenient for end-product to leave it as a .story becuase loosing the video controls of rewinding etc. Could you please align the output quality for .mp4 too?

Thank you!

Ashley Terwilliger

Hi Irina,

Thanks for those images and screenshots. Is the video a standard video file you've inserted or something created from a screen recording in Storyline? 

If you're able to share the Review 360 link or the MP4 that would also help our team take a look at the differences in published output quality! You can upload at this link using the Add Attachment button or you always have an option to share privately with our Support Engineers. Either way, we'll delete it when done testing.