How to install CLAP plugins on Windows

The reliable Windows installation is:

1. download the plugin from its developer or an authorized store;
2. run the supplied installer;
3. keep the standard CLAP destination;
4. open your DAW’s plugin manager and scan;
5. load the plugin, save a test project and reopen it.

The standard system-wide CLAP folder is:

C:\Program Files\Common Files\CLAP\

Image-Line documents this location for FL Studio, and it is the expected Windows system folder used by CLAP installers. You normally should not need to move files manually.

Before installing

Confirm four things on the official product page:

• the plugin supports Windows;
• its architecture matches your 64-bit host;
• the download actually includes a CLAP build;
• your DAW version supports CLAP.

A .clap file cannot load in a host that does not implement the format. If you are new to the terminology, read what a CLAP audio plugin is.

Step 1: use the official download

Download from the developer, your customer account or an authorized distributor. Avoid re-hosted installers. Keep the installer for the version used in important projects, especially when collaborating or archiving a session.

If Windows displays publisher or security information, read it rather than disabling protection globally.

Step 2: run the installer

When the installer offers formats, select CLAP. Keep the default CLAP destination unless the developer documents another supported setup.

For a manual distribution with no installer, place the complete .clap file or bundle in:

C:\Program Files\Common Files\CLAP\

Administrative permission may be required because this is under Program Files. Do not rename a .dll or .vst3 file to .clap; a developer must compile the actual CLAP interface.

Step 3: scan in FL Studio

Image-Line’s current workflow is:

1. open Options → Manage plugins;
2. choose Find installed plugins;
3. enable Verify plugins for a complete classification scan;
4. enable Rescan previously verified plugins when updating or troubleshooting;
5. wait for the scan, then favorite the plugin if you want it in the regular add menus.

CLAP support was introduced in FL Studio 2024.1. If you use an older version, update to a current supported release before troubleshooting the plugin.

Step 4: scan in REAPER

REAPER officially supports CLAP. Open Options → Preferences → Plug-ins and use the CLAP path/rescan controls documented by REAPER. Confirm that the standard CLAP location is included, then rescan.

After discovery, create a track and open the FX browser. Search the product name and verify that you are choosing the CLAP build when several formats are installed.

Step 5: scan in Bitwig Studio

Bitwig Studio supports CLAP alongside VST formats. Open its plug-in settings, confirm the relevant locations and ask Bitwig to rescan if the plugin has not appeared automatically.

Bitwig can prefer CLAP when it matches CLAP and VST versions of the same product. Still check the format shown in the browser before committing an important project.

If the CLAP plugin does not appear

Work through this order:

1. Check the host version

Confirm that the exact DAW version supports CLAP. “My DAW supports plugins” does not necessarily mean it supports this format.

2. Check the file location

Look under:

C:\Program Files\Common Files\CLAP\

Do not place the CLAP build inside Common Files\VST3 or an old VST2 folder.

3. Restart and run a full rescan

Close and reopen the DAW after installation. Use its complete scan rather than only a fast database refresh. In FL Studio, select Verify plugins and the options to rescan verified or errored plugins.

4. Check 64-bit compatibility

A modern 64-bit DAW needs a compatible plugin build. If the developer lists only another operating system or architecture, rescanning cannot fix it.

5. Remove unintended duplicates

Several copies of different versions can make diagnosis confusing. Keep the supported build in the documented location. Do not delete files if an older project may rely on them; archive the installer and establish which version the session needs first.

6. Check security and logs

Security software may quarantine an unfamiliar binary. Review the detection and verify the source rather than creating a broad exception. Your DAW’s plugin scan log may name a missing dependency or failed initialization.

7. Test a known current plugin

If no CLAP plugin appears, test another current CLAP build. If one works and one fails, the issue is likely product-specific. If neither appears, focus on the host version, path and scan configuration.

Test state before real work

Discovery is only the first check. Load the plugin, change controls, add automation, save the project, close the DAW and reopen it. Confirm that sound, state, automation and reported latency return correctly.

When moving a project to another computer, install the same plugin version in the same format. FL Studio’s project-sharing guidance specifically recommends matching plugin formats and using verified scanning.

CLAP or VST3 after installation?

Neither format inherently sounds better. Use CLAP when your host and plugin support it well or when you need its specific features. Use VST3 when another host or collaborator requires it. See the full CLAP vs VST3 comparison.

The Spectral Colors compatibility guide maintains the supported operating systems, host evidence and troubleshooting path for the current Windows CLAP plugin catalog.