---
title: "Moodle"
description: "Moodle matters to this directory for a reason that has little to do with its feature list: it is the LMS your content is most likely to land in, and mod_scorm is the de facto reference against which a great deal of SCORM content is informally tested. Whatever else you build for, you will end up building for this."
canonical_url: "https://scorm-tools.com/tools/moodle"
last_updated: "2026-10-31T10:22:00.872Z"
---

Moodle matters to this directory for a reason that has little to do with its feature list: it is the LMS your content is most likely to land in, and `mod_scorm` is the de facto reference against which a great deal of SCORM content is informally tested. Whatever else you build for, you will end up building for this.

As a SCORM host it is genuinely capable. The activity module implements SCORM 1.2 and 2004 data models separately, handles AICC, tracks multiple attempts, and exposes reporting that most commercial platforms charge for. Because everything is inspectable PHP, when a course misbehaves you can read the code that decided it misbehaved — which is not a small advantage during a support call.

The honest caveat is SCORM 2004 sequencing. It is implemented, and it has diverged from the reference behaviour in edge cases for years. Content that depends on non-trivial sequencing rules should be tested here specifically rather than assumed to work; content that passes here should still be tested elsewhere.

It is also not an xAPI platform. Core's xAPI code serves H5P internally, and reaching an LRS means adding the separately maintained Logstore xAPI plugin. There is no cmi5 support at all.

Development is continuous — the main branch is 5.3dev with commits within the week — and the plugin ecosystem around it is the largest in the category.