Installing a VST plugin should be straightforward: download a compatible version, install it into the correct location, and tell your digital audio workstation (DAW) to scan for it. The confusing part is that VST2, VST3, Audio Units (AU) and AAX are different plugin formats, and not every DAW supports all of them.
This updated guide walks through Windows, macOS, Ableton Live, FL Studio, Logic Pro and Pro Tools, with the actual system folders, common mistakes and fixes for plugins that do not appear. The most important rule is to choose the format supported by your DAW and follow the manufacturer’s installer rather than moving random files into a plugin folder.
Before you install: VST2, VST3, AU or AAX?
A plugin can be an instrument (such as a synthesizer or drum machine) or an audio effect (such as distortion, delay or EQ). Some manufacturers also provide a standalone application, but the standalone app is not necessarily the version your DAW loads.
- VST3: the modern VST format, commonly installed as a
.vst3file or bundle. Available in many Windows and Mac DAWs, including Ableton Live and FL Studio. - VST2: an older format. On Windows the plugin file is commonly
.dll; on macOS it is commonly a.vstbundle. Some DAWs still load supported VST2 plugins, but new installers may offer only VST3. - Audio Units (AU): Apple’s plugin format, commonly a
.componentbundle for AUv2 on macOS. Logic Pro loads Audio Units, not VST plugins directly. - AAX: the format used by current Pro Tools versions. Installing only a VST3 version does not make it available in Pro Tools.
Before downloading, confirm your operating-system version, processor architecture (Intel, Apple silicon or the relevant Windows architecture), DAW version and supported plugin formats. A 64-bit host cannot automatically load an obsolete 32-bit plugin. Different formats of the same product are not always interchangeable in saved DAW projects.
Where are VST plugins installed?
The following are common system plugin locations. Let a trusted manufacturer installer use its recommended location unless its instructions say otherwise.
| System / format | Typical installation folder |
|---|---|
| Windows VST3 | C:\Program Files\Common Files\VST3 |
| Windows VST2 (example) | C:\Program Files\Common Files\VST2 or another dedicated VST2 folder you selected |
| macOS VST3 | /Library/Audio/Plug-Ins/VST3 |
| macOS VST2 | /Library/Audio/Plug-Ins/VST |
| macOS Audio Units (AUv2) | /Library/Audio/Plug-Ins/Components |
Some macOS plugins install into the equivalent ~/Library/Audio/Plug-Ins/ folders for your user account. The tilde (~) refers to your home folder, not the system-wide Library. Open a path in Finder with Go → Go to Folder.
Do not put preset banks, sample packs, installers, ordinary DLL libraries or standalone executables in your VST3 system folder. Install sample libraries and presets in the locations specified by the developer. Keep VST2 and VST3 files in separate, appropriate folders. For platform-specific installation details, see Ableton’s Windows installation guide and macOS plugin locations.
How to install VST plugins on Windows
- Download from the developer. Choose a Windows installer that explicitly supports your Windows version and DAW. Verify whether you need VST3, VST2 or another format.
- Close the DAW before installing, unless the manufacturer explicitly instructs otherwise. If the download is an archive, extract it first and inspect its instructions.
- Run the manufacturer’s installer. Choose the plugin formats you actually need. Prefer the default VST3 system folder and use a consistent, separate VST2 location if installing VST2.
- Install any required content and authorise. Some products use a license manager, serial number or account sign-in. Sample libraries often have their own location.
- Restart your DAW and scan plugins. Enable the correct format or folder in the DAW’s settings, then find the instrument or effect under its plugin browser.
- Test an instance. Load the instrument on an appropriate instrument/MIDI track or add the effect to an audio track. Save and reopen a test project to check recall.
Do not assume that every Windows VST is a DLL: that applies to many VST2 plugins, while a VST3 commonly uses .vst3. If a downloaded DLL is not an audio plugin, copying it into your VST folder will not make it one.
How to install VST or Audio Units on macOS
- Check Mac compatibility. Identify whether your Mac uses Intel or Apple silicon, and whether the plugin provides a compatible native or universal build. Select AU, VST3 or VST2 based on your DAW.
- Download the official Mac installer. Open the developer’s
.pkgor the installer inside a.dmg, then follow its instructions. Some products use a developer-managed installation app instead. - Confirm the correct plugin format was installed. AU components and VST3 bundles go into different system locations. Do not rename a VST3 file to
.component; renaming does not convert plugin formats. - Open the DAW and enable the relevant plugin source. Allow it to finish scanning and any first-launch validation. Authorise the plugin using the developer’s supported method.
- Test the plugin in a project. If it will not load on Apple silicon, consult the developer about native builds and host compatibility before considering any Rosetta workaround.
On Apple silicon, compatibility is more specific than simply saying “Mac supported.” For example, Ableton says its native Universal build of Live 11.1 and later recognises VST plugins compiled for Apple silicon, although some Intel-only Audio Units can behave differently through macOS compatibility services. See Ableton’s Apple silicon guidance.
How to install VST plugins in Ableton Live
Ableton Live can host VST2 and VST3 plugins on supported Windows and macOS versions, plus Audio Units on macOS. Its plugin settings are under Settings/Preferences → Plug-Ins → Plug-In Sources in current versions; older releases may use a different tab.
- Install the plugin with its manufacturer installer, selecting the appropriate format.
- Open Live → Settings/Preferences → Plug-Ins and find the plugin sources section.
- For a normally installed VST3, enable Use VST3 Plug-In System Folder. For a custom-installed VST2, enable its dedicated custom folder and point Live to the actual VST2 location. On Mac, enable Audio Units when needed.
- Allow scanning to finish. Look under Plug-Ins in Live’s Browser and search for the plugin by name or developer.
- If it still does not appear, toggle the relevant source off and on. Ableton documents a deep rescan by holding Alt/Option while clicking Rescan.
For troubleshooting, use Ableton’s own missing-plugin checklist. Do not point both VST2 and VST3 custom sources at the same folder or assume a VST2 plugin and VST3 replacement will automatically recall each other’s project state.
How to add plugins in FL Studio
- Run the supported plugin installer for your system. If possible, use the standard VST3 system folder; choose a separate VST2 folder only when the installer requires it.
- In FL Studio open Options → File settings → Manage plugins, or navigate to the Plugin Manager through your version’s menus.
- Check the existing plugin search paths. Only add a custom path if the plugin was genuinely installed somewhere outside the standard locations.
- Click Find installed plugins. Use the available Verify plugins option if you want FL Studio to categorise effects and instruments appropriately.
- Locate the result in the plugin picker, Channel Rack or mixer effect slot according to the plugin type. Test a project and check that its settings recall.
Image-Line recommends avoiding unnecessary custom search paths and using the Plugin Manager to detect new devices. See the official FL Studio plugin installation manual. On Apple silicon Macs, check whether both FL Studio and the chosen plugin are running in a compatible mode.
How to install third-party plugins in Logic Pro
Logic Pro uses Audio Units rather than VST plugins. The old advice to add a VST folder in Logic was incorrect. If your plugin download provides both AU and VST3 versions, choose and install the AU version for Logic Pro.
- Download the official macOS installer with AU support, and check compatibility with your Logic Pro and macOS versions.
- Run the manufacturer installer. An AUv2 component is typically placed in
/Library/Audio/Plug-Ins/Components. AUv3 extensions can have a different app-based installation mechanism. - Restart Logic Pro and add the plugin through the Audio Units submenu in an instrument or audio-effect slot.
- If it is missing, open Logic Pro → Settings → Plug-In Manager. Check validation/enablement status and follow the supported rescan steps before altering system files.
Apple documents both third-party AU installation folders and how to troubleshoot Audio Units not showing in Logic. Installing only a VST3 build cannot make it show up in Logic’s AU menu.
And what about Pro Tools?
Modern Pro Tools uses 64-bit AAX plugins. Choose the manufacturer’s AAX installer or AAX option; a VST3-only install is not sufficient. Typical AAX locations are C:\Program Files\Common Files\Avid\Audio\Plug-Ins on Windows and /Library/Application Support/Avid/Audio/Plug-Ins on macOS. Avid documents the official Pro Tools plugin folder locations.
VST plugin not showing up? Troubleshoot in this order
- Confirm you installed the right format. Logic requires AU; Pro Tools requires AAX; the VST2 or VST3 plugin must be one your DAW actually supports.
- Confirm OS, CPU and host compatibility. Check 64-bit support and whether the developer supports your current Windows/macOS version and Apple silicon or other processor architecture.
- Check the installation location. Look in the real system or custom plugin folder, not your Downloads folder or a preset-bank directory.
- Complete activation. Some devices are hidden, disabled or cannot initialise properly until authorised or until required support software is installed.
- Run the DAW’s scan/validation tool. In Ableton, try enabling the correct plugin source and a deep rescan. In FL Studio, use Plugin Manager; in Logic, use Plug-In Manager.
- Restart and test a blank project. This isolates the problem from an existing session, duplicate plugin versions or a project-specific crash.
- Reinstall from the vendor if needed. Do not copy random DLLs, delete system plugin folders or disable macOS security as a first troubleshooting step. Check the vendor’s release notes and contact support with the exact plugin, DAW, OS and CPU versions.
If you are moving between computers, reinstall and authorise plugins through their official installers. Copying only the plugin binary may leave behind required support files, licensing services, presets or samples. To preserve an old project, keep track of the exact plugin format and version it originally used.
Where to find compatible techno instruments and effects
Once your host is configured, use Underground Talent’s VST Plugins Discovery directory to browse 50 source-linked instruments, drum machines and effects by category and developer. Its platform filters are based on published manufacturer information, but a supported operating system does not guarantee compatibility with every individual DAW.
If you are loading a preset bank rather than installing a new plugin, start with the correct parent instrument and check its own preset import workflow. Our Presets Discovery directory lists the exact target synth for each bank. For more practical production ideas, explore our techno music production guide and sound-design resources.
Final checklist: download the correct vendor installer, choose the host-supported format, use the proper installation folder, authorise if required, scan/validate in your DAW and test project recall. The right installation depends on the plugin and your specific software versions, not a one-size-fits-all “Add Folder” button.
Editorial update: November 2026. Technical instructions cross-checked against documentation from Ableton, Image-Line, Apple and Avid. Menu names and supported operating systems may change with future software versions.







