Pre-Fader vs Post-Fader Sends

Production guides · Meme Plugins · 1 November 2026

Use a post-fader send when the feed to an effect should follow the source track’s fader. Use a pre-fader send when that feed needs an independent level relationship. Check the actual tap point and mute behavior in your DAW; pre-fader does not automatically mean pre-effects.

This guide assumes you have already drawn the dry and return paths. Start with insert effects versus send effects if those routes are unclear.

1. Identify which control the send should follow

For a shared reverb, you may want the effect input to rise and fall with the dry vocal. For an independent musician’s monitor mix, you may want the main fader to change without altering that separate feed.

Ableton’s mixer reference documents a Pre/Post setting on each return track. In that implementation, the tap is before or after the source’s mixer stage, including its pan, volume and active controls. Other systems may put the choice on each send and provide additional tap points.

Locate the intended control rather than changing a global routing option by guesswork.

2. Keep effect input separate from return output

The source fader, send amount and return fader have different jobs. A send controls the effect feed; the return controls the audible processed result. If the return should contain only the effect, use its documented fully wet setting and keep the dry signal on its own path.

For a reverb with memory, reducing new input does not erase the tail already generated. Hear the transition through time instead of judging one instant after moving the fader.

Example: the same vocal fade in two routes

Imagine a repeated vocal phrase feeding one shared reverb. This is a hypothetical routing test, not measured or auditioned audio. Keep the source, reverb settings, send amount and return level fixed between trials; use a reverb without input-dependent changes for the clearest comparison.

  1. Post-fader trial: lower the vocal’s fader during the phrase. Confirm that the feed to the reverb decreases with it, while the existing tail continues to decay.
  2. Pre-fader trial: restore the starting fader position and change only the documented send tap. Repeat the same fade. Confirm whether new effect input remains while the dry vocal drops.
  3. Return trial: restore the baseline and lower the return fader instead. Hear the processed output change while the dry vocal stays in place.
  4. Decision: choose the path that gives the intended fade. If neither does, consider a deliberate send or return automation move and label which one it is.

Use a copied session or saved version for the comparison. The test separates source level, effect input and effect output rather than prescribing one routing for every mix.

3. Test mute, monitoring and export behavior

A mute, track-active control or solo can act at a different point from the volume fader. Check those controls separately so the effect does not keep receiving a signal when you expected silence.

When a return is routed to a separate monitor output, verify the destination and listening level. Keep feedback routes disabled unless you deliberately need and understand them.

4. Check the last phrase and actual file

Play the final line and its decay, then reopen the export. Confirm both the intended fade and enough duration for the tail. Use the reverb timing workflow when the tail itself needs adjustment.

For deliberate vocal rides around compression, see automation versus compression. Know whether the chosen ride changes a processor’s input or an already-processed output.

Is pre-fader the same as pre-effects?

No. It names a relationship to a fader. Read the actual signal tap and check the route in the host.


Browse all production guides → · Free browser audio tools