How to convert PowerPoint to SCORM - and what survives the conversion

Most training already exists as a slide deck. The request that follows is usually the same: "put it in the LMS so we can see who completed it".

Uploading the presentation as a file does not provide reliable progress tracking. At best, the LMS may know that somebody opened or downloaded it. That is not the same as knowing that they completed it.

This guide covers what the LMS actually needs, the three realistic ways to convert PPT to SCORM, and the failures that often show up only after you upload the package.

What is a SCORM file, really

A SCORM package is a ZIP archive containing web content and a file called imsmanifest.xml at the top level. The manifest tells the LMS what the course is called, which resource to launch and how the package is structured. Once launched, the course finds the JavaScript API exposed by the LMS and uses it to report information such as: started, bookmark is slide 7, completed.

That reporting layer is the important part. A SCORM package is not really a content format in the same sense as PowerPoint or PDF. It is a standard for packaging content and exchanging tracking data with an LMS. Almost anything a browser can display can sit inside a SCORM package; what makes it SCORM is the way the package is launched and how it communicates with the LMS.

Two versions are still commonly encountered.

SCORM 1.2 is the older version and remains the widest-compatibility choice for a simple slide-based course. It supports the things most presentation conversions need: completion status, bookmarking and time tracking.

SCORM 2004 adds more advanced sequencing and navigation rules and separates course completion from success or pass status. That can matter in more complex courses, but rarely adds much value to a straightforward converted presentation.

If nobody has told you which version to use and you are publishing a simple slide deck, SCORM 1.2 is usually the practical default.

Three ways to convert PPT to SCORM

1. A PowerPoint add-in

Tools such as iSpring Suite install as a tab inside desktop PowerPoint and publish the open presentation as SCORM. This is usually the highest-fidelity route. Animations, transitions, triggers and embedded media can be rebuilt as HTML5 rather than flattened into static pages.

The trade-off is that you need a dedicated authoring tool, desktop PowerPoint and, for tools such as iSpring, a Windows environment for authoring. This route makes sense when preserving the behaviour of the original presentation matters more than speed or simplicity.

2. Importing slides into an authoring tool

Authoring tools such as Articulate Storyline or Adobe Captivate can import PowerPoint slides as a starting point. You get a course that can then be expanded with quizzes, branching, variables and additional interactions.

Expect some cleanup. Fonts and positioning may shift, grouped objects may need attention, and complex animations, triggers or PowerPoint-specific objects may need to be rebuilt after import. In some authoring tools, imported PowerPoint slides also retain characteristics of the original fixed slide layout rather than automatically becoming fully responsive.

This route makes sense when the presentation is raw material for a proper e-learning course. It makes less sense when the requirement is simply: "make this exact deck available in the LMS by Friday".

3. Slides as images in a SCORM player

The simplest route is to export the presentation to PDF, render each PDF page as an image and place the images inside a lightweight SCORM player. The player handles navigation and reports progress back to the LMS. There is no PowerPoint add-in to install, and the process can work from any operating system.

The biggest advantage is visual consistency. Once the PDF pages have been rendered as images, the learner sees the same layout, fonts, charts and graphics regardless of which fonts are installed on their device.

The price is that the slide becomes a picture. Which brings us to the part many converter pages skip.

What survives the conversion - and what does not

With the image-based route, this is what happens to your deck:

• Layout, fonts, charts and images - preserved visually. The PDF freezes the rendered layout, and once each page is converted into an image, the learner does not need the original fonts installed.
• Animations and builds - flattened to their final state. A slide that reveals five bullet points one by one becomes a slide showing the final visible state.
• Transitions - gone. The SCORM player may add its own fade or slide transition, but the original PowerPoint transitions are not carried over.
• Embedded video and audio - do not survive the PDF-to-image workflow. At most, you get the visible poster frame.
• Speaker notes - remain in the source presentation. The learner does not see them.
• Hyperlinks - should not be relied on. Some PDF export workflows may preserve links, but once a slide is rendered as an image, the link is no longer inherently interactive unless the player recreates it separately.

