11 Replies
Katie Riggio

Hi, J H!

That definitely doesn't sound right, and I'm glad you reached out for help. Let's iron out some key details to help us explore further:

  • Are you on the latest update of Storyline 3? To check, click the Help tab, then click About Storyline. You should see Update 7 in the bottom-right corner. 
  • With your permission, we'd like to take a look at your .story and audio files. It'll help us get a clear picture of what's happening during the import, and we'll delete it after troubleshooting. If that works for you, here's the upload link to share those details with us privately!

Hi Katie,
Thanks so much! My Storyline version says "Update 3:3.15007.0." I'm not at liberty to share the .story file as it's under development w/in the gov't. But I can gladly share the audio files- both the source audio files I'm importing, and the exported /story_content .MP3s which for some reason get automatically re-named on publish. I must say I can't comprehend the decision to invoke that behavior, as opposed to just leaving the audio files with their native names, even if compressing for export. It further seems that since these are just source files being stored in the published folder, they could even just be straight copies of our originals, rather that re-packaging/re-compressing/re-writing the audio file. As it stands now, I've had to go through each audio file individually, to determine which published audio file corresponds to which original source. I have 63 more files to go, and that's just for the barebones prototype. Final products could need many more, when we subdivide the screen into finer grids of tones. So you can see this becomes rather prohibitive. Does "Update 7" export stereo audio, and moot the point?

Thanks again,

Lauren Connelly

Hi J H!

This discussion mentions the same snag that you're running into!

Unfortunately, Storyline 3 doesn't support stereo audio which is why it is converted after publishing. Here are the audio formats that Storyline 3 supports.

You'll also find a number of workarounds in the discussion I've linked. Worth a try to see if that will get your audio up and running!

To receive the most recent bug fixes, make sure to update Storyline 3!

Vincent Scoma

Hi JH,

At this time, Storyline 3 doesn't support stereo files and it will convert that file to mono when imported. Since this would be a new feature to Storyline 3, I'd love to have you share more thoughts with our team as a feature request

In the discussion that Lauren provided a link to, there is a workaround that a community member provided that I hope will help! You can find out more about this workflow here


Hi Vincent & Lauren-- Please then explain your colleague's initial response to my original post:
"Hi, J H!
That definitely doesn't sound right, and I'm glad you reached out for help. Let's iron out some key details to help us explore further:

Are you on the latest update of Storyline 3? To check, click the Help tab, then click About Storyline. You should see Update 7 in the bottom-right corner."

So I have now gone through our organization's lengthy and costly software security eval/approval process to get Storyline 3 updated to Update 7, and now you're telling me that this will not help??

What did not sound right about my OP? By what you're telling me now, IT WAS EXACTLY RIGHT.

So Update 7 was of no help and that was a complete waste of our time and money, correct??

Andrew's workaround is smart but prohibitive as we'd have to do it for hundreds of files for each project, and for each of those files, we'd have to find what exported hash filename corresponded to what original stereo file, which for that many files is basically impossible.

None of that "Feature Request" nonsense please, when we have work that needs to get done right now. Stereo Audio. For e-learning that meet 508 Compliance by law. This week. Please advise.

Lauren Connelly

Hi J H!

I'm happy to explain my colleague's request in further detail.

We offer troubleshooting steps based on the version of Storyline while also sorting through other specifics including which Windows environment, which project is the issue occurring, etc. 

Secondly, updating Storyline ensures the most recent bug fixes as well as features that obey current industry standards. You can see the changes we've made in Update 7 here.

And with that information, we can begin troubleshooting. 

Lastly, I don't have any details on when Storyline 3 will support stereo audio. Stereo audio increases the file size which is not a direction we're taking right now. If our team decides to reroute to this, we'll let you know in this discussion.


Thanks Lauren. Unfortunately that wasn't the main thing I need explained.

In response to my brief statement of the issue:
"Hi, I'm in Storyline 3 and my audio appears to be automatically converting to mono on import."

This was the first thing said by your colleague:
"That definitely doesn't sound right."

Please explain her statement, or acknowledge that it's plainly incorrect, as Storyline 3 is intentionally made to only offer mono audio.

Meaning the issue definitely does sound right, and no troubleshooting nor available patch can affect it, period.

Correct? Please confirm.