Yes — Moodle is SCORM compliant out of the box. Its built-in SCORM activity supports SCORM 1.2 and SCORM 2004: you upload a SCORM ZIP and Moodle launches the package and tracks completion, score and time. Most SCORM problems people blame on Moodle actually come from the package's manifest or browser settings, not the platform. For tracking that follows learning beyond the LMS, xAPI is often the better fit. edzlms supports both SCORM and xAPI, and adds edzlms AI and Gelato so content isn't just played, it's understood and practised.
Key takeaways
- Moodle is SCORM 1.2 and 2004 compliant out of the box via its native SCORM activity.
- You add SCORM content by uploading the package as a ZIP — no extra plugin needed.
- Moodle tracks completion, score and time, and reports them per learner.
- Most SCORM bugs trace to the package manifest or browser, not Moodle — test before rollout.
- Use xAPI for tracking beyond the LMS; edzlms supports both and adds edzlms AI and Gelato.
What does SCORM compliance in Moodle mean?
SCORM (Sharable Content Object Reference Model) is the most widely supported eLearning content standard — the common language that lets a course built in Articulate, iSpring or Captivate talk to your LMS. “SCORM compliance” simply means your LMS can import, launch and track those packages correctly.
Moodle ships with a built-in SCORM activity, so it's SCORM 1.2 and SCORM 2004 compliant with nothing extra installed. When a learner opens the activity, Moodle launches the package in a player and listens for the data the package sends back — whether the learner completed it, what they scored, and how long they spent. That data lands in Moodle's gradebook and SCORM reports like any other activity, which is what makes SCORM content first-class rather than just an embedded file.
How do you add SCORM content to Moodle?
The process is short, but a couple of settings decide whether tracking works.
Export a compliant ZIP (SCORM 1.2 or 2004) from your authoring tool, then add it as a SCORM activity in your course. The settings that matter most are the completion requirements (does “complete” mean opened, passed, or a minimum score?), the grading method and attempts allowed, and how the package opens (new window vs current). Set these deliberately — most “Moodle isn't tracking completion” complaints are really a mismatch between what the package reports and what the activity is told to count.
If you need tracking that follows learning across mobile apps, simulations and the real world — not just inside the LMS — consider xAPI instead. Compare the two in SCORM vs xAPI.
What are common SCORM problems in Moodle?
Three issues account for the vast majority of support tickets, and all three usually live in the package, not in Moodle:
Completion not recording. Almost always the package's completion logic (or the activity's completion settings) rather than a Moodle bug. Check what status the package actually sends, and that the activity is set to match it.
Score mismatches. The package and the gradebook disagree — typically a SCORM 1.2 vs 2004 reporting difference or a grading-method setting.
Mobile or playback issues. Often browser settings (pop-up blockers, cookies) or a package built for desktop only.
The fix is process, not panic: always test a package with a real learner account before rollout, and re-export from the authoring tool if the manifest looks wrong.
How edzlms solves this: edzlms is a Moodle-based platform with two AI layers — edzlms AI, an AI tutor and course builder, and Gelato, our Roleplay AI agent for scored conversation practice. edzlms supports both SCORM and xAPI, and adds edzlms AI so learners can ask questions about a SCORM module in context instead of getting stuck, plus Gelato so learning goes beyond static, click-through packages into real practice.
Need something custom-built?
Want custom Moodle plugins, SCORM/xAPI workflows, custom reports, activity modules or AI agents built around your team's exact process? edzlms designs and builds it for you. Book a free demo or email marketing@edzlms.com and we'll scope it with you.
- 1Get a compliant ZIP
Export SCORM 1.2 or 2004 from your authoring tool — don't unzip it.
- 2Add a SCORM activity
Turn editing on, Add an activity, choose SCORM package.
- 3Upload & set tracking
Upload the ZIP and configure completion, grading method and attempts deliberately.
- 4Test as a learner
Confirm completion and score record correctly with a real learner account.
- 5Roll out
Publish and monitor the SCORM report for the first cohort.
SCORM
- Universal, widely supported
- Tracks score and completion
- Works inside the LMS
- Limited offline / cross-app data
xAPI
- Tracks learning anywhere
- Richer data via an LRS
- Great for blended and mobile
- Needs more setup
Pro tip
Always test a SCORM package with a real learner account before rollout — completion and score bugs almost always come from the package manifest, not Moodle.
Frequently asked questions
Is Moodle SCORM compliant?
Yes. Moodle supports SCORM 1.2 and 2004 through its built-in SCORM activity, with no extra plugin required.
How do I add SCORM to Moodle?
Export a compliant ZIP from your authoring tool, add a SCORM activity in your course, upload the ZIP, and configure completion and grading settings.
Why isn't my SCORM completion recording?
Usually a mismatch between what the package reports and the activity's completion settings — not a Moodle bug. Check both and re-test with a learner account.
Should I use SCORM or xAPI?
SCORM for universal, in-LMS tracking; xAPI when you need to track learning across apps, simulations and mobile. edzlms supports both.
Does edzlms support SCORM?
Yes — edzlms supports SCORM and xAPI, and adds edzlms AI for in-context help and Gelato for practice beyond static modules.
See edzlms in action
Book a 45-minute demo and we'll show SCORM, xAPI and AI working together.