You can compress an audio file without uploading it by letting the browser re-encode it at a lower bitrate. The Aihangsoft Audio Compressor runs FFmpeg inside the page, so the file stays on your device while it shrinks. Enter a target size in megabytes and the tool calculates the bitrate for you.
It offers two modes. Target bitrate lets you pick 64, 96, 128, 192, 256 or 320 kbps for a predictable result, while Target file size takes the limit you type and works backwards from the length of the recording to a bitrate, clamped between 32 and 320 kbps, and prints the value it will use. Output is MP3, M4A or OGG, and each run reports the original size, the new size and the percentage saved next to a playback preview. The first run downloads the FFmpeg engine, about 30 MB, and later visits use the cached copy.
An audio file usually fails to travel for one of three reasons: it is too large for an email attachment, above the limit of an upload form, or longer than a messaging app will accept. Compressing it means re-encoding the audio at a lower bitrate, and the saving is predictable once you know the length of the recording. This guide covers the two modes, the arithmetic behind a target size, and the cases where the file cannot get smaller at all.
Audio Compressor
Add an audio file, choose a bitrate or a target size in MB, then download the smaller copy. The encoder runs in the page, so nothing is uploaded.
Why an audio file is too big to send
Size limits are the real reason people reach for a compressor, and the limits are low. Gmail rejects attachments above 25 MB, and many application forms stop at 2 MB or 10 MB. Bitrate is what makes a file that heavy: one hour captured at 320 kbps comes to roughly 138 MB, and the same hour at 128 kbps comes to about 55 MB. An uncompressed WAV is heavier still, since one minute of 44.1 kHz stereo audio takes about 10 MB. Those figures follow one formula, the same one the tool uses: bits per second times seconds, divided by eight.
How to compress an audio file in the browser
The whole job is five steps, and the file never leaves your device.
- Add the audio file. Drop one file onto the compressor or click to browse. MP3, WAV, M4A, AAC, OGG, FLAC and Opus are accepted, and the length is read on your device as soon as the file lands. A video file is refused rather than converted.
- Pick a mode. Target bitrate when you know the quality you want, or Target file size when a form has given you a number in megabytes to stay under.
- Set the value and the output format. Choose a bitrate, or type a size, then pick MP3, M4A or OGG.
- Read the estimate. The panel shows a line such as "Estimated output: about 4.6 MB at 128 kbps MP3", and it updates the moment you change a setting. In size mode it also prints the bitrate it will use.
- Compress, listen, download. Press Compress audio, wait for the progress bar, play the preview in the result panel, then download. The saved file gets a -compressed suffix, and the panel reports the before and after sizes.
Bitrate is the setting that decides everything
In Target bitrate mode there are six choices and no free text box, which keeps the result predictable. Each setting spends a fixed number of bits on every second of audio, so the size of the output can be worked out before anything is encoded. This is the most predictable way to make an audio file smaller.
| Bitrate | One minute | Five minutes | Ten minutes | Typically used for |
|---|---|---|---|---|
| 64 kbps | About 0.5 MB | About 2.3 MB | About 4.6 MB | Speech, notes, podcasts where size matters most |
| 96 kbps | About 0.7 MB | About 3.4 MB | About 6.9 MB | Speech with a little more headroom |
| 128 kbps | About 0.9 MB | About 4.6 MB | About 9.2 MB | The default, and the usual balance for casual listening |
| 192 kbps | About 1.4 MB | About 6.9 MB | About 13.7 MB | Music on decent headphones or speakers |
| 256 kbps | About 1.8 MB | About 9.2 MB | About 18.3 MB | Music where the file will be kept |
| 320 kbps | About 2.3 MB | About 11.4 MB | About 22.9 MB | A lossy master or an archive copy |
Those numbers come from the bitrate arithmetic alone, so a real file lands a little above them, because the container adds headers and tags. The trade is the same at every step: MP3, M4A and OGG are lossy, so a lower bitrate leaves the encoder less room for detail and throws more of it away. The preview button lets you hear that trade instead of guessing at it.
Compressing to a target size in megabytes
Target file size mode is the part most free online compressors do not offer. Instead of asking you to guess a bitrate, it takes the limit you must stay under and solves for the bitrate, which is what you know when a form says 10 MB.
How the bitrate is calculated
The tool multiplies the target in megabytes by 1,024 twice to get bytes, turns that into bits, and divides by the length of the recording in seconds. The result is rounded to a whole number of kilobits per second, and it is not restricted to the six chip values: any whole number between 32 and 320 kbps can be used. A 12 minute recording with a 10 MB limit works out at about 117 kbps, and the panel prints that value before you press anything.
When the target cannot be reached
The bitrate is clamped between 32 and 320 kbps, and the panel says when the clamp has kicked in. A one hour recording with a 5 MB limit needs about 12 kbps, which does not exist here, so the tool states that 32 kbps will be used instead and the output comes out around 13.7 MB. The clamp works the other way too: a ten second note with a 50 MB limit needs more than 40,000 kbps, so it is pulled down to 320 kbps and the file lands at about 0.4 MB. In both cases the target was a request, the bitrate is what the tool can deliver, and the panel says which one won.
Size mode also needs the duration of the file, read locally from the audio metadata. If a file uses an unusual codec and the duration cannot be read, the run stops and suggests switching to Target bitrate.
MP3, M4A or OGG: which output to pick
Three outputs are available and all three are lossy, so the choice is about compatibility rather than about avoiding quality loss.
| Output | Codec | Strengths | Pick it when |
|---|---|---|---|
| MP3 | libmp3lame | Plays almost everywhere, including older players and car stereos | You cannot be sure what will open the file |
| M4A | AAC | Slightly better quality than MP3 at the same bitrate | Phones and modern players are the destination |
| OGG | Vorbis | Open and royalty free | A web player or a game engine asks for it |
The format does not decide the size, because all three spend the bitrate you chose in the same way. Switching from MP3 to OGG at 128 kbps changes the sound character a little and leaves the size roughly where it was. If you need a different container rather than a smaller file, use the audio converter, and see the guide on converting audio in the browser.
What this compressor cannot do
These are the real edges of the tool, and knowing them saves a wasted attempt.
- It cannot shrink a file without losing quality. MP3, M4A and OGG are lossy, so a lower bitrate always removes detail. Re-encoding a file that is already compressed adds a second round of loss, which is why the original should stay on disk.
- The target size is an estimate, not a guarantee. The calculation covers audio data only, while a finished file also carries container headers and tags. Expect the download to land a few percent above or below the number you typed.
- The bitrate is clamped between 32 and 320 kbps. A target that needs something outside that window gets the nearest usable bitrate, and the tool says so in the panel. The output is then larger or smaller than requested, and no setting can change that.
- The first run downloads about 30 MB. The FFmpeg engine is fetched into the browser on first use and cached afterwards, so the first compression on a slow connection takes longer than later ones.
- There is no noise reduction or cleanup. The tool re-encodes at a lower bitrate and does nothing else. It has no denoise filter, no normalizer and no way to remove hum, clicks or background noise.
- There is no silence removal and no trimming. The encoder keeps the whole recording from start to finish. Cutting a section out is what the audio trimmer does, and trimming before you compress is often the cheapest way to reach a size limit.
- It takes one file at a time and only accepts audio. There is no batch queue here, so several recordings are compressed one after another. A video file is refused instead of being mined for its soundtrack; for that, use video to MP3 first and compress the result afterwards if it is still too large.
Compressing in the browser instead of uploading
An upload based compressor behaves the same way until you press the button, and then it asks you to hand over the file. Harmless for a published podcast, poor for a voice memo or a client call that would then sit on a server.
| Aihangsoft | Upload-based compressor | |
|---|---|---|
| Where the audio goes | Stays in the browser tab | Sent to their servers |
| Target size in MB | Supported, with the chosen bitrate shown | Offered by some services, usually behind a plan |
| How much you can run | No daily cap | Often capped per day or per file |
| Account | Not needed | Sometimes required above a size threshold |
| Works offline | Yes, after the first engine load | No |
The trade is straightforward: your own machine does the encoding, which is slower than a server for very large files, and the file never leaves the device.
The same approach covers the other file types people need to shrink. For an oversized image, the guide on compressing an image to 100 KB covers the picture side, and the article on the Gmail attachment size limit explains what happens once a message crosses the threshold. Trimming a long recording first, as described in the audio trimmer guide, often removes more weight than any bitrate change.