64-Bit Storyline 360

Is there a way to access a 64-bit version of Storyline 360? I noticed what I have installed through the 360 suite is only 32-bit and I'm finding that I may be reaching a ceiling with performance while developing my courses. I click on pretty much anything in the app and have to wait a full second before Storyline 360 responds. This has slowed my production down significantly. I was wondering if there's a way to get a 64-bit version or if anyone is having a similar issue.


84 Replies
Mateusz Szuter

I generally have given up hope long time ago, as any serious matters ... doesn't matter here and things that were implemented in another softwares years ago aren't even considered here. I guess we will never see 64-bit app as it will require to rewrite the whole application - too much money to loose ;) only hope is if windows drop all the 32-bit apps support.

However, reading all your guys problem I think you all takes Storyline a little too seriously or doing something really wrong. I sometimes get RedCross on layers or images, but for the long time that doesn't crash the app at all. I just need to restart and everything works good again.

I've opened now one of my recent big project - 160 slides, with almost 200 voiceovers and 1000 of high-quality images on every screen, (no video tho). Storyline takes only 550MB of RAM for this. Plenty left to utilize.

And to be honest, if you are doing big, complicated projects, like over 200 screens or more, that's not the proper way on doing courses this days. Split that into separate modules and your problems will be gone. Put the videos in the last, compress them beforehand. Don't use 5000x5000 pixels graphics when you produce 720p training. Don't use many pngs on one screen, go for jpg whenever you can. Maintain your resources! If you are indeed in need to make huuuuuge courses, also work on separate files and in the end import all this separate files into one and then publish. You know the project beforehand, so plan ahead of doing it. All this boosts up Storyline performance. I once was also angry about the time storyline took to process things, but gave it 2 day proper research, pinned down what was the problem and now I work quite ok with it.

However, with every update comes some new issues destroying overall workflow which is often left to be. Still I guess no other authoring tool have so many... versability like Storyline, where I easly can do many, many additional things that were never meant to be by the devs I guess. Gonna stick with the guy, let's call it though love and hope for more performance updates. I suppose the GPU acceleration helped a little with overall performance, so there's a light in the tunnel.

As someone mentioned, HR reps will be pleased because they can do their interactive powerpoint, but let's be clear - they are the main target for this software. Not us, the artists :D

Diarmaid Collins
Shannon Dunn

I think windows 12 will drop before we get the support you'd expect from $1000+ Per user software. 

Captivate's running 64 bit - Might be time for that change..

Woah, woah, woah... calm down there Shannon. Take a deep breath... breathe in.... and slowly, let it out.... there... you should be feeling better now.

That was quite a scare you gave us. Whew. There's no need to be so... uh, hasty!

As bad as some of the quirks in Storyline are, let us not get into the <bleurgh>... sorry, I just threw up in my mouth a little... nightmare <starts frantically scratching bald patch> that is <takes deep breath - whimpers - eye twitches> the "C" word.

Shannon Dunn

It genuinely gave me a giggle!

I loved the Storyline software, relatively easy to use, makes sense and is quick to produce; however, in today's media-intensive crowds through videos, interactions, animated gifs etc. Storyline dies. 


Currently working on a project -

  • ~130 VO's approximately
  • 1-1.5 hours.
  • Compressed slides (from approx 180 - > sub 100) etc,
  • used Jpeg and PNG's, gifs,
  • 12x videos

As soon as I attempt to preview the slide to QA/QC, the software stalls and won't move past 50%; I have to kill the process to get back in. I know it's not hardware - Running an i9, 3070RTX, 32Gb Ram, etc.


Let's look at this seriously for a moment - browse through the feature requests etc., and you'll see people asking for features that have been standard in other software packages for years; quite a lot have had no moment for up to 5 years (this thread included) - The moderates response is always the same - Tell us what you want, head over the feature request page and log your request; or I've raised that request on your behalf. 

We are paying $1000+ a year in sub fees for a software package that's only running at 50-75% of the competition. There are many other options other than the C-word, but at least with adobe, as expensive as it is, and non-intuitive software, they offer a monthly sub fee with software that covers 90% if not more of the requests. 

  • 360 images
  • 360 videos 
  • VR headset supports
  • 64 bit
  • better VTT/Closed captions/Translation.

I know I only stay with Storyline due to a lack of time to learn new software and rebuild my entire portfolio/library into a new software package. I can only assume that many others within this community would be in a similar predicament. 

