How to Fairly A/B Test Free VST Plugins in Your DAW

You've read the "10 Free Plugins That Beat Paid Ones" listicle a dozen times. Maybe you even downloaded the free EQ it praised, dropped it on a track, and thought, "yeah, this sounds pretty close." But did it actually sound close, or was it just louder?

That's the trap almost every casual plugin comparison falls into. A plugin turned up even slightly hotter sounds punchier, brighter, and more "exciting" regardless of what it's actually doing to the signal. Add in placebo (you already believe the paid plugin is better because you paid for it, or you already believe the free one is a hidden gem because a forum said so), and you end up with an opinion, not a result.

This guide walks you through a reproducible test you can run in any DAW, whether that's Reaper, Ableton Live, Cakewalk, or Studio One. Gain-stage both plugins identically, confirm the match with a null test, then run a blind listen focused on specific sonic details instead of vague impressions.

Why Casual A/B Tests Lie to You

Human hearing is highly sensitive to loudness and surprisingly bad at judging tone in isolation. A small level difference can shift your preference in a blind test, and most bedroom comparisons have level mismatches far larger than that. Switch between two plugins by ear when one is even slightly louder, and your brain will likely call it "better," "warmer," or "more present" when it's really just hotter.

The fix isn't complicated, but it requires discipline: match levels first, verify the match mathematically, then listen. Skip a step and the whole test falls apart.

Step 1: Choose One Test Signal and One Task

Pick a single, unprocessed audio clip or a simple synth patch you can recall reliably, ideally something relevant to the plugin category you're testing. For an EQ or compressor, use a dry vocal or bass DI. For a synth, use a basic sawtooth or pad patch with no other processing.

Decide on one specific task before you touch either plugin: a 3 dB cut at 2 kHz, a 4:1 compressor with a 10 ms attack, or a single held note at a fixed velocity. Testing two plugins doing two different jobs tells you nothing. This pairs well with sidechain noise gate settings for guitar: step-by-step explained.

Step 2: Gain-Stage Both Plugins Identically

1. Set your DAW track's input gain so peaks sit around -18 dBFS to -12 dBFS RMS before any processing. This headroom keeps you out of either plugin's non-linear "hot" zone, which can flatter or unfairly punish one of them.
2. Insert the free plugin on one track and the paid plugin on an identical duplicate track, both fed the exact same source audio.
3. Set both plugins' input trim to 0 dB (unity) and disable any auto-gain, output ceiling, or "loudness compensation" features. Many EQs and compressors include automatic makeup gain specifically to make changes sound more dramatic. Turn it off.
4. Route both tracks to a single bus fader so you can switch between them without touching a channel fader mid-test.

Step 3: Level-Match the Outputs by Ear-Assisted Metering

Once both plugins perform the same processing task, measure the output loudness of each track using your DAW's built-in loudness meter or a free LUFS meter plugin. Adjust the output gain (not the plugin's internal parameters, but a separate utility gain plugin after it) on whichever chain reads louder until both tracks match within 0.1 dB integrated LUFS or peak RMS.

This step alone removes the single biggest source of bias in home-studio plugin comparisons. Skip it, and everything downstream becomes unreliable.

Step 4: Confirm the Match With a Null Test

Almost nobody runs this step, and it's the difference between a guess and a genuine result.

1. Bounce or render both level-matched chains to audio files.
2. Import both files onto two new tracks, perfectly aligned to the same start point.
3. Invert the phase of one track using your DAW's polarity flip (often a small phase button on the channel strip, or a utility plugin).
4. Play both tracks together. Identical outputs cancel out completely, leaving silence.

You won't get true silence between two different plugins. That's expected, since they process the signal differently rather than just applying a gain shift. What matters is whether the residual signal after the null is dominated by tonal differences (the thing you actually want to compare) rather than a loud, broadband hiss or hum, which would signal that your levels still don't match. If flipping the output gain by even 0.1 dB dramatically changes how much cancels, your levels weren't matched yet. Go back to Step 3.

Step 5: Run the Blind Listen

With levels confirmed by the null test, the actual listening test can begin.

1. Ask a friend to label the two rendered files "A" and "B" randomly, or use a simple script or DAW marker trick so you don't know which is which while listening.
2. Loop a short section, no more than 10 to 15 seconds, and switch between A and B using a single key command or MIDI controller so there's no gap or fader move to tip you off.
3. Write down your impression of each pass before revealing which plugin was which. Do this at least five times per plugin pair.
4. Reveal the labels only after logging your notes.

This blind structure removes the brand bias that wrecks so many bedroom comparisons. You're judging sound, not a logo. See full coverage of analog vs digital budget polysynths: a daw ear test for additional background.

What to Listen For by Plugin Category

EQs

Focus on how each EQ's curve behaves away from the exact frequency you targeted. Free EQs sometimes use wider or less precise filter shapes, so listen for unwanted buildup or thinning in adjacent bands. Also compare the noise floor: solo the processed track and turn up your monitors to check whether one plugin introduces audible hiss or a subtle digital grain the other doesn't.

Compressors

Listen specifically to transient behavior at the exact attack and release settings you matched. Does one plugin let more of the initial snap through, or squash it more aggressively despite matching parameter values? Check the release tail for pumping or a "breathing" artifact, and listen for how each compressor handles the harmonic content of sustained notes. Some cheaper designs add subtle distortion under heavy gain reduction that a more transparent design won't.

Also read: see adobe audition won't open on windows 10? fix it fast

Synths and Samplers

Compare oscillator harmonic content by ear at a single sustained note, listening for aliasing (a metallic, ring-modulated quality) at higher pitches, which shows up more often in unoptimized free oscillators. Check the noise floor during silence between notes, and compare how each handles polyphony under a fast, repeated pattern. Some free synths introduce audible glitches or voice-stealing artifacts that paid competitors handle more cleanly.

What to Expect Next

Run this process on a handful of plugin pairs you're genuinely curious about, and expect two outcomes. Sometimes the free plugin holds up entirely, giving you real evidence instead of a forum recommendation. Other times you'll hear a genuine gap, maybe in noise floor, maybe in transient handling, that a loudness-biased casual test would have hidden. Either way, you'll form the verdict yourself, using a method you can repeat the next time someone tells you a plugin is "basically the same, but free."