How to Create SCORM: Step-by-Step Guide

What is creating SCORM and why it remains the standard that works?

Creating SCORM means packaging training content in a standard format that any LMS can read, execute and record automatically. A SCORM package is a .zip file containing the course (HTML, images, videos), a manifest file (imsmanifest.xml) describing its structure, and a JavaScript layer that sends the LMS data such as progress, time spent and score obtained.

SCORM (Sharable Content Object Reference Model) is an e-learning standard driven by ADL (Advanced Distributed Learning) that allows content to be imported into different LMS platforms and for that LMS to record key learning data: status (completed/not completed), score, time, progress, etc.

In day-to-day practice, SCORM remains the most widely used format in corporate training because it solves one of the biggest problems in corporate e-learning: compatibility across platforms and reliable learning tracking.

What’s inside a SCORM package

A SCORM is not “a course”. It is a .zip with a specific structure. Inside you will typically find HTML, CSS, JavaScript, multimedia resources and an essential file: imsmanifest.xml. That manifest tells the LMS what is inside the package, how it is organised and which resource to launch.

If the manifest is broken, the LMS may:

• Fail to open the course.
• Open it but record nothing.
• Record things partially (for example, learners view it but it never appears as completed).

The real problem is not understanding what SCORM is, but getting the package to work correctly in the LMS.

Basic components of a SCORM package

Creating SCORM correctly is not just about generating a .zip file. That file must have a specific structure and meet certain technical requirements so that the LMS can interpret it and record learner activity.

A SCORM package is essentially a set of organised, compressed files containing everything needed to run an e-learning course and communicate with the platform. It is not just visual content: it also includes technical instructions that enable learning tracking.

When you export a course as SCORM, what you generate typically includes:

• HTML, CSS and JavaScript files that shape the course and enable it to function.
• Multimedia resources such as images, videos or audio.
• The imsmanifest.xml file, which acts as the course “map” and tells the LMS how it is organised and what to launch.
• Elements or scripts that enable communication with the SCORM API to record data such as progress, score or completion status.

If any of these components is not correctly configured — especially the manifest or the API communication — the course may open but fail to record activity correctly. And that is where problems typically arise.

ASSET vs SCO: quick difference

Inside a SCORM package there are two types of resources: ASSET and SCO (Sharable Content Object). Understanding the difference is not just a technical matter: it directly affects how the LMS records learner activity.

An ASSET is a static resource.
An SCO is a trackable unit that communicates with the LMS.

The decision depends on what you need to measure.

Practical rule

If the content only needs to be viewed, it is an ASSET. If the content must send data to the LMS (completion, score, time), it must be an SCO.

For example, in a course with four assessed modules, it is common for each module to be an independent SCO. Conversely, an image or a supplementary document within that module would be an ASSET.

Making this decision correctly when structuring your SCORM prevents later tracking and reporting problems in the LMS.

Examples of SCORM package components

Imagine you are designing a course on Power Skills. You would start by defining the units of your course, which might be:

• Introduction to Power Skills.
• Most relevant Power Skills.
• Tools for developing Power Skills.
• Steps for building a Power Skills training strategy.

In SCORM terminology, this content translates into 4 SCOs, one per course unit:

• SCO 1: Introduction to Power Skills.
• SCO 2: Most relevant Power Skills.
• SCO 3: Tools for developing Power Skills.
• SCO 4: Steps for building a Power Skills training strategy.

And within each unit, there would in turn be further sub-units of SCOs related to the specific elements of each module.

Download a minimal SCORM package (structure + manifest + basic tracking)

When a SCORM fails to correctly record progress or does not mark as completed, the question is always the same: is the problem in the content or in the LMS configuration?

Before rebuilding the course or blindly modifying settings, the most effective approach is to use a validated minimal SCORM package as a control test. This type of template includes only the essentials for the LMS to communicate with the content: a basic functional structure, a correctly configured imsmanifest.xml and a simple completion event that sends data to the system.

What is it really for? To isolate the source of the error.

If that minimal SCORM works in your LMS and correctly records the completion status, the problem lies in your original package (structure, completion criteria or misconfigured tracking).

If it does not work either, the issue most likely lies in the LMS configuration.

