Free plan: 1 conversion/hour, 1 file at a time
Go Unlimited →

Change Audio Speed

Free Online Audio Speed Changer

Go with your files

*Files deleted after 24 hours

Optimize up to 1 GB files free, Pro users can convert up to 100 GB files; Sign up now

Uploading

0%

How to Change the Speed of Audio

1 Upload the audio files you want to retime.
2 Choose a multiplier — 0.5x for half speed, 2x for double — staying roughly inside 0.75x to 2x if the content is speech.
3 Run it; the time-stretch preserves pitch, so voices stay natural instead of transposing upward.
4 Download the retimed Audio file with picture and sound still in sync.

Change Audio Speed FAQ

Does the source format affect the result?
+
It does. this format is read and written by the same streaming pipeline as everything else we support. That determines whether the retimed result can be written back cheaply or has to be fully re-encoded.
Yes — the codec is detected from the stream, so a mislabelled extension does not derail the job. Worth knowing before you commit to a large speed change.
Concretely, pitch-preserving time-stretch is applied to whatever you uploaded, with the encode path chosen from the source codec. Choose a multiplier — 0.5x for half speed, 2x for double — and the whole file is retimed.
No. The time-stretch preserves pitch, so a 1.5x speech track sounds like the same person talking faster rather than like a chipmunk. That is the difference between a proper time-stretch and simply playing the samples faster.
Yes — ID3, Vorbis comments and MP4 atoms are carried across along with embedded artwork, so processed files still sort correctly in a music library.
MP3, WAV, AAC, M4A, FLAC, OGG, Opus, WMA and AIFF. Codecs are detected from the stream rather than the extension, so a mislabelled file still works and a mixed batch is handled per file.
Yes: free accounts process audio up to 200 MB per file whichever codec you brought; ffmpeg handles the decode and encode. In practice that limit only bites on uncompressed WAV; a compressed file of the same length is nowhere near it.
It depends on the source. Lossless input (WAV, FLAC, AIFF) is edited sample-exactly and loses nothing. Lossy input has already discarded detail once, so where the job can be done by copying the encoded stream rather than re-encoding it, that is the path taken.
WEBP.to is built around the modern replacement for both of the old defaults: one format that does lossy, lossless, alpha and animation, and reliably lands smaller than the JPEG or PNG it came from. People arrive here having decided the old defaults are costing them bandwidth, and that decision immediately raises the rest: what size, what quality, what happens to the transparency. Change Audio Speed is on the same upload and the same account so those questions get answered in one place.
The converter on this site moves images to and from WebP, PNG, JPG and AVIF, which is where you decide whether a smaller file is worth losing the older browsers. Doing it in that order matters: pick the pixels first and the container afterwards, because the container is the cheap decision and the pixels are the expensive one.
The engines are identical — same libraries, same workers, same caps. What is different is the opinion attached, and the opinion here rests on a property of the format this site is named after: the same .webp extension can hold a lossy VP8 frame, a lossless one, or an animation, so the sensible processing path is decided per file rather than per extension.
No account, and nothing is retained: uploads are deleted from the workers shortly after the job finishes, and nothing is inspected, listed or indexed. Accounts exist for history and batch size only.

Rate this optimizer
5.0/5 - 0 votes
ns6.com — Buy your domain from $2/year. Online in minutes.
Or position your files here