When publishing My Storyline courses on HTML5 format, I am having an issue with pictures that are displayed after a couple of seconds.
Looking at the published folder nearly all pictures in my course are being created as png files. And those files, even in low resolution are quite large.
For the same file: file size is 957Ko as png and 107Ko as jpeg.
I would like to have all my pictures created as jpeg files while publishing. Is this existing? If not can this be included for future developpement?
Storyline doesn't have a feature that converts all images to jpeg files after publishing. Are you finding that Storyline is converting jpeg files to png files in the published output?
I have populate my course by importing pictures I had on a powerpoint.
When publishing the course, those pictures are png files. Even if they are at low resolution their size is pretty high compared to the equivalent jpeg file.
I am having a large number of pictures, so I will not be able to treat them 1 by 1. This is becoming important as with the stoppage of flash, we will need to publish on html5. With large picture, we are having issues to use the courses: the pictures aree very slow to be displaid.
This fonctionnality is existing in other equivalent software, and would be needed with the extensive usage of HTML5.
The Image Quality slider that you see within the Publish Quality window only impacts JPEG/JPG files, not PNG files.
The reason you're seeing increased image sizes is because the resolution at which we publish PNG files has changed for the HTML5 player in Storyline 3 and Storyline 360.
I really appreciate your feedback and can certainly understand why this would be an important feature for you. I'll be sure to pass all of this along to my team as we consider new features in future updates!
I am having the same issue. Our LMS has a 150 KB/s average bandwidth and publishing HTML5 content with nice graphic backgrounds causes issues. I import .jpeg images to my course and they all get converted into .png's.
The problem is that it can take several seconds to load a slide because of this. The .jpeg version could be 100KB, but the .png that is exported is around 800KB! Huge difference and quality is the same.
PNG's are good for icons and transparency images, but pictures, that's where .jpeg shines. I hope this is resolved soon because our users aren't getting a good experience with this slow loading.
Sorry to hear that you've run into an issue with this. Would you be able to share a sample slide, in .story format, with one of your backgrounds in place so that we could take a look at what is happening during publish.
I have attached a sample of the course. Each of the images are .png files when I export as HTML5 with Flash fallback. The size of the images are roughly 800kb, which causes them to load slowly on our LMS. Is there a way to limit image size or format when publishing HTML5? Or have the system be smart enough to know what should be .png and .jpg?
I did peek at your output file and it looks like the settings were a little different than I expected.
Looks like it's published for the Web > Flash with HTML5 fallback and AMP > and an increased image quality setting.
Have you taken a look at reducing the quality settings to see if that gets you back in ranges you expected? Again, I did open a case for you so that someone can take a look with you :)
Thanks so much for chiming in. Since there are a few different issues mentioned in this thread, can you tell me more about what you're running into? Also, what version of Storyline are you using?
I am using Storyline 2 and 3 but I think I will use Storyline 3 later because we can choose different format of publication. It's interesting for my work.
I'm interested to publish with HTML5 format because Adobe Flash will finish soon... And we need to play the videos/animations after this Flash stop.
Yes, we have the same problem as Julien at our company. When we use Storyline 360 and publish content to HTML5 with Flash backup, Storyline publishes the content very innefficiently by converting ALL images into PNG's.
Problem with all PNG's is that the compression is non-existant and photos end up being almost 10x more kilobytes than of a JPEG image file (which is compressed). It would be nice to be able to have Storyline automatically know which files are photos and which ones are icons and less complex graphics, then choose the type of graphic export type.
Our course load times suffer because of these innefficient photo exports in Storyline 360. If there could be an update to get Storyline to export photos in JPEG format (with adjustable compression), that would be a HUGE help.
I took a look at your case, and saw that Renato also published your files but that they still had the JPEG files in the published output? Did you see his last response? It was on February 16th. Let me know and I'm happy to resend and Renato can keep working with you!
I didn't see Renato's response or published outputs with JPEG images in them. When I published, everything in HTML5 is defaulted to PNG images - including photographs, which is very innefficient and takes up unnecessary bandwidth.
Thanks for following up. I did take a look at the file and saw that photos were in their proper JPEG format. I tried publishing from my storyline with local files and I did see JPEG's as per Renato's published files.
Quick question on a comment Alyssa made earlier in this post.... " the resolution at which we publish PNG files has changed for the HTML5 player". Can you guys give me some details on that? It would be good to know for development purposes.
Has this issue ever been resolved. We are inserting JPG files into our course and they are being converted to very large PNG files. How can I prevent this from happening??
Hi Bob. Sorry we missed this comment! Basically, we're now doubling the sizes of images so that they display at proper resolution on high-DPI monitors.
Thanks for those details, Ted! The .jpg files remained intact in my own file when publishing to HTML5 only, both classic and modern player. Can you use the Add Attachment button here to share your .story file with me?
When you reply via email, attachments aren't included. Your email signature with contact info is in the discussion, though, so feel free to edit it out!
Hi, I'm having trouble with jpeg files converted to png files in the scorm output, This issue increase the size of images and it's a big problem for me. What can I do to avoid the conversion? I need only jpeg files (I'm using the last version of Storyline 360).
Additionally, would you mind sharing your .story file so I can try to replicate the behavior? You can share it publicly here, or send it to me privately by using this upload link. I'll delete it after troubleshooting.
Thank you, I sent you the file privately. This situation is happening with other projects. The .story file is stored locally, while the images are in other hard drive (could be this a problem?). I tried the web and scorm 1.2 publishing format.
29 Replies
Hi Hubert,
Storyline doesn't have a feature that converts all images to jpeg files after publishing. Are you finding that Storyline is converting jpeg files to png files in the published output?
Hi Alyssa,
I have populate my course by importing pictures I had on a powerpoint.
When publishing the course, those pictures are png files. Even if they are at low resolution their size is pretty high compared to the equivalent jpeg file.
I am having a large number of pictures, so I will not be able to treat them 1 by 1. This is becoming important as with the stoppage of flash, we will need to publish on html5. With large picture, we are having issues to use the courses: the pictures aree very slow to be displaid.
This fonctionnality is existing in other equivalent software, and would be needed with the extensive usage of HTML5.
Hi Hubert,
Thanks so much for clarifying that.
The Image Quality slider that you see within the Publish Quality window only impacts JPEG/JPG files, not PNG files.
The reason you're seeing increased image sizes is because the resolution at which we publish PNG files has changed for the HTML5 player in Storyline 3 and Storyline 360.
I really appreciate your feedback and can certainly understand why this would be an important feature for you. I'll be sure to pass all of this along to my team as we consider new features in future updates!
I am having the same issue. Our LMS has a 150 KB/s average bandwidth and publishing HTML5 content with nice graphic backgrounds causes issues. I import .jpeg images to my course and they all get converted into .png's.
The problem is that it can take several seconds to load a slide because of this. The .jpeg version could be 100KB, but the .png that is exported is around 800KB! Huge difference and quality is the same.
PNG's are good for icons and transparency images, but pictures, that's where .jpeg shines. I hope this is resolved soon because our users aren't getting a good experience with this slow loading.
Hi Martin,
Sorry to hear that you've run into an issue with this. Would you be able to share a sample slide, in .story format, with one of your backgrounds in place so that we could take a look at what is happening during publish.
Hi Leslie,
I have attached a sample of the course. Each of the images are .png files when I export as HTML5 with Flash fallback. The size of the images are roughly 800kb, which causes them to load slowly on our LMS. Is there a way to limit image size or format when publishing HTML5? Or have the system be smart enough to know what should be .png and .jpg?
Thanks for sharing the details and your sample .story file Martin.
I've opened up a support case on your behalf so that one of our support engineers can take a look and best assist you.
Be on the lookout for an e-mail from support@articulate.com :)
I did peek at your output file and it looks like the settings were a little different than I expected.
Looks like it's published for the Web > Flash with HTML5 fallback and AMP > and an increased image quality setting.
Have you taken a look at reducing the quality settings to see if that gets you back in ranges you expected? Again, I did open a case for you so that someone can take a look with you :)
Hi,
This problem with the JPEG and PNG is very important for me because I would like to publish courses in HTML5 in th future.
Do you know if this problem is resolved ? If not, when the software will be updated ?
Thanks.
Hi Julien!
Thanks so much for chiming in. Since there are a few different issues mentioned in this thread, can you tell me more about what you're running into? Also, what version of Storyline are you using?
Hi Alyssa,
I am using Storyline 2 and 3 but I think I will use Storyline 3 later because we can choose different format of publication. It's interesting for my work.
I'm interested to publish with HTML5 format because Adobe Flash will finish soon... And we need to play the videos/animations after this Flash stop.
Yes, we have the same problem as Julien at our company. When we use Storyline 360 and publish content to HTML5 with Flash backup, Storyline publishes the content very innefficiently by converting ALL images into PNG's.
Problem with all PNG's is that the compression is non-existant and photos end up being almost 10x more kilobytes than of a JPEG image file (which is compressed). It would be nice to be able to have Storyline automatically know which files are photos and which ones are icons and less complex graphics, then choose the type of graphic export type.
Our course load times suffer because of these innefficient photo exports in Storyline 360. If there could be an update to get Storyline to export photos in JPEG format (with adjustable compression), that would be a HUGE help.
Hi Martin,
I took a look at your case, and saw that Renato also published your files but that they still had the JPEG files in the published output? Did you see his last response? It was on February 16th. Let me know and I'm happy to resend and Renato can keep working with you!
Hi Ashley,
I didn't see Renato's response or published outputs with JPEG images in them. When I published, everything in HTML5 is defaulted to PNG images - including photographs, which is very innefficient and takes up unnecessary bandwidth.
Hi Martin,
I'll resend the email to you - keep an eye out for an email from Support@articulate.com!
Hi Ashley,
Thanks for following up. I did take a look at the file and saw that photos were in their proper JPEG format. I tried publishing from my storyline with local files and I did see JPEG's as per Renato's published files.
Thanks for following up!
Quick question on a comment Alyssa made earlier in this post.... " the resolution at which we publish PNG files has changed for the HTML5 player". Can you guys give me some details on that? It would be good to know for development purposes.
Has this issue ever been resolved. We are inserting JPG files into our course and they are being converted to very large PNG files. How can I prevent this from happening??
Hi there, Ted. In Martin's case, when he published his file to his local drive, his files were not converted to PNGs. Can you confirm...
If you can share your .story file here, I'm happy to test and see what's happening!
I am publishing for LMS
With HTML5 only option
Hi Bob. Sorry we missed this comment! Basically, we're now doubling the sizes of images so that they display at proper resolution on high-DPI monitors.
Thanks for those details, Ted! The .jpg files remained intact in my own file when publishing to HTML5 only, both classic and modern player. Can you use the Add Attachment button here to share your .story file with me?
When you reply via email, attachments aren't included. Your email signature with contact info is in the discussion, though, so feel free to edit it out!
This post was removed by the author
Hi,
I'm having trouble with jpeg files converted to png files in the scorm output, This issue increase the size of images and it's a big problem for me. What can I do to avoid the conversion? I need only jpeg files (I'm using the last version of Storyline 360).
Welcome, Primo. Happy to help investigate!
A few questions to help us narrow down why Storyline is converting .jpeg files to .png ones:
Additionally, would you mind sharing your .story file so I can try to replicate the behavior? You can share it publicly here, or send it to me privately by using this upload link. I'll delete it after troubleshooting.
Thank you, I sent you the file privately.
This situation is happening with other projects. The .story file is stored locally, while the images are in other hard drive (could be this a problem?).
I tried the web and scorm 1.2 publishing format.
Thank you for the support!