How to reduce audio file size to beat email & upload limits
- Step 1Find your destination's size limit — Note the cap you're up against: Gmail and Yahoo are 25 MB, Outlook.com is 20 MB, many corporate Exchange servers are 10 MB, and web forms are often 5–10 MB. That number is your target — minus a small safety margin.
- Step 2Drop the audio file onto the tool — Drag the MP3, WAV, M4A, OGG, Opus, FLAC or video file onto the dropzone. It loads locally — no upload. JAD shows the current size and duration, the two numbers that decide how far it can shrink at a given quality.
- Step 3Set the target a touch below the cap — Enter your target in Target size (MB) — e.g.
23for a 25 MB Gmail cap, or9for a 10 MB Exchange limit. Leaving a small margin absorbs MP3 padding and any metadata so the attachment is guaranteed to fit. - Step 4Run the reduction — Click Run Compress to Size. FFmpeg re-encodes to a constant-bitrate MP3 sized to your target. Short clips finish in seconds; a full-hour file takes longer because the entire stream is decoded and re-encoded.
- Step 5Confirm it clears the limit — Check the Output size on the result card against your cap. If it's comfortably under, you're done; if it's surprisingly small, you had headroom — raise the target and re-run for better fidelity while still fitting.
- Step 6Download and attach — Press Download to save the
-Nmb.mp3file, then attach it. Audition it in the inline player first if it's voice at a low bitrate — clarity holds up well, but it's worth a 10-second listen before it goes out.
Common attachment & upload limits to target
Set your target a little below these so MP3 frame padding and metadata don't tip the file over. Limits are provider defaults; your IT department may set a lower one.
| Destination | Limit | Suggested target | Notes |
|---|---|---|---|
| Gmail | 25 MB | 23 MB | Over 25 MB, Gmail switches to a Drive link instead of an attachment |
| Outlook.com | 20 MB | 18 MB | Web client; OneDrive link offered above the cap |
| Corporate Exchange | often 10 MB | 9 MB | Admin-configurable — confirm your org's actual limit |
| Yahoo Mail | 25 MB | 23 MB | Per-message total across all attachments |
| Generic web form | 5–10 MB | 4.5–9 MB | Read the on-form note; many cap at 5 MB |
What fits, by recording length
Approximate snapped MP3 bitrate JAD picks to fit a 25 MB cap (target 23 MB) at each duration, and how it sounds for speech.
| Recording length | Snapped bitrate @ 23 MB | Speech quality |
|---|---|---|
| 10 min | 256 kbps | Indistinguishable from source |
| 30 min | 96 kbps | Excellent |
| 60 min | 48 kbps | Clear, fully intelligible |
| 120 min | 24 kbps | Intelligible, audibly compressed |
| 180 min | 16 kbps | Understandable, rough — consider splitting |
Tier limits for this tool
Audio family limits from JAD's tier configuration. Files larger or longer than your tier allows are blocked before processing.
| Tier | Max file size | Max duration | Files per job |
|---|---|---|---|
| Free | 50 MB | 30 min | 1 |
| Pro | 200 MB | 120 min | 10 |
| Pro + Media | 100 GB | Unlimited | 100 |
| Developer | 100 GB | Unlimited | Unlimited |
Cookbook
Real send-it-by-email scenarios. Targets are set just under the provider cap to guarantee the attachment fits.
Voice memo too big for Gmail's 25 MB cap
A lossless iPhone memo exported as WAV balloons past 25 MB in minutes. MP3 at a modest rate clears it with room to spare and zero audible loss for voice.
Source: meeting-memo.wav · 22 min · 37 MB (PCM) Cap: Gmail 25 MB → Target 23 MB Math: 23 MB → ~143 kbps → snaps DOWN to 128 kbps Output: meeting-memo-23mb.mp3 · ~21 MB · 128 kbps Fits Gmail with headroom; voice quality untouched.
Hour-long webinar audio into a 10 MB Exchange limit
Corporate Exchange often caps at 10 MB. An hour of audio at that ceiling drops to a low bitrate, but speech holds.
Source: webinar.mp3 · 61 min · 84 MB (192 kbps) Cap: Exchange 10 MB → Target 9 MB Math: 9 MB → ~20 kbps → snaps DOWN to 16 kbps Output: webinar-9mb.mp3 · ~7.3 MB · 16 kbps Rough but intelligible. If too rough, send 2 halves instead.
Two-part send beats one over-compressed file
When the single-file bitrate would be too low, splitting the recording lets each half use a much higher bitrate and still fit the cap.
Source: lecture.mp3 · 90 min · 124 MB Cap: 25 MB per message Option A (one file): Target 23 MB → ~32 kbps (rough) Option B (split): /audio-tools/audio-splitter → two 45-min files each at Target 23 MB → ~64 kbps (clearly better) Send as two emails — double the quality, both under cap.
Form rejects 'file too large' at 5 MB
Many upload forms cap at 5 MB with no warning until you submit. Size below that and the submission goes through.
Source: statement.m4a · 8 min · 11 MB (AAC) Form cap: 5 MB → Target 4.5 MB Math: 4.5 MB → ~78 kbps → snaps DOWN to 64 kbps Output: statement-4.5mb.mp3 · ~3.9 MB · 64 kbps Clears the form; voice fully intelligible at 64 kbps.
Trim silence first to keep the bitrate high
If long pauses pad the duration, removing them shortens the file so the same MB target buys a higher bitrate. Strip silence, then size.
Source: call.wav · 35 min (incl. 9 min hold music/silence) Step 1: /audio-tools/silence-stripper → 26 min file Step 2: this tool, Target 23 MB Before strip: 23 MB / 35 min → ~88 kbps → 80 kbps After strip: 23 MB / 26 min → ~118 kbps → 112 kbps Shorter duration = higher fitting bitrate = better audio.
Edge cases and what actually happens
File already under the email cap
By designIf your recording is already smaller than the limit, you don't need this tool — attach it as-is. If you compress anyway with a target above the source size, JAD's computed bitrate exceeds 320 kbps and gets capped there, so you'll get a 320 kbps MP3 with no benefit. Only reduce when the file genuinely exceeds the cap.
Computed bitrate hits the 8 kbps floor
Quality lossA multi-hour recording squeezed into a small cap can resolve below 8 kbps and snap to that floor. At 8 kbps speech is robotic, though often still understandable. Better options: split the file with Audio Splitter so each part gets a usable bitrate, or strip dead air first with Silence Stripper.
Output is a few KB over the cap
ExpectedMP3 frame padding and ID3 tags add a small fixed amount on top of the audio. On tight caps that can push a result slightly over. Always target a little below the real limit (23 MB for a 25 MB cap, 4.5 MB for 5 MB) so the file is guaranteed to fit on the first try.
Recipient's server limit is lower than the sender's
Delivery riskEmail size limits apply at both ends, and the receiving server's cap can be smaller than yours. A 24 MB attachment that leaves your Gmail fine may bounce at a recipient's 10 MB corporate gateway. If you don't know the recipient's limit, target conservatively (9 MB clears most servers) or share via a link instead.
File exceeds the free 50 MB / 30 min limit
Tier limitFree tier blocks inputs over 50 MB or 30 minutes before any processing. The duration check is independent of size, so a 40-minute 28 MB podcast is also blocked on free. Pro raises both to 200 MB / 120 min. Most email-bound recordings are well within free limits.
Sending lossless to preserve quality
Wrong approachWAV and FLAC are not bitrate-bound, so target-size math doesn't shrink them the way it shrinks MP3 — and the browser tool outputs MP3 regardless. If a recipient needs lossless, don't email it; share a link to the original. For everyday voice and reference audio, MP3 at a fitting bitrate is the right call.
Re-compressing an already-small MP3
Generational lossShrinking a 96 kbps MP3 down to 48 kbps re-encodes lossy-on-lossy and stacks artefacts. If you still have the original WAV/M4A, compress from that instead for a cleaner result at the same size.
Unsupported or DRM-protected input
Decode errorFFmpeg can't read DRM-locked files (e.g. purchased .m4p) or corrupt downloads, and the run will fail rather than emit a broken file. Re-export from the source app, or convert through WAV to MP3 first to get a clean container, then size it here.
Frequently asked questions
How small can I make my file for email?
As small as you set the target — but quality drops as the bitrate falls. For a 25 MB cap, set the target to ~23 MB to leave a safety margin. JAD computes the bitrate from your file's duration and snaps down to a standard rate so the result clears the cap rather than landing over it.
What's Gmail's attachment limit, and how do I beat it?
Gmail caps attachments at 25 MB; above that it converts the file to a Google Drive link automatically. To keep it as a real attachment, target ~23 MB here. Voice recordings up to about an hour fit comfortably at that target with fully intelligible quality.
Why target below the limit instead of exactly at it?
MP3 frame padding plus any ID3 metadata add a few KB on top of the audio data, and some servers measure the encoded MIME size (slightly larger than the file). Leaving a 5–10% margin guarantees the attachment fits on the first send rather than bouncing.
Does my recording get uploaded to reduce it?
No — and that's the point for private recordings. Processing runs entirely in your browser via FFmpeg 8.1 (WebAssembly). The audio never leaves your device. See the no-upload size reducer guide for the privacy details.
My recording is too long to fit at decent quality — what now?
Two fixes: split it with Audio Splitter and send each part under the cap (each gets a higher bitrate), or strip silence with Silence Stripper to shorten the duration so the same MB target buys more bitrate.
Will the person I send it to be able to play it?
Yes. The output is a standard MP3, which every email client, phone and media player supports natively. No special software needed on their end.
Can I keep it lossless and still email it?
Usually not within a cap — lossless WAV/FLAC are large by nature, and this tool outputs MP3. If lossless is essential, share the original via a download link rather than email. For voice and reference audio, a fitting MP3 bitrate is indistinguishable for the purpose.
What if the file is bigger than the free 50 MB limit?
Free tier blocks inputs over 50 MB or 30 minutes. Most email-sized recordings are within that, but for larger sources upgrade to Pro (200 MB / 120 min) or split the file first. The duration cap applies separately from size.
Is this the same as the Discord or WhatsApp size tools?
Same engine, preset targets. Discord Fit fixes the target at 25 MB and WhatsApp Fit at 16 MB. Use this tool when you need an arbitrary target for an email or form limit.
Can I pick the bitrate myself instead of a size?
Not here — this tool is size-first. If your goal is a specific bitrate rather than a size cap, use Bitrate Changer, which lets you choose 64–320 kbps directly in CBR or VBR.
Does compressing change the loudness or fix quiet audio?
No. This only changes the bitrate to hit a size. To make a quiet or uneven recording louder and more consistent, run Loudness Normalizer or Speech Leveler first, then reduce the size.
Can I batch-reduce a folder of recordings?
Yes via the @jadapps/runner: pair it once and POST each file to the local audio-compressor endpoint with your targetMb. Everything stays on your machine. Pro's batch (10 files) also lets you queue several at once in the browser.
Privacy first
Every JAD Audio tool runs entirely in your browser via FFmpeg (WebAssembly) and RNNoise. Your audio files never leave your device — verified by zero outbound network requests during processing.