How to Use Send Effects

Updated May 2026

Send effects and return tracks are one of those concepts that separates producers who understand mixing from producers who are guessing. If you have ever wondered why your reverb-drenched mixes sound cluttered and incoherent, or why your tracks do not feel like they exist in the same room, or why your CPU spikes when you add a reverb to every channel — send effects are the answer to all three problems.

They are also one of the most misunderstood parts of any DAW. Many producers discover send knobs early, turn them up without knowing what they are doing, and then move on. Some producers use insert reverbs on every track for years without realizing a fundamentally better approach exists. This guide covers the concept completely — what sends are, why they exist, how to set them up in the three main DAWs, and a set of creative techniques that go well beyond simple reverb.

Insert Effects vs. Send Effects: What's Actually Different

Before building anything, the conceptual distinction needs to be clear — because confusing these two approaches creates problems that are genuinely hard to diagnose after the fact.

An insert effect sits directly in a track's signal chain. Every audio signal passing through that track runs through the effect. The effect processes 100% of the signal, in series — it cannot be avoided. When you drag a reverb plugin onto a channel strip, you have inserted it. The reverb receives the full signal, processes it, and outputs a blend of dry and wet audio that continues downstream. The dry/wet knob on the plugin itself controls the blend.

A send effect works differently. Instead of sitting in the track's path, it receives a separate copy of the signal via a routing mechanism called the send. The original signal continues untouched on its original track. The copy goes to a dedicated return track — also called an FX track or Aux track depending on your DAW — where the effect lives. The processed signal from the return track mixes back into the master alongside everything else.

The practical difference: with insert effects, every track that needs reverb gets its own reverb instance. With send effects, every track shares one reverb instance on a single return track. Both approaches make reverb happen. They make it happen very differently — and with very different results for your CPU, your mix coherence, and your creative control.

Why the Shared Reverb Approach Is Almost Always Better

There are three distinct reasons professional mixers almost always use send effects for reverb and delay rather than inserting them on individual tracks. Understanding all three helps you make better decisions about when to use each approach.

Reason 1: CPU Efficiency

High-quality reverb plugins — the kind that use convolution algorithms or dense feedback networks — are computationally expensive. A convolution reverb like Valhalla Room or FabFilter Pro-R running on a single track is manageable. The same reverb running on fifteen tracks simultaneously is a significant CPU load that causes buffer overruns, dropouts, and forces you to increase your audio buffer size, which increases latency.

A single return track with one reverb instance, receiving sends from fifteen tracks, costs the same CPU as a single instance. Period. This is not a marginal gain — it is the difference between a session that runs cleanly and one that chokes at the mixdown stage. If you have ever wondered why professional session templates look the way they do, shared reverb returns are a large part of the answer.

Reason 2: Coherent Acoustic Space

When you insert a separate reverb on every track, even if you use the same plugin with the same settings, each instance processes that track's audio independently. Small differences in timing, phase relationships, and plugin initialization mean the reverb tails from each track do not actually interact the way sounds in a real room do. The result is a mix where each element seems to occupy its own isolated space — a collage rather than a photograph.

A single shared reverb return processes all incoming audio together. The reverb tails from the snare, the vocal, and the piano all run through the same algorithm in the same instance. They share the same room. This is what engineers call mix glue — the quality that makes a multi-track recording sound like it was captured in a single physical space rather than assembled from separate recordings.

This is also why understanding how to use reverb in a mix is fundamentally about signal routing, not just plugin settings. The routing decision shapes the result more than any parameter adjustment.

Reason 3: Independent Control Over the Effect

When reverb is inserted on a track, the only way to control the wet/dry blend is the plugin's own wet knob. You cannot EQ only the reverb, you cannot compress only the reverb tail, and you cannot automate the reverb level independently of the track's volume. Everything is coupled.

On a return track, the effect is a separate mix element. You can place an EQ after the reverb and cut the low frequencies so the reverb does not muddy up the low end — a technique used on virtually every professional mix. You can add a high shelf to darken the reverb so it sits behind the dry signal. You can automate the return track's fader to bring the reverb up during a chorus and pull it back during a verse. You can compress the reverb tail. You can side-chain the reverb so it ducks when the dry signal is present. None of these are easily possible with inserted reverb.

The 100% Wet Rule: Why It Matters

This is the single most common technical error in send effect setups, and it has an immediate and audible consequence.

When you place a reverb on a return track, you must set the reverb's dry/wet control to 100% wet — meaning the plugin outputs only the processed (wet) signal and no dry signal. Here is why: the dry signal is already present on the original source track. That track's audio continues downstream completely untouched by the send routing. If the return track's reverb also outputs some dry signal, you now have two copies of the dry audio arriving at the master — one from the source track and one from the return. These two copies have a small time delay between them (the plugin's processing latency), which creates comb filtering and phase cancellation. The result is a hollow, phasey, thin-sounding track that is difficult to diagnose without understanding the cause.

