
Dithering is a small amount of deliberately added noise that you apply when you reduce a file's bit depth, most often on the final bounce from 24-bit down to 16-bit for a CD or a streaming upload. It sounds backwards to add noise on purpose, but that faint hiss prevents a far worse problem: the harsh, granular distortion that bit-depth reduction creates in the quietest parts of your music. Dither trades an obvious defect for a near-inaudible one.
Bit depth sets how many discrete steps are available to describe a sample's level. 24-bit gives you about 16.7 million steps; 16-bit gives you 65,536. When you convert from 24 to 16 bits, every sample has to be rounded to the nearest available 16-bit step.
For loud, busy passages that rounding is buried and harmless. The problem is the quiet parts, the tail of a reverb, a slow fade to silence, a soft piano note decaying. Down there the signal only uses a handful of steps, and the rounding error follows the music in a correlated way. Your ear hears correlated error not as noise but as : a gritty, granular, slightly metallic texture on the fade. That's quantization distortion, and it's the thing dither exists to kill.
Truncating bit depth without dither doesn't add hiss, it adds distortion that tracks the music. Dither converts that distortion back into honest, unobtrusive noise.
The reason the noise is worth it
Dither adds a tiny random noise to the signal before the rounding happens. That randomness decouples the rounding error from the music, so instead of a distortion that follows the notes, you get a steady, low-level hiss that sits politely in the background. The remarkable part: with dither, signals quieter than a single 16-bit step can still be reproduced on average. You're trading a structured, audible distortion for an unstructured, barely-audible noise floor, and the human ear vastly prefers the latter.
Most mastering tools go one step further with noise shaping: they push the dither noise up into the 15 to 20 kHz region where your hearing is least sensitive, making it even harder to notice. That's why dither plugins often offer several 'noise shaping' curves, they're all the same idea, tuned for different material.
This is where most mistakes happen. The rule is simple: dither only when you reduce bit depth, and only once, at the very end.
| Situation | Dither? | Why |
|---|---|---|
| Final export 24-bit to 16-bit | Yes | You're reducing bit depth; this is exactly what dither is for |
| Exporting at 24-bit or 32-bit float | No | No meaningful bit-depth reduction, so there's nothing to dither |
| Sending to a mastering engineer | No | Leave full bit depth; the mastering engineer dithers as their final step |
| Bouncing stems to import back in | No | Keep them 24-bit+; you'll process them further |
| You already dithered once | No | Never dither a dithered file; stacking dither just adds noise |
The single most common error is dithering more than once, for example dithering a stem, then dithering again on the final master. Each pass adds another layer of noise for no benefit. Dither is the last thing that touches the audio, full stop. Anything after it (even a gain change) technically undoes the careful rounding, which is why it goes dead last in the chain.

Partly. If you deliver a 24-bit master to a distributor or platform, you don't dither at all, you hand off full bit depth and let their pipeline handle conversion. Dither matters when you are the one creating the final 16-bit file: a 16-bit WAV master, a CD, or a download you're selling direct. In practice, the safest modern workflow is to keep everything 24-bit through mixing and mastering and only dither on the specific deliverable that has to be 16-bit.
It's worth being clear-eyed about scale. Dither is a refinement, not a make-or-break, the difference lives in the bottom few decibels of the quietest passages. Get your LUFS targets, your balances and your dynamic range right first; dither is the polish you apply once everything else is finished.
Here's the catch that quietly ruins careful dithering: it only survives in a lossless container. Dither lives in the lowest bits of the file; a lossy MP3 or AAC encoder throws those exact bits away and replaces them with its own quantization noise. So you dither to a 16-bit WAV or FLAC, not to an MP3. And once you've made that pristine 16-bit master, getting it to its destination unaltered is the whole game, drop it into a delivery Room rather than a chat attachment that will helpfully re-compress it for you.
Dithering is a small amount of low-level noise added when you reduce a file's bit depth (for example 24-bit to 16-bit). It prevents quantization distortion, the gritty texture that otherwise appears in quiet passages like fades and reverb tails, by replacing it with a faint, far less noticeable hiss.
Only when you reduce bit depth, and only once, as the very last step in your chain. The classic case is the final export from 24-bit to 16-bit. If you're exporting at 24-bit or higher, or sending to a mastering engineer, don't dither.
No. Dither lives in the lowest bits, and a lossy MP3 or AAC encoder discards those and adds its own noise, so dithering before lossy encoding is pointless. Dither only when creating a lossless 16-bit file like a WAV or FLAC.
When you reduce bit depth without dither, quiet sounds suffer quantization distortion, a gritty, granular distortion on fades, decays and reverb tails. On loud, full passages it's usually inaudible; it's the quiet moments that give it away.
You shouldn't. Each dither pass adds another layer of noise with no benefit. Dither is meant to be the single, final step on the audio. If a file is already dithered, leave it alone.
Noise shaping is an enhancement to dithering that pushes the added noise into the high frequencies (around 15 to 20 kHz) where human hearing is least sensitive, making the dither even harder to perceive. Most mastering dither plugins offer several noise-shaping curves.