None of this is a defect of a particular converter. It is a consequence of turning a presentation into static rendered pages.

It also tells you which decks are good candidates for this approach: policy briefings, product updates, onboarding overviews, internal presentations and other content designed mainly to be read. A deck that depends on a narrator clicking through builds, demonstrating animations or playing embedded media is a different job. For that kind of presentation, route 1 or 2 is the more appropriate choice.

Prepare the deck before you convert

• Turn important builds into slides. If a reveal matters pedagogically, duplicate the slide and show one more step on each copy. That survives almost any conversion route.
• Move essential narration onto the slide. If the learner needs information that currently exists only in speaker notes or in the presenter's commentary, put it into the visible content.
• Take video out. Consider publishing video as a separate LMS activity or embedding it later in a proper authoring tool. It will usually stream more reliably than media buried inside a converted slide deck.
• Split long decks. As a practical rule of thumb, consider dividing longer presentations into shorter modules, especially when learners are likely to stop and resume. Shorter modules also give the LMS more meaningful completion records.
• Check the aspect ratio. Use 16:9 unless you have a reason not to. Older 4:3 presentations usually leave more unused space inside modern widescreen course players.

Why the upload fails - or works and tracks nothing

1. "Manifest not found"

The classic. Someone unzips a package to look inside, then zips the folder instead of its contents. Now imsmanifest.xml sits one level down. The LMS expects the manifest at the root of the ZIP archive, so it reports an invalid package. Select and zip the package contents, not the folder that contains them.

2. The status stays "incomplete" forever

The course opens, the learner reaches the last slide, and the LMS still says incomplete. Usually the package never set the completion status, failed to finish the SCORM session cleanly, or lost pending data when the learner closed the window.

In SCORM 1.2, a simple course can report completion by setting cmi.core.lesson_status to completed. The package should also persist important progress during the session rather than relying entirely on the browser closing cleanly.

Decide deliberately what completion means:

• opening the course,
• viewing a defined percentage of slides,
• or reaching the final slide.

Then test exactly that behaviour.

3. It resumes from slide one every time

Bookmarking is not automatic. The player has to save the learner's current position, for example in cmi.core.lesson_location, and read that value again when the course is relaunched.

A package that skips bookmarking can still be a valid SCORM package. It is simply much less pleasant to use, particularly on phones and tablets, where sessions are interrupted more often.

4. It works in one LMS and not in another

A common cause is a standards mismatch: for example, a SCORM 2004 package uploaded to an LMS or course area configured for SCORM 1.2.

Another common problem is the launch environment. Some platforms open SCORM content in a new browser window or pop-up. Browser settings, security restrictions or the way the LMS exposes its SCORM API can then affect whether the course finds the API correctly.

Before blaming the course file, test the package somewhere neutral. SCORM Cloud is useful for this because it can show detailed information about how the package communicates with the SCORM API.

A shortcut, if you want one

We use the image-based route in our own production when a presentation needs to be online quickly, so we packaged the workflow as a free PowerPoint to SCORM converter. Save the presentation as PDF, drop it into the page and download a SCORM 1.2 package.

The player includes slide navigation, a progress bar, bookmarking and completion reporting - the four things described above, already built into the package.

• No account, no install. It runs in a browser tab and works across operating systems.
• Your source file stays with you. The PDF is rendered in your browser; only the generated slide images are sent for packaging - not the PDF, and not the original PowerPoint file.
• Honest limits. Up to 25 slides and 20 MB per deck, with ten exports per day. Everything in the "what does not survive" section still applies.

If the presentation is only one part of the training - slides, followed by a scored quiz and then a summary - the same slides can instead become part of a lesson in our SCORM course builder. The whole course can then be exported as one SCORM package with completion and pass criteria.

Related

• How to create H5P content with ChatGPT - the same kind of guide for interactive activities.
• Our e-learning platform - if you need somewhere to run the package.
• Talk to us if the deck deserves to become a real course.

PowerPoint® is a registered trademark of Microsoft Corporation. SCORM and all other product names mentioned here belong to their respective owners. This article and our tools are not affiliated with or endorsed by any of them.