How to Make Slowed Reverb Songs: Complete Tutorial and Preset Workflow

Making a slowed reverb edit is genuinely easy — upload, drag two sliders, download. You can do it in ninety seconds and the result will be recognisably the thing you were going for.

Making a good one is a different exercise, and the gap between the two is not talent or expensive software. It is a small number of decisions that are easy to get wrong and hard to diagnose afterwards, because the symptoms all sound alike. Everything muddy sounds like too much reverb even when it is not.

This tutorial covers the fast version first, then the reasoning underneath it: what order to set the controls in and why that order is not arbitrary, how to read a bad result back to its cause, and one specific trap in the settings that quietly undoes the thing you were trying to do.

1. The Ninety-Second Version

If you want a result right now, this is the whole procedure. Everything after it explains why these numbers rather than others.

• Open the slowed reverb generator. No account, no install — it runs in the browser and your file never leaves your device.
• Drop in an MP3, WAV, FLAC, or OGG. Use the best-quality version you have; this matters more than any setting you will touch later.
• Click the Slowed + Reverb preset. That sets 0.85x speed, 42% reverb, 2.8s decay, +1 semitone, and +3 dB bass.
• Play the chorus, not the intro. The loudest passage is where problems live, and the intro will happily convince you everything is fine.
• Adjust one thing, listen, then adjust the next. Never two at once.
• Download MP3 to post it, WAV if anything else will process it afterwards.

2. Set Speed First — This Is Not a Preference

The order matters, and speed genuinely has to come first. The reason is that slowing a track with varispeed does not only change tempo; it lowers every frequency in the recording by the same ratio. The whole track relocates down the spectrum.

That has consequences for every other control. Your bass setting is aimed at a fixed frequency region, so once the music moves, the boost is catching different material than it was — usually more of it, because content that sat above the corner has descended below it. Your reverb decay is being judged against a tempo that no longer exists; a 3-second tail that felt spacious at full speed may overlap the next phrase once everything is 18% longer.

So a bass level and a reverb decay dialled in before you set the speed are answers to a question you then changed. Set speed, live with it, and judge everything else against the slowed version.

For the record: 0.80x to 0.88x is where the genre has settled, and 0.85x is the single most common value. Below 0.75x, lyrics start to become genuinely hard to follow. Above 0.92x, most listeners will not register that anything was done.

3. The Pitch Trap

Here is the mistake that is worth the whole tutorial, because almost every guide on the internet recommends it without noticing what it does.

The standard advice when a slowed vocal sounds too dark is to add a semitone or two of pitch to brighten it back up. On this tool — and on most browser tools, because they are built the same way — speed and pitch are applied to the same playback rate, which means they multiply rather than operate independently.

Add +1 semitone to a 0.85x setting and you are not at 0.85x with a brighter vocal. You are at 0.90x. Add +2 and you are at 0.95x, which is barely a slowed edit at all. The advice to brighten with pitch quietly walks your tempo out of the range that made it a slowed edit in the first place, and because the change is gradual, it feels like it worked.

The tool now displays the combined rate whenever pitch is not zero, so you can see this happening. But the better fix is simply to use speed: if 0.82x sounds too dark, try 0.85x. You wanted a slightly faster, slightly brighter edit, and speed gives you exactly that with one control instead of two fighting each other.

4. Reverb: Wet and Decay Do Different Jobs

These two get conflated constantly, and the distinction is the difference between an edit that sounds spacious and one that sounds smeared.

Wet mix is how much of what you hear is reverb rather than the original. It controls how present the effect is. Decay is how long each reverb tail lasts. It controls how big the implied space is.

The failure mode people run into is raising wet when they wanted decay. Wanting a bigger, more atmospheric sound, they push the wet mix to 60% — and the vocal disappears behind a wash without the space actually feeling any larger. A longer decay at a lower wet mix gives you the cathedral; a high wet mix at a short decay just gives you less vocal.

Practical ranges: 35–45% wet suits most edits, with 30–35% when lyrics matter. Decay at 2.0–3.0s for vocal-forward tracks, 3.5–4.5s for dreamy and ambient. Past about 5 seconds you are making a specific artistic choice rather than a slowed edit, which is fine, but be doing it deliberately.

One tempo-dependent rule worth internalising: if one note's tail has not meaningfully decayed before the next note arrives, you are no longer adding space, you are adding mud. Slow, sparse tracks tolerate long decays. Busy ones do not.

5. Bass: The Least Free Control

Bass feels like a taste setting and is actually the most constrained control on the page, because it is the one that can run you out of headroom.

Boosting is addition rather than redistribution. Whatever you add has to fit under the digital ceiling at 0 dBFS, and how much room is available is a property of your specific file — not of the genre, and not of the slider position. A quiet, dynamic recording has room to spare. A modern master pushed close to the ceiling has essentially none, and the boosted low end gets flattened into distortion the moment the kick lands.

