Studio
Import a SCORM package
Upload SCORM 1.2/2004 zips, validation, limits, and native convert.
Mentor imports SCORM packages so training built in Articulate Rise, Storyline, Adobe Captivate, iSpring, and similar tools plays inside Mentor courses with full completion and score tracking. Importing requires Edit content (content:write).
What you can import
| Requirement | Detail |
|---|---|
| Format | A .zip file — the standard SCORM export from your authoring tool |
| SCORM version | 1.2 and 2004 (any edition) are both supported |
| Size | Up to 200 MB per package |
| Manifest | imsmanifest.xml must be present (at the zip root or one folder deep) |
| File count | Up to 800 files are extracted per package |
Export from your authoring tool as *SCORM 1.2* or *SCORM 2004* — not "Web" or "xAPI/TinCan" output.
Import steps
- Open Studio → Courses. The Import SCORM package panel sits under the course creation form.
- Decide where the content lands. Create a new course from this package is checked by default; untick it and pick an existing course from Select course… to append instead.
- Drop the file on Drop SCORM .zip here, or click to browse, or use Choose .zip file. The dropzone reminder reads *"Validated before import · max 200 MB · imsmanifest.xml required"*.
- Watch the progress captions: Checking file…, Requesting upload…, Uploading zip…, Validating SCORM package…, Importing into course…
- Review the validation report, then Mentor opens the course builder on the imported course.
The validation report
Every upload is validated before it touches a course. The report shows Validation passed (or failed) with the package title, followed by the detected version, launch file, and file count — for example *SCORM 2004 · launch index.html · 214 files · convert: partial*. Warnings appear as Note: lines and hard failures as Error: lines. Common errors:
| Message | Cause and fix |
|---|---|
| Choose a .zip SCORM package (export from Rise, Storyline, Captivate, etc.). | The file is not a .zip — re-export as SCORM |
| Package exceeds 200 MB limit. | Compress media in your authoring tool or split the course |
| File is not a ZIP archive. Export a SCORM package as .zip. | The file has a .zip name but is not a real zip |
| Missing imsmanifest.xml — this is not a valid SCORM 1.2/2004 package. | You zipped the wrong folder, or exported a non-SCORM web package. The manifest must be in the zip, not nested two folders deep. |
| Manifest has no <resources> — nothing to launch. | The manifest is malformed — re-export |
| Launch file not found in zip: {path} | The manifest points at a file that is not in the archive — re-export the full package |
| ZIP could not be opened (corrupt or unsupported). | The download or transfer corrupted the file — re-export and retry |
You may also see benign notes, such as *Using launch file index.html (manifest href was …)* when Mentor resolved the launch file for you, or a warning that packages with more than 800 files are truncated.
What "native convert" does
During import Mentor also attempts a best-effort native conversion so you get editable Mentor content where possible. The report's convert value tells you what happened:
- scorm_only — the package stays as a single SCORM lesson. The note reads *"Package kept as SCORM. No editable outline/quizzes could be extracted (common for Rise/Storyline)."* This is normal for packages whose content is compiled JavaScript.
- partial — Mentor read the manifest outline and created one SCORM lesson per launchable item, so a multi-SCO course arrives as multiple lessons. *"Outline extracted from manifest; quizzes stay inside the SCORM package."*
- converted — Mentor also extracted quiz questions from the package's HTML into native, editable Mentor quizzes (created with a 70% pass score). If correct answers could not be detected reliably you will see *"Questions extracted without reliable correct answers — review before publishing."* — always open converted quizzes and verify answers before publishing.
Conversion never alters the package itself: the original SCORM content still plays inside the lesson, with tracking.
After import
The imported course is a draft. Open the builder, reorder or retitle the SCORM lessons like any other module, add native content around them if you like, then Publish and Assign. Learner behavior — launch, progress, resume, scores — is covered in SCORM courses in the player.
If an import fails or a package will not play, see SCORM playback and tracking problems.