What a SCORM file is
A SCORM file is a .zip archive. Inside is a small website (HTML, JavaScript, CSS and media) plus imsmanifest.xml, which tells an LMS how to launch it. There is no special program that "opens SCORM". You open the website inside it, and optionally give it the SCORM API it expects. For a primer on the format, read what SCORM is and how 1.2 and 2004 differ.
Option 1: unzip it and find the launch file
- Extract the zip into a new folder.
- Open imsmanifest.xml in a text editor and find the resource element with adlcp:scormtype="sco" (SCORM 1.2) or adlcp:scormType="sco" (SCORM 2004). Its href attribute is the launch file.
- Storyline exports usually launch index_lms.html. Rise exports usually launch a page in the scormdriver folder, with the course itself in scormcontent/index.html.
- Open that file in a browser.
This is the quickest way to read the content, but expect problems. Browsers restrict pages opened with file:// from loading other local files, so many modern courses show a blank screen or a "loading" spinner. And because there is no LMS, the course's SCORM driver cannot find the API. Some courses show an error such as "unable to find the LMS API", others just do not save progress.
Option 2: serve the folder from a local web server
Running a tiny web server fixes the file:// restrictions. From the extracted folder, run one of these commands and open the printed address followed by the launch file path:
- Python 3: python -m http.server 8000
- Node.js: npx serve .
The course should now play. Tracking still does not work, because no SCORM API is present, so this is good for checking content and layout, not completion or scoring.
Option 3: preview it with a simulated SCORM runtime
SCORM Packager has a browser preview in every project, including on the free tier. Upload the zip to a translation, merge or accessibility project and open the preview. The course plays with a simulated SCORM runtime: both the SCORM 1.2 API and the SCORM 2004 API_1484_11 object are provided, so the course starts normally instead of complaining about a missing LMS.
- Good for: clicking through the content, checking that the package is valid, comparing an original with its translated version or remediated version.
- Not a substitute for LMS testing: the simulated runtime accepts every call and keeps data in memory only, so nothing persists after you reload. Preview sessions last an hour.
- xAPI packages play, but their statements are not sent to a learning record store.
Option 4: a test LMS
To test real tracking, such as completion, score and resume, you need an LMS. Rustici's SCORM Cloud has a free trial built for exactly this, with detailed logs of every API call. A throwaway Moodle site works too; see how to test SCORM courses in Moodle.
Ways to open a SCORM file without your production LMS| Method | Plays content | Tracks progress | Setup |
|---|
| Double-click the launch file | Sometimes | No | None |
|---|
| Local web server | Yes | No | Python or Node.js |
|---|
| SCORM Packager preview | Yes | Simulated, not saved | Free account |
|---|
| SCORM Cloud or a test Moodle | Yes | Yes, with logs | Account or server |
|---|