This is why '+5 dB of bass' is not meaningful advice on its own, and why the same setting sounds enormous on one track and like crackling mush on another. If your edit is distorting, the reverb is usually not the culprit — the bass is.

The reliable approach is to measure rather than guess. Run the file through the volume booster first, which reports how much headroom you actually have, then treat that number as a budget. There is a full explanation of the arithmetic if you want it. Failing that, +2 to +4 dB is a safe default, and judge it on headphones — a laptop speaker cannot reproduce the range you are adjusting, so you will reliably push it too far trying to hear something the hardware was never going to produce.

6. Troubleshooting by Symptom

Most bad edits are one of six things, and they are much easier to fix when you can read the symptom back to its cause rather than randomly adjusting.

• Muddy, can't hear the words — usually decay too long for the tempo, not wet too high. Shorten decay before you reduce wet, or you will lose the atmosphere along with the mud.
• Crackling or distorted, especially on the low end — headroom, not reverb. Reduce the bass boost, or lower the overall level and boost afterwards.
• Sounds thin and weak — the slowdown moved the low end down and possibly out of what your playback can reproduce. A small bass boost is the correct fix here; this is what it is for.
• Swirly, watery, metallic in the cymbals — the source file. Lossy compression artefacts stretch along with the music, so a 128 kbps rip that was fine at full speed becomes audible at 0.85x. No setting fixes this; find a better source.
• Barely sounds different from the original — check the combined rate. If you added pitch, you may have undone the slowdown without realising.
• Fine on your laptop, wrong on your phone — you mixed on speakers that cannot reproduce bass. Always check bass decisions on headphones.

7. Starting Points by Genre

These are opening positions, not destinations. Every one of them assumes you will preview the chorus and adjust. Note that pitch is 0 throughout — for the reason in section 3, brightness is better handled with speed.

• All-purpose — 0.85x, 40% wet, 2.8s decay, +3 dB bass.
• Pop / vocal-forward — 0.85x, 35% wet, 2.5s decay, +2 dB bass. Keep wet down so the hook survives.
• Sad / emotional — 0.78x, 42% wet, 3.5s decay, +3 dB bass. The slowest setting here that still keeps lyrics intelligible.
• Rap / lyric clarity — 0.82x, 30% wet, 2.0s decay, +2 dB bass. Short decay is doing the work; dense verses cannot tolerate long tails.
• Phonk / bass-forward — 0.86x, 25% wet, 2.0s decay, +5 dB bass. Reverb stays out of the way of the low end.
• Lo-fi / chill — 0.88x, 35% wet, 2.5s decay, +3 dB bass. The gentlest slowdown in the list.
• Short-form video — 0.80x, 40% wet, 2.5s decay, +4 dB bass. Slightly exaggerated, because platform compression flattens subtlety.

8. Exporting: MP3 or WAV

The rule is short: export lossy only when the file is the final artefact.

If the edit is going straight to a platform and nothing else will touch it, MP3 at 320 kbps is fine — about 2.4 MB per minute, so roughly 7 MB for a three-minute track. If it is going into a video editor, export WAV. The editor will encode when it renders, and handing it a WAV means the only lossy step left is that one. WAV runs about 10.6 MB per minute at CD quality, so around 32 MB for three minutes.

The reason to care is generation loss. Each pass through a lossy encoder discards detail, and the losses accumulate — the second encoder cannot recover what the first removed, and makes its own cuts on top. Most people posting an edit are four or five generations deep and have deliberately chosen one of those steps. There is a fuller treatment of formats if you want the detail.

One thing worth knowing about platforms: essentially all of them normalise loudness on playback, which means making your export as loud as possible achieves nothing except reducing your headroom. Published targets shift over time and differ per service, so rather than chasing a number, leave yourself margin below the ceiling and let the platform do what it will do regardless.

9. Habits That Separate Good Edits From Bad Ones

None of these are difficult. They are just easy to skip.

• Preview the chorus, never the intro. Problems live in the loud parts.
• Change one control at a time and listen between changes. Stacking adjustments makes the result impossible to diagnose.
• A/B against the original often. Ears normalise to whatever they have been hearing for two minutes, and over-processing creeps.
• Judge on headphones. Laptop and phone speakers hide exactly the problems that matter.
• Start from the best source you can get. It is the one variable nothing downstream can repair.
• When it sounds wrong, diagnose before adjusting. The symptom table above will usually get you there faster than instinct.

The Short Version

Set speed first, because it moves everything else. Use speed rather than pitch to control brightness, because on this tool they share one playback rate and adding pitch speeds the track up. Use decay rather than wet to control the size of the space. Measure your headroom before boosting bass. Preview the loudest section on headphones.

That is genuinely the whole craft. Open the generator and try it on a track you know well — the fastest way to hear what each control does is to move exactly one of them.