How to Send Large Audio Files Through Email: Caps and Fixes

Key takeaways

• Gmail caps attachments at 25 MB and Outlook at 20 MB, so most lossless WAV masters and stem folders will not fit as email attachments.
• FLAC or ALAC compresses a WAV to roughly half its size with no quality loss, making it the right format for emailing masters that fit under the cap.
• WhatsApp and Messenger transcode audio sent as media, so attach files as Documents or paste a cloud link to keep quality intact.
• Above 100 MB, or for any folder of stems, use a dedicated transfer tool like WeTransfer or an audio portal instead of an attachment.
• Verify delivery by comparing file sizes or running an MD5 or SHA-256 checksum on the sent and received files.

You can send large audio files through email up to Gmail’s 25 MB attachment cap, which fits a single MP3 but almost never a lossless master or a folder of stems. For anything bigger, compress to a zip and stay under the cap, or upload the WAV and email a download link from WeTransfer or a dedicated audio transfer app instead.

What is the maximum audio file size you can email through Gmail and other providers?

Email providers cap attachments well below the size of a single mix. Gmail allows 25 MB per attachment and automatically switches to a Google Drive link if you go over. Outlook caps at 20 MB. Apple Mail and Yahoo sit in the same range, though Apple adds Mail Drop for larger files.

That math matters because lossless audio is heavy. A 3-minute stereo WAV at 44.1 kHz/24-bit runs roughly 85 MB, and a folder of dual-mono stems multiplies that fast. No email provider on the list comes close.

Provider	Attachment cap	What happens over the cap
Gmail	25 MB	Falls back to a Google Drive link
Outlook	20 MB	Blocks the send
Yahoo Mail	25 MB	Blocks the send
Apple Mail	~20–40 MB	Offers Mail Drop upload

The cap is confirmed in Google’s Gmail help documentation, which also describes the Drive fallback.

For a client who only needs a streaming preview, a link works. For a collaborator who needs lossless masters, you need a transfer route built for audio, such as a branded portal like Audio Portal or a general service like WeTransfer.

How do you compress a large audio file without losing quality before emailing it?

ZIP is lossless but saves little on WAV; FLAC or ALAC cut size roughly in half with no quality loss; MP3 and AAC trade quality for size and should only carry previews. Which one fits depends on whether the client needs the master or just an approval.

ZIP a WAV: when it helps and when it does not

Zipping a WAV or AIFF keeps every bit intact, but the gain is small. PCM audio is already dense, so a zipped mix might shrink by a few percent, sometimes less. ZIP makes sense for bundling a session folder of stems into one attachment, not for shrinking a single master under Gmail’s 25 MB cap.

FLAC and ALAC: lossless halving for masters and stems

FLAC (and ALAC if your client lives in Apple’s ecosystem) compresses losslessly, typically landing around half the original WAV size. A 24-bit/96 kHz master that blows past email limits as a WAV often fits comfortably as FLAC. When you decode it back to WAV, the checksum matches. This is the right format for delivering masters and stems where lossless matters and the recipient can handle the format.

MP3 and AAC previews: acceptable for approval, never for delivery

A 320 kbps MP3 or AAC file is a fraction of the WAV size and fine for client approval on earbuds or a car stereo. It is not a master. Send the preview, then deliver the lossless file once the mix is signed off.

How do you send large audio files through WhatsApp and Messenger when they exceed the size limit?

Both apps cap media uploads well below the size of a single lossless mix, let alone a folder of stems. WhatsApp compresses anything sent as media, and Messenger behaves similarly. The workaround in both is to stop treating your audio as media and send it as a file, or skip the app entirely with a cloud link. For reference on where email caps sit too, Microsoft documents a 20 MB attachment limit for Outlook (Microsoft Support).

WhatsApp: document send vs. media send and what it does to your audio

Sending a WAV as media means WhatsApp transcodes it to a lossy format, which is fine for a rough bounce and useless for a master. Attach the same file as a Document instead and it arrives byte-for-byte. On Android, tap the paperclip and choose Document; on iPhone, use the plus button, then Document, then browse to the file. Stems sent this way keep their original quality, though WhatsApp still applies its own per-file cap.

Messenger: limits and the cloud-link workaround

Messenger offers no document mode on most accounts, so a large WAV either fails to upload or gets compressed. The practical route is uploading to Drive or Dropbox and pasting the link into the chat, which keeps the transfer lossless and gives the client a download instead of a streamed preview.

How do you send large audio files from an iPhone using Mail, iCloud, or a transfer app?

Mail Drop: what it does above the attachment cap

iPhone Mail caps attachments at 20 MB. Anything bigger triggers Mail Drop, which uploads the file to iCloud and pastes a download link into the email instead. The recipient gets a link that works for 30 days, and the file itself never touches the mail servers. Note that Mail Drop counts against your iCloud storage, and it needs the upload to finish before you hit send, so a 2 GB master can take a while on hotel Wi-Fi.

Sharing from Files and Voice Memos without quality loss

WAVs in Files share fine: long-press the file, tap Share, and pick Mail, Messages, or AirDrop. For lossless delivery, AirDrop to a nearby collaborator beats email outright since nothing gets compressed. Voice Memos defaults to compressed M4A, so open the memo, tap Share, and choose uncompressed WAV if the recipient needs to work from it.

