A complete inventory of a course file in seconds: narration runtime and word count, caption coverage track by track, what is eating the megabytes, and the things that quietly survive into a published package. Reads Storyline projects, SCORM packages and Rise exports. The file is read in your browser and never leaves your computer.
Free · No account · Your files never upload
A Storyline .story file, a published SCORM package, or a Rise export. It is read on your computer and never uploaded.
Course files are zip archives with a project file inside. This reads that project file and tells you what is actually in there: how many slides, how much narration and how fast it is spoken, how many audio tracks have captions attached, what every asset weighs, and which decisions made months ago are still sitting in the file. It reads Storyline projects, published SCORM packages, and Rise exports, which publish as SCORM.
Your file is opened here, in this tab, by code that came down with the page. It is not uploaded, and there is no server to upload it to. That matters more for this tool than for most: a source file carries client names, unreleased content, and the working paths of everyone who touched it. Handing it to a stranger’s server to be told how big it is would be a bad exchange.
A sixty megabyte project reads in well under a second, because the megabytes are all media, and file sizes can be read from the archive’s own index without unpacking any of it.
A file lands from a vendor or a colleague and you need to know what you have inherited before you quote on it. A package will not run in the LMS and you want to see whether the manifest is promising a file that is not in the zip, which is the usual answer. A course is too big to upload and you need to find the megabytes rather than guess. Or the accessibility review is next week and you would like the caption count to be a fact rather than a hope.
It will not tell you which media in a Storyline project is unused. Storyline records a usage count on every asset that looks exactly like the answer, and it is zero on everything, including logos sitting on the first slide. The field is written once and never updated. Walking the project’s internal references instead does not work either: those identifiers are not unique, and a reference walk built on them reports confident nonsense. A tool that tells you to delete an asset that is in use is worse than one that stays quiet, so this one stays quiet.
It also does not open your course, so it has no view on whether the writing is any good, whether the interactions work, or whether the assessment measures anything. It reports what the file records about itself. That is a narrow claim, and it is the reason you can trust the numbers.