It is not a substitute for an authoring tool or a production solution. It is a diagnostic tool that lets you identify the root of the problem without spending hours testing blindly.

How to create SCORM in 3 steps (the real process that actually works)

Step 1: Choose the method (tool vs manual) based on your context

If you are going to create one-off, very simple content, you can use quick conversion methods (for example, from PowerPoint) as long as the objective is linear and does not require much interaction. This is a valid solution when you need speed and tracking complexity is low.

If you are going to create training on a recurring basis, work with multiple courses or need visual consistency, collaboration and fewer technical issues, the usual approach is to opt for an authoring tool that exports SCORM in a stable, multi-LMS-compatible way.

Creating SCORM manually is also viable, but it means building the manifest, integrating the SCORM API, correctly defining tracking events and testing each package before publishing. In practice, it only makes sense when you have a technical team and a very specific case that cannot be solved with standard tools.

Practical conclusion: if your priority is total control and you have a technical background, manual development can make sense. If your priority is efficiency, stability and fewer production errors, an authoring tool is usually the safest and most scalable option.

Step 2: Design the course with tracking in mind, not just content

The typical mistake is designing “a nice presentation” and then exporting it to SCORM expecting everything to be recorded automatically. For SCORM to track correctly you need to define what “completed” means and where that condition is triggered: at the end, after passing a test, after visiting X screens, etc.

This is where authoring tools tend to save a great deal of time, because they already come with navigation logic, assessments and configurable completion criteria without touching code.

Step 3: Export, test and validate before uploading to production

This is the step most people skip. And it is the one that prevents the most problems. Before uploading to the “real” LMS, validate the package in a neutral environment. For this, SCORM Cloud is the de facto standard for testing packages independently.

If you are not sure where to start when choosing your authoring tool, take a look at our Whitepaper: Step by step to choose your perfect authoring tool

The 5 most common mistakes when creating SCORM (and how to avoid them)

Competitors cover the creation process, but no one explains why courses fail in production. These are the five errors that appear most often in real corporate projects:

1. Misconfigured or incomplete manifest

The imsmanifest.xml is the most critical piece. If the path to the launch file is incorrect or the metadata is poorly defined, the LMS cannot execute the course. Solution: validate the manifest in SCORM Cloud before publishing.

2. Completion criteria not defined

If you do not configure when a learner has “passed” the course, the LMS will not know when to mark it as completed. Solution: always define whether completion depends on score, time or full viewing, and configure it explicitly in the export settings.

3. SCORM version incompatibility with the LMS

Publishing in SCORM 2004 for an LMS that only supports SCORM 1.2 generates silent communication errors: the course runs but records no data. Solution: check the destination LMS documentation before choosing the export version.

4. File paths with special characters or uppercase letters

Linux systems are case-sensitive. A file named Slide01.html referenced as slide01.html in the manifest will cause a silent 404 error. Solution: always use lowercase and avoid accents, spaces and special characters in file names.

5. Not versioning the SCORM before updating

Uploading an updated version of the SCORM with the same name can delete the progress history of learners who already completed it. Solution: create a new version of the course in the LMS and keep the previous one active for learners still in progress.

Best tools to create SCORM [2026 Comparison]

Choosing the right software is key to saving time and avoiding compatibility problems. However, there are many types of tools for creating SCORM on the market. Here are two broad groups to explore:

Free SCORM tools (when they make sense)

Free options can work when you need to run quick tests or validate a workflow, when you are going to create simple, one-off content, or when you do not need advanced design or a high level of interactivity. Even so, it is worth noting that they typically come with common limitations such as reduced customisation, partial or limited export options, a less optimised user experience and lower scalability as the volume of courses or content complexity grows.

Paid SCORM tools (why they pay off for companies)

If your company is going to create training on a recurring basis, a paid tool will typically pay for itself through time savings in design and production, fewer incidents during publishing and maintenance, visual consistency across courses and teams, and better results thanks to more polished experiences (higher engagement and completion rates). They also tend to offer support and continuous updates, which is key when you need long-term stability and LMS compatibility.

How to test your SCORM in SCORM Cloud (and exactly what to review)