Sending from a transfer app on iPhone

Most transfer apps work from Safari, but a dedicated app handles background uploads better: start the upload of a 3 GB stem folder, lock the phone, and it keeps going. This is where a branded portal earns its keep — clients get a link that looks like yours, with folder-level access and preview-only options for mixes.

When should you use a cloud link instead of attaching an audio file to an email?

Decision flow by file size and quality need

Under 20 MB, attach the file. A single MP3 bounce or a short preview WAV usually fits inside Gmail’s 25 MB limit, and the client gets it with zero extra clicks.

Between 20 and 100 MB, compress to FLAC or zip the WAV, or move to a link. If the recipient needs lossless, a link to the original file beats a compressed attachment every time.

Above 100 MB, or anything resembling a folder of dual-mono stems, use a dedicated transfer tool. For reference on where messaging caps sit, WhatsApp documents top out at 2 GB per the WhatsApp Help Center on document sharing limits. Email caps are far lower, so multi-gig stem folders never belong in an attachment.

What generic cloud links miss for audio work

Dropbox and WeTransfer move the file, but they treat a 24-bit master like a PDF. No streaming previews, no version history across mix revisions, no preview-only links that stop a client from downloading the unmastered rough.

That gap is why we built RockScience Audio Portal: branded transfers, streaming previews, folder-level access, and collaborators handled in one place. Honest limitation: it is web-based, so it will not help you text a file over WhatsApp.

Dedicated audio tools such as Filepass, Boombox, Samply, and Audome exist for the same reason. Pick whichever fits your margin, but stop sending stems as email attachments.

Which app to send large audio files is best for phone users?

Comparison criteria for audio transfer tools

Judge any transfer app on five things: how big a file it accepts, whether clients can stream a preview before downloading, whether the page carries your studio’s name, how you handle revisions, and what it costs monthly. Messenger caps attachments at 25 MB, so anything beyond a rough MP3 sketch needs a dedicated tool (Meta Messenger Help). WeTransfer handles the size problem but gives you a generic page and no version history. Filepass, Boombox, Samply, and Audome are built for audio, with streaming previews and client feedback, and each prices for working engineers rather than teams.

How RockScience Audio Portal holds up against the same criteria, including where it falls short

The honest rundown: RockScience Audio Portal is a branded portal you run under your own domain, so clients land on your studio’s page instead of a WeTransfer splash screen. You get streaming previews, preview-only links, folder-level access for collaborators, and version history on mixes and masters, which matters when a client asks for “the one from Tuesday.” It handles lossless stems and dual-mono stems without compression, and the Pro tier sits at $9/month, priced for solo engineers billing per project. Where it falls short: there is no native mobile app, so sending from your phone happens through the browser, and the free tier’s limits are tighter than WeTransfer’s. If you only send one file a month, a plain WeTransfer link is cheaper and fine. If you send revisions weekly and want every delivery on brand, the portal earns its keep.

How do you keep audio quality intact when sending large files from your phone?

Stop apps from transcoding your WAV on share

iOS and Android both try to help by shrinking files on share. Mail Drop on iPhone and most messaging apps will offer to compress a WAV or convert it to AAC before it leaves. Always pick “Keep Original” or share the file from the Files app rather than exporting from your DAW’s mobile companion or a voice memo app, which bakes in a lossy export before the transfer even starts.

Check the sample rate and bit depth before you send. A 48kHz/24-bit master viewed in Files should show the same specs on the receiving end. If your client opens a 128kbps MP3 when you sent a WAV, the conversion happened on your phone, not theirs.

Verify what arrived matches what you sent

The cheapest check is file size. Note the exact byte count before sending, then compare against what the recipient sees. If the numbers match, the file did.

For a proper check, run a checksum. Apps like Hashstream or a terminal on the receiving machine give you an MD5 or SHA-256 hash; matching hashes mean bit-identical audio. For client-facing sends, a branded transfer portal keeps the original untouched and shows the file size on the download page, so verification takes seconds instead of a support email.

FAQ

Can I email a WAV file, or do I need to convert it first?

You can email a WAV if it fits under your provider’s cap, which Gmail sets at 25 MB and Outlook at 20 MB. Most full-quality WAVs exceed that, so convert to FLAC for a lossless half-size file, bounce a 320 kbps MP3 for approval, or upload the WAV and email a download link instead.

Why does my audio sound worse after sending it through WhatsApp?

Because WhatsApp treats files sent as media like photos or video and transcodes them to a lossy format before upload. Attach the same file as a Document instead, using the paperclip on Android or the plus button on iPhone, and it arrives byte-for-byte. For anything beyond WhatsApp’s per-file cap, paste a cloud link.

How many MB is a 5-minute song, roughly?

A 5-minute stereo WAV at 44.1 kHz/24-bit runs roughly 140 MB, which no email provider accepts as an attachment. The same song as a 320 kbps MP3 lands around 12 MB and fits Gmail’s 25 MB cap easily. FLAC typically cuts the WAV size roughly in half with no quality loss.

Is WeTransfer free for sending audio to clients?

Yes, WeTransfer’s basic tier is free and handles files far larger than any email attachment cap, which makes it a workable default for occasional sends. The tradeoffs are a generic download page, no streaming previews, and no version history across mix revisions. If you deliver revisions weekly, a dedicated audio portal is worth comparing.