Skip to content

Compress an audio file

Make a recording small enough to email, upload or fit on a phone. You choose the bitrate and see the estimated size before anything is encoded — no guessing, and nothing is stored.

  • Never stored
  • No queue, no waiting
  • No signup, no watermark

How it works

1

Add your file

Any audio: MP3, WAV, M4A, AAC, OGG, FLAC or WMA. Its current bitrate and size are read straight away, so you know what you are starting from.

2

Choose how small

Pick a bitrate and the estimated size updates as you go. For speech, mono at 64–96 kbps is usually the right answer and can cut the size by ten times.

3

Download the smaller file

The result says exactly how much came off, and warns you if the settings could not actually make it smaller.

What a bitrate buys, and when there is nothing left to save

The bitrate is how many bits of storage each second of sound is allowed, and everything about audio compression follows from it. At 320 kbps an encoder has enough room to keep nearly everything; at 128 it must decide what to discard; at 64 it is discarding a great deal and the decisions become audible — cymbals turn to a hiss, applause turns to static, and reverb tails flutter. The useful shorthand: 192 kbps for music going on a phone, 128 for spoken word, 320 when size is not a concern and you want the safest file.

Compressing an already-compressed file is the case to think about before you press the button. The sound has already been through an encoder that threw away what it judged inaudible; a second pass throws away more, starting from less, and cannot tell the original recording from the first encoder's approximations. Re-encoding a 128 kbps MP3 to 128 kbps saves essentially no space and costs real quality — the worst possible trade. Going from 320 to 192, on the other hand, roughly halves the file for a difference most people cannot hear on most equipment.

Where compression genuinely shines is the first pass from something uncompressed. A WAV runs to about 10 MB a minute; the same recording at 192 kbps runs to about 1.4 MB a minute, and the reduction is around nine tenths for a quality difference that takes careful listening on good headphones to identify. That is the compression worth doing, and it is why the format took over.

Speech has far more headroom than music and is worth treating differently. A lecture, a podcast or an interview at 96 or even 64 kbps in mono is perfectly clear and a fraction of the size — a two-hour recording drops from 170 MB to under 60. Halving the channels alone halves the file, and for a single voice there was never any stereo information to lose.

When you want something else

Variable-bitrate encoding is a better idea than picking one number, and ffmpeg exposes it: ffmpeg -i in.wav -c:a libmp3lame -q:a 2 out.mp3 spends bits on the passages that need them and saves them on the quiet ones, landing near 190 kbps on average with better quality than a fixed 190. -q:a 0 is the top setting, around 245 kbps.

For a library rather than a file, foobar2000 and fre:ac convert thousands of files unattended while keeping tags and artwork, and both are free. And if the target is a modern device rather than an old one, Opus at 96 kbps sounds better than MP3 at twice the size — -c:a libopus -b:a 96k — which is a far larger saving than any amount of careful MP3 tuning.

Frequently asked questions

How small can I make it without ruining it?

It depends entirely on what is in it. A single voice stays perfectly clear at 64 kbps mono, which is often a tenth of the original. Music needs 128 kbps at the very least and 192 kbps to be comfortable. Applause, rain and anything crowded needs more than you expect. Halve the bitrate, listen, and only go further if it still sounds right.

Why did my file not get smaller?

Because you asked for a bitrate at or above what it already has. Compressing a 128 kbps MP3 at 192 kbps makes a bigger file that sounds slightly worse — the extra bits are storing the first encoder's mistakes. The page shows the current bitrate and warns you when the setting cannot help.

Should I make it mono?

If it is one person speaking, yes — it halves the size and there is nothing in the second channel worth keeping. For music, interviews recorded with separate microphones, or anything where position matters, keep it stereo.

Does compressing twice make it worse?

Yes, and it is the most common way people quietly ruin a recording. Every lossy encode throws away more, and it never comes back. If you have the original WAV or the first recording, compress from that rather than from an MP3 you made earlier.

Is my file stored anywhere?

No. Nothing is stored, and a big file compresses as readily as a small one — which is the whole point when the file was too big to send in the first place.

What about a two-hour recording?

Fine. The output is written to the browser's own storage as it is encoded rather than held in memory, so length is limited by your disk rather than by the tab. Progress is shown and can be stopped at any point.

Good to know: Compression is lossy and cannot be undone — keep the original. A file already at a low bitrate has little left to give, and re-encoding it costs quality without saving much space.

Put this tool on your website

Free for any blog, class page or help article. Paste one snippet and your visitors can use it right on your page.