Plugin not showing in Ableton Live? Fix it step by step.
When a plugin is missing from Ableton Live, the cause is usually one of five things: the wrong format, an unsupported build, an incorrect folder, disabled plugin preferences, or a failed scan. Work through the checks below in order.
Fix the whole setup—not just one plugin file.
A dependable result accounts for software, formats, versions, licenses, presets, supporting files, and the sessions that depend on them.
Confirm compatibility
Live supports 64-bit plugins. The plugin must also support your operating system, processor, and Live version.
Check the right folder
VST3 uses standard system folders, while VST2 may use a custom folder configured in Live.
Force a real rescan
Toggling plugin folders off and on or using the rescan controls can rebuild Live’s view of installed devices.
Try this quick fix sequence first
Close every instance of Live
Make sure Live has fully quit. On Windows, check Task Manager; on macOS, check Activity Monitor.
Restart the computer
This clears background installer, licensing, and indexing processes that can interfere with discovery.
Reinstall or update the plugin
Use the vendor’s official installer or product manager and install the correct 64-bit format.
Open Live and wait
After a large install or Live update, allow the Browser and plugin indexing process time to finish.
Run a full rescan
Open Live’s plugin preferences, confirm the required formats are enabled, and trigger a rescan.
Check the plugin format and compatibility
On Windows, Ableton Live supports VST2 and VST3. On macOS, it supports VST2, VST3, and Audio Units. Current Live versions require 64-bit plugins; a 32-bit plugin will not appear.
- Confirm that the plugin supports your exact operating system and Live version.
- On Apple Silicon, install a native Apple Silicon or universal build when using Live natively.
- If a legacy Intel-only plugin is required, check whether the vendor supports running Live through Rosetta.
- Do not assume AU, VST2, and VST3 instances are interchangeable inside an existing Set.
- Update licensing tools such as iLok License Manager before rescanning protected plugins.
Check Ableton Live's plugin folder settings
Windows VST3
VST3 plugins normally install to the system VST3 location and should be detected when VST3 support is enabled in Live.
Windows VST2
VST2 files can be installed to a custom folder. In Live’s Preferences or Settings, enable the custom VST2 folder and point it to the exact folder containing the plugin .dll files.
macOS VST3 and Audio Units
These formats normally use standard macOS system or user Library folders. Enable the corresponding VST3 or Audio Units option in Live.
- Do not place VST2 files inside the VST3 folder.
- Do not place unrelated system DLLs in a VST2 folder.
- Avoid cloud-synced or network folders for active plugins.
- Use the plugin vendor’s installer rather than moving a standalone app into a plugin folder.
See exact paths in the audio plugin install locations guide.
How to rescan plugins in Ableton Live
Open Live’s Preferences or Settings and go to the Plug-ins section. Confirm that the relevant format and custom folder options are enabled.
- Turn the affected plugin-folder option off, wait, then turn it on again.
- Use the Rescan button after correcting paths or reinstalling the plugin.
- Hold the modifier key documented by Ableton while clicking Rescan when you need a deeper full rescan in versions that support that behavior.
- Watch Live’s status area and allow indexing to finish before searching again.
In Live 12.1 and later, plugin scan information is stored in a separate plugin database. Ableton documents resetting the database when missing plugins persist after compatibility, installation, and path issues have been ruled out.
Advanced fixes when the plugin is still missing
Check Live’s scan logs and crash behavior
A single outdated or incompatible plugin can interrupt scanning. Update suspect products, temporarily remove the failing plugin from its folder, and rescan.
Reset Live’s plugin database
Follow Ableton’s official database-reset instructions for your Live version. Back up files before deleting or renaming any database item.
Check Windows security software
Windows Defender or third-party antivirus software can block installers or plugin-folder access. Review quarantine and controlled-folder settings.
Check macOS security and architecture
Make sure the plugin is properly signed, supported on the current macOS version, and compatible with the way Live is running on Apple Silicon.
Reinstall with the vendor manager
Use Waves Central, Native Access, Arturia Software Center, UA Connect, Plugin Alliance Installation Manager, or the vendor’s official installer. Do not rely on copied binaries.
When this happened after moving computers, use the complete plugin migration guide and compare the new inventory against the old one with FX Recall.
Official resources
Related FX Recall guides
Move Ableton Live to a new computer Audio plugin install locations
Frequently asked questions
Why is my VST3 not showing in Ableton Live?
The usual causes are an unsupported or 32-bit build, a failed installation, disabled VST3 support, an interrupted scan, or Apple Silicon incompatibility.
Where are plugins in Ableton Live 12?
Open the Browser and use the Plug-ins area or relevant filters. The available organization can differ from earlier Live versions.
Can Ableton Live use 32-bit plugins?
Current Live versions support 64-bit plugins only. A 32-bit plugin will not appear without an unsupported third-party bridging workflow.
Why does the standalone app work but not the plugin?
The standalone application is separate from the VST, VST3, or AU component. Re-run the installer and make sure the plugin format is selected.
Do not rebuild your plugin library from memory.
Scan your old computer with FX Recall, save a cloud-synced inventory, and track what still needs to be installed on the new machine.