By Erick Finn, independent music producer and audio engineer.
Part of the Sound Forge Pro 2026 Guide — start there if you're new to the editor.
This fix is part of the Sound Forge Pro Mastering hub. If your plugins are visible again, return there for the EQ, Plug-In Chainer, Statistics and mastering workflow guides.
This guide is part of the Sound Forge Pro Troubleshooting hub. Start there if you need symptom-first fixes for no sound, recording/input problems, ASIO routing, Windows audio devices or missing VST plugins.
Tested with Sound Forge Pro 17 and 18 on Windows 11, using a mix of VST2 and VST3 plugins from Waves, iZotope, and FabFilter. Last tested July 2026.
You installed a plugin. Sound Forge Pro doesn't show it anywhere. Not in the Plug-In Chainer, not in FX Favorites, not in the Plug-In Manager. This is one of the most common complaints about Sound Forge going back over a decade, and it almost always comes down to one of a handful of causes: the wrong folder path, a stuck scan, a VST2/VST3 mismatch, or a plugin that got hidden without you realizing it.
Quick answer: Go to Options, Preferences, VST Effects. Check that the folder your plugin actually installed to is listed as a search folder. Sound Forge only scans the folders you specify here. If your plugin installed somewhere else, like a manufacturer-specific subfolder under Program Files, Sound Forge will never find it no matter how many times you rescan.
Don't reinstall Sound Forge yet. If the plugin works fine in another host like Reaper or Cubase, the plugin itself is fine. The problem is entirely in how Sound Forge is scanning, or not scanning, the folder it lives in. If you're also dealing with input or recording problems separately, the recording troubleshooting guide covers that on its own.
Before You Start: Identify the Exact Problem
Different symptoms point to different fixes.
The plugin never appears anywhere, in any menu. The folder isn't being scanned at all. Go to Fix 1.
The plugin is checked in Preferences, but doesn't show in the Chainer or FX Favorites menu. It's scanned but not added to your menu structure. Go to Fix 2.
You installed the 64-bit or VST3 version, and it's nowhere to be found. Older Sound Forge versions can't load it. Go to Fix 3.
Sound Forge freezes or hangs when you open it, or when you open the Plug-In Manager. The scanner is stuck on a specific plugin. Go to Fix 4.
You bought the Suite edition and the bundled plugins aren't showing. They installed to a separate folder Sound Forge doesn't search by default. Go to Fix 5.
A plugin that worked last month is gone now. Something changed in the folder scan order, or the cache is stale. Go to Fix 6.
You know you saw the plugin before, and now it's just gone from every list. It may have been hidden, intentionally or by accident. Go to Fix 7.
You installed a synth or instrument plugin, not an effect, and it's nowhere to be found. Sound Forge is built as a single-file audio editor and effect host, not a MIDI instrument DAW. See the FAQ below on VST instruments.
Fix 1: Wrong or Missing VST Folder Path
Go to Options, Preferences, VST Effects. This is the same setup step confirmed in our own Sound Forge install guide: Sound Forge won't find plugins automatically, you have to point it at the folder manually, using Add folder and then Scan. This tab lists the folders Sound Forge searches. If your plugin's install folder isn't listed, add it with the folder browser. Click OK, not Apply, when you're done adding a folder, and give the scan time to finish before doing anything else.
The exact install location varies by manufacturer, but a few paths cover most cases:
- C:\Program Files\Common Files\VST3 (the standard VST3 location almost every manufacturer uses)
- C:\Program Files\VstPlugins (common for older or manually installed VST2 plugins)
- C:\Program Files\Steinberg\VstPlugins (Steinberg-branded installers often default here)
- C:\Program Files\Common Files\Steinberg\VST2 (another common VST2 location on newer systems)
- C:\Program Files (x86)\VstPlugins (only relevant for old 32-bit plugins on a 32-bit build)
Steinberg-branded plugins sometimes install into a Steinberg subfolder that isn't the same as the general VST folder other plugins use. If you pointed Sound Forge at one specific subfolder and it's still not finding a plugin, try pointing it one level higher, at the parent folder, so the scan can search subfolders too.
A KVR Audio forum thread on this exact problem confirms the pattern: a plugin installed into a manufacturer-specific subfolder didn't get picked up until the search path was set one level up, at the general Program Files or Steinberg folder rather than the specific VstPlugins subfolder. Older Sound Forge versions may show one default folder plus two alternate folders in this tab. If your installed version limits the number of paths you can add, consolidate plugins into fewer parent folders rather than trying to add a separate path for every manufacturer.
A few manufacturers cause this problem more often than others, and each has its own quirk worth checking:
Waves plugins not showing in Sound Forge Pro. Waves installs a single WaveShell file per format rather than one DLL per plugin. If Sound Forge is scanning for individual plugin DLLs and skipping the WaveShell, none of your Waves plugins will show up even though the install technically succeeded. Confirm the WaveShell VST or VST3 file is actually inside a folder Sound Forge scans.
iZotope RX or Ozone not showing in Sound Forge Pro. iZotope installers sometimes let you pick which formats to install, and it's easy to leave VST or VST3 unchecked if you only meant to install the standalone or AAX version. Rerun the iZotope installer and confirm VST3 is selected, then rescan in Sound Forge.
FabFilter plugin missing in Sound Forge Pro. FabFilter ships both VST2 and VST3 builds in the same installer. Check that the VST3 folder specifically has the FabFilter files, not just the older VST2 folder, and confirm you installed the 64-bit build if you're on a 64-bit Sound Forge version.
Fix 2: Plugin Is Checked in Preferences But Doesn't Show in Menus
This is a different problem from Fix 1. Your Sound Forge Pro plugin is not in the Plug-In Chainer even though it's checked in the VST Effects list in Preferences. It scanned successfully, but it never shows up when you go looking for it in the Chainer or in the FX Favorites menu.
Open the Plug-In Manager from the View menu. Look for your plugin in the folder tree, similar to how Windows Explorer organizes files. If it's there, drag it directly into a data window to load it into the Plug-In Chainer. This works even when the plugin hasn't been added to any custom menu. The Plug-In Chainer guide covers the full workflow once your plugins are showing up correctly.
To get a plugin into the FX Favorites menu specifically, right-click it in the Plug-In Manager and choose to add it to FX Favorites, or use Recreate by Plug-In Name from the FX Favorites menu to rebuild the whole favorites structure automatically based on your plugin names. A KVR Audio user with a similar problem on Sound Forge Audio Studio found that a plugin showed correctly under Plug-Ins, Third Party, but needed a manually created folder inside FX Favorites before it would appear in that specific menu. The plugin was never actually missing. It just wasn't organized into the menu the user was looking in.
Fix 3: VST2 vs VST3, or 32-bit vs 64-bit Mismatch
If you installed a plugin and it simply doesn't exist anywhere in Sound Forge, check whether you installed a version your copy of Sound Forge can actually load. This shows up most with plugin suites like iZotope's RX or Ozone, which have moved to 64-bit and VST3-only releases in recent versions.
Current 64-bit Sound Forge builds are built around modern VST workflows, and VST3 is the standard format most manufacturers ship today. Sound Forge also still loads legacy DirectX effects if you happen to have any left over from older software. If you're on an older Sony-era version predating the 64-bit transition, 64-bit or VST3-only plugins won't load at all, and no amount of rescanning fixes that. Check Help, About in Sound Forge to confirm your exact version and build before troubleshooting the plugin itself. The practical fix for an old version is either installing the 32-bit build of the plugin if the manufacturer still offers one, using a bridging tool like jBridge to run 32-bit plugins inside a 64-bit host or vice versa, or updating to a current version of Sound Forge.
If you're already on a current 64-bit version and a VST3 plugin still won't show, double check you installed the VST3 build specifically and not just a VST2 build with a similar filename. Some manufacturers ship both formats in the same installer with separate checkboxes, and it's easy to miss one during setup.
Fix 4: Scanner Freezes or Hangs on Startup
Sound Forge locks up when it opens, or specifically when you open the Plug-In Manager, and it won't respond. This usually means the scanner is stuck trying to load one specific plugin that's crashing or taking an unreasonable amount of time to initialize.
Open Task Manager while Sound Forge is frozen. Look for a process related to Sound Forge's plugin or VST server component under Processes. End that specific process rather than force-closing Sound Forge entirely. This often lets Sound Forge continue past whatever plugin caused the hang, though you may need to repeat this if more than one plugin is problematic.
Once you're back in, add your VST folders one at a time instead of all at once. Add one folder, let the scan complete, click OK, then add the next. This makes it much easier to identify which specific plugin or folder is causing the freeze, since you'll see exactly where the scan stalls. Avoid using Refresh in the plugin list once you've made progress, since Refresh restarts the entire scan from the beginning rather than continuing from where you are.
Fix 5: Suite-Bundled Plugins in the Wrong Folder
If you bought a Suite edition of Sound Forge that bundles third-party plugins, those plugins sometimes install into a dedicated folder inside the Sound Forge program directory itself, separate from your normal VST folder where you keep everything else.
A user on the MAGIX support forum documented this directly with Sound Forge Pro 12 Suite: the bundled plugins installed into a MAGIX Plugins folder inside the Sound Forge Pro installation folder, and the installer gave no option to choose a different location. Since older Sound Forge versions only allowed two search folder slots, users who already had both slots pointed at their existing VST collections had no room left to add the bundled Suite folder without giving up one of their existing paths.
If this applies to your installation, go to Options, Preferences, VST Effects and check the Sound Forge program folder itself for a subfolder with a name referencing the plugin bundle or manufacturer. Add that specific path as one of your search folders. If you're out of slots, consolidate your existing VST folders into one parent folder first, freeing up a slot for the bundled plugins.
Fix 6: A Plugin That Worked Before Has Disappeared
Nothing changed on purpose, but a plugin that showed up fine last week is gone now. Two things typically cause this.
First, folder scan order. If you have the same plugin, or plugins with similar names, installed in more than one of your search folders, Sound Forge may stop looking further once it finds a match in the first folder it scans. If you recently added or removed a folder from your search paths, the order changed, and a plugin that used to be found in one location might now be shadowed by a different, possibly broken, copy in another folder that gets scanned first.
Second, a stale plugin cache. Sound Forge stores scan results locally so it doesn't have to rescan everything every time it opens. If that cache gets corrupted, plugins that were previously found can silently drop out of the list. Forcing a full rescan usually resolves this: go to Options, Preferences, VST Effects, and use whatever rescan or rebuild option is available in your version. If a full rescan doesn't bring the plugin back, consolidate any duplicate folder paths first, since Sound Forge may simply be finding a different, non-working copy before it reaches the one that used to work.
Fix 7: Plugin Was Hidden
Sound Forge's Plug-In Manager includes a Hide feature specifically so you can remove a plugin from view without uninstalling it. This is meant for cases like a codec getting misidentified as an audio plugin, but it's easy to trigger by accident with a stray right-click.
Open the Plug-In Manager from the View menu and check whether your missing plugin shows up with a different visual state, or doesn't show at all because it's filtered out. Don't edit the registry as your first step. Start with something reversible: remove the VST folder from Preferences, VST Effects, then add it back and force a full rescan. Check whether the plugin reappears in the Plug-In Manager before doing anything else.
If a full folder rescan doesn't bring it back, Sound Forge's plugin cache may need a reset, which has historically involved a specific registry key tied to plugin scan results in older Sony and MAGIX-era versions. The exact key and path change between versions and aren't something to guess at. Contact Boris FX support for the correct steps for your installed version rather than editing the registry on your own, since changing the wrong key can affect settings unrelated to plugins.
Common Causes at a Glance
| Symptom | Most likely cause | Fix |
|---|---|---|
| Plugin never shows up anywhere | Folder not added as a VST search path | Options, Preferences, VST Effects, add the correct folder |
| Plugin checked in Preferences, missing from menus | Not added to FX Favorites or menu structure | Drag from Plug-In Manager directly, or use Recreate by Plug-In Name |
| 64-bit or VST3 plugin missing entirely | Older Sound Forge version without 64-bit/VST3 support | Update Sound Forge, install a 32-bit build, or bridge with jBridge |
| Sound Forge freezes on startup or in Plug-In Manager | Scanner stuck on one specific plugin | End the VST server process in Task Manager, add folders one at a time |
| Suite-bundled plugins not found | Installed to a folder Sound Forge doesn't search by default | Add the bundle's specific install folder as a search path |
| Plugin that worked before is gone | Scan order changed, or cache is stale | Force a full rescan, consolidate duplicate folder paths |
| Plugin used to show, now missing entirely | Hidden through the Plug-In Manager | Remove and re-add the VST folder, force a full rescan, then contact Boris FX support if a cache reset is needed |
| Synth or instrument plugin missing | VSTi is not an audio effect | Use a DAW for instrument work, then bring the rendered audio into Sound Forge |
Frequently Asked Questions
Why doesn't Sound Forge Pro find my newly installed VST plugin?
The most common reason is that Sound Forge only scans the folders you've explicitly listed under Options, Preferences, VST Effects. If your plugin installed to a folder that isn't on that list, it will never appear no matter how many times you open Sound Forge. Add the correct folder and let the scan finish.
Why does my plugin show as checked in Preferences but not in the plugin menu?
This means the plugin scanned successfully but wasn't added to your FX Favorites or menu structure. Open the Plug-In Manager from the View menu and drag the plugin directly into a data window to use it immediately, or use Recreate by Plug-In Name from the FX Favorites menu to rebuild your menu automatically.
Does Sound Forge Pro support VST3 plugins?
Current 64-bit Sound Forge builds support modern VST effect workflows, including VST3 in versions where VST3 support is available, along with legacy DirectX effects. Older Sony-era versions predating the 64-bit transition may not load modern 64-bit or VST3-only plugins at all, which is a common reason newer releases from manufacturers like iZotope simply never appear. Check your exact version under Help, About before troubleshooting the plugin itself. The full Sound Forge review covers current version details.
Why does my VST instrument not show in Sound Forge Pro?
Sound Forge is an audio editor and effect host, not a MIDI instrument DAW. The official Sound Forge product page states this directly: Sound Forge intentionally does not function as a digital audio workstation, and it's designed as a specialist tool for working on a single audio file. VST effects belong in the Plug-In Chainer and process audio you already have. VST instruments, synths, samplers, and MIDI generators create new audio from MIDI input, which needs a track-based sequencer to work the way it does in Reaper, Cubase, FL Studio, or Ableton Live. If you're looking for a synth plugin in Sound Forge and not finding it, that's expected. Use a DAW for instrument work, then bring the rendered audio into Sound Forge for editing, restoration, or mastering.
Why does Sound Forge Pro freeze when I open the Plug-In Manager?
A specific plugin in your scan path is likely crashing or hanging during initialization. Open Task Manager, find the process related to Sound Forge's VST scanning component, and end that process specifically. Then add your plugin folders back one at a time rather than all at once, so you can identify which plugin caused the freeze.
Why did a plugin that used to work in Sound Forge Pro disappear?
Usually either a change in folder scan order, where a duplicate or broken copy of the plugin in a different folder now gets found first, or a stale plugin cache that dropped the entry. Force a full rescan through Preferences, VST Effects, and consolidate any duplicate folder paths if the plugin still doesn't reappear.
Can I hide a plugin in Sound Forge Pro without uninstalling it?
Yes. Right-click the plugin in the Plug-In Manager and choose Hide. This is useful for plugins or codecs that get misidentified and clutter your list. To restore a hidden plugin, you typically need to reset the plugin cache and force a full rescan rather than simply unhiding it through the same menu.