BPM Changer
Change the tempo of a track without changing its pitch, then download the result as a WAV. You supply the original BPM; it is not detected. Processing is local to your browser, with no upload.
How to change the BPM of a song
- Choose a WAV, MP3 or M4A file.
- Type its original BPM and the target BPM you want. The target must be 0.5x to 2x the original.
- Select Change BPM. Longer files and slower tempos take longer. Cancel stops the tempo change and discards the run, but a file check or decode already under way finishes in the background first.
- Compare the before and after players, then download.
Examples
The new length is the old length multiplied by original BPM divided by target BPM.
| Original | Target | Tempo | Length |
|---|---|---|---|
| 120 | 150 | 1.25x | 3:00 becomes 2:24 |
| 120 | 96 | 0.8x | 3:00 becomes 3:45 |
| 90 | 180 | 2x | 3:00 becomes 1:30 |
| 140 | 70 | 0.5x | 3:00 becomes 6:00 |
Limits
- Length: up to 5 minutes at up to 48 kHz. Higher sample rates allow proportionally less.
- File size: WAV up to 120 MB, MP3 and M4A up to 20 MB.
- Result: up to 8 minutes at up to 48 kHz, so a 5-minute track cannot be slowed all the way to 0.5x. Higher sample rates allow proportionally less.
- Files whose length cannot be read before decoding are refused, including compressed WAV, free-format MP3, fragmented M4A and M4A that is not AAC, such as Apple Lossless.
- Channels: mono or stereo.
- Tempo: 0.5x to 2x.
- Files near the limit need a lot of memory and may fail on a phone. If that happens, try a shorter file.
How it works
Speeding up playback raises the pitch, so this tool does something else. It uses WSOLA (waveform similarity overlap-add), which rebuilds the track from short overlapping slices of the original, spaced to fit the new tempo and aligned so each slice continues the waveform of the last. It looks for sharp attacks such as drum hits and tries to keep them intact, but this is not reliable: hits that sit close together can be lost, especially when speeding up, so check percussive tracks by ear. The result is real new audio with a different length, not a playback setting.
For a different approach, where speed and pitch are live playback settings rather than a new file, see how the voice modulation demo was built.
Frequently asked questions
Does this detect the BPM of my song?
No. The original BPM is not detected: you type it in. The output length is the original length multiplied by original BPM divided by target BPM, so a wrong original BPM gives a wrong tempo. A DAW or a tap-tempo tool can tell you the BPM first.
Is my audio uploaded?
No. There is no upload. The file is decoded and processed on your device, in your browser, and the result is created there too.
Will the pitch change?
It should not. On test tones and widely spaced click tracks, the downloaded WAV keeps its pitch and the clicks land on the new tempo. Closely spaced hits can be lost, especially when speeding up. No listening test on real music has been done, and large tempo changes can add audible artifacts, so check the result by ear.
What file do I get back?
A 16-bit WAV with the same channel count as your file. WAV input keeps its sample rate; MP3 and M4A input is decoded at 44.1 kHz. Slowing a track down makes the file larger: an 8-minute stereo result at 48 kHz is a WAV of about 92 MB.
Why is there a limit?
Changing tempo holds the original and the result in memory at once, and phones have far less of it than computers. A small compressed file can decode to hours of audio, so file size alone does not protect your browser: the length is estimated from the file before anything is decoded, and ordinary files over the limits, or whose length cannot be read, are refused. A deliberately malformed file can still get past the estimate and take a long time to decode.