How Audio Compression Trims File Size
What this compressor does
Compressing audio here means re-encoding a recording at a lower bitrate — and, if you want, at a lower sample rate or with fewer channels — so the file carries less data for every second of sound. The tool decodes your source with the browser's Web Audio API, applies the settings you choose, and re-encodes the result to MP3 using an in-page LAME encoder (lamejs).
You can start from one of four presets — High Quality, Medium, Small Size, or Minimum Size — or open the custom panel and set the bitrate, sample rate, and mono or stereo yourself. An optional normalize step evens out the volume before encoding.
When to reach for it
It earns its place when a file is too heavy for where it needs to go: an email attachment, a chat app with an upload limit, or a podcast host that bills by storage. Spoken-word content — interviews, lectures, voice memos — is the easiest win, because speech stays clear at bitrates well below what music needs.
The Minimum Size preset is tuned for exactly that, trading away fidelity you won't notice in speech for a much smaller result. For music you still want to enjoy, High Quality at 192 kbps holds up well while cutting size.
A concrete example
Say you have a 60 MB stereo WAV of a recorded talk. Switching to mono immediately halves the channel data, and re-encoding to a 96 kbps MP3 instead of raw PCM drops it sharply — often to a few megabytes. Before you commit, the estimated size and compression ratio update as you change settings, so you can aim at a target — under 10 MB, say — and see whether your choices reach it without processing the whole file first.
Formats, quality, and limits
You can load MP3, WAV, OGG, FLAC, AAC, or M4A files up to 500 MB, and the output is always MP3. Lower bitrates shrink the file but discard more detail, so the trade-off becomes audible past a point — 64–96 kbps suits voice, while 128–192 kbps keeps music pleasant.
Because everything runs on your own machine, very long or high-resolution files can exhaust the browser's memory; when that happens, a shorter clip or a smaller source usually processes cleanly. A file with an unusual or unsupported codec may fail to decode, in which case converting it to a common format like WAV first tends to fix it.