--- title: "Pre-Fader vs Post-Fader Audio Routing Explained | Gawergy Audio" description: "Understand where inserts, sends, meters, and automation tap a signal relative to a fader, with host-specific routing caveats." canonical_url: "https://gawergy.com/learn/pre-fader-vs-post-fader" md_url: "https://gawergy.com/learn/pre-fader-vs-post-fader.md" last_updated: "2026-09-23" date_published: "2026-09-23" --- # Pre-Fader vs Post-Fader Processing: What’s the Difference? Pre-fader means a signal is taken or processed before a particular fader; post-fader means after it. The distinction controls whether moving that fader changes the level reaching a send, processor, meter, or destination. It sounds simple, but a DAW can have multiple faders and tap points, and its insert order or automation behavior may vary. A precise answer names the fader and the signal route rather than assuming one universal console diagram. ## Key takeaways - Pre and post are relative positions in a signal path, not intrinsic sound-quality modes. - A pre-fader send can remain independent of the source track fader; a post-fader send usually follows it. - An insert before a fader receives a different level relationship from one after it. - Meters and automation must be interpreted at their actual tap points in the chosen host. ## Always name which fader you mean A track may have clip gain, an input trim, insert processors, a channel fader, sends, a group bus, and a Main fader. 'Pre-fader' has meaning only relative to one of these gain controls. A send tapped before the track's mixer fader can feed a return independently of that fader; a send tapped afterward generally follows its level. Ableton Live 12 documents pre/post toggles on returns and defines them relative to its mixer stage, including pan, volume, and track-active behavior. That is a concrete host implementation, not a claim about every DAW. Routing can have more than two choices. Ableton's routing documentation describes Pre FX, Post FX, and Post Mixer tap points when a track receives audio from another track. Those positions answer different questions: before devices, after devices, or after the mixer's level and pan stage. A producer who says 'the signal is pre-fader' but does not mention pre- or post-effects may still leave a critical ambiguity. Read the host's own labels and trace the specific path. The distinction is about causality. If a fader sits after a tap point, moving it cannot change the level at that tap. If the fader sits before the tap, moving it changes what the later stage receives. That simple model explains why a monitoring send can stay steady while the main mix level changes, and why a post-fader reverb send may fade with the dry track. It does not prescribe which topology a song should use. ## How send behavior changes with position A send duplicates or routes some signal toward another path. In pre-fader mode, its level can be controlled independently of the source channel fader, subject to the host's exact routing. This can be useful for a separate monitor mix, as Ableton's mixing manual explicitly describes. In post-fader mode, lowering the source fader commonly lowers the amount sent as well. That relationship may preserve a chosen effect-to-dry balance when the channel level changes. The two modes serve different routing goals; neither is inherently more professional. The return or destination has its own processors and gain controls. A pre-fader send is not automatically unprocessed: it may be tapped after inserts but before the mixer fader, depending on the host. Ableton's separate Pre FX, Post FX, and Post Mixer choices illustrate this nuance. The phrase *pre-fader send* alone does not tell you whether EQ or compression on the source track reaches the send. The tap point must be located in the actual DAW. Feedback routing adds another consideration. Some hosts permit a return to feed itself or another return, and Ableton notes that runaway feedback can rise unexpectedly. The pre/post choice can affect how gain changes propagate through such paths. This article is not a recipe for feedback effects; it is a reminder that signal-flow diagrams matter for level and stability. A fader move may not tame a route that branches before it. ## Before or after a processor changes its behavior An insert before the channel fader receives a level independent of later fader moves. If it is a compressor, lowering the fader afterward changes the volume of the compressed result without changing the detector's input. If it is a clipper, the waveform shaping remains; the fader makes it quieter. An insert after the fader receives the fader-adjusted signal and may respond differently. The [master-fader clipping article](/learn/master-fader-clipping) applies that logic to a final output path. The effect is strongest for level-dependent processors. A static linear gain or fixed EQ has different order relationships from a nonlinear clipper or compressor. Move gain before a clipper and fewer or more samples may hit its curve; move gain after and the curve's output is simply scaled. The [linear-versus-nonlinear article](/learn/linear-vs-nonlinear-audio-processing) explains why order changes an effect's response. This is a topology explanation, not a chain blueprint. Host designs vary. Some have fixed insert slots before fader, others offer post-fader slots, and some expose configurable routing. Plug-ins can also include their own input and output trims. The placement of a processor in a list does not always reveal every internal gain stage. Use the host's documentation and the plug-in's meters to locate the point where an overload or tone change first occurs. ## A meter reports its own tap point A pre-fader meter can show the signal feeding the channel before the fader; a post-fader meter can show the level leaving it. If the fader is down, the two may differ greatly even though both are accurate. Some DAWs offer switchable meter positions, while a plug-in displays levels at its own input or output. A red pre-fader meter may warn about upstream overload that a low post-fader output conceals. A red post-fader meter may indicate a downstream issue despite clean source tracks. Meter type is another axis. Sample peak, true peak, RMS, LUFS, and gain reduction measure different properties. The fader location alone does not define the metric. The [sample-peak versus true-peak guide](/learn/sample-peak-vs-true-peak) covers one important distinction. Read both the meter's tap point and its measurement definition before deciding what a displayed number means. The same signal can give several valid readings at once. A monitoring path can include output trim or hardware gain after the DAW meter. A post-fader meter inside the host may not show later analog overload. Likewise, a pre-fader meter may not show a clipper inserted later. The signal path, not the most prominent display, determines which boundary is being checked. This matters when troubleshooting clipping and preparing an export. ## Automation depends on which gain control it moves A DAW may automate the track fader, clip gain, plug-in parameters, or a dedicated trim. These controls act at different stages. Automating a post-insert fader can fade a processed signal while leaving the processor's response unchanged. Automating clip gain before a compressor can change the detector input and the amount of compression. Automating a post-fader send can alter the destination feed in relation to the channel. The [clip-gain-versus-compression guide](/learn/clip-gain-vs-compression) compares those pre-processing level changes. The host may smooth automation values, and some effects or send routes have their own latency. Ableton's audio fact sheet discusses volume automation as a signal change and notes implementation details for its engine. One should not assume sample-perfect behavior or a universal timing model from the word *automation* alone. For the current question, first determine which parameter moves and where it sits relative to the processor or tap under discussion. A static mix state is easy to draw; automation makes the relationship time-dependent. A pre-fader monitor send can remain steady while the main fader follows a fade, but a separately automated send can still change. Post-fader usually means a level relationship, not a permanent fixed ratio under every possible automation setup. The routing and active control both matter. ## Parallel paths make placement audible When a dry path and processed return are blended, pre/post routing influences how their levels track. If the send is post-fader, a source-channel fade may reduce both dry and return feed. If it is pre-fader, the return may continue receiving signal while the dry fader moves. That can change the effective balance dramatically. The [parallel-processing article](/learn/parallel-processing-mixing) explains dry/wet topology and the additional issue of latency or phase when paths recombine. The pre/post choice is one part of that topology. A wet plug-in's own mix control may also create an internal parallel path. Its placement before or after a fader changes what it receives, while its internal dry/wet setting changes how its paths recombine. These are separate controls that can be confused in a complex session. A routing diagram or a simple signal-flow trace often clarifies more than a preset name. The question is which versions of the signal meet again and at what levels. Latency compensation may align host paths, but not every creative or external route behaves identically. Phase differences can change the summed sound even if send levels seem correct. This is an implementation and monitoring consideration, not a reason to avoid parallel processing. Check the actual result in the chosen host. ## Pre and post tell you who follows whom Pre-fader and post-fader describe where audio is tapped or processed relative to a named fader. The choice determines whether a send, insert, or meter sees that fader's gain change. DAWs provide different tap points and routing options, so the exact signal path must be verified for the session. Neither position is intrinsically better; each serves a different operational purpose. When troubleshooting an effect or overload, identify the source, insert order, fader, send tap, return, meter, and output. Once those are in order, the behavior becomes a predictable consequence of routing rather than a mystery about one knob. ## About G-Clipper Pro A clipper before a fader shapes the input it receives; moving the later fader changes level but not the shape already produced. ## Sources & References - [Mixing — Ableton Reference Manual Version 12](https://www.ableton.com/en/manual/mixing/) - [Routing and I/O — Ableton Reference Manual Version 12](https://www.ableton.com/en/manual/routing-and-i-o/) - [Live Audio Effect Reference — Ableton Reference Manual Version 12](https://www.ableton.com/en/manual/live-audio-effect-reference/) - [Audio Fact Sheet — Ableton Reference Manual Version 12](https://www.ableton.com/en/manual/audio-fact-sheet/) - [FabFilter Pro-C 3 Help — Time controls](https://www.fabfilter.com/help/pro-c/using/timecontrols) ## Continue Reading - [Does Turning Down the Master Fader Prevent Clipping?](https://gawergy.com/learn/master-fader-clipping) - [What Is Parallel Processing in Mixing?](https://gawergy.com/learn/parallel-processing-mixing) - [Clip Gain vs Compression](https://gawergy.com/learn/clip-gain-vs-compression) ## Sitemap See the full [Gawergy.com sitemap](https://gawergy.com/sitemap.md).