Guides

Why Your Slowed and Reverb Sounds Muddy (And How to Fix It)

2026-10-11

A diagnosis guide for muddy slowed edits: reverb mix too high, stacked bass, dark tone with a long tail, a weak source, phone speaker summing. The fixes, in the order to try them.

Muddy is the word everyone uses and nobody defines. In a slowed + reverb edit it usually means some combination of: you cannot make out the lyrics, the kick has no point, the whole thing sounds like it is coming through a wall, and turning it up makes it worse rather than clearer. The style flirts with all of those on purpose. The trick is staying on the right side of the line.

Mud has a small number of causes, and they are easy to tell apart once you know what to listen for. This guide goes through them in the order you should check, from the most common to the least, with the specific fix for each in the free slowed reverb maker. Two controls come up repeatedly, Bass and Tone, because they are the ones that stack with reverb to cause the problem. If your edit is a vocal track and the words are the issue, the clear vocals guide is the companion to this one.

First, a one-minute test

Before adjusting anything, do this:

1. Play the edit through headphones. Note what sounds wrong.
2. Switch to the Dry preset mid-playback. Is the source itself clear at this speed? If not, the problem is the file or the speed, not the effects.
3. Switch back. Lower Reverb to 20%. Did the mud go away? If yes, cause 1. If only partly, keep going.
4. With Reverb still at 20%, set Bass to 0. Did it clear up more? Cause 2 is in play.
5. Set Tone to 0. If this made a big difference, cause 3.

Most muddy edits are solved by step 3 alone. The rest of the guide goes through each cause in detail so you can fix it without losing the sound you wanted.

Cause 1: the reverb mix is too high

This is the cause nine times out of ten. Reverb in this editor is a wet mix, and above about 45% the dry signal that carries all the detail, the consonants, the drum transients, the pick attack, is being replaced by a smeared copy of itself. Turn the mix up far enough and there is no detail left to hear.

How to recognise it: words run together inside a line. The kick is a thud. Everything sounds equally distant.

The fix: lower Reverb in steps of 5 until the detail returns. For vocal tracks that is usually 35 to 42%. For instrumentals you have more room, up to 55%. If you lose too much of the atmosphere when you do this, add it back with Space instead: raise the decay by 0.4 to 0.8 s. A longer tail at a lower mix gives you the sense of a big room without burying the source. The reverb decay guide explains that trade in depth.

Cause 2: bass stacking

Slowing a song already moves every frequency down. A kick at 60 Hz goes to 50 Hz at 0.84x. Bass guitar, low synths and the body of male vocals all shift down into a region that most headphones exaggerate. On top of that, the Bass control is a low shelf that can add up to +12 dB. And on top of that, reverb tails are bass-heavy by nature because real rooms absorb highs faster than lows.

Three sources of low-end energy, stacked. The result is a boom that sits under everything and masks the midrange where the detail lives.

How to recognise it: the edit sounds heavy and thick but not clear. Turning it up makes your headphones rattle before the vocal gets louder. On a phone speaker it just sounds quiet, because the speaker cannot reproduce the energy you added.

The fix: lower Bass to +3 or +4 dB. That is usually enough for the slowed feel. Go higher only on sparse rap and trap where there is nothing in the low mids for the shelf to collide with. If you are at Reverb 50% and Bass +10, you have both cause 1 and cause 2, and fixing either one on its own will not be enough.

A useful habit: set Bass last, after Reverb and Space, and set it while listening to a section with both the kick and the vocal. If the vocal gets thinner as you raise Bass, you have gone past the point where the shelf is helping.

Cause 3: dark tone plus long decay

Tone is a high shelf. Negative values cut the top end of the whole signal, dry and wet together. The reverb tail also loses highs over time, because the convolution reverb models a real space where air and surfaces soak up treble. A long Space value gives the tail more time to darken.

Set Tone to -8 and Space to 4.5 s and you have two independent darkening processes working on the same signal. Everything above 4 kHz, which is where consonants, cymbal detail and the air in a vocal live, is gone.

How to recognise it: the edit is not necessarily boomy, but it sounds like it is under a blanket. Sibilance is missing. You cannot tell an s from an f. Hi-hats are just a tick.

