How to Use 32-Bit VST Plugins in a 64-Bit DAW

The computing world has moved to the 64-bit standard, but some older plugins in your collection may still be 32-bit. On Windows, FL Studio and REAPER can load many of them through a bridge. On a current Mac, look for a compatible 64-bit version or open the old project on a system that can still run the original plugin.

A 32-bit plugin uses a different architecture from a 64-bit DAW. A bridge lets the DAW communicate with the old plugin in a separate process. This is about how the software runs and addresses memory. The bit depth of your recordings is a separate setting.

At A Glance

  • Start with the developer’s native 64-bit release if there is one. Check that it comes in a format your DAW can load.
  • On Windows, jBridge can run old 32-bit VST2 plugins in a compatible 64-bit host that scans VST2. It leaves the original plugin in place.
  • Another option is to find similar-sounding 64-bit VSTs that resemble the 32-bit ones you want to replace.
  • FL Studio and REAPER can bridge on Windows. The VST Bridge in Cubase 4 to 8.5 and Nuendo 4 to 7 belongs to those older releases.
  • Test a bridged plugin in a copy of the project before relying on it. Check that the settings come back after reopening and that the render sounds right.

Why 32-bit VSTs Don’t Work On 64-bit DAWs By Default

A 64-bit DAW cannot load a 32-bit plugin directly. A bridge starts a separate process for the original plugin and passes audio and control data between that process and the DAW.

A 64-bit release may take the place of the original, but check how the developer handles old sessions. A new VST3 can appear as a separate plugin from the old VST2. If the project doesn’t recall the original patch, reopen the old session and write down or export the settings before changing anything.

Of course, you can alternatively just try to find another plugin with a similar sound, but of course, certain VSTs have very distinct sounds and one cannot simply replace them with something else. 

How To Get 32-Bit VSTs To Work On 64-Bit DAWs

First, check the developer’s downloads for the exact plugin and your OS. Confirm both the architecture and the format your host accepts. For example, a Windows VST2 .dll needs a Windows host that still scans VST2, even if you have a 64-bit wrapper for it.

If there is no native version and you are on Windows, jBridge can wrap a 32-bit VST2. Keep the original plugin and the generated wrapper in separate folders. In jBridger, select a 64-bit host, point it at the original plugin folder and choose a separate folder for the wrappers. Add that output folder to the DAW’s VST2 search paths, rescan, and try opening the plugin in a blank project first. The developer offers a demo for checking compatibility, with limits on saving and loading.

DAWs That Support 32-bit Plugins

FL Studio for Windows automatically bridges a scanned 32-bit plugin when needed. The wrapper settings show the plugin’s bit version and whether it is bridged. FL Studio for macOS uses 64-bit plugins and has no equivalent built-in bit bridge.

The internal VST Bridge was available in the Cubase 4–8.5 and Nuendo 4–7 era. Current Cubase and Nuendo require a different approach. On supported Intel or Windows configurations, enabling VST2 in recent versions restores the ability to scan that format. It takes a compatible third-party bridge to run old 32-bit code in a current Windows host.

REAPER can automatically detect when a Windows VST needs bridging. In the FX Browser, right-click the plugin and look under Run as. Separate process can share one bridge among plugins. Dedicated process gives the selected plugin its own bridge, which can help contain a crash.

Problems With Bridging 32-bit Plugins

On a Mac, macOS Mojave was the last release to run 32-bit apps. Old tools such as jBridgeM and 32 Lives were for compatible legacy systems. Rosetta on Apple silicon translates compatible 64-bit Intel code, so an old 32-bit plugin still needs a system that can run it.

A bridged plugin may add CPU load or lose its interface, automation or preset recall. Save the project under a new name and reopen it before you commit. If you can still open the old session, export the affected tracks from a common start point. Keep dry and processed audio and save MIDI parts separately where you might need to edit them later.

Should I Use 32 or 64-bit?

Use 64-bit plugins for new projects in a 64-bit DAW. Keep access to the old host, installers and authorizations if you need to recall sessions built with discontinued 32-bit plugins.

Ableton Live uses 64-bit plugins. On a Mac, check separately for Apple silicon support in the plugin format you plan to use. For any host, the developer’s requirements tell you more than the plugin filename alone.

Summary

When you need to recover an old session, a native 64-bit update is usually the easiest path if it can recall the original plugin state.

For an irreplaceable Windows VST2, try the bridge in your DAW or test jBridge. If the old plugin runs only on an earlier system, export the parts there while you can still hear and edit the session.

Brian Clark
Brian Clark

I’ve been a writer with Musician Wave for six years, turning my 17-year journey as a multi-instrumentalist and music producer into insightful news, tutorials, reviews, and features.

Musician Wave
Logo