How to import a SCORM file into Articulate Storyline?

Hi - I´m new to Articulate and trying to find out how to import content on SCORM format into Articulate storyline. I've received some learning material on that format and I've heard that I should be able to upload it to Articulate. Can anyone give me a step by step guide on how to do so?

Thanks in advance!


38 Replies
Lauren Connelly

Hello Buildbase Training!

The published output folder doesn't include the source file, so there isn't a way to edit a Storyline course without the .story file. The .story file should always be saved on your local drive, typically the C: Drive, and isn't changed when publishing a project. I'd recommend looking for the .story file and opening it in Storyline 360 to make edits.

Leslie McKerchie

Hi Jeanelle, and welcome to E-Learning Heroes. 😊

We recommend adding slides directly in the .story project file and re-publishing. You have a couple of options:

  • If you have Storyline and the vendor can send you the .story file, you can add it yourself and then republish.
  • You can send the information needed for an introduction slide directly to the vendor to include it in the SCORM Package sent to you.
ToriShana Johnson-Niño

Hello, Buildbase Training, I wonder about the same thing. I have what I think is a NEW question, or needs some clarity.

What if I don't want to edit the course. I just want to import the SCORM packaged file as is and then publish it online so other employees can take the course who may not have access to the LMS. Is that possible? If it helps one of the creators used ARTICULATE to create this SCORM packaged file. Any advice would be greatly appreciated.

Leslie McKerchie

Hi ToriShana,

If the published output is a SCORM Package, you could upload this .zip file to another LMS  environment if needed.

If you're wanting to host the content on a web server for more employee access, the .story file will need to be re-published for the web:

Storyline 360: Publishing and Sharing Content

We do not support modifying the published output, but someone in the community may be able to help.

Leslie McKerchie

Hi Peggy,

No, you cannot upload SCORM files into Storyline. As Lauren shared above just a few days ago, the published output folder doesn't include the source file.

Yes, you need the .story files. There is no way to edit a Storyline course without the .story file. 

I hope this clarifies what has been previously shared here.

Thierry Nguyen Cuu


This is a very interesting thread yet I think the question has not been understood, or maybe I am misunderstanding myself ..:o)

The idea is to add an existing content from a SCORM package and not reverse engineering it.

For example, I have a 2 SCORM packages, 1 is how to cook pasta, and 2 is how to make a sangria ..

Say, I want to create a storyline project adding these two packages AS IS, with no modification whatsoever to any of them.

Is this possible with the current 32 bit storyline360?

if not, is this something we can expect to come along soon?

This is a great opportunity of integration which would make storyline stand out from the competition: the capability to imbedding any SCORM standard packages into a storyline project.

YAY .. 


Zechariah Dice

My guess is that there is lost metadata that a published SCORM file does not contain.  Much like a layered photoshop file can be easily manipulated, but once flattened into something like a .PNG, it loses the layers.  My best guess is that reverse engineering a project from a SCORM file requires a great deal of inference by the import system which inevitably fails to capture the construction of the source product.

Joseph Francis

It would also be a great way to steal someone else's code. That is why Macromedia removed the source .FLA from published Flash SWFs many years ago, and completely changed the output format a few revisions after that.

While it is convenient to have the ability to decompile your project any time you want, having and enforcing retention policies and procedures for all assets is a small price to pay to protect intellectual property.