How to install plugins in Ableton, FL Studio and Logic (macOS and Windows).

The weak link in plugin installation is the folder, rather than the plugin. The installer writes where the system allows it, the DAW scans where you told it to, and if the two paths do not match, the plugin exists on disk but never appears in the menu.

This guide gives paths by DAW and system, explains rescanning and permissions, and finishes with the operation that causes the most anxiety but carries the least risk when done correctly: moving large libraries to another drive.

Where each plugin goes in each DAW

Before installing anything, three concepts: the installer copies the file and registers whatever is needed; the default folder is where the DAW looks by default; and enabling is the step in which you tell the DAW to scan that folder. The table summarises the destination in each case.

If you arrived here unsure about formats, recall this before installing: Plugin formats explains which applies to your system.

Installing plugins on Windows

On Windows, the short route is to let the installer work: run it, choose the target DAW if asked, and accept the default path, almost always C:\Program Files\Common Files\VST3. Two warnings:

• Administrator permissions. Installing in C:\Program Files requires elevation; if you launch without permissions, it may finish without copying anything or warning you.
• Do not mix formats. VST2 .dll files go in one folder and .vst3 files in another; the Ableton manual explicitly recommends not pointing both folders to the same location.
• Permissions and antivirus. If the system denies writes to C:\Program Files, or antivirus isolates the newly copied file, installation ends without an apparent warning. Check the destination folder immediately after installation: if the .vst3 is absent, no scan will find it.

Installing VST in Ableton

Open Preferences > Plug-Ins and enable sources: on Windows, enable the custom VST2 folder with its path and the VST3 system folder. Then press Rescan. If properly installed, the plugin appears in the browser’s Plug-Ins group, separated into instruments and effects.

Installing VST in FL Studio

FL Studio searches several default paths and accepts extra paths through Plugin Manager (Options > File settings > Manage plugins). Three practices from Image-Line’s manual save problems:

1. Enable Verify plugins: quick scanning identifies plugins by filename and misses any renamed plugin; verification registers unique codes.
2. Never install in FL Studio’s installation folder, intended for old native plugins.
3. If the plugin does not appear, select Rescan previously verified plugins and Rescan plugins with errors.

Installing plugins on macOS

Mac has two families of folders: system folders in /Library/Audio/Plug-Ins/ (VST, VST3, Components, CLAP), and user folders in ~/Library/Audio/Plug-Ins/, which are also hidden by default. Installers usually request administrator permission to write to the system folder; that is normal.

Practical rules:

• Install in the format’s default folder. A VST3 in /Library/Audio/Plug-Ins/VST3 and an Audio Unit in /Library/Audio/Plug-Ins/Components.
• One folder per format. Mixing VST and VST3 in the same directory causes failed cross-reading.
• Completely restart the DAW after installation. Hosts do not reload their component lists while open.

Installing AU in Logic

Logic does not read VST: it reads Audio Units. After installing the .component in /Library/Audio/Plug-Ins/Components, go to Logic Pro > Settings > Plug-in Manager and check the compatibility column. If the plugin is marked incompatible or does not appear, use Reset & Rescan Selection on it, or reset all Audio Units if the scan stopped halfway through. Apple also documents that, if a newly installed plugin does not appear, first restart the Mac and confirm that the plugin is 64-bit.

Third-generation Audio Units (AUv3) are installed as applications and appear in the same menu with the corresponding version identifier.

Scanning, permissions and rescanning

Rescanning is the process’s most misunderstood operation. General guidance:

1. Normal rescan after installing a new plugin.
2. Deep rescan if it does not appear: in Live, hold Alt or Option while pressing Rescan; in FL Studio, use Verify plugins with error rescanning; in Logic, rescan the selection in Plug-in Manager.
3. One plugin at a time. If a mass scan fails, identify the culprit by disabling folders in sections.
4. Do not scan while the plugin is in use. Close the DAW before installing or moving files.

The detail causing half the scares: the DAW remembers plugins that failed. Until you force a rescan, it will not try again, so reinstalling without scanning fixes nothing.

One more point about that memory: each DAW keeps its own index of what it scanned, retaining old names when you move or rename a plugin. You then see ghost entries in the browser, or the correct plugin missing despite its file being in place. In those cases, the answer is rebuilding the index rather than reinstalling: reset the DAW’s plugin database and rescan only authorised folders. A clean index avoids half the wrong diagnoses, because the catalogue forgetting something does not mean the file is broken.

Moving libraries to another drive

Sample libraries weigh hundreds of gigabytes and need not live on the system drive. The safe operation has three steps: move, link, rescan.

• In Ableton, the manual allows an alias of the plugin folder placed in the custom VST folder or the system folder on Mac: Live scans the folder and its aliases, letting you point to an external drive without changing anything else. For samples, move the library and mark its location again in the browser’s Places.
• In FL Studio, add the new location as an extra search path in Plugin Manager and use browser search folders for samples.
• In Logic, Audio Units have no configurable path: move the folder and leave a symbolic link in /Library/Audio/Plug-Ins/Components pointing to the new drive, so the system keeps finding them.

Precautions: move nothing while the DAW is open, do not rename the destination after the first scan, and check that the external drive is mounted before opening a project. If the drive does not appear, the DAW will see plugins but not samples.

Final check before opening a project

Closing checklist:

1. The plugin appears in the browser with its correct name, separated into instruments and effects.
2. It can be instantiated on a track and its interface opens.
3. After restarting the DAW, it still appears.
4. Enabled folders do not overlap between formats.
5. External libraries are in place and the drive is connected.

If step 4 or 5 fails, return to the paths section: it is almost always a wrongly chosen folder, rather than a faulty plugin.

One rule prevents repeating the whole process: install one at a time and check as soon as each plugin enters the browser. If the next fails, you will know exactly what changed, rather than examining fifteen recent installations blindly.

Next step

With plugins in place, the next improvement comes from working better rather than installing more: templates, naming conventions, versioning, freeze and bounce so a project can grow without breaking. That workflow is in Production workflow: templates, versioning, freeze and bounce.