Compressing Audio for Email Attachments Without Sacrificing Quality
Email size limits got you stuck? Here's how to squeeze audio files down to manageable sizes while keeping them listenable.
You've recorded a great interview, mixed a demo track, or captured the perfect voice memo. Now you need to email it. You hit send and—boom—Gmail spits it back at you. "Attachment too large."
Welcome to the email attachment size problem.
Most email services cap attachments at 25MB. Some corporate servers are stricter (10MB or even 5MB). Meanwhile, a 3-minute WAV file sits comfortably at 30-50MB. The math doesn't work.
But here's the thing: you don't actually need to send that WAV. There are smarter ways to compress audio files without turning them into garbled messes. Let me show you how.
Why Audio Files Are So Big
Audio files record sound as thousands of tiny snapshots per second. A standard CD-quality WAV captures 44,100 samples per second, with 16 bits of data per sample, across two channels (stereo). That's about 10MB per minute.
For a 5-minute song? 50MB, easy.
Formats like WAV and AIFF are uncompressed—they store every single bit of audio data. That's great for editing and archiving, but terrible for emailing.
The Solution: Lossy Compression
MP3, AAC, and OGG are lossy formats. They throw away audio information your ears probably won't miss—ultra-high frequencies, quiet sounds masked by loud ones, stereo details you can't perceive.
The result? Files that are 80-95% smaller and still sound perfectly fine to most listeners.
Here's what a 5-minute song looks like in different formats:
- WAV (uncompressed): ~50MB
- MP3 at 320 kbps: ~12MB
- MP3 at 192 kbps: ~7MB
- MP3 at 128 kbps: ~5MB
- AAC at 160 kbps: ~6MB
Suddenly, emailing audio doesn't seem so hard.
Picking the Right Format and Bitrate
Not all audio needs the same treatment. A podcast interview doesn't need the same fidelity as a mastered music track.
For music:
- Use MP3 at 192 kbps or AAC at 160 kbps. This is the sweet spot—good sound, reasonable file size.
- If you're picky about quality, go 256 kbps. It's still way smaller than WAV.
- Avoid 128 kbps for music unless you're desperate. It starts sounding thin.
For spoken audio (podcasts, interviews, voice memos):
- You can get away with 64-96 kbps. Voices don't need much bandwidth.
- Mono encoding cuts file size in half (because you're not wasting space on stereo separation).
- A 30-minute podcast at 64 kbps mono = ~15MB. Totally email-friendly.
Tools like KokoConvert's audio compressor let you pick the exact bitrate and format you need. No guessing, no installing software.
MP3 vs AAC: Which One Should You Use?
Both work great for emailing. Here's the quick comparison:
MP3: Universal compatibility. Every device, every player, every person can open it. It's the safe choice. Slightly less efficient than AAC, but who cares when the difference is 1-2MB.
AAC: Better sound quality at lower bitrates. It's what Apple uses (M4A files), what YouTube uses, what most streaming services prefer. If your recipient is on an iPhone or Mac, they'll have zero issues. Slightly less compatible with ancient Windows software.
My take? Stick with MP3 unless you know the recipient's setup. It just works.
How to Actually Compress the File
You've got a few options:
1. Use an online converter (easiest)
Upload your file to KokoConvert, pick your format and bitrate, and download the compressed version. Takes 30 seconds. No software installation, no learning curve.
2. Use desktop software (more control)
Audacity (free and open-source) can export to MP3 with custom bitrates. VLC can convert files too. If you're doing this regularly, it's worth learning.
3. Use command-line tools (for nerds)
FFmpeg is the gold standard. It's powerful, scriptable, and free. But it's also overkill unless you're batch-processing hundreds of files.
When Compression Isn't Enough
Sometimes even a compressed file is too big. A 2-hour recording, even at 64 kbps, can hit 60MB. What then?
You've got a few escape hatches:
- Cloud storage links: Upload to Google Drive, Dropbox, or WeTransfer and email the link instead. Fast, reliable, no size limits.
- Split the file: Break it into chunks (Part 1, Part 2, etc.). Clunky, but it works.
- Trim unnecessary parts: Does the recipient really need that 10-minute intro? Cut it.
Most of the time, though, smart compression gets you under the limit without needing workarounds.
A Quick Reality Check on Quality
People obsess over audio quality, but here's the truth: most listeners can't tell the difference between 192 kbps MP3 and a lossless WAV file. Especially if they're listening on laptop speakers, AirPods, or in a noisy environment.
Audiophiles with $2,000 headphones? Sure, they might notice. But if you're emailing a demo to a client, a podcast episode to a friend, or a voice memo to a colleague, 192 kbps is more than enough.
Don't overthink it.
What About Sending Multiple Files?
Emailing an album or a collection of recordings? Compress each track individually, then zip them into a single archive. It won't make the audio smaller (MP3s don't compress further), but it makes sending easier.
Most email clients handle ZIP files just fine. Just make sure the total size stays under 25MB.
The Bottom Line
If you're trying to email audio, don't send WAV files. Convert to MP3 at 192 kbps (or 64-96 kbps for speech). You'll get files that are 80-90% smaller, still sound great, and actually fit through email filters.
Use tools like KokoConvert to handle the conversion in seconds. No installations, no complicated settings—just upload, compress, and send.
And if the file's still too big? Cloud storage links are your friend.
Email attachment limits are annoying, but they're not hard to work around once you know the tricks.