Never wonder what changed
in a Storyline course again.
Drop in a .story file (or two versions, or a whole folder) and get a plain-English changelog, health check, quiz answer key, and translator-ready text export in seconds. In your browser. Files never leave your machine.
$24/month after a 7-day free trial · no signup needed for the demo
See exactly what’s inside before it ships
When the course is safety or compliance training, a wrong answer key or a quietly dropped caption is a liability, not a cosmetic bug. Real output from real Storyline courses, built for instructional designers and compliance teams, and everyone who reviews their work alongside them.
Never wonder what changed again.
Drop in two versions of a .story file and get a plain-English changelog in seconds: a changed quiz answer, a course-wide navigation trigger that changed without a note in the update, a slide’s narration sync that got stripped, a new accessibility gap, a question bank swapped out entirely. All the things “I made a small update” tends to leave out, checked on every slide and every layer, not just the ones you remembered to click through.
Ship clean. Every time.
Broken jump triggers, orphaned slides and layers, missing alt text or captions, oversized media, even a custom JavaScript trigger shown in full with its own syntax check: all flagged automatically, no previous version required. It also walks your course’s own jump triggers to find the fewest slides a learner can see and still reach “course complete,” catching the shortcut that lets someone get certified without seeing the content.
Catch the wrong answer before your learners do.
Every Multiple Choice, Multiple Response, True/False, Matching Drag-and-Drop, and Freeform Drag-and-Drop question, correct answers already marked. Sign off on a course’s quiz in minutes instead of a full click-through.
Send a translator the words, not the software.
Every heading, body line, and button label, pulled out in reading order and grouped by slide. Hand it to a translator, SME, or reviewer. Nobody needs a Storyline license just to proofread your course.
Audit your whole library before your LMS admin has to.
Point StoryAudit at a folder of .story files and sweep every course for the same issues at once: broken references, orphaned slides, accessibility gaps, bloated media, all ranked and ready to triage instead of buried one course at a time. Save a baseline snapshot of the folder today and diff the whole library against it next quarter, no original files needed. Or set policy rules, like “no broken references allowed,” and get a pass/fail table for every course at once.
- Course outline: numbered to match Storyline's own Scenes panel in multi-scene courses
- Course settings summary: tracking, completion, pass scores, resume and navigation behavior
- Glossary and Resources: every saved term, file, and link
- Media inventory with sizes, alt text, and caption transcripts, per slide
- Media change tracking between versions
- Web Object and interactive shape inventories: embedded pages, Markers, Hotspots, Sliders, Dials
- Content search across the whole library, by text or exact image
- Placeholder scan: TODOs and lorem ipsum that shouldn’t ship
- JavaScript trigger listing with a syntax check on every trigger
- Variable map flagging anything unused
- Estimated seat time for documentation
- Run history and value recap: what every audit caught, totaled for your team (stored only on your device)
Built inside the workflow it audits
I've been building compliance courses in Storyline, and Presenter before it, since 2008. StoryAudit started as the tool I needed for my own review cycles, built to answer the two questions that eat them: what's actually inside this course, and what exactly changed since sign-off. I still run it on my own course work, and because a compliance audit tool is only as good as its accuracy, that's where the engineering effort goes:
- Regression-tested against real courses. Every release runs an automated test suite against a library of real Storyline .story files (real slide XML, real triggers, real quiz structures) before it ships. When the parser learns a new edge case, that course becomes a permanent test. See how this actually works.
- Nothing to intercept. Your files are parsed locally in your browser and never touch a server, so there's no upload pipeline to fail or leak. Read the security overview.
- Changes in the open. Every release is documented in the public changelog, so you can see exactly what changed in the tool that tells you what changed in your course.
- Honest about limits. When StoryAudit can't determine something from the file, the report says so rather than guessing; an estimate is always labeled an estimate.
— Eric AllenStoryAudit's founder, and still its most demanding user. Questions this page doesn't answer? Email support@storyaudit.app.
One course library, everyone on the same page
When a whole team ships courses, "what changed?" is a conversation that happens in every review cycle. A Team plan gives every designer, reviewer, and QA lead their own login (no shared passwords), self-serve, with the same 7-day free trial.
- Self-serve setup in minutes. Name your team, invite people by email, add or remove seats anytime from the team menu in the app header.
- Nothing for IT to review on the data side. Course files are parsed locally in each person's browser and never uploaded: there's no server-side course data to assess. The security overview is written to hand straight to your IT or infosec reviewer.
- Procurement-friendly. A data processing addendum and subprocessor list is available to start that conversation. Need an invoice, a purchase order, or a vendor questionnaire answered? Email support@storyaudit.app and it gets handled.
Ready to see what’s really in your courses?
Need something bigger, or have procurement questions? Read our security overview or email support@storyaudit.app.
Questions
Does StoryAudit upload my course files anywhere?
No. Every .story file you drop into StoryAudit is parsed locally, in your browser, using JavaScript. Nothing is uploaded to our servers or any third party. That includes the file itself, any report it generates, and any PDF, CSV, JSON, or text export you download from it.
Do I need Storyline installed to use it?
No. StoryAudit reads the .story file directly. You don't need an Articulate Storyline license, and StoryAudit isn't affiliated with Articulate Global, LLC.
Which versions of Storyline does it support?
Confirmed working with Storyline 2, Storyline 3, and Storyline 360. Day-to-day development and the bulk of testing happens on Storyline 360 courses; backward compatibility with Storyline 2 and Storyline 3 has been separately verified against real client files, not synthetic ones. It needs the original .story project file, not published output (see the next question). If you drop in a file StoryAudit can't read, it tells you immediately; nothing is uploaded and nothing silently half-parses.
Can it audit my published SCORM or xAPI package?
No. StoryAudit audits the source .story project file, not published SCORM, xAPI, or web output. That's deliberate: the answer key, triggers, variables, and accessibility data all live in the source file at full fidelity, before publishing flattens them. If you administer an LMS, ask your course developers for the .story file behind the package. One Health Check report tells you more than unzipping the SCORM package will.
Is there a CLI or API for automated pipelines?
Not currently. StoryAudit runs entirely in the browser, which is also what keeps your files on your machine. For recurring QA, Batch Check covers most of what a pipeline would: point it at a folder, sweep every course against the same policy rules (like "no broken references"), get a pass/fail table, and export results as CSV or JSON for your own tracking. Save a baseline snapshot and diff the whole library against it next quarter. If a CLI would unblock your team, email support@storyaudit.app; it helps to know who needs it.
What can I check with one file, vs. two?
Drop in one .story file for a Health Check (broken references, orphaned content, accessibility gaps, and more) and Course Docs (outline, settings summary, glossary and resources, quiz answer key, text export, media inventory). Drop in two versions of the same course for Compare mode's plain-English changelog. Point StoryAudit at a whole folder for a Batch sweep across your entire library at once.
Can I try it before paying?
Yes: every new account starts with a 7-day free trial. A card is required to start the trial, but you won't be charged until day 8, and you can cancel anytime before then from your account menu, with no partial-month charges. Want to try it with zero commitment first? Try the live demo right now, no signup and no card. It runs the real app on a bundled sample course.
What browsers does StoryAudit work in?
Current versions of Chrome, Edge, Firefox, and Safari. It's best used on a desktop or laptop browser; the app isn't optimized for small screens.
I need this for my whole team. How does that work?
Switch the pricing toggle below to "Team": it's $18/seat/month or $168/seat/year (3-seat minimum), self-serve, same 7-day free trial. Everyone gets their own individual login instead of sharing one account. Whoever sets it up names the team, invites people by email, and can add or remove members any time from the team menu in the app header. Need invoicing, a purchase order, or a security review first? Email support@storyaudit.app, read our security overview, or start from our data processing addendum.