If you're buying an LMS, someone will eventually ask whether it "supports SCORM."
The answer matters. SCORM is still the standard format for packaged eLearning courses, especially compliance training, certification prep, safety modules, and off-the-shelf course libraries. If your LMS handles SCORM poorly, you will feel it fast: courses will fail to upload, completions will not save, scores will look wrong, and learners will swear they finished something the system says they never touched.
But SCORM support is not the whole LMS decision.
A modern training program usually includes more than SCORM packages. You may have videos, PDFs, images, downloadable checklists, webinar recordings, policy documents, worksheets, external resources, and files from old systems that still need to count toward completion or certification renewal. If you buy an LMS that treats SCORM as the only "real" training format, you can end up rebuilding content that was already working fine.
So yes, ask about SCORM. Test it. Take it seriously. Just do not stop there.
The Plain-English Version
SCORM is a packaging and tracking standard for eLearning courses.
In practical terms, a SCORM course is usually a ZIP file exported from an authoring tool like Articulate, Captivate, iSpring, Lectora, or Camtasia. You upload that ZIP file to your LMS. The LMS launches it for the learner. While the learner takes the course, the course sends information back to the LMS.
That information usually includes:
- whether the learner started the course
- whether they completed it
- whether they passed or failed
- their score
- how much time they spent
- where they left off, so they can resume later
If you want a broader explanation first, start with the executive guide to SCORM. If you want the deeper operational version, read the complete SCORM guide for training teams.
What "SCORM Support" Should Actually Mean
Some LMS vendors say they support SCORM because they can accept a ZIP file.
That is not enough.
For buyers, SCORM support should mean the LMS can reliably handle the full course lifecycle: upload, launch, tracking, reporting, troubleshooting, and long-term recordkeeping.
Here is what to look for.
The LMS Should Upload Real SCORM Packages Without Weird Workarounds
You should be able to upload a normal SCORM package exported from a mainstream authoring tool. No manual unzipping. No vendor services ticket. No "send it to our implementation team and we will convert it."
Ask whether the LMS supports both SCORM 1.2 and SCORM 2004. Most teams still use SCORM 1.2 because it is simple and widely compatible, but SCORM 2004 still shows up in newer authoring tool exports and in more complex content libraries. If you are deciding between versions, the short version is this: use SCORM 1.2 unless you have a specific reason to need SCORM 2004. The longer version is in SCORM 1.2 vs SCORM 2004.
Also ask about file size limits. A beautifully built course does not help if your LMS rejects it because the ZIP is too large.
Edaxu supports SCORM 1.2 and SCORM 2004 packages directly, with no conversion step.
The Course Should Launch Cleanly for Learners
This sounds obvious, but it is where a lot of problems show up.
When a learner clicks the course, it should open in a stable player, fit the screen, work in modern browsers, and return the learner to the right place when they finish. If the LMS uses popups, ask how it handles popup blockers. If it launches in an iframe, test whether your courses behave correctly there.
Do not evaluate this from a sales demo alone. Upload one of your own SCORM packages and have someone take it like a real learner would: start it, leave halfway through, resume it, finish it, pass the quiz, fail the quiz, and try it on a laptop and phone.
SCORM does not magically make bad course design mobile-friendly. A course built for a 1024px desktop window may still feel awful on a phone. That is a content design issue, not only an LMS issue.
Tracking Should Match What Your Program Actually Needs
The bare minimum is completion tracking.
For most compliance and certification programs, that is not enough. You probably need to know:
- who was assigned the course
- who started it
- who completed it
- who passed or failed
- what score they received
- when the record was created
- whether completion triggers a certificate, CE credit, renewal, or manager notification
This is where "SCORM support" turns into training operations. A course completion is not useful if it sits in a report no one can act on.
For certification programs, completion should connect to the next workflow: issue a certificate, update a renewal status, add CE credits, or preserve evidence for an audit. Otherwise, your team is still stuck reconciling reports by hand.
Bookmarking Should Work
Bookmarking means the learner can leave a course and return to the right place later.
It is easy to overlook until it breaks. Then your support inbox fills up with people saying, "I already did this section, why am I back at the beginning?"
Ask the vendor to show bookmarking with your own content. Test it across normal learner behavior: close the tab, log out, come back tomorrow, switch browsers, resume from the course page. You do not need to understand the SCORM data model to evaluate this. You just need to confirm the learner experience behaves the way a reasonable person expects.
Reports Should Be Usable Without a Developer
A good LMS should not force non-technical admins to dig through raw SCORM fields just to answer a basic compliance question.
You should be able to report on completion, score, status, learner, date, course, group, and certification requirement. You should be able to export the records. And if your program has audits, the report should show enough context to prove what happened without five screenshots and a spreadsheet explanation.
Raw SCORM data can be useful for troubleshooting. It should not be the main reporting experience.
Admins Should Have a Way to Troubleshoot
SCORM issues happen. Sometimes the package is malformed. Sometimes the launch file is wrong. Sometimes the course does not call the LMS correctly. Sometimes the authoring tool export settings were wrong.
The LMS should help you figure out what went wrong.
At minimum, ask whether admins can see upload errors, launch details, completion status, and the SCORM version detected. If you have a package that will not import, Edaxu's free SCORM manifest parser can help you inspect the imsmanifest.xml file before you upload it.
Do Not Buy an LMS That Only Thinks in SCORM
Here is the trap: SCORM is important, so buyers over-focus on it.
Then six months later, the training team realizes half their program is not SCORM at all. The safety team has MP4 walkthroughs. HR has PDFs. The compliance manager has signed policy acknowledgments. The association has downloadable worksheets. The implementation team has image-heavy reference guides. Someone has a ZIP file of field resources that still needs to be distributed and tracked.
None of that should require rebuilding everything as SCORM.
SCORM is great for interactive packaged courses. It is not the right format for every training asset.
Other Content Types Your LMS May Need to Support
When you evaluate an LMS, ask about content support in plain operational terms. What can we upload? What can learners view? What can we track? What can count toward a requirement?
Video
A lot of training is video: software walkthroughs, safety demos, recorded webinars, orientation clips, product training, supervisor briefings.
For video, ask whether the LMS supports common formats like MP4, MOV, WEBM, and AVI. Then ask the more important questions: can it track watch progress, support captions, handle large files, organize chapters, and report completion in a way your admins trust?
If the LMS only lets you paste a video link and call it a day, that might be fine for informal learning. It is weaker for compliance programs where completion records matter.
Edaxu supports video uploads, including MP4, MOV, WEBM, and AVI, with progress tracking.
PDFs and Documents
Policies, manuals, study guides, job aids, codes of conduct, technical references, and accreditation materials often live as PDFs.
Do not assume these should be converted into SCORM. Sometimes a PDF is the right format. The LMS should make it easy to view, assign, track, and report on it.
Ask whether the LMS can track page-level progress, document completion, acknowledgments, annotations, and searchable text. For audit-heavy teams, ask how the record appears later: does it show who viewed the document, when, and as part of which requirement?
Edaxu supports PDFs and document-based training resources.
Images and Reference Materials
Some training assets are diagrams, signage, maps, inspection plates, equipment reference images, or step-by-step visuals.
These may not need a full course wrapper. They need clean viewing, version control, assignment, and proof that the right learners received the right material.
Edaxu supports image uploads including PNG, JPG, and JPEG.
General Files and Downloads
Worksheets, checklists, templates, CAD resources, policy packets, ZIP resources, and offline exercises often sit outside traditional course formats.
Ask whether the LMS can track file downloads or acknowledgments. A download receipt is not the same as proof of learning, but for the right use case it is still useful evidence.
Edaxu supports general files and tracked downloads for resources that do not belong in a course player.
Live, In-Person, and External Training Records
Not every requirement happens inside the LMS. People attend workshops, complete field observations, join webinars, submit external certificates, or earn CE credits through approved third parties.
Even if the LMS does not deliver that content directly, it should help you manage the record. For certification and compliance programs, this is often the difference between a useful system and another place to store files.
Ask whether external completions can update a certificate, renewal window, CE ledger, or audit report. If the answer is "export to CSV and fix it yourself," budget for the manual work.
Edaxu is built around certification records, renewal workflows, CE credit tracking, verifiable certificates, and audit-ready reporting, so uploaded content is connected to the larger compliance record instead of sitting off to the side.
What About xAPI, cmi5, and AICC?
You may hear vendors mention xAPI, cmi5, or AICC.
Here is the non-technical version:
- AICC is older than SCORM and still appears in some legacy environments.
- xAPI is a more flexible tracking standard that can record learning activity outside a traditional LMS course launch.
- cmi5 tries to bring xAPI-style tracking into a more structured LMS launch model.
These can matter, especially for organizations with advanced learning data requirements, simulations, mobile apps, or a Learning Record Store. But most buyers should not let these acronyms distract from their actual operating needs.
Ask a simple question: what content do we have today, what records do we need tomorrow, and what reports will we need during an audit?
If the answer is mostly packaged eLearning courses, SCORM support is still essential. If the answer includes videos, PDFs, downloads, external CE credits, and offline records, you need broader content and record support too.
Edaxu supports SCORM 1.2 and SCORM 2004 today. cmi5 is a future consideration, not something we claim as current support.
A Practical LMS Content Checklist
Before you buy, put the vendor through a real test.
Use your own training materials, not polished demo content.
Test SCORM
Upload at least one SCORM 1.2 package and one SCORM 2004 package if you have both.
Confirm:
- the package imports without conversion
- the course launches cleanly
- the learner can leave and resume
- completion saves correctly
- scores appear in reports
- failed attempts behave correctly
- admins can see useful troubleshooting information
If you are still choosing an authoring tool, the SCORM authoring tools comparison will help you understand what those tools export and where they differ.
Test Non-SCORM Content
Upload a video, PDF, image, and general file.
Confirm:
- learners can access each format cleanly
- progress or completion can be tracked where appropriate
- the record can count toward a requirement if needed
- admins can report on it
- certificates, CE credits, or renewals can use the completion record
This is the part buyers often skip. It is also where a lot of hidden implementation work shows up.
Test Reporting
Run the report you would need if an auditor emailed you tomorrow.
Do not accept a dashboard screenshot as proof. Export the data. Look at the fields. Make sure you can explain what happened without asking engineering to interpret raw SCORM values.
For compliance and certification programs, the report should connect the training item to the learner, requirement, completion status, score if relevant, date, certificate, renewal, or credit record.
Test the Admin Workflow
Have a real admin upload the content, assign it, preview it, fix a typo, replace a file, and pull a report.
This tells you more than a product tour. If the workflow feels fragile during evaluation, it will not magically feel better after launch.
Questions to Ask LMS Vendors
Use these in procurement calls:
- Which SCORM versions do you support?
- Do you support SCORM 1.2 and SCORM 2004 without conversion?
- What is the maximum SCORM package size?
- Can I upload a test package during evaluation?
- How do you track completion, score, pass/fail, time, and bookmarking?
- Can SCORM completion trigger certificates, renewals, CE credits, or notifications?
- What reports can admins run without custom work?
- Can admins inspect upload or launch errors?
- What video formats do you support?
- Can videos track watch progress and completion?
- How do PDFs, images, and files count toward training requirements?
- Can external or offline completions be recorded?
- Do you support xAPI, cmi5, or AICC? If not, are they on the roadmap?
- What happens when we replace a course with a new version?
- Can we export historical completion records?
The goal is not to collect yeses. The goal is to understand what happens on a normal Tuesday when your team is running real training.
What Edaxu Supports
Edaxu supports SCORM, but we do not treat SCORM as the only content that matters.
Today, Edaxu supports:
- SCORM 1.2
- SCORM 2004
- video uploads, including MP4, MOV, WEBM, and AVI
- PDFs
- images, including PNG, JPG, and JPEG
- general files and downloadable resources
- tracked downloads
- certificates
- CE credit records
- certification renewal workflows
- audit-ready reporting
Edaxu supports large training assets, with up to 5 GB per asset and storage allowances that scale by plan.
The important part is not just that these files can be uploaded. It is that they can live in the same operational system as your completions, certificates, CE credits, renewals, and reports.
That is what most teams actually need.
The Honest Take
SCORM support is table stakes for an LMS that claims to handle serious training programs.
But it is not enough by itself.
If your LMS supports SCORM but treats videos, PDFs, images, downloads, and external records like second-class citizens, your team will eventually work around the system. That usually means spreadsheets, shared drives, manual certificates, and messy audit prep.
Buy the LMS that supports your actual training library, not just the acronym everyone asks about on the first call.
For most teams, that means strong SCORM support plus flexible content handling plus records that are useful after the learner closes the course.
That is the real test.
Want to test your own content? Start a free Edaxu trial, upload your SCORM packages, videos, PDFs, and files, then see how completions, certificates, CE credits, and reports behave with real training assets.
Frequently Asked Questions
Is SCORM still important when buying an LMS?
Yes. SCORM is still the most common standard for packaged eLearning courses. If you use off-the-shelf compliance training or authoring tools like Articulate, Captivate, iSpring, Lectora, or Camtasia, you will likely need SCORM support.
Should every training asset be converted to SCORM?
No. SCORM is useful for interactive eLearning courses, especially when you need completion, score, and bookmarking data. But videos, PDFs, images, worksheets, downloadable resources, and external training records often make more sense in their native formats.
What SCORM versions should an LMS support?
Most buyers should look for SCORM 1.2 and SCORM 2004 support. SCORM 1.2 is still the safest default for broad compatibility. SCORM 2004 is useful for some content libraries and more advanced tracking scenarios.
Does SCORM track everything a compliance team needs?
Not by itself. SCORM can track course-level activity like completion, score, pass/fail status, time, and bookmarking. Compliance teams usually need more than that: assignments, certificates, renewal dates, CE credits, audit exports, and historical records.
What content formats does Edaxu support?
Edaxu supports SCORM 1.2, SCORM 2004, video files, PDFs, images, general files, and tracked downloads. Edaxu also connects training records to certificates, CE credits, certification renewals, and audit-ready reporting.
Does Edaxu support cmi5?
Not today. Edaxu supports SCORM 1.2 and SCORM 2004 today. cmi5 is a future consideration, but it is not current support.
Further Reading and Sources
Research for this post drew from the following sources: