What's inside a .story file, and how to open one without Storyline

You've been sent a Storyline course to review, translate, or sign off on, and you don't have Storyline. Here's what the file actually is, and what your real options are.

What a .story file actually is

A .story file is the source project Articulate Storyline saves while a course is being built: every slide, every layer, every trigger, every quiz question and its correct answer, every piece of on-screen text, and references to every image, audio, and video file the course uses. It is not the finished course a learner sees. That's a separate, published output (usually a folder of HTML/JS/SCORM files, or a single web package) that Storyline generates from the .story file when the author is ready to ship.

Structurally, a .story file is a zip archive with a different extension, containing a set of XML files that describe the course. That's why the content inside it is fully readable by software other than Storyline itself, if that software knows how to parse Storyline's specific XML structure, its trigger and variable model, and its per-slide layer system. Generic zip or XML tools can see that there's data in there; they can't make sense of what any of it means.

Why you can't just rename or unzip it into something useful

Renaming a .story file to .zip and extracting it does technically work; you'll get a folder of XML files. What you won't get is anything readable. Storyline's internal XML uses its own tag names, its own ID scheme for cross-referencing slides and triggers, and its own encoding for things like quiz answer correctness and variable logic. There's no single file in there that says "here's the text on slide 12" or "here's the correct answer to question 4" in a form a human can just open and read. Making sense of it requires actually parsing that structure, the same way a spreadsheet program has to parse a .xlsx file's internal XML to show you a grid instead of markup.

This is the wall most reviewers hit: they have the file, they can technically look inside the zip, and none of it means anything without a tool built to interpret it.

Your actual options

• Ask for a Storyline license. Works, but it's the most expensive and slowest option for someone who just needs to review one course once, and it's often not something a reviewer, translator, or compliance officer is in a position to buy or get approved quickly.
• Ask the course developer to publish and share the output. Gets you something viewable, but published output has already been flattened; the quiz answer key, the full on-screen text in reading order, and the file's own internal accessibility data (alt text, captions) are all harder or impossible to extract cleanly from a published package, and re-publishing every time something changes for review is slow.
• Use a tool built specifically to read the .story file, without needing Storyline. StoryAudit reads the .story file directly in your browser and turns it into the things a reviewer, translator, or LMS admin actually needs: a slide-by-slide read of everything on screen, the quiz answer key, an accessibility and broken-reference check, and (if you were sent two versions) a list of exactly what changed between them.

If the file won't open at all (Storyline says it's corrupted, or nothing happens), that's a different problem: see what to do when a .story file is corrupted.

What StoryAudit shows you, with no Storyline license

Drop a .story file into StoryAudit and it reads the file the same way Storyline itself would, entirely in your browser (nothing is uploaded anywhere; see the security overview if that needs to be verified). From one file, you get:

• Every slide's on-screen text, media, and interactive elements, in reading order, whether or not the slide has a title. Course Docs → Slide-by-slide contents
• The full quiz answer key, every question type, correct answers marked. Course Docs → Review & sign-off
• An accessibility and broken-reference health check: missing alt text, missing captions, broken jump triggers, orphaned slides nothing can reach. Health Check
• If you have two versions of the same course, a changelog of exactly what changed, including quiz answers that flipped correct/incorrect. Compare

↑ Back to top