Syntho

Testing your VST

Load a built VST3 in a plugin host and check its audio, controls, MIDI, and state.

A VST is a plugin, so it needs a host to provide audio or MIDI input and route the processed signal to an output. This page uses VST3 examples; for another plugin format, choose a host that supports that format.

Start with the Steinberg test host

For a VST3 plugin, the smallest developer-oriented host is Steinberg's VST 3 Plug-in Test Host. It is included with the VST3 SDK and can load a plugin, simulate audio and note events, open the plugin editor, load presets, and run VST3 conformity tests.

Get the test host

Steinberg does not publish VST3PluginTestHost as a separate app download. It is bundled with the full VST3 SDK archive. Use Steinberg's SDK download page or its direct SDK ZIP link, then open VST3PluginTestHost.app (macOS) or VST3PluginTestHost.exe (Windows) from the extracted SDK's bin directory. The SDK links page confirms that the full ZIP includes the test host while the GitHub repository does not.

Build the plugin first:

pnpm build:vst3

Then open VST3PluginTestHost from the SDK's bin directory and load the plugin. Use the host's audio input for an effect, or its event input for an instrument. An audio file, a generated signal, or a MIDI pattern is enough for the first check.

Open View → Open Plug-in Unit Tests Window and run the conformity tests. Treat failures as host-compatibility issues to investigate before testing the plugin in a DAW.

Other hosts

The official test host is useful for VST3 behavior and conformance. Also test in at least one general-purpose host, because hosts differ in buffer sizes, sample rates, automation, MIDI routing, and editor lifetime:

  • REAPER is a practical DAW host for audio, MIDI, automation, and recording checks.
  • Kushview Element is a standalone plugin host for quickly wiring VST3 effects and instruments.

A short smoke test

  1. Load the plugin at 44.1 kHz and 48 kHz.
  2. For an effect, send silence, a sine wave, and a short audio file through it.
  3. For an instrument, send note-on and note-off events across a few octaves.
  4. Move every parameter through its minimum, default, and maximum values.
  5. Bypass and re-enable the plugin, then close and reopen its editor.
  6. Save and restore a preset or host session.
  7. Repeat the check with several buffer sizes if the host allows it.

Listen for silence, clicks, clipping, stuck notes, incorrect channel routing, and parameters that do not persist. Host testing complements the project's offline render and audio-quality checks; it does not replace them.