Eric Richko
Michelle McKinney

Oh really?! Is it that bad? As I mentioned in my last comment, I've honestly never even looked at Captivate, but my recent issues were making me wonder if I should. 

I've used Captivate, Lectora and Storyline.  Lately I use Storyline because it is far superior with tracking branching.  Pros and cons to all of them, but from the ability to have ultimate control Lectora is the best for me.  Plus doesn't have the issue with running out of memory due to being 32 bit only that Storyline has.  I don't want to migrate my current work due to size, but may have to out of necessity.  I mean come on, how Storyline not be 64 bit yet?  Requesting that feature update just keeps falling on deaf ears.

Diarmaid Collins

Honestly, it's been quite a few years since I last used it (maybe 5??) and it's probably about 7 or 8 years since I had to work with it full-time but to describe it as clunky would be an understatement.

If one wanted to do anything... "interesting" ... there were widgets. So many widgets. Lots of widgets to provide what I would consider basic functionality. That somehow one couldn't edit. If one wanted something to look 'styled' or part of a coherent visual plan it was frustrating, to say the least.

But, and coming from a graphic design background, it did allow for text styling functionality all those years ago. Something Storyline has only adopted this year. Incredible.

One of the most frightening things I found when I changed to Storyline was how 'loose' everthing felt. I could do stuff. Actual things. And make it look good. And there were ways of making it look like this, or this, or that and wow... it was such a liberating feeling.

There was something about working within the limits of Captivate (similar to QuarkXpress for any ol' pre-press workhorses out there <touches chest - "salute"> prior to InDesign) that made it kind of hardcore, like trying to write a book without using the word "the". Or ride a bike without a saddle. And front wheel. It could be done but damn, it took a hell of a lot of effort.

Sure, drop-down accordions are easy to do (ish) in Captivate and nigh on impossible (programmatically challenging) within Storyline but that has been the only thing I really missed from Captivate.

Maybe it's come on in leaps and bounds. Maybe it's loosened up. I dunno.

When I last had to use it, and subscribed and opened the slick-looking new interface of Captivate up I was kind of disgusted the way nothing had really changed. Like throwing a sheet over a bed of nails and hoping folks think it's comfy.

I'd love to know if it has changed. But I am not going to check it out. My therapist has told me not to go back there. 

Ever again.


Michelle McKinney

I wanted to share an update on this issue, which I had attributed to a new work laptop that was 64 bit. Articulate and the story file in question I was encountering issues with had worked fine on my previous work issued laptop

After working extensively with me through a support ticket, the Articulate Service Desk identified the culprit as a custom font that wasn't supported by my computer. I'm not even sure where the font came from - I imagine at some stage I downloaded a template from the community and it was in it. When I opened my story file a warning message would pop up indicating that the font wasn't supported, but I had gotten into the habit of just clicking "ok" and moving on with my work.  On my old computer this never presented any issues, so I didn't suspect it as a cause on my new computer. However, on the recommendation of the Articulate service desk I rooted out and replaced all instances of the custom font (using instructions at end of this post) and immediately my performance issues improved.

Over the course of 2 weeks working extensively with this large project I had maybe 2 memory related crashes - not ideal, but a HUGE improvement to the dozens daily I was seeing before I removed the custom font packages.

I don't understand why the fonts caused such an issue, but suffice to say, I was delighted to get to the bottom of it. Many thanks to the Articulate service desk who I had a lot of correspondence with on my issues.

How to replace fonts:


Tai Saxty

This is an issue we see regularly. The cause of the issue is a system issue.
Windows can only allocate a maximum of 2GB memory to 32bit applications. This is a combination of all of the 32bit applications you have open. We quite often see that clients are using Microsoft Office applications and their installed office programme is the 32bit version.

Ideally they would need their IT department to give them the 64bit version so that this free's up the memory to be used by Storyline 360.

To see what you are using you can open up your task manager (Ctrl+Shift+Esc) and any open 32bit applications will have (32bit) after the name of the application.

The interim option is to get the user to close down the other applications so that Storyline can have more use of the memory so that the crashes stop and they don't get the low memory error showing up.

The only other thing we can do as mentioned by Articulate staff is to put in a feature request to the Articulate Development team and the more it is mentioned the more hope we have of them looking in to a 64bit version of Storyline 360

I hope this helps.