---
title: "Claroline"
description: "Claroline Connect is the Symfony and React rewrite of the long-standing Claroline project, developed by the Claroline Consortium. Its shape is workspace-centric: a workspace holds a resource tree, and everything — a text, a quiz built with the exo plugin, a file, a SCORM package — is a resource with the same permissions and tracking model. That consistency is its main strength and the reason it suits institutions that want to build course structures rather than upload finished modules."
canonical_url: "https://scorm-tools.com/tools/claroline"
last_updated: "2026-10-31T10:22:00.015Z"
---

Claroline Connect is the Symfony and React rewrite of the long-standing Claroline project, developed by the Claroline Consortium. Its shape is workspace-centric: a workspace holds a resource tree, and everything — a text, a quiz built with the `exo` plugin, a file, a SCORM package — is a resource with the same permissions and tracking model. That consistency is its main strength and the reason it suits institutions that want to build course structures rather than upload finished modules.

SCORM lives in a plugin with its own entities for SCOs and per-learner tracking, and it is the stronger half of the platform's standards story: both 1.2 and 2004 are handled, with the player exposing `window.API` or `window.API_1484_11` as appropriate. Import is strict about the manifest version string, which is worth knowing before you migrate a library.

The gap is everything else. There is no LTI, no xAPI and no cmi5 in the repository. If your integration plan involves launching external tools or forwarding statements to an LRS, this is not the platform.

Development is steady — 351 stars, active commits through August 2026, releases tagged — but it is a smaller ecosystem than Moodle or OpenOLAT, and the documentation is thinner than the codebase deserves. AGPL-3.0 is a real consideration for hosted use.