Audio Compressor

Why compress audio files?

Audio files can be surprisingly heavy. A few minutes of uncompressed WAV can run to tens of megabytes, a high-bitrate podcast episode can balloon a download, and lossless FLAC albums easily fill a drive. Whether you’re emailing a voice memo, uploading a podcast, attaching a song to a message, or saving space on your phone, shrinking the file makes everything faster and cheaper to move and store — usually with no audible difference at sensible settings.

Because this tool runs entirely on your device, it is also the private way to do it. Most online audio compressors upload your recording to a remote server, process it there, and send it back — which means a copy of your voice or music sits on someone else’s machine. Here, your file is read into memory, re-encoded with a WebAssembly build of FFmpeg, and handed straight back to you. It never touches a network.

That local-only design has practical benefits beyond privacy. There are no upload or download waits for the file to cross the internet, no queue behind other people’s jobs, and no file-size cap imposed by a server you don’t control. The first time you use the tool it downloads the FFmpeg engine once; after that, the same engine is reused for every file, and even repeated compressions stay fast because all the work happens on your own processor.

Bitrate vs. quality: how to choose

The single biggest lever on audio file size is the bitrate— the number of kilobits used to store each second of sound, written as kbps. Halve the bitrate and you roughly halve the file. The trade-off is that lower bitrates discard more detail, so the goal is to pick the lowest bitrate at which your ears still can’t tell the difference.

Bitrate also interacts with the kind of audio you’re encoding. Dense, complex music — busy mixes, cymbals, distorted guitars — is harder to compress and benefits from a higher bitrate, while a simple voice recording stays clear even when squeezed hard. There’s no single “correct” number; the best setting is the one that sounds clean on the speakers or headphones your listeners will actually use. A quick way to decide is to export the same clip at two bitrates and compare them back to back. Use these as starting points:

• 256 kbps — near-transparent for music; choose this when you want the smallest file that still sounds essentially like the original.
• 192 kbps — excellent quality for music with a meaningful size saving over the source.
• 128 kbps— the classic all-rounder. For most listeners it’s indistinguishable from CD-quality music on everyday speakers and headphones, at a fraction of the size.
• 96 kbps— ideal for spoken-word content such as audiobooks, podcasts and voice memos, where there’s no music to preserve.

One important caveat: both MP3 and AAC are lossy, and re-encoding a lossy file always throws away a little more. Always compress from the highest-quality source you have, and never re-encode a file you’ve already compressed at a low bitrate up to a higher one — that only inflates the size without recovering any lost detail.

It also helps to know what a target file size implies in practice. Bitrate is roughly file size divided by duration, so a one-minute clip at 128 kbps lands around one megabyte, and a typical three- to four-minute song at the same bitrate comes in near three to four megabytes. If you have a hard size limit to hit — an email attachment cap, an upload form, or a messaging app — divide that limit by the track length to estimate the bitrate you can afford, then round down to the nearest preset.

MP3, AAC, WAV and FLAC explained

Audio formats fall into two camps. Lossless formats like WAV and FLAC keep every sample of the original recording — WAV stores it uncompressed (huge), while FLAC packs it smaller without losing anything. Lossy formats like MP3, AAC and OGG permanently remove sound the human ear is least likely to perceive, which is how they achieve dramatic size reductions. You can read a clear technical overview of these codecs in MDN’s guide to web audio codecs.

This is exactly where the biggest savings live. Converting a WAV or FLAC file to a 128 kbps MP3 or AAC routinely cuts the size by 80–90%, because you’re moving from storing every sample to storing only what you can hear. If you’re keeping a master archive, hold on to the lossless original — but for sharing, streaming or uploading, a lossy copy is almost always the right call. When you need maximum compatibility, pick MP3; when you want the best sound at a given bitrate or you’re in the Apple ecosystem, pick AAC (.m4a).

A common point of confusion is the difference between a container and a codec. An .m4a file is a container that usually holds AAC-encoded audio, while .mp3is both a container and its codec. OGG, meanwhile, is a container that most often carries Vorbis or Opus audio. This tool always hands you a clean MP3 or AAC result regardless of what you put in, so you don’t have to worry about mismatched extensions or files that won’t open — the output is exactly what its name says it is and plays in browsers, phones, car stereos and editing software alike.

Tips for the best results

• Match the bitrate to the content.Drop spoken-word recordings to 96 kbps and reserve 192–256 kbps for music you want to keep close to the source.
• Don’t up-convert.Re-encoding a 96 kbps file at 256 kbps won’t restore quality; it just makes the file bigger. Start from the best original you have.
• Extracting audio from a clip? If your sound is trapped inside a video, shrink the video first with the video compressor, which re-encodes the audio track as part of the job — then bring the exported audio here for finer control over bitrate and format.
• Keep a lossless master. Compress copies for sharing, but archive the original WAV or FLAC so you can always re-export at a different quality later.
• Mind your device on huge files. Because encoding runs in your browser, a several-hundred-megabyte WAV needs a fair amount of memory. On a phone, compress one big file at a time and close other tabs if you hit a slowdown.