Forum Discussion
File size? Slow to publish
Hello,
I have a Storyline file that is 87 MB. It is slow to publish if it publishes at all, I have to reduce the quality to publish to Review, and I can not preview the course.
The course is no larger than other courses I have built - 137 slides. There are no large videos - just a few images, text boxes, and audio on each slide. It's a pretty basic course but there is some branching.
Is there a way to figure out what specifically is contributing to the file size and/or slow publishing?
5 Replies
Hello, Erika.
A couple things that may help reduce the overall file size:
- Remove all unused slide and feedback masters.
- Check image format and size. JPGs compress to a smaller size than PNGs. Also, if you edited images within Storyline (e.g., cropping), the image data remains and may effect final publish size.
Sorry you're hitting that snag, Erika!
Great tips from Onoda, and here are a few more things to check and try:
- Is this happening with a particular file or any Storyline project? If with a specific one, do you see any improvements when importing the project into a new file?
- Have you checked that your machine meets the minimum system requirements here?
If you're still hitting a wall, I'm happy to test your .story file to see what's causing the lag. If that works for you, you can share the file privately with me here. I'll let you know what I find, and will delete it after troubleshooting!
Thank you both so much! It is a single file that I am having trouble with but I think the image sizes may be to blame. I hadn't used the media library yet, but that was helpful in finding the largest images. I also had some unused slide masters that I deleted. If I am still having issues after compressing the images, I will try importing it to a new project.
Nice detective work and glad you're enjoying the media library, Erika!
Best of luck, and you know where to find us if you need anything else. 😊
All of a sudden, it was taking a long, long time to publish. Then I remembered I had added a high-resolution logo to the template. That's probably what is killing me.
