Format guide

Slow Down WAV File Online

Slow down a WAV file in your browser with speed, reverb and bass controls. Why WAV is the cleanest source, 16 vs 24 bit, memory use and the MP3-only export.

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.

A WAV file is the best thing you can feed a slowed edit. It is uncompressed, so there are no encoder decisions to be exposed when you stretch it, and whatever quality went into the recording comes out the other side of the speed change intact. The editor above decodes WAV in your browser, slows it anywhere from 0.50x to 1.50x, adds reverb, bass, tone and width if you want them, and encodes the result locally. Nothing is uploaded.

This page is about the WAV-specific details: what bit depth and sample rate mean for your edit, how big these files get in browser memory, and the one thing people most often get wrong, which is expecting a WAV back. The export is MP3, and the reasons and the workaround are below. If your source is compressed instead, the MP3 page covers why bitrate matters, and the FLAC page covers the lossless-but-compressed middle ground. For the controls themselves, start with the slowed reverb maker.

Why WAV is the best source for slowing

Slowing a recording stretches time and lowers pitch. Anything the source got wrong gets stretched too. An MP3 encoder hides its cuts in places your ear ignores at normal speed, and slowing moves those cuts into places your ear notices. A WAV has no such cuts. The high end is all there, the transients are all there, and the quiet reverb tails of the original recording are all there.

In practice this shows up in three places:

• Cymbals and S sounds stay smooth at 0.75x instead of turning into a swirl.
• Reverb tails you add blend with the natural room of the recording instead of sitting on top of a hollowed-out one.
• Deep slowing below 0.75x stays usable for vocals, where an MP3 source would already sound underwater.

If you have a WAV and an MP3 of the same song, always slow the WAV. The difference is small at 0.90x and large at 0.72x.

16 bit versus 24 bit, 44.1 kHz versus 48 or 96 kHz

The honest answer is that 16 bit, 44.1 kHz is all this editor can make use of. The browser decodes every WAV to 32-bit float internally, so bit depth above 16 adds no precision that survives processing, and the MP3 export is 32 kHz, which discards anything above 16 kHz anyway. A 96 kHz file decodes fine but costs double the memory for no audible gain. If you have a hi-res master and a CD-quality version, use the CD-quality version here and keep the master for a DAW.

What does help is that the WAV is a real lossless capture and not an MP3 someone converted to WAV. Converting a 128 kbps MP3 to WAV gives you a large file with all the MP3 artifacts baked in. The container does not restore what the encoder removed.

WAV files are large in browser memory

A stereo 16-bit 44.1 kHz WAV is roughly 10 MB per minute on disk. Once the browser decodes it for processing, it becomes 32-bit float, which is about double that in memory. A four minute song is around 40 MB on disk and around 80 MB decoded. That is fine for a laptop and fine for a phone for a few tracks.

It stops being fine when you load a whole album of WAVs at once on a phone, or a very long DJ mix on any device. The browser tab has a memory ceiling, and when you approach it the page slows down or the tab reloads.

Practical rules:

• On a laptop or desktop, load an album of WAVs freely. If the tab gets sluggish, export what is done and Delete Selected to free memory before loading more.
• On a phone, load three to five WAV tracks at a time. Export, clear, repeat. The bulk converter page describes the group workflow.
• For a very long file, such as a two hour mix, consider slowing it in a DAW instead, where memory is managed on disk.

Loading is also slower for WAV than for MP3 simply because there is more data to read from disk, although decoding is faster since there is no compression to undo.

The export is MP3, not WAV

This is the part to read twice if you came here for a WAV out. The editor exports MP3 at 96 kbps, 32 kHz, encoded in a web worker. It does not export WAV, AIFF, FLAC or any lossless format, and it does not export MP3 at higher bitrates.

The reason is practical. The whole editor runs in the browser with no server, and the MP3 encoder at 96 kbps finishes a track in a reasonable time on a phone. For the destinations most people are aiming at, YouTube, TikTok, Reels and Shorts, this is fine, since each platform re-encodes uploads to its own compressed formats. Your clean WAV source still matters in that chain, because it means the one lossy step you control starts from a clean input. A 96 kbps encode of a WAV-sourced edit sounds noticeably better than a 96 kbps encode of a 128 kbps MP3-sourced edit.

But if your end goal is a lossless file, this editor is not the final step.

If you need WAV output

Use this editor to find your settings, then reproduce them in a DAW that exports WAV. The settings translate directly because the controls are standard audio operations.

Audacity does all of this for free, and the Audacity comparison shows the exact menus. Reaper, FL Studio, Ableton and Logic all do it too. The online versus DAW page lays out when the browser is enough and when it is not.

A reasonable hybrid workflow: audition and batch in the browser for speed, post the MP3s to video platforms, and only rebuild the handful of tracks that need a lossless master in the DAW.

Settings for WAV sources

Because a WAV hides nothing, you can slow further and use less darkening than you would on an MP3. These are starting points.

Note the Tone values are less negative than on the MP3 page. A WAV source does not need its top end hidden.