When suspend data overflows, the LMS refuses the save or truncates it silently, and the learner loses their place deep into the course. Paste the actual value or estimate from the shape of the course, and see it against all three SCORM limits, counted both ways.
Free · No account · Your files never upload
| SCORM 1.24,096 charactersThe one that catches everyone. Storyline packs slide state, variables and progress into it, and a long course fills it. | 0% | |
| SCORM 20044,000 charactersSecond and third edition. Slightly smaller than 1.2, which surprises people migrating. | 0% | |
| SCORM 2004, 4th edition64,000 charactersFourth edition raised it sixteenfold. Only helps if the LMS actually implements the fourth edition. | 0% |
Measures suspend data against all three SCORM limits, in characters and in bytes, and says which of them it will fit. If you cannot get the real value out of your LMS, it will estimate from the shape of the course instead, clearly labelled as an estimate.
The specification counts characters. A great many LMS platforms store the value in a database column sized in bytes. For plain English those are the same number and nobody ever notices. Add an accented character, a curly quote or an emoji and they diverge, so a course that saves perfectly in English silently stops resuming in French. That case is flagged separately, because it is invisible until it is a support ticket.
The LMS either refuses the save, usually with a 351, or truncates the value silently. Either way the learner loses their place, and it happens deep into the course when they have the most to lose. It is also intermittent by nature, which is why it gets diagnosed as “the LMS is flaky” rather than as a size limit.
The estimate is derived from the shape of real Storyline suspend strings and is a guide, not a calculation of your course. If you can get the actual string, paste it: that is a measurement and this is not.