E-learning & online courses

Import a SCORM package

Upload e-learning content built with Storyline, Rise or iSpring: Certeef handles SCORM 1.2 and 2004, CMI tracking and resume.

Updated on June 14, 2026 Read: 4 min

The SCORM lesson type lets you host e-learning content produced with market tools (Storyline, Rise, iSpring…) without rebuilding it in Certeef.

Prerequisites

  • Admin role.
  • An existing course with at least one module. See Create an online course.
  • A .zip SCORM 1.2 or 2004 file exported from your authoring tool.

1. Add a SCORM lesson

In your course, add a lesson and select the SCORM type.

2. Upload the package

Drop the .zip file exported by your authoring tool:

  1. The browser reads the imsmanifest.xml manifest to detect the version (1.2 or 2004) and the launch URL.
  2. The files are uploaded to Certeef storage.
  3. A progress bar shows during the transfer.

Important: any manifest error (missing file, invalid XML) is shown on screen. Re-export from the source tool with default SCORM settings.

3. Progress tracking (CMI)

During playback, Certeef exposes the SCORM APIs the content expects and persists CMI state: status, completion, success, score, position and resume data. The learner resumes where they left off.

Tip: the SCORM score feeds the course aggregate score, which can condition certificate issuance.

4. From SCORM to certification

The CMI status is translated into lesson progress and feeds automatic certification. A terminal but failed SCO stays “in progress”, the learner can retake it.

What’s next?

Frequently asked questions

Which SCORM versions are supported?
SCORM 1.2 and SCORM 2004. The player exposes the APIs the content expects and persists CMI state server-side.
Does a failed SCORM module still issue the certificate?
No. A SCORM module that finished but failed stays in progress: the learner can retake it, and it does not count toward the completion required for the certificate.
What if the upload fails with a manifest error?
Check that the ZIP contains an `imsmanifest.xml` at the root and that the manifest points to a valid launch URL. Most authoring tools (Storyline, Rise, iSpring) export conformant packages, re-export from the source tool if the error persists.
Can the learner resume where they left off?
Yes. The CMI state (position, resume data) is persisted server-side on each SCORM commit. On the next open, the player restores exactly the previous state.

Ready to de-risk your next audit?

A 30-minute demo, a case applied to your organization, and a quote within 24 hours. No pressure, no commitment.

No credit card required

© 2026 Certeef