Guides

Best Export Bitrate for Slowed Reverb on YouTube, Shorts and TikTok

2026-01-03 · Updated 2026-10-11

What bitrate reaches listeners after YouTube and TikTok re-encode, why the source file matters more than the export setting, and when you need a DAW and a lossless master.

Bitrate questions come up constantly from people posting slowed edits, and most of the answers online are either sales copy ("export at 320 kbps for studio quality") or wrong in the other direction ("bitrate does not matter"). The truth sits in the middle and depends on where the file is going.

This guide is going to be unusually direct about our own tool. The free slowed reverb maker on this site exports MP3 at 96 kbps, 32 kHz, and nothing else. No WAV, no FLAC, no 320 kbps option. We will explain why that is the right choice for YouTube, Shorts, TikTok and Reels, why it is not the right choice for a streaming release, and what to do in each case. Along the way it should become clear why the quality of the file you load, whether that is an MP3, a WAV or a FLAC, matters far more than the number on the export.

What bitrate means, briefly

Bitrate is how many bits per second a compressed audio file spends describing the sound. Higher means more detail kept, lower means more thrown away. Lossy codecs like MP3 and AAC throw away the parts of the signal a model of human hearing says you are least likely to notice, starting with very high frequencies and quiet sounds masked by louder ones.

For MP3 specifically:

Sample rate is a separate number. 44.1 kHz is CD standard and can represent frequencies up to 22 kHz. 32 kHz can represent up to 16 kHz. Since a 96 kbps MP3 encoder cuts above about 15 kHz anyway, pairing 96 kbps with 32 kHz loses nothing further and lets the encoder spend its bits on the range it is actually keeping.

What happens when you upload

This is the part most guides skip. No major platform plays your file. Every one of them decodes what you upload and re-encodes it into their own formats at their own bitrates, so the bitrate that reaches listeners is theirs, not yours.

These are observed behaviours, not published specifications, and the platforms change their encoders without announcement. The precise numbers matter less than the pattern: the platform's encode is the bottleneck.

Two consequences follow:

1. Uploading a 320 kbps file does not get listeners a 320 kbps stream. It gets them the platform's AAC stream, re-encoded from your 320 kbps file.
2. Every re-encode loses a little. A 96 kbps MP3 re-encoded to 128 kbps AAC loses less than you would think, because the AAC encoder has more bits than it needs to describe what is left. A 64 kbps file re-encoded would lose more, because the artifacts in it are now part of the signal the AAC encoder is trying to preserve.

The honest summary: for YouTube, Shorts, TikTok and Reels, the difference between uploading at 96 kbps and at 320 kbps is small, and much smaller than the difference the platform's own encoder makes. We have compared our 96 kbps exports against higher-bitrate exports of the same edit after upload and the differences are at the edge of what we can hear on good headphones, and inaudible on a phone.

Why our export is 96 kbps and 32 kHz

Because the editor encodes in your browser, in a web worker, with no server. A 320 kbps encode of a five-minute slowed track at 44.1 kHz would take several times longer on a phone and produce a file three times the size, for a gain that the platform then throws away. 96 kbps at 32 kHz is tuned for that constraint: fast enough to be usable on a mid-range Android, small enough to batch twenty tracks into a ZIP, and good enough that the platform re-encode is the limiting step rather than our file.

We could add a higher bitrate option. We have chosen not to for now because it would mostly give people a slower export and a false sense of quality on platforms where it makes no difference, and it would still not be a master, which is what people who ask for 320 kbps usually need. The right answer for them is in the DAW section below.

What we will not do is claim this is studio quality. It is not. It is social-platform quality, and we would rather say that plainly.

Why the source matters more than the export

Think of the chain as a series of filters. The final quality is limited by the worst one.

• Source: 320 kbps MP3 or lossless. Export at 96 kbps. Platform re-encodes to about 128 kbps AAC. The weakest link is our 96 kbps export, which is clean to about 15 kHz. Result: fine.
• Source: 128 kbps MP3 from a questionable site. Export at 96 kbps. Platform re-encodes. Now the source already had artifacts, slowing moved them down into clearly audible range, our encoder preserved them faithfully, and the platform's encoder preserved them again. Result: swirly cymbals and a watery top end, and no export setting would have saved it.
• Source: a video rip that has already been through YouTube once. Same as above, worse. The file has been lossy-encoded at least twice before you touched it.

Slowing is particularly unforgiving here. Pitch drops with speed, so the compression damage that lived above 15 kHz in the original, where most people cannot hear it, is at 12.6 kHz after a 0.84x slow. Reverb then takes that damaged top end and smears it across time.

The practical rule: spend your effort on the input. A purchased 320 kbps MP3, a FLAC from Bandcamp or a CD rip to WAV all give the editor something clean to work with. The export setting is fixed and it is fine. The source is your choice and it is decisive.

A decision table

When you need a DAW

Three situations, and they are all about the destination rather than the platform.

A release through a distributor. Spotify, Apple Music and the rest take WAV or FLAC and encode to their own formats. They expect a lossless master and some distributors reject MP3 outright. The browser editor cannot produce that file. Audition the edit here, note the settings, then rebuild it in a DAW from a WAV source and export WAV. The online vs DAW guide walks through carrying settings across. Note also that releasing a slowed version of someone else's song through a distributor needs a licence, which is a separate and larger question covered in the copyright guide.

Work for a client. If someone is paying for a slowed edit, they expect a WAV. Even if their end use is TikTok, delivering a 96 kbps MP3 looks careless and gives them nothing to work from.

Further processing. If the slowed edit is going into a video project where you will add more effects, mix it with voiceover or master it alongside other tracks, start from lossless. Each lossy generation compounds.

In every other case, which is most cases, the browser export is the right tool: faster, no install, and the platform discards anything beyond what it gives you anyway.

Loudness is the setting that actually matters

If you want your slowed uploads to sound as good as possible on YouTube and TikTok, bitrate is the wrong thing to worry about. Loudness is the right one.

YouTube normalises audio to a target level, around -14 LUFS integrated, and turns down anything louder. TikTok does something similar. Slowed edits with heavy reverb and a big bass shelf are often quieter in perceived loudness than the original, because reverb spreads energy out and the bass boost eats headroom. The platform will not turn a quiet upload up, so a slowed edit that peaks fine but sits at -20 LUFS will play back noticeably quieter than the videos around it.

The browser editor handles clipping but does not have a loudness target. If your uploads sound quiet next to others, the fix is in your video editor or a DAW: normalise the slowed MP3 to around -14 LUFS before you attach it to the video. The video guide covers where that step sits in the workflow.

Settings that help a 96 kbps export sound its best

Small choices in the edit itself affect how well the file survives encoding, both ours and the platform's.

• Tone at -2 or lower. A slightly darker top end gives the encoder less high-frequency content to describe, so it spends its bits on the midrange where the vocal lives. Slowed edits usually want this anyway.
• Width at 1.2 or below. Very wide stereo is expensive to encode because the two channels share less information. It also sums badly to a phone speaker.
• Reverb under 50%. Dense reverb tails are noisy signals that encoders handle poorly at low bitrates. The clean-vocal range of 35 to 42% also happens to be encoder-friendly.
• A clean source. Said already, worth saying again.

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.