To install plugins in Reaper, run the plugin’s installer (or copy the plugin file into a known folder), tell Reaper where that folder is in Preferences, rescan, and the plugin appears in the FX browser. This works for VST, VST3, AU on macOS, and Reaper’s built-in JS effects.
Knowing how to install plugins in Reaper unlocks third-party EQs, compressors, reverbs and instruments beyond Reaper’s stock set. Here is the reliable way to do it on both Windows and macOS.
Step 1: Run the plugin installer
Most commercial plugins ship with an installer. Run it and, when asked, note or set the VST install folder — write down that path. On Windows, plugins are typically .dll (VST2) or live in a VST3 folder. On macOS, formats include VST3 and AU (Audio Unit) components, which install to the system Components and VST3 folders automatically. Free plugins sometimes come as a loose file you copy yourself into your VST folder.
Step 2: Tell Reaper where your plugins live
Open Reaper’s Preferences and go to Plug-ins > VST. You will see a list of VST paths. Click Edit/Add path and make sure the folder where your plugins installed is in that list. If you keep your own VST2 plugins in a custom folder, add it here so Reaper knows to look there. AU plugins on macOS are found automatically from the system Components folder, so you usually do not add a path for them.
Step 3: Rescan so Reaper finds the new plugins
Still on the VST preferences page, click “Re-scan” (or “Clear cache/re-scan”). Reaper scans the folders and adds any new plugins it finds. A full clear-and-rescan helps if a plugin was updated or moved and is not showing up. Close Preferences when it finishes.
Step 4: Load the plugin on a track
Click the FX button on any track to open the FX chain, then click Add. Use the search box at the top of the plugin browser and type part of the plugin’s name. Filter by category (VST, VST3, AU, JS, Instruments) on the left if the list is long. Double-click the plugin to add it to the chain. The plugin’s interface opens so you can start dialling it in.
If you are loading EQ and compression, our primer on EQ and compression fundamentals helps you set them with intent rather than guessing.
Understanding the plugin formats
Reaper is unusually format-friendly, which is a big part of why it scans so much gear without fuss. It helps to know what each format is so you install the right build for your system — if the whole idea of a plugin format is new to you, that explainer covers the basics:
- VST2: the long-standing standard. On Windows these are usually loose .dll files that live wherever you point Reaper, which is why the VST path list matters most for this format.
- VST3: the newer standard with a fixed install location that installers handle for you. You rarely need to add a path manually for VST3.
- AU (Audio Unit): macOS only, installed to the system Components folder and detected automatically. Good to have enabled if you also run other Mac DAWs that prefer AU. If you are unsure which build to grab on a Mac, our breakdown of VST vs AU plugins explains when each one matters.
- JS (JesuSonic): Reaper’s own scriptable effects. They are already inside Reaper, so there is nothing to install — just search the FX browser and filter to JS.
When a plugin offers more than one build, pick one and stay consistent. Loading both the VST2 and VST3 version of the same plugin clutters your browser and gains you nothing.
How to keep your plugin folder organised
A tidy install habit saves hours later. Decide on one custom VST2 folder up front — for example a single “VSTPlugins” folder — and point every installer at it rather than letting each one scatter files around. Add that one folder to Reaper’s path list and you will almost never chase a missing plugin again. Keep your installers and licence files in a backup location too, because reinstalling after a system move is far quicker when you are not hunting for downloads.
It is also worth scanning in small batches when you add several plugins at once. If something goes wrong, a smaller batch makes it obvious which plugin caused the problem.
Common mistakes to avoid
- Installing to a folder Reaper never scans: the installer’s default path and Reaper’s path list must agree. If in doubt, set both to the same custom folder.
- Skipping the rescan: Reaper will not show a new plugin until it scans the folder again. This is the single most common reason a freshly installed plugin seems to be “missing”.
- Mixing 32-bit and 64-bit: modern Reaper is 64-bit and will ignore 32-bit-only plugins. Always download the 64-bit build where one exists.
- Ignoring the activation step: many paid plugins install fine but stay silent or show a nag screen until you authorise the licence. Complete the maker’s activation before assuming the install failed.
If a plugin won’t appear
- Wrong architecture: a 32-bit-only plugin will not load in modern 64-bit Reaper. Use the 64-bit version.
- Path not added: the install folder is not in Reaper’s VST path list — add it and rescan.
- Format mismatch: on macOS, check whether you installed the VST3 or AU build and make sure the matching scan is enabled.
- Blocked scan: some plugins are slow to scan; let the scan finish fully before judging.
Once your effects are in, you might want to keep CPU under control on busy projects — see how to freeze tracks in a DAW. And if you are routing plugin-heavy reverbs and delays efficiently, setting up sends and returns in a DAW is worth a read. The same path-and-rescan logic applies in other hosts too, so the general guide to how to install VST plugins is handy if you switch DAWs.
Frequently asked questions
Does Reaper support VST3 and AU plugins?
Yes. Reaper supports VST2, VST3, and Reaper’s own JS effects on all platforms, plus AU (Audio Unit) plugins on macOS. Enable the formats you use in the Plug-ins preferences and rescan.
Where should I install plugins so Reaper finds them?
Install to the standard VST3 folder (handled by most installers) or to a custom VST2 folder that you have added to Reaper’s VST path list. After installing, run a re-scan in Preferences > Plug-ins > VST.
Why does my new plugin not show up after installing?
Usually the folder is not in Reaper’s path list, you need to rescan, or the plugin format is not enabled. Confirm the path, run a clear-cache rescan, and check you installed the 64-bit build.
Do I need to restart Reaper after installing a plugin?
Not usually. A rescan in Preferences is normally enough to make a new plugin appear in the FX browser. A restart only helps in rare cases where a plugin’s installer has changed system files or registered components that Reaper reads at start-up.