Some plugins label this knob differently. In Valhalla Room it is the Mix knob — set it to 100%. In Ableton's built-in Reverb it is the Dry/Wet knob — turn it fully clockwise. In FabFilter Pro-R it is the Space knob — set it to 100%. The label changes, the principle does not.

Setting Up Send Effects in Ableton, Logic Pro, and FL Studio

The conceptual model is identical across DAWs. The interface details differ. Here is exactly how to do it in each of the three most common production environments.

Ableton Live

In Ableton Live, return tracks are created via the Create menu: Create > Insert Return Track. They appear to the right of your regular tracks in Session View or below them in Arrangement View, labeled A, B, C, and so on. On each regular audio or MIDI track, send knobs labeled A, B, C appear in the track's mixer section, corresponding to these return tracks.

To set up a reverb send: insert your reverb plugin (Ableton's built-in Reverb, Valhalla Room, or any other) as a device on the return track. Set the plugin to 100% wet. On the source tracks you want to feed into this reverb, raise the corresponding send knob. The send knob controls the level of signal sent to the return — treat it as a wet level control per track.

By default, sends in Ableton are post-fader, meaning the send level scales with the track fader. If you lower a track's volume, less signal goes to the reverb. To change a send to pre-fader (the send level is independent of the fader), right-click the send knob and select Pre Fader. Ableton also has a global send toggle — the small triangle icon next to the return track label — which lets you solo or mute return routing for comparison purposes.

Ableton Live 12 also introduced improved return track visibility in Arrangement View, making it easier to manage complex return setups without switching to Session View. If you are working in Arrangement and cannot see your returns, check the View > Returns toggle. For a full overview of what changed in the latest version, see the Ableton Live 12 review.

Logic Pro

In Logic Pro, the equivalent of a return track is an Aux channel strip. Open the Mixer (press X), then use the plus (+) button at the bottom left to add a new Aux channel. Alternatively, on any source track, click the Sends section of the channel strip and select Bus > Bus 1 (or any available bus number). Logic automatically creates an Aux channel strip routed from that bus if one does not already exist.

Add your effect plugin to the Aux channel strip's insert slots, set it to 100% wet, and adjust the send level on each source track's channel strip. Logic's send knobs default to post-fader behavior. To switch to pre-fader, click the send level knob and look for the pre/post toggle that appears in the channel strip's send section.

Logic Pro 11 added a significant improvement to bus routing visualization, making it easier to see which tracks are feeding which Aux channels directly in the Mixer window. The Aux channel strips are color-coded by bus assignment, which helps with complex template management. For producers coming from other DAWs, the Logic Pro beginner's guide covers channel strip routing in detail.

FL Studio

In FL Studio, send effects use the Mixer's routing system rather than a dedicated return track concept. Add your effect plugin to an empty Mixer track (set it to 100% wet). On the source Mixer track you want to send from, click the routing arrows at the bottom of the Mixer to enable the connection to your effects Mixer track. Adjust the send level using the knob that appears in the routing section once the connection is active.

Both the dry source track and the wet effects track feed independently into the Master track. This means the effects track functions as a return — its output adds to the mix alongside the dry signal from the source track. One important FL Studio note: by default, when you route a track to an effects track in FL Studio, the original track still outputs to the Master. You can disable this by clicking the green arrow indicator on the source track to stop it from also sending directly to Master — but for standard send effect setups, leaving both active is the correct behavior (source track dry signal to Master, effects track wet signal to Master).

For a side-by-side comparison of workflow differences between FL and Ableton that includes routing behavior, see FL Studio vs Ableton Live.

Send Effect Settings Reference

Pre-Fader vs. Post-Fader Sends: When to Use Each

This is one of the subtler distinctions in send routing, but it has meaningful practical consequences depending on what you are trying to achieve.

Post-fader send (the default in all three DAWs) means the signal level going to the return track scales with the source track's fader. If you lower the track volume, less signal feeds the return. If you mute the track, the send stops entirely. This is the correct behavior for almost every standard reverb and delay send — you want the effect level to follow the dry level. As a vocal gets quieter in the mix, you want its reverb contribution to diminish proportionally. Post-fader maintains the wet/dry ratio you have set regardless of volume changes.

Pre-fader send means the send level is fixed independently of the track fader. You can lower a track to silence while the send continues to feed signal to the return. You can mute the source track and the return still receives signal. This has specific uses:

• Monitoring reverb: In live sound and recording contexts, a pre-fader send to a headphone mix or monitoring reverb means the performer hears the effect regardless of fader adjustments in the control room.
• Ghost sends: You want a reverb tail to linger even after the source track is muted — a creative effect where the room continues to ring after the direct signal cuts.
• Independent parallel processing: You want to control the wet and dry levels completely independently, treating them as entirely separate mix elements with no coupling.
• Effects automation: Building up a return level before a track enters — you can automate the source track fader up from silence while the reverb is already being fed, so the reverb starts before the dry signal becomes audible.

In most standard mixing situations, post-fader is correct. Pre-fader is a specialized tool. Knowing the difference means you reach for pre-fader deliberately rather than stumbling onto it by accident and wondering why muting a track does not stop the reverb.

Creative Send Effect Techniques Beyond Basic Reverb

The send/return architecture is not just for standard room reverb. Once you internalize the routing model, the entire concept becomes a framework for any parallel processing you want to apply in a mix. These are the techniques working mixers actually use.

Parallel Compression (New York Compression)

Parallel compression — sometimes called New York compression — is one of the most widely used drum processing techniques in modern production. The concept: blend a heavily compressed version of the drums with the original uncompressed signal. The result is density and sustain without sacrificing the impact of the original transients.

Set up a return track with a compressor. Use a fast attack (1–5 ms), fast to medium release (50–150 ms), high ratio (8:1 to 20:1 or even limiting), and enough gain reduction to bring the level down 10–15 dB. Then apply makeup gain to bring it back up. Send the kick, snare, and room mics to this return. Slowly raise the return fader until you hear the sustain and density filling in between hits. The transients come from the original uncompressed signal on the source tracks — the compressed return adds the body and glue underneath them.

The key distinction from insert compression is that you are never touching the original transient. The attack of the snare is preserved perfectly on the source track. The compressor on the return only affects the copy. This is why parallel compression is often described as having the "best of both worlds" — the punch of an uncompressed signal with the density of heavy compression.

For a deeper look at how compression parameters interact with drum signals before you set up a parallel chain, the guide on how to use compression on drums covers threshold, ratio, and attack settings in detail.

Parallel Saturation

Saturation adds harmonic content — overtones that make a sound feel richer, warmer, and more present. But applied directly as an insert effect, even subtle saturation can change the character of a sound in ways that are hard to un-hear. Parallel saturation solves this: send the signal to a return with a saturator set to 100% wet and a medium-heavy saturation amount, then blend the return in at a low level.

The result is harmonic richness layered underneath the clean original signal. The source retains its character; the saturation adds texture without overwriting it. This technique works especially well on drums (adds presence and grit), bass (adds upper harmonics that translate on small speakers), and synth pads (adds organic warmth to overly clean digital sounds).

Add an EQ after the saturator on the return and apply a low-pass filter around 6–8 kHz. This removes the harsh high-frequency artifacts that heavy saturation can introduce while keeping the body of the harmonic content intact.

Frequency-Selective Reverb Sends

Standard reverb sends process the full-bandwidth signal from each source track. But some of the most sophisticated reverb techniques involve sending only a frequency range to the reverb. This is done by inserting an EQ before the reverb on the return track (or by inserting an EQ on the source track's send chain, if your DAW supports per-send inserts).

A common application: on a vocal reverb return, cut everything below 300–500 Hz with a steep high-pass filter before the reverb. The low frequencies of the vocal — the chest resonance and proximity effect — never enter the reverb algorithm, so they never come back as low-mid mud in the reverb tail. The reverb only processes the clarity and presence of the vocal, not its weight. This keeps the low end clean while the reverb still sounds full.

Another application: send only the high-mids and highs of a snare to a large hall reverb. The thump of the snare stays dry and punchy; only the crack and snap gets the huge room treatment. This is a common technique in film scoring and cinematic production where you want dramatic-sounding reverb without destroying the rhythmic impact of the drum hits.

Multiple Return Tracks: Building a Reverb Architecture

Professional mix templates typically have two or three distinct reverb returns rather than one. Each serves a different depth function:

• Close room (short decay, 0.4–0.8 s): Used for drums, percussion, and any element that needs presence without pushing back in the mix. Keeps energy tight and rhythmic.
• Mid room or plate (medium decay, 1.0–2.0 s): Used for vocals, lead instruments, snare. Creates sense of space and depth without smearing transients significantly.
• Hall or large space (long decay, 2.5–6.0 s): Used sparingly for pads, strings, ambient elements, or deliberate effect throws. This reverb should appear in the mix at a much lower level than the others.

The key discipline: not every track needs to send to every return. The bass almost never sends to any reverb. The kick drum typically only sends to the close room, if at all. The lead vocal sends to the plate or mid room. Pads send to the hall. Selective routing is how you create a mix with genuine depth and dimension rather than a wash of undifferentiated reverb.

Shared Delay Bus

A delay return works on exactly the same principle as a reverb return. Set up a return track with a delay plugin — tape delay, ping-pong delay, or a sync'd tempo delay — at 100% wet. Route sends from multiple tracks to this delay return. Now multiple elements share the same delay timing and character.

This technique is particularly powerful when the delay is tempo-synced. If the delay is set to a dotted eighth note at the session tempo, sends from the snare, the vocal, and a synth lead all decay in rhythmic lockstep. The mix feels tighter and more intentional because all the delays speak the same rhythmic language.

For specific techniques on how delay and reverb interact with vocals in a mix, the guide on how to use reverb on vocals covers the depth-positioning techniques used in professional vocal mixing.

Creative Effects Throws

Send effects do not have to be always-on. One of the most dramatic creative uses of a send is the effects throw: automate the send knob on a source track to briefly spike to a high level at a specific moment, then return to zero. The result is a sudden flood of reverb or delay on a single note, syllable, or phrase.

Classic applications: automate the send on a vocal to spike on the last word before a chorus drop, sending it deep into a large hall reverb and letting the tail carry the listener into the new section. Or spike the send on a snare hit to create a single reverb bloom on a specific beat for dramatic emphasis. These automation moves take seconds to draw in and have immediate, audible impact on the energy and emotion of a mix.

This kind of detailed send automation is one of the key tools described in any serious guide to using automation in your DAW — it is a mixing technique as much as a production technique.

Common Send Effect Mistakes and How to Fix Them

After covering what to do, it is worth addressing the specific mistakes that appear most frequently — because they are easy to make and the results are often attributed to the wrong cause.

Mistake 1: Not Setting the Return Effect to 100% Wet

Already covered in detail above, but worth repeating because it is the most common error. If your reverb sounds phasey, hollow, or weirdly comb-filtered, check the wet setting on the return plugin first. It must be 100% wet with zero dry signal output.

Mistake 2: Too Many Things Sending to the Same Reverb

A shared reverb return is not an invitation to route everything to it at high levels. When too many tracks send large amounts of signal to a single reverb, the return becomes saturated with overlapping reverb tails and the mix loses definition. The reverb should be a support element in the texture, not a dominant presence. As a starting point, keep individual send levels conservative — many professional engineers start sends at around –20 dB and bring them up from there rather than starting high and pulling back.

Mistake 3: Sending Low-Frequency Sources to Reverb Without Filtering

Bass instruments, kick drums, and 808s should almost never send to a reverb return without first applying a high-pass filter — either on the return track's EQ or at the source. Low-frequency reverb creates a thick, resonant mud that builds up in the low-mid range and destroys the clarity of the mix. High-pass the reverb return at 200–400 Hz as a default starting point, then adjust by ear.

Mistake 4: Ignoring the Return Track Fader

The return track fader is a global level control for the entire effect. Many producers set the fader at 0 dB and control everything with individual send knobs. But the return fader is a powerful tool: use it to ride the overall reverb level during mixdown, automate it for dynamic control, or lower it to quickly audition how the mix sounds without the effect. Treating the return fader as a mix element — not just a default-and-ignore control — opens up significant creative and technical control.

Mistake 5: Confusing Pre-Fader and Post-Fader Behavior

This causes an extremely confusing symptom: you mute a track but the reverb keeps running. Or you lower a track fader to zero but still hear the effect. If this happens, you have accidentally switched a send to pre-fader mode. Right-click the send knob (in Ableton) or check the send section (in Logic or FL Studio) to confirm and correct the pre/post status.

Understanding send effects also directly informs how you approach the entire structure of a plugin chain on any track. The decisions you make about what processing goes on a source track versus what goes on a return track shape the character of everything downstream. For a broader look at how to sequence effects intelligently, see the guide on how to build a plugin chain.

Send effects are not an advanced technique reserved for experienced engineers. They are a fundamental part of how professional mixes are built, and they become available to any producer the moment they understand the routing concept. The CPU savings are immediate, the mix coherence improvement is audible from the first session, and the creative possibilities — parallel compression, selective frequency sends, automated reverb throws — represent a substantial expansion of what you can do with the tools you already have.

The entire paradigm of send effects rests on one insight: effects do not have to live on the tracks they affect. They can live on their own tracks, be shared across the whole session, and be treated as independent mix elements with their own processing chains, fader automation, and creative roles. Once that model is internalized, the architecture of a professional mix starts to make complete sense.

Practical Exercises

Frequently Asked Questions