Before uploading your package to the definitive LMS, it is recommended to validate it in a neutral environment such as SCORM Cloud. This tool lets you check whether the file communicates correctly with the SCORM API and whether it is sending the data you actually need to measure.

When running the test, it is not enough for the course to “open”. What matters is verifying three key things:

• That the completion status is correctly recorded (completion).
• That the score is sent if there is an assessment (score).
• That the system is saving time or session data (session time).

The basic validation flow would be:

• Upload the .zip file to SCORM Cloud.
• Run through the full course.
• Check that completion and score are recorded.
• Review the debug log if any data does not appear.

How to interpret the results?

If in SCORM Cloud the course correctly records completion and score, but in your LMS it does not, the problem is likely in the LMS configuration (completion criteria, tracking mode, etc.).

If it also fails to record correctly in SCORM Cloud, the problem lies in your SCORM package (manifest, tracking events or export configuration).

This prior validation can save you hours of trial and error and prevent incidents when you publish to production.

SCORM 1.2 vs SCORM 2004: differences and which to choose in 2026

Before exporting your course, you need to make a key decision: which version of SCORM to use. SCORM 1.2 and SCORM 2004 serve the same general purpose (interoperability + tracking), but they have important differences.

Which to choose?

• If your priority is universal compatibility and zero incidents, SCORM 1.2 is usually the best option.
• If you need advanced path control, navigation restrictions or complex sequences, SCORM 2004 makes sense… as long as your LMS supports it well.

Practical recommendation 2026: in most corporate environments, SCORM 1.2 remains the safest option, especially for compliance.

How to create SCORM: Different options

After hearing so many terms, it can seem as though creating a SCORM is a far more complex task than it really is. However, it will depend greatly on the method and tool you use when starting to create your e-learning content. Here are 4 ways to create SCORM free without needing to know how to code:

Which to choose?

• If your priority is universal compatibility and zero incidents, SCORM 1.2 is usually the best option.
• If you need advanced control of the learning path, navigation restrictions or complex sequences, SCORM 2004 makes sense… as long as your LMS supports it well.

1. Convert PowerPoint to SCORM (and make the most of what you already have)

Converting PowerPoint to SCORM is one of the most common ways to create a SCORM package without coding, especially when you already have developed training content.

To do it correctly you need an authoring tool that lets you import PPT files and export them as SCORM 1.2 or SCORM 2004.

The usual process is:

• Import the PowerPoint into the authoring tool.
• Review the structure and adapt the navigation (not everything that works in PPT works the same way in e-learning).
• Add real interactivity: buttons, activities, assessments or checkpoints.
• Define what “completed” means (for example, passing a test or viewing all screens).
• Export as a SCORM package.

2. Create SCORM for free (with coding)

The second method for creating SCORM is to do it with code. It is a more complex process than the previous ones, and involves developing the training content using HTML, CSS and JavaScript, creating the manifest file that will define the course structure and included resources, integrating the SCORM API into your content so it can communicate with the LMS, and writing the JavaScript code needed to initialise, track progress and end the learning session.

You will then need to package the content, organising all course files (HTML, CSS, JavaScript, imsmanifest.xml) into an appropriate folder structure, compressing the files into a ZIP package and uploading them to your LMS.

Additional resources for creating SCORM without authoring tools

There are resources that can make it easier to create SCORM without authoring tools, such as SCORM converters, SCORM packagers and SCORM players. Converters transform documents such as PDFs and PPTs into interactive SCORM modules. Packagers are used by developers to make HTML content SCORM-compatible by adding SCORM API commands. SCORM players or testers are useful for reviewing and ensuring that a SCORM file is error-free before distributing it in your LMS. These resources are useful for those who prefer not to invest in new technologies.

3. Convert documents to SCORM with AI Autopilot by isEazy Author

With isEazy Author you can make AI your main ally when creating SCORM content. With the new AI Autopilot feature, creating SCORM is very simple and automatic.

• Start with an idea or upload your documents.
• The AI analyses your content and automatically generates a didactically sound structure.
• It also selects at each point the most effective resource type. Games, comparisons, videos, role plays… in just one click.
• Adjust each step or slide or add new content quickly and easily.

In addition, you can choose your style, colours and template, and the AI will apply your corporate identity throughout the project, maintaining full visual consistency at all times. See it in action!

