external_files folder

May 28, 2013

When publishing to LMS with the new v3 Storyline, it does not create an external_files folder, so my hyperlink to the resources doesn't work. When publishing to CD, it does create an external_file. I can manually add the external_files folder and its content after publishing to LMS and it then works normally. 

8 Replies
Christine Hendrickson

Hi there Jonathan,

First, can you please confirm you're working with local project files?

  • Work on your local drive (your C: drive). Working on a network drive or a USB drive can cause erratic behavior, including file corruption, loss of audio, and other unexpected behavior. 
  • You should also make sure the directory path to your project files and your published output is less than 260 characters (for example C:\Articulate).
  • Avoid using special characters, accents or symbols in your file names (this includes spaces and underscores).

Additional information regarding "Naming Files, Paths, and Namespaces" in Windows operating systems can be found in the following Microsoft article.

If you create a new, blank Storyline project, does the same thing happen when you publish the file for your LMS? How about publishing for Web, instead of CD?

I know you mentioned you can manually add the folder, but I'm curious why it isn't being generated automatically. 


John Botham

Hi Christine,

I think I have discovered what is happening. It is not an issue with the dot points you suggested.
I use the resources tab in the player to store files that I link to in the slides when needed. I don't want users to look in the resources tab for the files because the files are region specific (I use a variable to select the correct ones) so I hide the player resources. In previous versions of Storyline this worked well, but I appears in v3 that if you hide the resources tab, it does not create an external_files folder. Is there a workaround for this, or do I have to add the folder manually each time I publish?

Incidentally, it worked when I published to CD because I had activated the resources tab to test it.

Christine Hendrickson

Hi there John,

I've been able to replicate this on my end with Update 3 installed. However, I don't have an active version of Update 2 installed to verify whether or not this differs between the two versions. 

I can sort of  understand why the folder is removed if you disable the Resources tab for the player itself - I'm guessing that Storyline sees that as removing the attachments/links from the tab. 

If copying and pasting that file into your published output directory works for you, I would suggest sticking with that method for the time being. 

I'll keep an eye on this and see if I'm able to find any other options for you.

Thanks John!


Math Notermans

I am using the external_file folder to add Javascript libraries i want to use in combination with SL2.  I cannot manually add the folder and files after each publish, especially because i do need to publish everytime i work with Javascript because it doesnot work in preview mode.

So an option to have the folder created and filled, but not visible in the player would suit my needs.



Phil Mayor

There is a sneaky trick to make it not visible.  Turn off the resources in the player.  Create a new scene and on that one slide set the player controls to custom and enable the resources.

As long as that slide is not visible to the user the resources will be hidden but the external files folder is created and all content available. The only downside is that the player will change to accommodate the additional tab, normally not an issue.

By the way great way of including external javascript libraries.

Math Notermans

Thx Phil. Allready found that option and indeed works fine.

Another thing i am running in to when using Javascript this way, is that somehow my 'attached' js-files dont get updated whenever i change them in Sublime.
Workaround for that offcourse is remove and add again into the resources of the player, but that is quite timeconsuming and no fun really.

Any clue how to fix that ?

This discussion is closed. You can start a new discussion or contact Articulate Support.