---
title: "Moodle Mod Scorm"
description: "Not a product but a core Moodle activity module, and worth a listing precisely because of that. Moodle's installed base means mod_scorm is the runtime most SCORM content meets after leaving the authoring tool, so its behaviour has become the de facto second opinion — if a package works in SCORM Cloud and in Moodle, it usually works."
canonical_url: "https://scorm-tools.com/tools/moodle-mod-scorm"
last_updated: "2026-10-31T10:22:00.966Z"
---

Not a product but a core Moodle activity module, and worth a listing precisely because of that. Moodle's installed base means `mod_scorm` is the runtime most SCORM content meets after leaving the authoring tool, so its behaviour has become the de facto second opinion — if a package works in SCORM Cloud and in Moodle, it usually works.

What it does: unpack a package interchange file, parse the manifest, present the organisation as a table of contents, run each SCO in a frame or new window, and persist tracking per attempt with reporting, grade integration and a debug window that logs API calls when an administrator enables it. Both data models are implemented in full (`scorm_12.php`, `scorm_13.php`), AICC HACP survives as an optional legacy path, and mobile clients are supported through web services.

Its limits are worth knowing before you blame your content. The manifest parser only recognises 2004 3rd and 4th Edition strings and silently treats anything else as 1.2. Sequencing and navigation exist but are partial, which is where 2004 packages most often diverge between Moodle and commercial platforms.

You cannot lift the player out — it is bound to Moodle's database, file and permission layers. Maintenance is not in question: this is core code in a project with paid maintainers, a fixed release cadence and a security process.