Storyline says this file is corrupted. Here’s what to do.

What “corrupted” usually means

A .story file is a zip archive holding the XML files that describe the whole course. When Storyline says it’s corrupted, something in that structure didn’t survive intact. It’s almost always one of three things:

• An interrupted saveA crash, a forced shutdown or a lost network drive left the file cut short.
• A sync tool mid-saveOneDrive, Dropbox or a network share rewrote the file while Storyline was still writing it.
• A damaged zip directoryThe index Storyline uses to find everything in the archive broke, separately from the content.

The course content is often still recoverable.

Why Storyline won’t tell you more

Storyline’s open routine either reads the archive or shows one generic error, and it’s the same error whether ten bytes are missing or the whole file is lost. Before you spend time on autosaves, backups or IT, it helps to know whether this file is a five-minute fix or gone.

What to try first

1. Check Storyline’s autosave. Storyline keeps a recovery copy alongside the working file, and offers to recover unsaved changes on the next launch. It may be a clean, more recent copy.
2. Check the file finished copying. If it came from a network drive, OneDrive, Dropbox or an email attachment, copy it again straight from the source, after any sync has finished.
3. Get a specific diagnosis. If neither turns up a working copy, run the free diagnosis. It says what’s wrong and how much of the course is still there.