CLAP Plugin Format Explained: What It Is and Who Supports It

What is the CLAP plugin format?

CLAP is a plugin format, like VST3 or AU, that defines how a DAW and a synth or effect talk to each other. The official site describes it as an audio plug-in ABI that "defines a standard for Digital Audio Workstations and audio plug-ins (synthesizers, audio effects, …) to work together"^[1].

What makes it different is who owns it and what it was designed for. u-he states that CLAP is open source under the MIT license, so no fees, memberships or proprietary agreements are required to build a CLAP host or plugin^[2]. For you as a producer, a CLAP plugin shows up in a supporting DAW as one more format option, usually next to the VST3 version of the same plugin. If you want the broader overview of every format first, start with plugin formats explained: VST, AU and AAX; the rest of this page stays on CLAP.

Who created CLAP and when?

CLAP started as a side project and became an industry standard when Bitwig and u-he backed it. The CLAP team's own history gives the timeline below^[3], and Bitwig published the joint announcement on June 15, 2022^[4].

What does CLAP do that VST3 and AU don't?

CLAP's headline features are richer modulation, smarter use of CPU cores, and faster plugin scanning. Some of these ideas exist in other formats in some form, but CLAP puts them in the core design. Here is what u-he and the CLAP specification list^[2].

• Polyphonic modulation Polyphonic plugins can have per-voice parameters modulated for individual notes, which u-he calls "MPE on steroids". In a CLAP-aware DAW, one LFO can move a filter differently for every note in a chord.
• Non-destructive modulation Parameter modulation applies a temporary offset. When the modulation ends, the parameter returns to its original value, so automation and modulation don't overwrite each other.
• Per-note automation CLAP supports per-note automation and modulation in line with the MIDI 2.0 specifications, and plugins can send and receive MIDI on multiple ports.
• Thread pool Host and plugin can share CPU cores through a "thread-pool", so the DAW manages threading even for plugins that do their own multicore processing.
• Faster scanning Hosts can read plugin metadata without waiting for each plugin to initialize, which speeds up plugin scans.
• Extensions Features are added as extensions. The specification repository lists ones for state, parameters, latency, voice info, remote controls and preset discovery, which lets a host index a plugin's presets in their native format^[5].

The licensing gap has narrowed

Early coverage often framed CLAP as the open alternative to a proprietary VST3. That changed in late 2025: Steinberg's developer portal states that since version 3.8, VST 3 is licensed under the MIT license, with no fees or memberships required^[6]. Licensing is no longer the main difference. The case for CLAP now rests on its modulation model, threading and simpler design.

Which DAWs support CLAP plugins?

Bitwig Studio, Reaper, FL Studio and Studio One Pro are the best-known DAWs with CLAP support. The CLAP Audio Software Database, which the CLAP team calls the most up-to-date source^[7], lists these hosts with the first version known to support CLAP^[8].

If your DAW isn't on that list, assume it doesn't load .clap files and check its manual. Ableton's own plug-in documentation for Live on Mac covers VST2, VST3 and AU^[11], and Logic Pro loads Audio Units. In those DAWs, use the VST3 or AU build of the same plugin.

CLAP vs VST3 vs AU at a glance

For most producers the deciding factor is simple: use the format your DAW supports best, and choose CLAP when your DAW supports it and you want its modulation features. The table compares the points that matter day to day.

The CLAP folder paths come from the specification's entry header, which also lists user-level folders and a CLAP_PATH environment variable that hosts must check^[13]. For VST3 and AU paths on both systems, see where VST plugins are stored.

How do you install and use CLAP plugins?

Install the .clap file into the standard CLAP folder, rescan in your DAW, and pick the CLAP entry from the plugin list. Most installers that include CLAP handle the folder for you.

1. Confirm your DAW supports CLAP
   Check the host table above or your DAW's release notes. An unsupported DAW simply won't list .clap files.
2. Run the installer and tick CLAP
   Many installers let you choose formats. If you install manually, copy the file to /Library/Audio/Plug-Ins/CLAP on a Mac or %COMMONPROGRAMFILES%\CLAP on Windows^[13].
3. Rescan plugins
   Use your DAW's plugin manager to scan for new plugins. If nothing appears, follow the plugin not showing up checklist.
4. Choose one format per plugin
   When a plugin appears as both CLAP and VST3, pick one and stick with it in your template. A project saves the specific format you inserted, so switching later means re-inserting and re-dialing settings.
5. Try the modulation features
   In a host with CLAP polyphonic modulation, such as Bitwig, modulate a CLAP synth's filter and play a chord to hear each voice move on its own. That per-voice movement is the main reason to pick the CLAP build.

Should you use CLAP versions of your plugins?

Use CLAP when your DAW supports it, you work mostly alone, and the plugin's CLAP build offers something you'll use. Stick with VST3 or AU when you share projects with people on other DAWs, because a session with CLAP instances won't open correctly on a machine or DAW without CLAP.

Free CLAP plugins make testing easy. Surge XT, the open-source synth, lists CLAP alongside VST3 and AU, running on Windows, macOS on Intel and Apple Silicon, and Linux^[14]. The CLAP database also lists commercial releases such as FabFilter Pro-Q 4 from version 4.0 onward. On a Mac, check that whatever you install is Apple Silicon native too; the Apple Silicon plugin compatibility guide shows how. And for installers that don't include CLAP, the plugin install guide covers VST3 and AU placement.