Forum Discussion
Ridiculous save times - teensie file!
I am about to build a course in StoryLine. My file has 3 slides, a small amount of text and 1 graphic 273kb in size. No triggers besides the default ones. No variables. The SL file is 589kb. When I save this file as described, it takes a good minute (60 sec). What can account for this?
As I build this file, will I be facing 2-hour save times?
What can authors do to keep save times sane? I read another thread advising to save locally. I am saving locally.
Thank you in advance for helpful tips on this!
*Note: I removed the 1 element I was working with, a box with a few sentences of text, and tried again. Was saving normally and frequently, then as soon as I applied some styles, the save time went from 1/2 second to going on 4 minutes. This must be a bug. No way a file this small can take 4 minutes plus to save. Help!
5 Replies
- JohnJohnson-6a8Community Member
Thank you all for your replies. I do have SL updated (first thing I check at the beginning of each work day. The file "lives" on the internal drive of my PC. Based on some experimenting I did, the problem may have been network-related. Today, I'm in the same place, same network, and my save times are normal.
I will keep all of your tips handy for future, and thank you again!John
- MuhammadAbbasiCommunity Member
Hi John - that is definitely not normal for a 3-slide, 589kb file, and the fact that it started right after you applied a new style is the biggest clue. A few things worth checking before you rebuild:
1. Try File > Save As to a fresh .story file. If the new copy saves fast, the original had some leftover bloat from the old style or theme.
2. Check whether the style brought in a custom or embedded font, or a large theme image. A font that Storyline cannot embed cleanly can make every save re-process the file.
3. Make sure the file is on a truly local, non-synced folder. Even a folder that looks local can be a OneDrive, Dropbox or network drive - sync tools scan the file on every save and can turn seconds into minutes. Pause sync and test with the file on your Desktop.
4. If you use antivirus, try excluding .story files from real-time scanning just for a test save - that is a known cause of very slow Storyline saves.
5. Test in a brand-new project: apply the same style to a blank file with one text box and save. If that is also slow, the style itself is the problem, and it is worth reporting to Articulate support with both files, as Judy suggested.
The isolation test in step 5 will tell you quickly whether the problem is the style or something on your machine. Good luck with the course build!
- JudyNolletLegend
JohnJohnson-6a8: For an issue like this, it's best to contact Articulate support directly. When you do, I suggest you upload 2 files: the version that saves quickly and the version that saves slowly.
- JonMichaelCommunity Member
That’s definitely not normal for such a small file. Try updating Storyline and checking if the styles are causing the slow save times.
- shoudownloaderNew to the Community
That does sound wrong for a file that small. I would test the styled box in a new blank file first. If the slow save follows that box, the style is likely the cause. If the blank file saves fast, try copying your slides into a fresh file one at a time. It is also worth closing other programs and checking that the file is not syncing in the background. Please share which style change made the biggest difference.
Related Content
- 3 months ago
- 1 year ago
- 2 months ago
- 4 months ago