---
title: "Moodle Mod Scormremote"
description: "This solves a specific commercial problem: you sell or licence SCORM content, and handing over a zip means handing over the asset. mod_scormremote inverts that. The client's LMS receives a wrapper SCO that loads the real course from your Moodle in a sandboxed iframe and relays the SCORM API across domains with postMessage. You keep the content, you can replace it in place, and you get usage back — accounts, enrolments and completion appear in your Moodle as remote learners work through it."
canonical_url: "https://scorm-tools.com/tools/moodle-mod-scormremote"
last_updated: "2026-10-31T10:22:02.771Z"
---

This solves a specific commercial problem: you sell or licence SCORM content, and handing over a zip means handing over the asset. mod_scormremote inverts that. The client's LMS receives a wrapper SCO that loads the real course from your Moodle in a sandboxed iframe and relays the SCORM API across domains with postMessage. You keep the content, you can replace it in place, and you get usage back — accounts, enrolments and completion appear in your Moodle as remote learners work through it.

The seat-limiting is the other half of the pitch. Clients are defined by their domains, tiers cap how many seats each client may consume, and a single wrapper file identifies which client is using it from the requesting domain. That is closer to a licensing system than an activity module, and it is why the plugin exists at all.

Know the constraint before you build on it: the wrapper is SCORM 1.2. It vendors only the scorm12 build of scorm-again and never defines `API_1484_11`, so 2004-specific tracking on the remote side is not available. Frame embedding must also be permitted at both ends, which not every corporate client's LMS will allow.

Catalyst maintain it against a single MOODLE_39_STABLE branch, with CI and commits as recent as July 2026 — a supported vendor plugin rather than a hobby project, though support is explicitly best-effort unless you sponsor work.