The fix: pick one. Either keep the long decay and bring Tone back to -1 or -2, or keep the dark Tone and shorten Space to 1.6 to 2.2 s. The Haze Chamber preset is a good illustration: it runs Tone at -10, the darkest possible, but pairs it with a very short 1.2 s decay. The darkness comes from the shelf, not the tail, and the result is dense rather than muddy.

Cause 4: the source file

Every lossy encoder throws away high-frequency detail first. A 128 kbps MP3 is usually clean to about 16 kHz and smeared above that. A 96 kbps file is smeared from 14 kHz. A YouTube rip run through two or three generations of re-encoding can be smeared from 12 kHz and have swirly, watery artifacts in the upper mids.

Slow that file to 0.84x and everything moves down three semitones. The smear that was at 14 kHz is now at 11.8 kHz, well into the range where you hear it. Add reverb, and the reverb is now reverberating artifacts.

How to recognise it: the Dry preset at your chosen speed already sounds wrong. There is a watery or underwater quality that reverb did not add. Cymbals sound like they are made of paper.

The fix: there is no setting that repairs a bad source. Tone at -2 can hide some of it, but you are hiding the problem by also hiding real detail. The actual fix is a better file: a purchased 320 kbps MP3, a FLAC or a WAV. The FLAC page covers using lossless sources. If the only copy you have is a low-bitrate one, keep the speed at 0.88x or above so the artifacts move down less.

Quality of the source matters more than the quality of the export. The editor exports MP3 at 96 kbps, 32 kHz, and that is fine for YouTube and TikTok because the platforms re-encode, but the input needs to be as clean as you can get it.

Cause 5: phone speaker summing

You made the edit on headphones. It sounded wide, deep and clear. You played it on your phone and it sounded like mush. Nothing changed in the file. What changed is the speaker.

Phone speakers are mono or close to it, have no output below about 150 Hz, and have a peak somewhere around 2 to 5 kHz. Three consequences:

• Width collapses. A Width setting of 1.3 or 1.5 relies on the difference between left and right channels. Summed to mono, that difference partly cancels, and the reverb, which is the widest part of the signal, can disappear or sound hollow.
• Bass vanishes. All that +8 dB low shelf is below the speaker's range. It did nothing except eat headroom and make the file quieter overall.
• Reverb blurs. Small speakers do not resolve the fine time detail of a reverb tail. A 40% mix on headphones is a 55% mix on a phone, in effect.

How to recognise it: clear on headphones, muddy on the phone.

The fix: make the edit on headphones, then always check on a phone speaker before posting. If it falls apart there: Width to 1.0, Bass down to +3, Reverb down 5 points. Re-export. Most of your audience is listening on exactly that speaker.

Cause 6: too slow for the material

Less common than the others but worth checking. Below about 0.78x, vocals in a low register lose their definition regardless of effects. Dense arrangements with a lot of midrange, rock and orchestral music especially, pile up as everything shifts down into the same band.

How to recognise it: the Dry preset at your chosen speed is muddy even with no reverb and no EQ.

The fix: go up. 0.85x solves most of it. If you need the deep feel, keep the speed and compensate: Reverb down to 32%, Bass at +2, Tone at -1. The speed guide has more on matching speed to material.

The fix order

If an edit is muddy and you do not know why, this sequence resolves it with the fewest steps:

1. Reverb down to 35%. Listen.
2. Bass down to +4. Listen.
3. Tone up to -2. Listen.
4. Width to 1.0 if you are checking on a phone.
5. Speed up 0.03x if it is still unclear with everything above.
6. Check the source with the Dry preset. If it is bad, find a better file.

Then add things back one at a time until it starts to blur, and stop one step before that.

A clean and a muddy version, side by side

The second column is still unmistakably a slowed + reverb edit, deep and spacious. It just lets the song through.

When mud is the goal

Some edits want to sound like they are coming through a wall from the apartment next door. That is a legitimate aesthetic, and the ambient and lo-fi end of the style lives there. The difference between intentional haze and accidental mud is that in the intentional version you can still hear a shape: the kick still marks time, the vocal melody is still followable even if the words are not. If you want that sound, start with the Haze Chamber preset, lower Bass to +6 so it does not boom, and keep Width at 1.2 or below so it survives on phones.

Open the free editor: upload MP3, WAV, AAC, OGG or FLAC, adjust speed, reverb, bass, tone, width and space, then export MP3 or a ZIP of many tracks. Everything runs in your browser.