Need help with pluginval?
Click the “chat” button below for chat support from the developer who created it, or find similar developers for support.

About the developer

206 Stars 30 Forks GNU General Public License v3.0 193 Commits 12 Opened issues


Cross platform plugin testing and validation tool

Services available


Need anything else?

Contributors list


master: Build Status Build Status

develop: Build Status Build Status


pluginval is a cross-platform plugin validator and tester application. It is designed to be used by both plugin and host developers to ensure stability and compatibility between plugins and hosts.

If you are a plugin user looking to report a problem with a plugin to the developers, you can use

to create a detailed log which can drastically improve the time to fix issues. Please follow the instructions here to get started: Testing plugins with pluginval
  • Test VST/AU/VST3 plugins
  • Compatible with macOS/Windows/Linux
  • Run in GUI or headless mode
  • Validation is performed in a separate process to avoid crashing


Either grab one of the pre-compiled binaries from the Releases page or clone the repo and build from sources. The projects are generated by the Projucer so you may have to build that first to generate the various project files. The easiest way to do this is to run one of the build scripts in the

$ git clone --recurse-submodules
$ cd pluginval/install
$ ./mac_build
> git clone --recurse-submodules
> cd pluginval\install
> ./windows_build.bat

Third-party Installation

Chocolatey (Windows):
> choco install pluginval

You can find the chocolatey package of pluginval here, and the source of the chocolatey package here, currently maintained by Xav83.

N.B. Enabling VST2 Testing:

The VST2 SDK is no longer included in JUCE so VST2 support isn't available out from a fresh clone. To enable VST2 testing do one of the following: 1. Before running one of the

scripts, set the
environment variable to point to the VST2 source directory on your system. This will then modify the
file automatically. E.g.
$ git clone --recurse-submodules
$ cd pluginval/install
$ export VST2_SDK_DIR=~/SDKs/vstsdk2.4
$ ./mac_build
or ```shell

git clone --recurse-submodules cd pluginval\install set VST2SDKDIR=C:\SDKs\vstsdk2.4 ./windows_build.bat ```

  1. Manually open then
    , select the
    module and change the
    . Now you'll have to either have the VST2 SDK path in your Projucer Global Settings, or you'll need to add it to the
    Header Search Paths

Running in GUI Mode

Once the app has built for your platform it will be found in

. Simply open the app to start it in GUI mode. Once open, you'll be presented with an empty plugin list. Click "Options" to scan for plugins, making sure to add any directories required. Alternatively, you can drag a plugin file and drop it on the list to add only that plugin.

Once the list has populated, simply select a plugin and press the "Test Selected" button to validate it. The plugin will be loaded and each of the tests run in turn. Any output from the tests will be shown on the "Console" tab. If you find problems with a plugin, this can be useful to send to the plugin developers.

Running in Headless Mode

As well as being a GUI app,

can be run from the command line in a headless mode. This is great if you want to add validation as part of your CI process and be notified immediately if tests start failing.
Basic usage is as follows:
./pluginval --strictnessLevel 5 --validate 

This will run all the tests up to level 5 on the plugin at the specified path. Output will be fed to the console. If all the tests pass cleanly,

will return with an exit code of
. If any tests fail, the exit code will be
. This means you can check the exit code on your various CI and mark builds a failing if all tests don't pass.

is optional but can be between 1 & 10 with 5 being generally recognised as the lowest level for host compatibility. Lower levels are generally quick tests, mainly checking call coverage for crashes. Higher levels contain tests which take longer to run such as parameter fuzz tests and multiple state restoration.
You can also list all the options with:
./pluginval -h



If you would like to contribute to the project please do! It's very simple to add tests, simply: 1) Subclass

    struct FuzzParametersTest  : public PluginTest
2) Override
to perform any tests
    void runTest (UnitTest& ut, AudioPluginInstance& instance) override
3) Log passes or failures with the
    ut.expect (editor != nullptr, "Unable to create editor");
4) Register your test with a static instance of it in a cpp file:
   static FuzzParametersTest fuzzParametersTest;

If you have a case you would like tests, please simply write the test in a fork and create a pull request. The more tests the better!


Licensing is under the

as we want
to be as transparent as possible. If this conflicts with your requirements though please let us know and we can accommodate these.

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.