← All posts ·

EQ After Reverb: When It Helps and How to Set It Up

Producer adjusting EQ after reverb in a studio

Put EQ after a reverb when the problem lives in the reverb's own tail: a boomy bloom, a harsh shimmer, a wash that crowds the vocal. Put EQ before the reverb when the problem is in what you feed it. Most mixes end up using both, and the order matters far less for a clean EQ than for anything that reacts to level. Below, we walk through how to decide, how to set it up on an insert or a send, and which moves actually clean up a reverb.

TL;DR

Table of Contents

The short answer: it depends on what you are fixing

There is no universally right order. Sound On Sound makes the same point in its guide to reverb treatments: the order can significantly change how an effect sounds, and neither choice is correct everywhere.

A useful way to frame it, which ProducerHive also uses, is to ask whether you want to control what goes into the reverb or what comes out of it.

That second point is the real reason post-reverb EQ exists. Audiotent puts it this way: EQ after reverb also processes frequencies the reverb generated, which an EQ placed earlier cannot touch.

What actually changes when you swap the order

With a transparent EQ and a reverb, reversing the order often produces little audible difference apart from how the wet/dry balance behaves, according to Sound On Sound. The bigger differences show up when something in the chain is level-dependent or modulates time or pitch.

The reasoning is simple. A level-dependent processor placed after a reverb sees the reverb's long, smeared envelope. The same processor placed before it sees only the short envelope of the source. Sound On Sound uses this to explain why order matters more for dynamics processors than for a plain EQ.

For your session, that means:

  1. If your chain is EQ and reverb only, pick the order by what is easiest to hear and adjust.
  2. If you add a compressor, a ducker or a saturator, think about whether it should react to the dry source or to the long tail. Those are different sounds.
  3. If you are unsure, bypass each order in turn and listen with the full mix playing.

The second point is where reverb ducking earns its place. Our post on reverb ducking with sidechain EQ covers how to keep depth while the dry vocal stays clear. Any movement you hear from that kind of setup is dynamics processing responding to the source. It is not something the EQ did.

When to EQ the signal going into the reverb

Pre-reverb EQ is a cleanup move. You are deciding what deserves a tail.

Sage Audio treats EQ before reverb as a practical default: if you remove or shape frequencies first, there are fewer unwanted tones for the reverb to process and emphasize. That matches what we see in sessions. Low-frequency energy is the usual offender. A kick or bass note that rings into a long hall turns into a low-end fog that is hard to clean up afterward.

Good candidates for pre-reverb EQ:

ProducerHive gives a concrete example for backing vocals: an EQ before the reverb with a high-pass around 500 to 600 Hz and a low-pass around 10 kHz, to cut mud, excess brightness and sibilance. Treat that as a starting point for that one source, not a rule. A lead vocal, a snare and a pad each want different corners.

Pre-reverb EQ also has one more benefit: it stays stable. Producer Alexander Schiebel argues for putting EQ before an overall reverb when you want a dependable chain, because changing the reverb later can alter the sound enough to make post-reverb EQ choices stop applying. If you swap a plate for a hall at the end of a session, a pre-reverb filter still does the same job.

When to EQ the reverb output

Post-reverb EQ is a sculpting move. The reverb exists, you hear its character, and you want to change it.

Reach for it when:

If you are stacking moves, keep each one small. A reverb tail is a wide, diffuse signal, and large boosts on it tend to sound like a different effect rather than a better one.

Muddy, boomy or harsh: where to put the move

Problem you hear Likely cause Where the EQ goes Typical move
Low-end fog under the mix Low energy in the source feeding the reverb Before the reverb High-pass, set by ear
Brittle or hissy tail Bright source or bright algorithm Before first, after if it persists Low-pass or high shelf cut
Boomy bloom at one pitch Resonance in the reverb itself After the reverb Narrow cut
Sibilance smeared into the tail S sounds hitting the reverb Before the reverb De-essing or a cut in the sibilant range
Tail feels dull and closed Reverb is dark After the reverb Gentle high-shelf lift
Tail masks the vocal Reverb crowds the vocal range After, or use ducking Small midrange cut or ducking

The pattern is consistent: problems that exist in the source are cheaper to fix before the reverb, and problems that appear only once the reverb runs are cheaper to fix after it.

Insert or send: where the EQ lives

On an insert, the reverb sits directly on the track. Order in the chain is your control: EQ above the reverb is pre, EQ below is post. The dry/wet knob of the reverb decides the balance, and one thing to remember is that a post-insert EQ will also shape the dry signal passing through that reverb plugin if it is set to partial wet. That is why we prefer sends for anything beyond quick jobs.

On a send/return setup, the typical workflow, as Cognitone describes it, is to split the source with a send, place the reverb on a separate return channel and blend the dry source with the returned effect. The same source notes that you can EQ the aux return independently, which lets you reduce or reshape the reverb layer without changing the source channel.

That gives you a clean three-point layout:

  1. EQ on the source track shapes the dry sound and, if the send is post-fader, what the reverb hears too.
  2. EQ before the reverb on the return shapes only what the reverb hears.
  3. EQ after the reverb on the return shapes only what comes back.

