What makes published SWF files large?

Oct 01, 2015


I've just taken a piece of content that we previously created using Powerpoint and proprietary Flash authoring tools and recreated it in Storyline 2. The published output produced by Storyline contains over 150 separate SWF files, adding up to over 7 megabytes. Applying maximum optimisation in the publishing settings doesn't reduce this very much. By contrast, our old version was less than 2 megabytes.

The content contains 25 slides, originally imported from Powerpoint but modified extensively, and quite complex use of layers.

Does anyone have any insights into the factors that determine the file size of Articulate's published output, and how to reduce this? Are there any particular features that should be avoided because they result in inordinately large published output files?

Keeping the files small is quite critical for the project I'm working on, so any help would be much appreciated!


1 Reply
Justin Wilcox

Hi Andrew. 

The number of SWF files used to generate Storyline content will be dependent upon a variety of factors. The good news is that our published output is designed to work for the majority of online users, including low bandwidth users. The total size is not really as important as how the individual slides load. You can modify the quality settings of your published output but unless you have a specific reason to do so, I wouldn't recommend it. You can do that in the publishing wizard under Quality. My suggestion would be to not be too overly concerned about overall project size unless you are running into issues that are directly related to that. In most situations, this won't happen. Storyline published output does not try to load an entire presentation when you are viewing it. It only loads the elements of the presentation you need to view the slide you are currently viewing while pre-loading some content in the background. 

This discussion is closed. You can start a new discussion or contact Articulate Support.