Pre-deploy checklist: before uploading SCORM to the LMS

Accessibility in SCORM

More and more teams are facing the same reality: it is no longer “nice to have”. Accessibility is a growing requirement by regulation and quality standards. The most common framework for validating digital content is WCAG (W3C).

In SCORM this translates into very concrete solutions: keyboard navigation, subtitles, contrast, visible focus, coherent structure, alternative texts… and, above all, avoiding interactions that only work with a mouse or have no alternatives.

Best practices when creating SCORM content

Creating effective and engaging SCORM content is essential to ensure a successful and enriching online learning experience. To help you achieve this, here are some of the best practices for SCORM content creation, focusing on the main characteristics of this standard:

1. Interoperability

Interoperability allows SCORM content to be used across different learning platforms without compatibility issues. To ensure interoperability:

• Use recognised tools and standards: Use authoring tools that adhere to SCORM specifications.
• Choose a good LMS: Verify that your SCORM content deploys and works correctly in your LMS.

2. Reusability

The reusability of SCORM content allows learning modules to be reused in different contexts and courses. To maximise this feature:

• Design independent modules: Create units of content that can be used independently across various courses, ensuring maximum use of resources.
• Label correctly: Use descriptive metadata that makes it easier to search for and reuse content.

3. Durability

Any SCORM content must maintain its relevance and functionality over time, even in the face of technological change. To ensure durability:

• Adopt approved standards: Make sure your content complies with the latest versions of SCORM.
• Update regularly: Periodically review and update your content to keep it current with new technologies and learning methodologies.

4. Accessibility

Accessibility in e-learning is fundamental and is governed by regulations such as the Web Accessibility Act in Spain, aligned with European Directive 2016/2102; Section 508 of the Rehabilitation Act in the United States, which requires companies to provide equal access to information for people with disabilities; and the criteria of the Web Content Accessibility Guidelines (WCAG).

These regulations urge educational institutions and organisations to ensure their content is accessible to people with disabilities. Implementation of these standards is growing in Spain and globally, reflecting the increasing importance of offering inclusive and equitable education. Complying with these standards is not only a legal obligation but also improves the learning experience, ensuring all users can access content, participate fully and benefit from educational opportunities.

5. Scalability

Finally, scalability allows you to create SCORM that adapts to different audience sizes and course expansion. To ensure scalability:

• Optimise performance: Make sure multimedia files are optimised for fast loading times.
• Design for growth: Create content that can easily be expanded or modified to add new lessons or modules without needing to rebuild the entire course.

By following these best practices, you will be able to create SCORM content that not only meets technical standards but also provides a rich and accessible learning experience for all users. Correct implementation of interoperability, reusability, durability, accessibility and scalability will ensure your e-learning courses are effective and sustainable in the long term.

Creating accessible SCORM: WCAG 2.1 and how to comply without technical effort

An accessible SCORM must meet at least level AA of WCAG 2.1: full keyboard navigation, compatibility with screen readers (ARIA labels, correct semantic roles), adequate colour contrast, subtitles on all videos and no content that flashes more than 3 times per second.

Creating this version manually requires very high technical expertise. isEazy Author generates it automatically on export: the same click that creates the standard SCORM also produces an accessible version at level AA and up to 80% of level AAA of the WCAG, at no additional production cost. In corporate environments subject to equality regulations (the European Accessibility Act in force from 2025), accessible training is no longer optional.

Final considerations

The use of intuitive authoring tools, such as isEazy Author, can significantly simplify the process of creating e-learning content. These tools offer ready-to-use resources that allow users, regardless of their technical experience, to create engaging and effective courses in very little time.

Our tool also features customisation capabilities that let you adapt courses to your corporate identity, as well as productivity features such as automated translation generation, voiceovers, subtitles and final assessments — all in just a couple of clicks thanks to AI!

Moreover, with the new AI Autopilot feature, HR teams, instructional designers or anyone who wants to create a SCORM course will be able to transform ideas or documents into interactive courses with a pedagogical structure, applied branding and full accessibility in minutes, without technical knowledge. What are you waiting for to request a demo? Discover the easiest authoring tool on the market.