OBS’s built-in audio filter supports VST 2.x plug-ins, not VST3. To use an effect in OBS, install a compatible VST2 build, add the VST 2.x Plugin filter to the audio source you want to change, then test the sound and levels before going live.
The format is the first thing to check if a plug-in is missing: a VST3-only effect will not appear in the built-in filter’s selector. The rest of the setup is straightforward, but a plug-in can still be unsuitable if it is built for a different operating system or architecture, or makes OBS unstable.
Check the format before choosing a plug-in
OBS documents a built-in VST 2.x Plugin audio filter for Windows, macOS and Linux. Its VST 2.x Plugin Filter documentation says OBS does not support VST1.x, VST3.x, MIDI control or input in VST plug-ins, or shell VST plug-ins. These are limits of this filter, not a claim that every other audio application has the same limits.
That distinction matters when you search for effects. Many plug-in makers offer more than one format, while some offer only VST3. Check the product page or installer for an explicit VST2 option before downloading. The words “VST plug-in” on their own do not tell you which generation the plug-in uses.
Format is only one part of compatibility. The plug-in must also have a build for your operating system and architecture. An effect that runs on Windows does not automatically run on a Mac or Linux system, and a 64-bit host needs a compatible build. Use the vendor’s installation instructions rather than copying a file into a directory at random.
If your effect is VST3-only, OBS’s built-in filter is not the route for it. A separate host or routing arrangement may be possible, but it introduces another place for audio to fail or become difficult to monitor. Verify that workflow against current documentation for the host, plug-in and OBS version you use; there is no universal bridge recommendation here.
For a streamer who only needs basic voice processing, it is often simpler to start with one effect that has a documented VST2 build than to build a more elaborate routing chain. If your stream is mainly a continuous music or ambience file, consider whether live voice processing is needed at all. A discussion of the broader 24/7 YouTube channel setup choices can help distinguish a live microphone setup from a file-based channel.
Choose an effect for a specific problem
Choose the job before choosing the plug-in. An equaliser (EQ) changes tonal balance; compression controls the difference between quieter and louder parts; a gate can reduce low-level room noise between phrases; and a denoising tool targets noise. Each can also make the sound worse when used unnecessarily or too strongly.
A restrained starting chain for speech might use corrective EQ followed by gentle compression. Add a gate or noise processor only if the room noise is noticeable and the effect does not cut off the beginnings or endings of words. There is no one setting that suits every microphone, room or speaking voice. Listen to your own recording and adjust for intelligibility rather than copying values from someone else’s setup.
OBS identifies REAPER ReaPlugs and Melda Production among the plug-ins used during development and testing of its VST support. That is useful evidence that the projects were considered in OBS testing, not a guarantee that every product, version or system combination will work for you. Check each effect’s format and platform support before installing it.
Cockos describes ReaPlugs as a free VST FX suite. Its ReaPlugs page lists Windows VST 2.36 installers in 32-bit and 64-bit builds, dated 2 January 2016, and includes ReaEQ, ReaComp, ReaGate and ReaFIR. Treat those platform and date details as stated on Cockos’s page; do not assume it provides a current Mac or Linux installer. A suitable Windows build may be a practical way to try basic processing without buying a plug-in, but it still needs to be tested in your setup.
| Processing need | What the effect changes | What to listen for |
|---|---|---|
| EQ | The balance of tones in the voice | Speech should remain natural and clear, not thin or harsh |
| Compression | The difference between quieter and louder speech | Words should be more consistent without sounding pushed down or unnaturally loud |
| Gate | Low-level sound when you are not speaking | Room noise may reduce between phrases, but word beginnings should remain intact |
| Denoising | Background noise in the input | Noise may reduce, but listen for artifacts or changes to the voice |
The best choice is the lightest processing that solves a real problem. A plug-in can sound impressive in a demonstration and still be a poor fit for your microphone, room or speaking distance. Make changes one at a time so you can tell whether the effect helped.
Add the VST filter in OBS
First add your microphone or other audio input to OBS and confirm that its mixer meter responds. If the source is not present or its meter does not move, solve that before adding a plug-in. A filter cannot process a source OBS has not captured.
Install the VST2 plug-in using the vendor’s instructions, then check whether OBS can discover it. OBS scans documented plug-in directories; its VST filter guide lists locations for Windows, macOS and Linux. On Linux, check whether the VST_PATH environment variable is set: if it is, OBS uses the paths specified by that variable instead of the other scan locations.
Open the Filters dialog for the source you want to process. Add VST 2.x Plugin in the audio filters section, then select the installed plug-in from the filter’s selector. The filter behaves much like another source audio filter. Follow the plug-in’s own instructions to open its controls, if needed, and save your OBS settings before experimenting.
The sequence is deliberately short: confirm the source, confirm VST2 and the correct build, install, add the filter, choose the effect, then listen. If you are moving between a microphone and desktop audio, remember that filters apply to their own source. A microphone filter will not change the sound of a separate game, music or browser source.
Keep a note or backup of settings before making changes. OBS warns that some plug-ins can crash and that some can use a great deal of CPU. If a problem begins after adding an effect, you want to be able to remove that effect or restore the previous configuration rather than rebuild the entire scene collection.
Put processing on the audio source that needs it
Think of OBS sources as separate paths into the mixer. Put voice processing on the microphone source. Put processing for a music input on that music source. A filter on one path does not automatically affect every sound that OBS sends to the stream.
This makes source choice a useful first diagnostic. If your voice still sounds unchanged, check that you added the filter to the active microphone, not to desktop audio or another microphone that is muted. If the effect works in the filter controls but the stream mix sounds different, check which sources are audible and whether a duplicate input is also active.
A typical voice chain can start with EQ and compression, but do not add every available effect by default. Compression can make quiet room noise more noticeable; a gate can make pauses cleaner but clip the start of a soft word; denoising can create artifacts. Listen at the level your audience is likely to hear, using headphones or a recording, and adjust the chain in small steps.
If you monitor your microphone through OBS, check for echo or a delayed copy of your voice. Monitoring arrangements differ between setups, so the goal is not to prescribe one universal setting: make sure you hear the signal you intend to broadcast, and avoid creating a second audible route by monitoring the same input elsewhere. Record a short sample and listen back from the recording rather than relying only on what you hear locally.
For a channel that plays a continuous audio playlist, VST filtering is a separate concern from keeping the broadcast running. For example, a guide to looping podcast audio on YouTube Live addresses playback continuity; it does not mean a microphone filter will process that audio. Keep the signal path clear, especially if voice commentary is mixed with a file or desktop source.
Check levels before going live
A plug-in can change the level as well as the tone. Compression may make quiet speech more audible, while gain controls or an effect’s output can push peaks higher. Check the source level before processing and the processed signal in OBS afterwards. Do not assume that a meter that moves means the stream will sound comfortable or undistorted.
OBS’s audio mixer guide advises checking levels and balancing sources; its meter’s red region is a warning that the signal is close to clipping. Keep speech away from clipping, then balance it against music, game audio or other sources by listening to a recording. A voice that appears prominent on a meter can still be hard to understand if background audio competes with it.
Use this pre-stream check:
- Speak at your normal distance and volume, not a deliberately loud test voice.
- Watch the microphone meter before and after enabling the filter. If the processed signal is too high, lower the source or output level and check again.
- Listen for pumping, harshness, clipping, dropouts, or a gate cutting off quiet syllables.
- Record a normal session with the other sources you expect to use, then play it back and listen to the whole mix.
- Check that the recording is not one-sided. OBS notes that mono sources are heard in both left and right channels; for stereo sources, channel assignment matters. If appropriate, review the Downmix to Mono setting in Advanced Audio Properties.
A short recording is useful because it catches things that a live meter cannot: a voice that is too quiet beside music, an effect that exaggerates room noise, or a channel-routing problem that makes sound one-sided. Test at your normal pace and include pauses and quieter phrases if those occur in your actual broadcast.
If you are preparing a long-running channel, also consider what happens after the initial sound check. An OBS session that depends on a microphone and local plug-in is different from a video file broadcast that needs to keep playing when your own computer is off. A guide to keeping YouTube radio audio running when OBS loses focus is relevant to continuity, but it does not replace testing the audio chain you actually send.
Troubleshoot a plug-in that is missing or unsuitable
If a plug-in does not appear in the selector, check the likely causes in order. First, confirm that it is VST2 rather than VST3 or VST1. Then confirm that the installed build matches your operating system and architecture, and that it is in a directory OBS scans. Restart or reopen OBS after installing, then check the selector again.
On Linux, inspect VST_PATH if the normal scan locations do not help. When that variable is set, OBS uses its specified locations rather than the other documented paths. If you have the right VST2 build and directory but still cannot find it, consult both the OBS plug-in guide and the plug-in vendor’s installation notes; avoid downloading an unverified copy from a third-party site.
If the product only offers VST3, its absence is expected with OBS’s built-in filter. Do not treat repeated reinstalling as a fix for a format mismatch. Decide whether a separate, documented host and routing arrangement is worth the added complexity, or choose a VST2 effect with a compatible build instead.
If OBS becomes unstable or audio breaks up after you add an effect, disable or remove the new filter and restore your saved settings. Re-enable one plug-in at a time and watch CPU use while listening. OBS explicitly cautions that some VSTs may crash and some can be CPU hungry; a successful installation is not proof that an effect is reliable in a long session.
If the effect appears to do nothing, verify that it is enabled and attached to the source carrying the sound you are listening to. If sound clips, reduce the input or output level and record another sample. If a gate cuts off words, reduce its effect or remove it; if a denoiser changes the voice, compare recordings with and without it. You do not need to keep an effect just because it is installed.
If the sound is one-sided, check the source’s mono or stereo behaviour and OBS channel settings. If voice competes with music or game audio, lower the competing source and listen to a recording of the combined mix. The guide to YouTube live settings for a 24/7 Punjabi music channel covers broadcast settings rather than VST compatibility, but it is a useful reminder that audio quality and stream configuration need separate checks.
A VST effect is only one part of a live setup. If a stream’s continuity depends on leaving OBS running on a particular computer, the audio plug-in does not remove that dependency. StreamNeo can take away the specific task of keeping a prepared video file broadcasting after you switch off your computer; it is YouTube-only and does not host OBS VST processing or replace a live microphone chain.
Before committing, compare the operating options on the pricing page. When the file and channel are ready, start free — 24-hour trial, no card.
FAQ
Does OBS support VST3?
OBS’s built-in VST filter is documented for VST 2.x and does not support VST3. A VST3-only plug-in will not appear in that filter’s selector. Check for a VST2 build or verify a separate host and routing workflow against current documentation.
How do I add a VST to OBS?
Install a compatible VST2 plug-in, then open Filters for the audio source you want to process. Add VST 2.x Plugin, select the effect and test the result in a recording before broadcasting.
Why isn’t my VST plugin showing up in OBS?
The most common checks are format, operating system and architecture, and installation location. Confirm it is VST2, check that it is in a scanned directory, and on Linux see whether VST_PATH has changed which locations OBS scans.
Can I use any VST2 plug-in for a 24/7 stream?
No. A compatible format and build do not guarantee that a plug-in will be stable or sound suitable in your setup. Test the effect in a normal recording, watch CPU use, and keep a way to restore your previous OBS settings.