A SCORM package is a compressed ZIP file containing all the files needed to deliver a SCORM-compliant eLearning course — HTML files, CSS, JavaScript, media assets (images, audio, video), quiz logic, and the imsmanifest.xml file that tells the LMS how to interpret and track the content. When you “upload SCORM” to an LMS, you are uploading this package.
What’s Inside a SCORM Package
- imsmanifest.xml: The table of contents — tells the LMS what modules exist, in what order, and how they relate to each other
- HTML files: The course screens and interactions, rendered in the learner’s browser
- JavaScript files: The SCORM API communication code that sends tracking data (completion status, score, time spent) back to the LMS
- Media assets: Images, audio narration, video clips, and animation files embedded in the course
- Quiz engine: Logic for question presentation, answer evaluation, and score calculation
SCORM 1.2 vs SCORM 2004 Packages
SCORM 1.2 is the older standard (2001) but still the most widely used — virtually every LMS supports it, and most authoring tools default to it. It tracks: completion status (completed/incomplete/passed/failed), score, and time spent. SCORM 2004 (multiple editions: 2nd, 3rd, 4th) adds more granular tracking — multiple objectives per SCO, more completion criteria, and better sequencing — but has compatibility quirks with some LMS platforms. For most organisations, SCORM 1.2 is the safer choice.
Uploading a SCORM Package to an LMS
Export the SCORM .zip from your authoring tool (Articulate, Captivate, iSpring, Rise) → Upload to the LMS course builder → Configure tracking settings (complete by status, score threshold, or time) → The LMS automatically handles delivery, tracking, and reporting for every learner who accesses the course.
Upload any SCORM package to EdzLMS
SCORM 1.2 and 2004 support — plus AI that reads your package and generates flashcards, quizzes, and summaries automatically.
See SCORM Analyser →