OBS Studio · Practical guide

VST Plugin Missing in OBS: Check Format Before Reinstalling

Distinguish VST2 from unsupported plugin formats, check the documented search location, and test one audio plugin without rebuilding the whole chain.

START HERE

OBS’s built-in VST filter supports many VST2.x plugins, not VST3, MIDI instruments or shell plugins. Confirm the plugin format, installation location and compatibility before expecting it in the selector.

Distinguish VST2 from unsupported plugin formats, check the documented search location, and test one audio plugin without rebuilding the whole chain.

In this guide
Before you start
  • The plugin’s official installer or format information.
  • A backed-up OBS configuration and one test audio source.

A plugin installed in a music app may not be usable in OBS

Many audio products offer several formats under the same product name. A working VST3 instance in an editor does not establish that OBS can load it through its built-in VST2 filter. Start by checking exactly which format the installer placed on the machine.

The OBS VST guide documents support for many VST2.x plugins and excludes VST1, VST3, MIDI input/control and shell plugins. It also warns that not every plugin has been tested and that some can crash. Treat format support and actual compatibility as separate checks.

Use the vendor’s installation choices deliberately

Read the official installer options and the plugin’s platform support. If a VST2 build is provided, select the appropriate build for the OBS environment and note its destination. Do not rename a VST3 file to another extension or copy random binaries from an unofficial download site.

Keep your existing audio chain unchanged while establishing discovery. Save its settings first and use a test source if possible. A missing plugin should not become a reason to replace every filter or reset the whole OBS configuration.

Check format, search path and one instance

  1. Confirm a supported format

    Identify the installed VST2 component rather than assuming every edition of the product includes one. If only VST3 is supplied, stop expecting the built-in VST2 filter to list it.

    Look for: You know whether the plugin format meets the documented OBS requirement.

  2. Compare the installation path

    Check the VST2 location against the platform’s search directories in the OBS guide. For example, Windows lists Common Files/VST2 and VSTPlugins locations; macOS lists the system and user Audio/Plug-Ins/VST folders.

    Look for: The supported component is in a location OBS is documented to search.

  3. Test one filter instance

    After installation and a fresh OBS launch, add VST 2.x Plugin to the test source, select the plugin and make a short recording with it bypassed and enabled.

    Look for: Discovery, loading and audible processing are verified as separate stages.

Describe whether the failure is discovery or processing

If the plugin is absent from the list, keep investigating format, path and compatibility. If it appears but crashes when opened, that is a loading or runtime failure. If it loads but sounds wrong, inspect its own settings and the signal level. These stages should not all be described as OBS does not support my audio.

Monitor the real workload after the plugin runs. A processor that behaves acceptably alone may add too much work when several sources and encoders are active. Keep a bypass comparison and remove the test instance if it makes the output unstable.

Keep the chain recoverable after updates

Record the plugin version, format and settings used in the successful sample. When updating it, preserve the previous working configuration through the vendor’s supported method. A product name in the filter list does not tell you whether its processing behavior stayed identical across versions.

If you need support, report the exact plugin format, platform, OBS version and stage of failure. Include a minimal reproduction and relevant log after reviewing it. That gives the developer something concrete to investigate without exposing your complete streaming setup or unrelated account details.

Still stuck?

The product works in a DAW but is missing in OBS.

Check which plugin format the DAW loaded; a VST3 installation does not satisfy OBS’s built-in VST2 filter requirement.

Keep troubleshooting

Check the model and connection before trying another change. The device page gathers the related symptoms.

More help with OBS Studio ↗

Sources & references

Based on the linked first-party OBS documentation checked on 4 November 2026. The exercises and acceptance checks are editorial workflows for you to run; no hands-on OBS session or hardware benchmark is claimed.

  1. OBS — VST 2.x Plugin Filter ↗Checked 2026-11-04

Spotted something out of date? Let Alex know.

How we put our guides together ↗
READ NEXT

A few places to go from here.

All stories

OBS Audio Filter Order: Hear What Each Stage Changes

Build a microphone chain around specific problems and retune thresholds after moving filters.

OBS Support Report Builder: Explain the Failure Before Sharing the Log

Draft a focused OBS help request with your setup, reproduction steps, expected result and checks already tried. Export it before sharing.