Validate My Plugin

✅

744 Plugins Validated!

Drop your zipped plugin here

Windows, macOS or Linux!
VST3 and Audio Unit only
Zip before uploading
macOS must be universal or x86_64

Plugins are transmitted securely to runners and deleted after each run.

Sponsored by

A public service from

Frequently asked questions

What is plugin validation? Who is this for?

This is a service for audio developers making plugins.

As an audio dev, you want your effect and instrument plugins to work on all DAWs and all platforms you support.

That turns out to be a tall order! Manually QAing each platform isn't time effective or reliable. Waiting for users to tell you which DAWs your plugin has trouble with is also a bad strategy.

Validation, on the other hand, bubbles potential issues up immediately. It ensures your plugin conforms to the VST3 and Audio Unit spec and can handle unexpected inputs and edge cases.

This service gives you a taste of what validation looks like. If you find it valuable, running pluginval in your CI pipeline is the most reliable way to ensure ongoing compatibility and reliability — freeing you up to worry about the actual hard stuff (like UI!).

Is this cross platform?

Yes! You can upload a zipped macOS, Windows or Linux plugin.

Can I see an example run?

Check out an example run here.

What exactly happens when I upload my plugin?

The zip is sent to our servers, where we verify it contains an audio plugin of a supported architecture. If it does, we forward it to a job runner on the appropriate platform.

The job runner then runs pluginval on the plugin, reporting back its status and logs and then deleting the plugin.

The logs are available at a secret url, and then can optionally be deleted.

So, should I just download pluginval?

Yes!

This site is just to give you a quick taste of plugin validation. To go deeper (and actually troubleshoot validation issues) you'll want to grab the latest pluginval release from GitHub and read more about pluginval over on Melatonin's blog.

Why won't my macOS plugin work?

We currently only have x86_64 runners running macOS. That means if you are compiling on an apple silicon machine you'll need to make sure you are compiling a universal binary.

If you use CMake, ensure you have something like this in your CMakeLists.txt:

set(CMAKE_OSX_ARCHITECTURES arm64 x86_64)

What pluginval 'strictness' does this service run?

It's currently running at strictness level 10. In addition to validating API compatability, this includes fuzz testing, and running Apple's auval on macOS.

I'm having trouble, who do I contact?

Please post the issue you are seeing on the official thread on the JUCE forum.