How Moodle H5P works — interactive video, branching scenarios, drag-and-drop, xAPI tracking, and the content bank — plus when H5P beats SCORM.
Got an LMS decision on your plate?
45-minute call. Plain-English audit. Fixed-price quote if there's a fit, or a "no" if there isn't. No deck. No pitch.
A practical look at AI course authoring for corporate training — what it speeds up, where human review is mandatory, and why an owned platform keeps your content yours.
A plain-English comparison of SCORM, xAPI, and cmi5 — what each does, where they differ, and which to choose for your training content.
A plain-English explainer of what a learning record store is, how it works with xAPI and your LMS, and when a mid-market training team actually needs one.
If your training still looks like a slide deck with a quiz stapled to the end, learners tune out and completion numbers tell you less than you think. Moodle H5P is the built-in way to fix that: it lets you build genuinely interactive content — video with embedded questions, branching decision scenarios, drag-and-drop exercises — directly inside the platform, without buying a separate authoring tool and without paying per author. And because you own the Moodle install, you own the content you make.
This is a practical look at what H5P is, what you can build with it, how it tracks learner interactions, and when it is the right choice versus SCORM. If you are exploring faster ways to produce courses generally, pair this with our guide to AI course authoring.
H5P stands for HTML5 Package. It is an open-source framework for creating interactive content that runs in any modern browser, including on phones and tablets. Rather than being one tool, it is a library of content types — dozens of them — each designed for a particular kind of interaction.
The important thing for a Moodle buyer is that H5P is not a bolt-on you have to license separately. In modern Moodle it is built into the core content bank, so authoring interactive content is a native part of the platform. You create an element once, it lives in the content bank, and you drop it into as many courses as you like.
That matters for ownership. When your interactive content is authored inside a Moodle install you control, there is no external SaaS authoring subscription metering your team by the author seat, and no vendor holding your source files hostage.
You do not need all of H5P's content types. In corporate training, a handful do most of the work:
These are effective because they ask the learner to do something. That is also what makes their tracking data more useful than a completion checkbox, which brings us to reporting.
The workflow is straightforward, and it is entirely inside Moodle. An author opens the content bank, chooses a content type, and fills in the interaction — the video and its questions, the branches of a scenario, the drag targets. The result is saved as a reusable content-bank item that can then be added to any course.
A few practical consequences follow from that:
For teams looking to move even faster, AI-assisted drafting can generate first-pass content that authors then make interactive with H5P — a combination we cover in AI course authoring.
Here is where interactive content pays off analytically. H5P content can emit xAPI statements — structured records of what a learner did, not just that they finished. Instead of "course complete," you can see that a learner chose the wrong branch twice in a scenario before getting it right, or which hotspot they missed on the equipment diagram.
Moodle can capture these interaction statements, and if you run a dedicated Learning Record Store, they can flow there for deeper analysis across content and time. That distinction between simple completion tracking and rich interaction data is exactly what xAPI was designed for, and we unpack the standards in SCORM vs xAPI vs cmi5. For where all that interaction data lives and how you query it, see the learning record store explained.
The practical value: when a scenario consistently trips people up at the same decision point, that is a signal your procedure or your training needs attention — and you only see it if the interactions are tracked.
Both have a place, and the answer usually depends on where the content is made and how portable it needs to be.
Reach for H5P when:
Reach for SCORM (or its modern successors) when:
Many owned Moodle platforms use both: SCORM for purchased library content, H5P for the interactive material the team builds in-house. That flexibility is one more argument for a platform you control rather than one that limits your formats.
Interactive content is real work to produce, which makes it a real asset. On a rented, per-seat platform with a separate authoring subscription, that asset is entangled with fees that grow as your team and headcount grow, and it can be awkward to extract if you ever leave.
On an owned Moodle install, the interactive content your team builds with H5P is simply yours — stored in your content bank, reusable across every course, exportable, and free of per-author metering. You built it, you keep it, and you can change it whenever your operation changes. That is the whole point of owning the platform instead of renting it.