I’m Jesse Taber, engineering manager for Storyline 360, here with the first Engineering Product Highlight. My plan is to regularly cover a new or upcoming Storyline enhancement from an engineering perspective to provide technical insights you won’t find in release notes or product documentation. This first highlight is all about 64-bit.

In November 2023, we released a 64-bit version of Storyline 360 to public beta that appears in the Articulate 360 desktop app as “Storyline 360 x64.” Since then, we’ve heard a lot of excitement about this new version of Storyline 360—but also some confusion. To address this feedback, I wanted to offer an FAQ that goes beyond the basics covered in the support article about 64-bit Storyline 360.

What is Storyline 360 x64, and how does it differ from the version of Storyline 360 I’ve been using?

Storyline has traditionally been a 32-bit application. The primary difference between 32-bit and 64-bit applications is the amount of system memory they can use. In Windows, 32-bit applications can access, at most, ~4GB of memory, while 64-bit applications can access far more memory than any modern consumer-grade PC can accommodate.

Put simply, the 64-bit version of Storyline 360 can take advantage of the relatively large amounts of memory available on most modern PCs.

Does Storyline 360 x64 provide performance improvements?

The primary benefit of targeting 64-bit processor architecture is the ability to use more system memory. When Storyline 360 opens a project file, it loads it all into memory. Very large projects, particularly those with many rich media assets, can experience issues opening, saving, and publishing in the 32-bit version of Storyline 360. Projects like this should be much more stable in Storyline 360 x64.

Aside from memory usage, most authors will likely see performance on par with the 32-bit version of Storyline 360. While performance improvements were not a primary driver for creating Storyline 360 x64, we plan to invest more directly in performance improvements going forward.

Is Storyline 360 x64 a full rewrite of Storyline?

No. Storyline 360 x64 comes from the same source code as the 32-bit version of Storyline 360. The difference is that it’s compiled to support 64-bit processors and operating systems.

What functionality differs between the 32-bit and 64-bit versions of Storyline 360?

Because both versions of Storyline 360 share the same source code, their functionality should be identical. However, certain third-party components Storyline 360 uses don’t work with a 64-bit processor architecture. We’re currently working on removing, updating, or replacing those features.

For example, the screen recording feature was not available in early builds of Storyline 360 x64 because a third-party component it relies on did not support 64-bit. As of Update 85, however, the screen recording functionality is available in the 64-bit version.

The support article about 64-bit Storyline 360 lists the features we plan to remove (deprecate).

Storyline 360 x64 is in public beta. Is it okay to use for my day-to-day work?

We feel confident that Storyline 360 x64 is stable and suitable for production work. We have been using it internally for months without issue. We have also gotten positive feedback about its stability from several Storyline 360 users who have been using it regularly since it was in private beta. We plan to move Storyline 360 x64 out of public beta and into general availability in the second half of 2024. Most of the remaining work centers around providing a seamless experience for all customers to migrate from the 32-bit version.

Because it shares source code with the 32-bit version of Storyline 360 there are no compatibility issues. That means that if you run into problems with Storyline 360 x64, you can always close your project and reopen it with 32-bit Storyline 360.

If you do encounter issues, please use the “Report a Bug” option at the top right corner of the application window to report them directly to the Storyline engineering team. 

Screenshot depicting the location of the “Report a Bug” option in Storyline 360 x64.

Why did it take Articulate so long to deliver a 64-bit version of Storyline 360?

Articulate released Storyline 1 in 2012. At that time, 64-bit processors and operating systems were becoming more popular in consumer-grade PCs, but 32-bit software was still prevalent. In the years that followed, memory got cheaper, which meant more PCs with memory greater than 4GB hit the market. Larger amounts of memory drove the need for 64-bit processors and software that supported them. We opted not to update Storyline 360 to support 64-bit until 2023, which we now realize was a mistake.

When we consider the changes we want to make to Storyline 360, we have to weigh the impact that each change will have and the effort required to implement it. We must also consider the opportunity cost of choosing certain changes over others. We believed the effort to make Storyline 360 support 64-bit processor architecture was far higher than the impact it would have on our customers since it wouldn’t bring dramatic performance improvements.

The Storyline codebase is over a decade old, and to say it is large and complex would be a gross understatement. Ensuring this code and the various third-party components would work properly in a 64-bit environment was daunting. Customers were also asking for many other features that would need to be put on hold if we committed to the 64-bit work. The team discussed 64-bit support many times in the 10 years that I’ve worked here. Each time, we reached the conclusion that it didn’t make sense.

So what changed? Why now?

Over the past several years, some of the third-party components that were roadblocks to 64-bit support have been updated or removed through the normal course of expanding and improving Storyline 360. More importantly, some intrepid software engineers on the Storyline team spent their Hackathon—a quarterly event where engineers can work on self-directed projects—proving that getting Storyline to support 64-bit processor architecture was more feasible than previously thought.

When Kerry Munz came on board as our CTO, she brought a fresh perspective. She correctly surmised that our customers interpreted the lack of 64-bit support as a signal that we were not investing in Storyline 360. She directed us to prioritize this work as the first of several projects to modernize Storyline 360 and cement our commitment to its future.

Will there always be both 32-bit and 64-bit versions of Storyline 360 available?

The number of 32-bit processors and operating systems actively in use today is extremely low. Eventually, we will only build and ship Storyline 360 in a 64-bit configuration. We’re currently working on a plan to make this transition as seamless as possible for our customers. We’ll share more details when they’re available.


I hope this product highlight has clarified the “what, how, and why” of Storyline 360 x64. If you haven’t already, I recommend trying out the public beta, particularly if you need to work with large or media-heavy projects. And remember to use the “Report a Bug” option at the top right corner of the application window to share any feedback directly with the engineering team.

Stay tuned for future engineering journal entries! And please leave a comment below if there are specific topics you’d like me to cover.

Jesse Taber
Daniel McHugh
Albina Podgraska
Jesse Taber