Forum Discussion
Webp image format
Hello,
I am new to storyline 360 and when I published my PowerPoint (converted in storyline 360), I found my webp images (PowerPoint has no issue with the format) have not only been converted to PNG file format but drastically reduced in size. So I am wandering why webp file format (10 years old), better at size changing with reduced destruction of the images, smaller in size, and web browsers love them is not used in storyline 360?
Opening my now html version of PowerPoint, I find, when I increase the course size in a browser, I am getting fuzzy images that I did not have in PowerPoint doing the same thing?
So by using storyline 360 publisher I reduce my images using storyline 360 interpolation tool, reducing size and quality, it that about it?
Anyone else see an issue with this? Maybe this feature should be added asap for the best quality images in published courses?
I know I could reduce my image size, make it a png, but in the end I get the same result if I increase the screen size of the course material, yes?
I’ve run into something similar before. A couple of quick things you could try:
1. Storyline doesn’t natively support .webp yet, so it will always convert to PNG/JPG on publish. Best to pre-convert your images to PNG/JPG before bringing them in.
2. Try bringing in larger resolution images than you think you’ll need—Storyline will scale them down on screen, but if learners resize the browser, they’ll still look sharper.
these basics usually keep images from looking blurry after publish.
3 Replies
You're absolutely right to bring this up. WebP is a more efficient format, especially for web delivery, but currently, Storyline 360 converts all images to PNG or JPG during publishing—often reducing quality to optimize performance. This can lead to fuzzy visuals when scaling, especially if the original resolution is high.
A feature to support WebP natively or maintain image fidelity during publishing would definitely improve visual quality. You’re not alone—this is a valid concern, and it's worth submitting as a feature request to Articulate. Hopefully, they'll prioritize it soon!
Hi RichardHanson-2,
Thank you for sharing your experience and feedback!
I’ve informed our product team of your need for WebP image support in Storyline. We’ll let you know if it becomes available in a future update.
Please feel free to share any other ideas or suggestions you may have.
I’ve run into something similar before. A couple of quick things you could try:
1. Storyline doesn’t natively support .webp yet, so it will always convert to PNG/JPG on publish. Best to pre-convert your images to PNG/JPG before bringing them in.
2. Try bringing in larger resolution images than you think you’ll need—Storyline will scale them down on screen, but if learners resize the browser, they’ll still look sharper.
these basics usually keep images from looking blurry after publish.