Set the reverb to 100 percent wet on the return so the dry signal never passes through it. For timing questions on that return, such as how long the delay before the tail should be, the echo versus reverb timing guide is a handy companion when you decide where the reverb starts relative to the dry signal.

One caution for parallel returns: whenever you run the same material through parallel paths and recombine them, check phase before you trust your ears. Our walkthrough of parallel EQ routes in three DAWs explains why phase comes first, and the five-step parallel effects routing setup shows a layout you can reuse.

A worked example: vocal plate on a return

Here is a routine we use when a vocal reverb feels heavy but turning it down makes the vocal feel dry.

  1. Create a return with a plate or hall at 100 percent wet. Send the vocal at a modest level.
  2. Put an EQ ahead of the reverb. High-pass until the tail stops adding weight to the low end. Do it while the full mix plays, not solo, because solo exaggerates what you can afford to lose.
  3. Add a gentle low-pass or a small cut where sibilance is being smeared into the tail.
  4. Put a second EQ after the reverb. Sweep a narrow boost across the tail to find any ring or boom, then flip it to a cut.
  5. If the tail still masks consonants, add a ducker keyed from the dry vocal rather than cutting more EQ.
  6. Bypass both EQs, then re-enable them, and compare at matched levels. Loudness differences fool the ear into thinking the louder version is better.

The last point matters. If an EQ move changes the overall level, compensate before judging it. Our tilt EQ post covers level matching and bypass checks in detail.

Keeping the low end of a reverb tidy without losing size

A common worry is that high-passing a reverb makes it thin. In practice the opposite is often true: a tail without low-end buildup sounds larger because the mix stays clear enough to hear its length. If you do want some low-mid body, try keeping it only in the post-reverb stage, where you can add it back in a controlled shelf rather than letting the reverb generate it unchecked.

This idea, treating different frequency regions of an effect differently, goes further than a single EQ. We wrote about it for vocals in frequency-selective reverb, and the same logic applies to echoes in frequency-specific delay and ducking delay.

If you want to split a signal and process the bands separately, the DAW-agnostic frequency split post explains how to avoid phase problems when you do it by hand. A note on filters: a minimum-phase EQ does not add delay in the way a linear-phase one does, but it still has group delay around its corner frequencies, so check any parallel path that mixes filtered and unfiltered copies.

Our perspective

We are a small design studio, and most of what we build comes from sessions where a reverb did something we could not fix with the controls it came with. The pattern repeats. Engineers reach for one EQ, in one place, and then fight the result.

Our view is that the "before or after" debate is really a question about which band is the problem. Low-end buildup is usually a source problem, so it belongs before the reverb. A boom or glare at one region is usually the reverb's own doing, so it belongs after. Treating the whole reverb as a single lump forces you to compromise on both.

Our perspective

We also think dynamics deserve their own line. When a reverb seems to swell or pull the mix around, that comes from compressors, ducking or other level-dependent processing in the chain, and you can fix it there. It does not come from the EQ filters, and moving the EQ will not cure it.

The practical upshot: do the cheap fixes first, before the reverb. Then use a post EQ sparingly on what is left. When you find yourself needing different treatment in the lows, mids and highs of one effect, a lane-based approach, with each band getting its own handling inside one insert, saves a lot of routing.

— Kai

One way to do this in a single insert

If you would rather not build extra buses for every band, we made ToneLab for this kind of work. It runs multiple parallel effect lanes in one insert, with EQ targeting each lane, so you can keep the lows out of a reverb lane and shape the tail separately. It costs $73.99 as a one-time license, and a free demo is available to try on your own sessions.

Vector-dsp

The same result is fully achievable with sends, returns and a couple of EQs, and everything above works in any DAW. A tool just makes the repeated setup quicker.

Quick checks before you commit to an order

Audiotent suggests the same final step: A/B both placements and judge the source and the reverb together. That is the one test that settles the order for your specific track.

FAQ

Should I put EQ before or after reverb?

Use both when needed. Put EQ before the reverb to control what feeds it, such as low rumble or harsh sibilance. Put EQ after it to fix tones the reverb generated, such as a boomy resonance. If you only add one, start with the pre-reverb EQ because it holds up better if you change the reverb later.

Does EQ after reverb change the dry signal?

Not if the reverb is on a send/return and set to fully wet. The EQ then affects only the returned reverb. On an insert with a partial wet mix, a post-reverb EQ shapes both the dry and wet sound together, so a send is safer for tail-only changes.

What frequencies should I cut on a reverb return?

There is no universal number, because it depends on the source and the reverb. Start with a high-pass to clear low-end buildup, then sweep a narrow cut to find any ring or boom in the tail. ProducerHive's backing-vocal example, a high-pass around 500 to 600 Hz and a low-pass near 10 kHz, shows how far some mixes go, but your lead and your drums will want different settings.

Does the order matter for a plain EQ?

Often very little. Sound On Sound notes that with an EQ and clean delays, swapping the order usually produces little audible difference apart from wet/dry behavior. It matters more when compression, ducking or modulation sits in the chain. Test both with the full mix playing and keep what sounds better.

Sources