How to fix an audio file that's too big to send on whatsapp
- Step 1Identify why WhatsApp rejected it — If WhatsApp refused or stalled on an audio attachment, the size is the usual reason — anything over 16 MB won't send as a document/audio file. Check the file size first; if it's under 16 MB, the issue is likely format or network, not size (see edge cases).
- Step 2Drop the rejected file onto the tool — Drag the over-cap MP3/WAV/FLAC/M4A/OGG/Opus/video onto the dropzone. It's decoded locally to read the duration — nothing is sent, even though the earlier WhatsApp attempt failed.
- Step 3Let the tool size it under 16 MB — No settings. It computes the bitrate for your clip's length and rounds down to a standard MP3 bitrate so the output lands safely below the cap. You don't pick anything.
- Step 4Run and confirm the new size — FFmpeg re-encodes to MP3. The result panel shows the output bytes — verify it reads under 16 MB (it always will). The filename gains a
-16mbsuffix. - Step 5Re-attach the new MP3 in WhatsApp — Attach
yourfile-16mb.mp3as a document/audio file. It should send immediately. If you record it into the chat instead, WhatsApp will re-compress it as a voice note. - Step 6Still failing? Check format and network — If a sub-16 MB file still won't send, it's not a size problem. Convert exotic formats to MP3 with bitrate-changer, or convert an Opus/OGG voice note with convert WhatsApp voice to MP3, and check your connection.
Why WhatsApp rejects audio — and which the tool fixes
whatsapp-fit addresses the size cause. Format/network causes need a different fix.
| Symptom | Likely cause | Does this tool fix it? |
|---|---|---|
| Attachment won't add / 'too large' | Over 16 MB audio cap | Yes — re-encodes under 16 MB |
| Sends but plays in external app | WAV/FLAC not inline-playable | Yes — outputs inline-playable MP3 |
| Sub-16 MB file still won't attach | Format/codec or network | No — convert with bitrate-changer |
| Voice note arrives low quality | WhatsApp re-encodes recorded notes | No — send as a file, not a recorded note |
| Received OGG voice note won't open elsewhere | Opus container | No — use convert WhatsApp voice to MP3 |
Bitrate the fix applies, by clip length
Output always lands under 16 MB. Sizes are approximate MP3 at the selected bitrate.
| Original length | Selected MP3 bitrate | Approx. fixed size |
|---|---|---|
| 5 min | 320 kbps (capped) | ≈ 11.4 MB |
| 10 min | 192 kbps | ≈ 13.7 MB |
| 20 min | 96 kbps | ≈ 13.7 MB |
| 30 min | 64 kbps | ≈ 13.7 MB |
| 45 min | 48 kbps | ≈ 15.4 MB |
| 60 min | 32 kbps | ≈ 13.7 MB |
Max input size you can drop in, by tier
If the rejected file is bigger than your tier allows, trim it first.
| Tier | Max input size | Max duration | Files at once |
|---|---|---|---|
| Free | 50 MB | 30 min | 1 |
| Pro | 200 MB | 120 min | 10 |
| Pro-media | 100 GB | Unlimited | 100 |
| Developer | 100 GB | Unlimited | Unlimited |
Cookbook
Each fix shows the rejected input and the resulting under-cap MP3. Bitrate = floor(16 MB × 8 × 0.96 ÷ seconds) snapped to a standard MP3 value.
30-minute MP3 that WhatsApp wouldn't attach
A 192 kbps, 30-minute MP3 is ~43 MB — well over the cap. The tool re-sizes it.
Rejected: talk.mp3 (192 kbps, 30:00, ~43 MB) Math: 16MB*8*0.96 / 1800s = ~72 kbps -> snap 64 kbps Fixed: talk-16mb.mp3 (64 kbps, 30:00, ~13.7 MB) Result: attaches and sends
WAV that 'sent' but opened in an external player
WhatsApp may accept a small WAV but not play it inline. Converting to MP3 fixes playback even when size wasn't the issue.
Source: clip.wav (1411 kbps, 1:30, ~15.9 MB) Output: clip-16mb.mp3 (320 kbps capped, 1:30, ~3.4 MB) Result: plays inline in the chat now
Hi-res FLAC over the cap
A 24-bit/96 kHz FLAC is far over 16 MB. The tool transcodes to a sendable MP3.
Rejected: master.flac (24/96 lossless, 8:00, ~85 MB) [Pro] Math: 16MB*8*0.96 / 480s = ~268 kbps -> snap 256 kbps Fixed: master-16mb.mp3 (256 kbps, 8:00, ~14.6 MB)
Audio from a video the recipient asked for
They only want the audio of a long video. Extract and size it under 16 MB in one pass.
Source: webinar.mp4 (audio track, 50:00) Math: 16MB*8*0.96 / 3000s = ~43 kbps -> snap 32 kbps Fixed: webinar-16mb.mp3 (32 kbps, 50:00, ~11.4 MB) Result: audio-only, attaches fine
File still over the cap because it's too long
A 3-hour recording exceeds even the input limit on Free. Trim to the needed section, then fix the size.
Too big: seminar.mp3 (3:00:00, ~165 MB) — exceeds free 30-min limit
Fix path: audio-trimmer to the 25-min Q&A, then this tool:
qa.mp3 (25:00) -> 80 kbps -> ~14.3 MB, sends fine
See: /audio-tools/audio-trimmerEdge cases and what actually happens
Sub-16 MB file still won't send
Not a size issueIf the file is already under 16 MB and WhatsApp still refuses it, size isn't the cause — it's usually an unusual codec/container or a network problem. Re-encode to a clean MP3 with bitrate-changer, confirm your connection, and retry.
Rejected file is bigger than your tier's input cap
RejectedFree allows 50 MB / 30 minutes of input. A 3-hour recording is refused before compression. Trim the clip with audio-trimmer to fit the limit, then compress — or upgrade for the larger caps.
Output is right near 16 MB
PreservedMid-length clips land at 13–15 MB because the snapped bitrate nearly fills the budget — that's intentional, maximizing quality under the cap. WhatsApp's check is on the actual file size, and the output is always below 16 MB, so it will attach.
You re-recorded the MP3 into the chat
Re-compressedHolding the mic to 'send' the fixed file plays and re-records it as a voice note, which WhatsApp re-encodes to low-bitrate Opus — undoing your fix. Attach the MP3 as a document/audio file instead.
Quality looks worse than the original
By designGetting under the cap means lowering the bitrate, so long clips lose fidelity. For music especially, expect audible compression on 30-minute-plus files. Trim to the part you need so a higher bitrate fits, or accept the trade-off for speech.
Tags and album art are gone after the fix
Not carried overThis is a size pass; ID3 tags and embedded artwork aren't preserved. Restore them with id3-editor if needed before sending.
The fixed file came out tiny on a short clip
ExpectedShort clips hit the 320 kbps ceiling and end up well under 16 MB. That's correct — it preserves quality rather than inflating the file. It will send fine.
Corrupt download won't load
ErrorIf the file is truncated or isn't really audio (wrong extension), the decoder can't read a duration and the tool errors out. Re-download or re-export the source and try again.
Frequently asked questions
What's the actual limit I'm hitting?
WhatsApp caps audio/document attachments at 16 MB. Audio files over that won't attach. This tool re-encodes your file to an MP3 sized under 16 MB so it sends.
Why does WhatsApp reject the file without a clear error?
Often it just refuses to add the attachment or stalls. The most common reason is the 16 MB size cap. Compress with this tool and re-attach; if a sub-16 MB file still fails, the cause is format or network, not size.
Do I need to change any settings to fix it?
No — that's a feature here. The tool is fully automatic: fixed 16 MB target, MP3 output, bitrate chosen from the clip length. Misconfigured settings can't cause a still-failing retry because there are none.
My WAV sent but only opens in an external app — can this fix that?
Yes. WhatsApp's inline player handles MP3, M4A/AAC, and OGG/Opus but not WAV/FLAC. Because this tool always outputs MP3, the converted file plays inline in-chat.
Will the recipient see reduced quality?
On long clips, yes — fitting under the cap requires a lower bitrate. Speech stays clear; music shows audible compression on 30-minute-plus files. Trim to the essential part for higher quality.
Is the rejected file uploaded when I use this tool?
No. Compression runs in your browser via FFmpeg 8.1 WebAssembly. Even after a failed WhatsApp upload, the file stays on your device.
What if my file is too long even for the tool?
Free tier accepts up to 30 minutes / 50 MB. For longer recordings, trim with audio-trimmer to a sendable section first, or upgrade for larger input limits.
Can I fix several rejected files at once?
Free processes one at a time; Pro up to 10 and Pro-media up to 100. For a single stuck attachment, one pass is enough.
The output is barely under 16 MB — is that risky?
No. The tool always snaps below the cap, and WhatsApp checks the actual file size, which the result panel shows. A 14–15 MB MP3 attaches fine.
Does this make a voice note?
No — it makes a standalone MP3 you attach as a file. WhatsApp voice notes are recorded in-app and encoded to Opus by WhatsApp itself. Send the MP3 as a document to keep its quality.
I received an OGG voice note that won't open elsewhere — does this help?
That's the opposite problem — converting Opus/OGG to a portable format. Use convert WhatsApp voice to MP3. whatsapp-fit is for shrinking large files to fit the cap.
My tags disappeared after fixing the size — can I get them back?
The size pass doesn't preserve ID3 tags or cover art. Re-add them with id3-editor before sending if they matter.
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.