Decapitator 6 is the version I keep installed on the master bus template now, and the reason has less to do with the saturation engine and more to do with not having to think about it mid-mix.
We’ve had Decapitator in the plugin folder since the original. It earned that slot by being the one saturation box that behaves like a hardware unit you stopped fiddling with years ago. The update doesn’t rewrite that relationship. It tightens the screws.
So what actually changed, and more to the point, which modes still get reached for when a track is actually being finished?
The five modes, honestly ranked
Decapitator’s core is the mode selector: A, E, N, T, and P. Each one models a different analog circuit’s saturation curve. If you’ve used it before, none of these are new. What version 6 refines is the underlying modeling and the way the Drive and Punish controls interact with the tone stack.
Our own ranking, based on what actually gets used session to session:
- Mode A: The all-rounder. Sits on drums, guitar, and synth without complaint. It’s the one we patch in first when someone says a part feels flat.
- Mode E: Brighter characteristic, useful on vocals where the added upper harmonic makes a line cut without an EQ.
- Mode N: Darker, thicker. If a bass is thin, this is the one that adds weight before the sub gets touched.
- Mode T: The tape-flavored one. Best for bus work where you want saturation you can hear but not pinpoint.
- Mode P: The most aggressive. Reserved for parallel destruction or sound design. On a main channel it almost always goes too far unless the Drive is barely cracked.
Punish is the wildcard. The chip-based, crunchy extra bit of drive that you either love or ignore. We ignore it about 80% of the time. The other 20% it’s on a sound design layer where nothing else will do.
What version 6 actually improves
The headline for us is the stability around parameter changes. Automation of Drive used to be a little steppy in a way that could bite you on a vocal ride. That’s been smoothed out.
The oversampling behavior is also cleaner. When we push the plugin hard on a master, the aliasing fingerprint that used to sit under the material in the high mids is less present. Not gone, but reduced enough that we don’t reflexively reach for a low-pass after the Decapitator any more.
The interface tweaks are small: better scaling on high-DPI monitors, and a slightly clearer read on the input and output meters. We’re not going to pretend the old one was hard to read, but the new one is easier to glance at during a long session.
It is not a new plugin. If you were hoping for a new mode or a redesign of the tone controls, that’s not what this is. Set expectations accordingly.
The misuse that kills a mix
The single biggest mistake with Decapitator is leaving Drive high across every track. It sounds great soloed and muddy in context. Saturation is additive. If every element is being pushed, nothing is. The mix flattens into a wall of harmonics and you lose the ability to make anything stand out.
Our approach: one or two elements get the aggressive treatment, the rest get either nothing or a whisper of Mode T on the bus. Saturation is a spice. Not a base ingredient.
The other one: using Decapitator to fix a weak arrangement. If a part feels dull because it’s clashing with the kick, no amount of drive is going to resolve it. That’s a balance problem. Reach for the fader first.
And watch your output level. Decapitator’s gain staging is not forgiving. The auto-gain button helps, but it’s not a limit, and we’ve seen plenty of masters where the only issue was a Decapitator bumping the peaks up a couple of dB into the limiter. Watch the meters, trim the output, move on.
The unwanted answer to the version 6 question
Most people don’t need to upgrade. Version 5 still sounds like version 5 and if that’s working in your sessions, the refinements in 6 are not going to change a record.
Upgrade if you automate Drive heavily, work at high sample rates, or use a 4K monitor and got tired of squinting. Otherwise the money is better spent somewhere else in the chain.
The one caveat: the version 6 installer is straightforward, but the update path from older licenses can be fiddly depending on where your licence sits (iLok vs Soundtoys account). Back up your plugin folder before running the installer. It’s the kind of thing that eats an evening when you want to be tracking.
Where Decapitator still wins
We keep coming back to it because it sounds like an instrument rather than a processor. The modes are distinct and characterful. The tone stack is musical. Punish does something no other plugin does well.
But it’s not the only saturation tool. If you’re mastering and you want frequency-specific control, Saturn 2’s multiband approach gives you more precision, and its tube setting handles harmonic distortion and compression with a flexibility Decapitator can’t match. If you’re looking for something cleaner to glue a full bus, a tape-oriented plugin with a subtler fingerprint is often a better fit. Decapitator’s strength is character, and character is not always what a mix needs.
For a distortion on individual parts, a parallel destructor, or a low end that needs teeth, it’s still the first one we open. Version 6 makes that case easier without changing the argument.
One more thing that applies across the whole line: sound design and heavier saturation work benefit from splitting the signal into bands before driving it. The reason is straightforward. When you divide the signal, you’re no longer pushing every frequency the same way, and the character stays where you want it. Push the mids through Decapitator and leave the highs cleaner and the lows leaner. It’s the difference between a distorted element that fits and one that eats the mix.
That’s the real version 6 takeaway. The update is respectable. The workflow question is whether you’re using the plugin like a producer or like someone who just bought a saturation tool and wants to hear it on everything. First is a craft decision. Second is a season.