SCORM, xAPI and LTI solve three different problems. SCORM is a way to package a course so that any compliant LMS can play it and record the result. xAPI is a way to record what people do, inside or outside an LMS. LTI is a way to plug an external tool into an LMS without a second login. Most organisations end up using more than one.
The three at a glance
| SCORM | xAPI | LTI | |
|---|---|---|---|
| What it is | A content packaging and tracking model | A format for recording activity | A way to connect tools to a platform |
| Maintained by | ADL | IEEE | 1EdTech |
| Current version | SCORM 2004 (1.2 still widely used) | IEEE 9274.1.1-2023 | LTI 1.3 |
| Where the content lives | Inside the LMS, as an uploaded package | Anywhere | On the tool's own servers |
| What it records | Completion, score, time, within the LMS | Any activity, as statements | Grades passed back to the LMS |
| Typical use | Compliance modules from an authoring tool | Tracking across apps, simulators, offline work | Adding a third-party tool to a course |
Definitions from scorm.com, xapi.com and 1edtech.org, checked on 2026-11-13.
SCORM
SCORM stands for Sharable Content Object Reference Model. It was created by ADL, and it covers two things: how a course is packaged, described in an XML manifest, and how the running course talks to the LMS.
In practice, an authoring tool exports a ZIP file. You upload it to your LMS, the LMS launches it in the browser, and the package reports back things like completion status and score.
There are two versions you will meet. SCORM 1.2 is older and, according to scorm.com, remains the most widely adopted. SCORM 2004 extends it and adds sequencing and navigation, which lets a package control the order in which learners see its parts.
SCORM is the right choice when you buy or build self-contained e-learning modules and need them to work in more than one LMS. Its limits come from its age. The content has to be launched from an LMS in a browser, and the data model is fixed. It can tell you someone scored 80%. It cannot easily tell you what they did in a simulator or on a phone without a connection.
xAPI
xAPI, the Experience API, was designed to remove those limits. It grew out of a research effort called Project Tin Can, which ADL commissioned, and it is still sometimes called the Tin Can API. It is now an IEEE standard, IEEE 9274.1.1-2023.
The idea is simple. Every activity is recorded as a statement with an actor, a verb and an object: "Maya completed the fire safety drill." Statements are sent to a Learning Record Store, or LRS. An LRS can be a separate system or part of an LMS, and LRSs can share statements with each other.
Because a statement can come from any application, xAPI can track things SCORM cannot reach: a mobile app, a simulator, a real-world task that a supervisor signs off. The content does not have to live in an LMS, and a device only needs to connect occasionally to send what it has recorded.
The trade-off is that xAPI gives you data without telling you what to do with it. You need an LRS, and someone has to decide which statements matter and how to report on them. If all you need is "did they finish the module and pass", SCORM is less work.
LTI
LTI, Learning Tools Interoperability, is a standard from 1EdTech. It does not package content or define a record format. It connects a learning platform to an external tool so that learners can open the tool from inside a course without logging in again.
The current version is LTI 1.3. Its security model is based on OAuth 2 and JSON Web Tokens, and it comes with a set of services called LTI Advantage:
- Names and Role Provisioning Services tells the tool who is in the course and what role they have.
- Assignment and Grade Services lets the tool create gradebook columns and send grades back.
- Deep Linking lets a teacher pick a specific item inside the tool and place a link to it in the course.
LTI is what you use when the content stays with its provider: a virtual lab, a publisher's homework system, a proctoring service, or another LMS. A platform can be an LTI "platform" (it launches tools), an LTI "tool" (it is launched by other platforms), or both.
Which one do you need
Start from what you are trying to do.
You bought compliance courses from a content vendor, or built them in an authoring tool. You need SCORM, and your LMS has to be able to import the version the vendor exports.
You want a record of learning that happens outside the LMS, or richer data than completion and score. You need xAPI and an LRS.
You want to use a third-party tool inside your courses, or offer your courses inside a university's LMS. You need LTI 1.3.
You write your courses directly in your LMS and your learners take them there. You may need none of the three. Native lessons, quizzes and assignments are tracked by the platform itself. Standards matter when content or data has to cross from one system to another.
Common mistakes
Treating SCORM as a quality mark. A SCORM package is a container. It says nothing about whether the course inside is good, and a native lesson in your LMS is not worse for being built there.
Asking for xAPI without a plan for the data. Statements are easy to produce and hard to use. Decide which questions you want answered before you choose an LRS.
Assuming "supports LTI" means the same thing everywhere. Ask which version, whether the product is a platform, a tool or both, and which LTI Advantage services it supports. Grade passback, for example, depends on Assignment and Grade Services.
Forgetting to test with real packages. Vendors differ in how strictly they follow each version. Before you sign a contract, upload two or three of your actual SCORM packages or connect your actual LTI tool.
Support in LearnHouse
For readers evaluating LearnHouse: SCORM 1.2 and 2004 import and LTI 1.3 are part of the Business plan on LearnHouse Cloud and of the Enterprise Edition when you self-host. They are not in the free open source edition. If you need SCORM and LTI at no cost on your own server, several of the platforms in our open source LMS comparison include them.
LearnHouse does not include an xAPI Learning Record Store. If xAPI is a requirement, plan for a separate LRS or choose a platform that has one built in.
New to the category as a whole? What is an LMS starts from the beginning.
Frequently asked questions
Is SCORM outdated?
It is old, and it is still in everyday use. Rustici Software, which maintains scorm.com, describes SCORM 1.2 as the most widely adopted version and still supported by the major LMSs. If your content is self-contained modules, it still does the job.
Does xAPI replace SCORM?
It can do everything SCORM tracking does and more, but it does not define packaging in the same way. Many organisations keep SCORM for packaged modules and add xAPI for activity outside the LMS.
What is the difference between LTI and SCORM?
With SCORM, you upload the content into your LMS. With LTI, the content stays on the provider's servers and your LMS opens it securely. SCORM moves files. LTI connects systems.
What is an LRS?
A Learning Record Store is the database that receives and stores xAPI statements. It can be a standalone product or a component inside an LMS.
Do I need any of these to run online courses?
No. If you create courses in your LMS and learners take them there, the platform tracks progress itself. You need a standard when content or learner data has to move between systems.

