Apple will keep Rosetta 2 running through macOS 27, then remove it, and every Intel-only audio plugin on your Mac stops loading. macOS 26.4 already started throwing warnings when you open one. That alert is not a suggestion.
VST 2 is caught in the same net. On macOS, the format only ever ran under Rosetta, never natively on Apple silicon, so Steinberg's slow retirement of it and Apple's hard cut-off now land together.
Windows buys you time, not immunity. VST 2 does not run on Windows on ARM at all, and abandoned plugins do not rebuild themselves.
In Cubase and Nuendo 14 and 15, VST 2 plug-ins are disabled by default. You can switch them back on through the VST Plug-in Manager, press the VST 2 button, and let it rescan. The support is still in there, but you have to ask for it now.
Old projects are where this bites. A session saved with a VST 2 instance will not automatically pick up the VST 3 version of the same plugin, so you get a blank slot and lost settings rather than a clean swap.
Why old plugins vanish after a system update is usually this, not corruption. The files are sitting exactly where you left them. The host has simply stopped looking.
There is a sting buried in the middle of that. macOS 27 uninstalls Rosetta 2 automatically if you already had it, so you have to reinstall it deliberately to keep Intel code running through that cycle.
Native is not a marketing word here. A universal binary carries Apple silicon and Intel code in one file, and once Rosetta 2 goes, anything without the Apple half is dead weight on the drive.
Finding the stragglers takes about ten minutes. Activity Monitor has a Kind column that tells you whether a running process is Apple or Intel, and a host stuck in Rosetta mode drags the whole session down with it.
Open the projects you still care about before you update, not after. Note every plugin without a native build, and check whether the developer is still trading.
The technical pitch is real. Parameter modulation is non-destructive, so a value returns to where it started once the modulation stops, and hosts can read plugin metadata without loading the plugin, which makes scanning far quicker.
Support is patchy, though. Bitwig Studio, REAPER since version 7, and FL Studio load it, while Ableton Live and Logic Pro do not, and Pro Tools stays locked to AAX.
None of it rescues a plugin whose developer has walked away. Rebuilding a dead lo-fi chain usually means shopping, and plenty of that money goes on newer vintage-flavoured effects that install cleanly on current systems.
Bounce the stems while the old plugins still open. A rendered audio file outlives every format war, and it costs nothing but disk space and one boring afternoon.
VST 2 is caught in the same net. On macOS, the format only ever ran under Rosetta, never natively on Apple silicon, so Steinberg's slow retirement of it and Apple's hard cut-off now land together.
Windows buys you time, not immunity. VST 2 does not run on Windows on ARM at all, and abandoned plugins do not rebuild themselves.
Steinberg already switched VST 2 off by default
Steinberg called time on 19 January 2022, saying its hosts would offer VST 3 compatibility only within 24 months. The timeline slipped. The direction did not.In Cubase and Nuendo 14 and 15, VST 2 plug-ins are disabled by default. You can switch them back on through the VST Plug-in Manager, press the VST 2 button, and let it rescan. The support is still in there, but you have to ask for it now.
Old projects are where this bites. A session saved with a VST 2 instance will not automatically pick up the VST 3 version of the same plugin, so you get a blank slot and lost settings rather than a clean swap.
Why old plugins vanish after a system update is usually this, not corruption. The files are sitting exactly where you left them. The host has simply stopped looking.
macOS 27 is the last stop for Intel-only plugins
Golden Gate, the macOS 27 release expected in September 2026, is the final version with full Rosetta 2. macOS 28 strips it out, keeping only a narrow slice aimed at old Intel-based games.There is a sting buried in the middle of that. macOS 27 uninstalls Rosetta 2 automatically if you already had it, so you have to reinstall it deliberately to keep Intel code running through that cycle.
Native is not a marketing word here. A universal binary carries Apple silicon and Intel code in one file, and once Rosetta 2 goes, anything without the Apple half is dead weight on the drive.
Finding the stragglers takes about ten minutes. Activity Monitor has a Kind column that tells you whether a running process is Apple or Intel, and a host stuck in Rosetta mode drags the whole session down with it.
Open the projects you still care about before you update, not after. Note every plugin without a native build, and check whether the developer is still trading.
CLAP is the open format filling the gap
While that clear-out runs, a third format has been picking up hosts. CLAP, short for CLever Audio Plug-in, was launched in 2022 by Bitwig and u-he, and it sits under the MIT licence with no fees and no membership.The technical pitch is real. Parameter modulation is non-destructive, so a value returns to where it started once the modulation stops, and hosts can read plugin metadata without loading the plugin, which makes scanning far quicker.
Support is patchy, though. Bitwig Studio, REAPER since version 7, and FL Studio load it, while Ableton Live and Logic Pro do not, and Pro Tools stays locked to AAX.
None of it rescues a plugin whose developer has walked away. Rebuilding a dead lo-fi chain usually means shopping, and plenty of that money goes on newer vintage-flavoured effects that install cleanly on current systems.
Bounce the stems while the old plugins still open. A rendered audio file outlives every format war, and it costs nothing but disk space and one boring afternoon.
