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.

Key takeaways

• Every mix revision should include a labeled bounce, revision number, date, short reference notes, and a stated feedback deadline.
• Use a zero-padded naming convention like SongName_v03_2025-01-14_vocalup.wav and never overwrite an old bounce.
• Send streaming preview links for early rounds and reserve 24-bit WAV delivery for final sign-off.
• Collect timestamped comments in one channel per song instead of assembling notes from texts and emails.
• State the included revision count and the price per extra round in your quote before the first bounce leaves your studio.

Knowing how to share mix revisions with clients comes down to one system: a single branded link that carries both a streaming preview for quick listens and a lossless download for final approval, with every version labeled by date and revision number. That replaces the WeTransfer-and-SoundCloud patchwork, keeps feedback in one thread, and makes each round easy for the client to play back consistently.

What should you include when sending a mix revision to a client?

A mix revision needs five things: the labeled bounce, the revision number, the date, short reference notes on what changed, and a deadline for feedback. Skip any one of them and you invite a second round that exists only because the client was guessing.

The revision bundle checklist

• Labeled bounce in the format your client can actually play, at the quality you agreed on.
• Revision number and date in the filename: SongName_v03_2025-01-14.wav.
• Reference notes: three bullet points on what you changed and what you want their opinion on.
• A feedback deadline, stated plainly, so the round closes instead of drifting.

Host the bundle somewhere the client can stream it without downloading, with a preview-only link if they are early in the process. A portal like RockScience Audio Portal keeps every round in one branded place, so version history lives with the audio instead of in your sent-mail folder.

Why a naked MP3 link creates more rounds

A bare link with no notes forces the client to reconstruct context from memory. They hear one thing, you meant another, and the round produces comments on parts you already fixed. Most streaming apps also normalize loudness, so if your client evaluates on a streaming app, tell them that in the notes. Context in the bundle is cheaper than an extra revision round.

How do you label and version mix revisions so nothing gets confused?

The fix is two things: a naming convention both sides use, and one place where every version lives. When a client texts “the chorus one,” you need to know exactly which bounce they mean.

A naming convention that survives email and text threads

Use this pattern on every export:

SongName_v03_2025-01-14_vocalup.wav

That gives you the song, the revision number (zero-padded so v10 sorts after v9), the date, and a short note on what changed. No spaces, no parentheses, nothing that breaks in a text message or gets mangled by a download manager. When you change something, the number goes up. Never overwrite v02 to make v03; the old bounce is your proof of what the client approved.

Keeping a version history the client can see

Your version history can’t live only in your session folder. If the client has to dig through a WeTransfer email chain to find the latest bounce, they will reference the wrong one. Keep every revision in one folder the client can open, newest at top, so both of you point at the same file. RockScience Audio Portal does this with folder-level access and version history under your own branding, and Filepass and Boombox offer similar client-facing versioning. Where a plain Dropbox link falls short is labeling: it shows filenames, not which revision is current, so say “latest is v04” in the message itself every time.

Which file format and streaming quality should clients use to evaluate a mix?

Match the format to the stage: streaming previews for rounds one and two, lossless WAV only when the client is signing off. A 320 kbps-style stream is fine for judging balance, vocal level, and arrangement notes, but it hides exactly the things a final approval rests on: cymbal decay, low-level reverb tails, and the top end of a master.

Preview-only links for round one

Send a streaming preview link, not a download, for early revisions. Previews stop the client from dragging your mix into their phone’s music library and judging it against commercial masters, and they make it obvious which version is current. Label the link with the revision number so “the one from Tuesday” never enters the conversation.

Lossless for the final pass

For sign-off, send a 24-bit WAV at your session’s native sample rate. Uncompressed formats preserve the full signal chain without codec artifacts, which is why most delivery specs name WAV or another lossless format for masters. The point for your client is simpler: the file they approve should be the file you deliver, bit for bit, so nobody approves one bounce and receives another.

Confirming the client hears the same master you do

The risk in the preview stage is loudness normalization. Phone players and some browser players turn tracks up or down automatically, so your client may hear a different level than you bounced. Ask them to listen on one consistent setup, note which device they used, and if their notes mention a level problem you cannot reproduce, request a screenshot of their player or a quick call. A separate preview-only link keeps this stage contained instead of leaking full files into every revision round.

How do you collect consolidated feedback instead of scattered notes?

Scattered feedback is the fastest way to miss a note. A text at 11pm, a voicemail the next morning, and an email with “also the vocal feels a touch loud in the second chorus” means you’re assembling the revision list yourself, and something always slips. One channel, one song, one list.

Timestamped notes beat paragraph emails

Ask clients to comment at the moment they hear the problem, not after. “2:14 – snare too loud” takes them five seconds and takes you zero interpretation. Paragraph emails force you to scrub the timeline guessing where “that bit” is. A timestamp turns vague notes into an actionable list, and it makes patterns obvious: three comments at the drop means the drop needs work.

One feedback channel per song

Pick a single place for notes per song and say so in your delivery message. If the client insists on texting, you transcribe their notes into the channel yourself so the list stays complete. Tools built for this, like Filepass, Boombox, Samply, Audome, or our own RockScience Audio Portal, let clients comment directly on the waveform, so notes land with timestamps attached instead of in your inbox.

When should you send a bounce versus a full session export?

Bounces for approvals, sessions for handoffs

Send a stereo bounce whenever the goal is approval: revisions, mix checks, mastering previews. The client listens and gives notes; nobody needs the raw material. A full session export is for handoff, when another engineer will keep working on the material. If you are the last set of hands on the project, the client never needs the session.

Stems and dual-mono stems: when they’re actually needed

Stems earn their place when the client’s engineer will re-balance, edit for picture, or print alternate versions. Dual-mono stems matter for live sound and broadcast delivery, where L and R need independent processing. If the deliverable list does not name stems, do not bounce them; they double your render time and invite unauthorized edits.

One honest caveat: most client-facing portals, including our own Audio Portal, are built around bounces and streaming previews, not session handoff. For stem bundles, a transfer tool like WeTransfer or a direct portal such as Filepass still fits the delivery step.

Which sharing method fits which client and revision stage?

The decision framework

Match the method to the client and the stage, not to whatever you used last time.

Method	Best for	Stage
Streaming preview link	Clients judging balance and level on their own speakers	Rough mixes, early revisions
Branded transfer portal (RockScience, Filepass, Boombox, Samply, Audome)	Stems, lossless masters, version history, consolidated comments	Approved direction, final delivery
Generic transfer (WeTransfer)	One-off bounces for a hands-off client	Any stage, no feedback needed
Session export	Collaborators with their own DAW	Only when they’ll actually open it

Run each row through the same test: does playback stay consistent, is feedback in one place, and is the version label unambiguous? Generic transfer fails all three, which is fine for a client who never sends notes and never confuses files.

Where a branded portal fits, and where it doesn’t

Honest take on our own tool: RockScience Audio Portal wins on folder-level access, preview-only links, and dual-mono stem delivery under your own branding, at $9/mo. It does not replace a session export, and a client who just wants an MP3 in their inbox gains nothing from a portal login. For that client, WeTransfer is the right answer, not a compromise.

How do you handle endless revision requests without scope creep?

Endless revisions die the moment your quote says how many are included. State a number, state the price per extra round, and put both in writing before the first bounce leaves your studio. Solo engineers absorb the cost of vague terms, because every “one more tweak” lands on a fixed fee. A written deliverable count is the cheapest insurance you can buy.

Setting the revision count in your quote

Two or three rounds is the common norm for mix and master work, but the number matters less than the boundary. Write it plainly: “Includes two revision rounds. Further rounds billed at $X per round.” Also define what counts as a round, because a client sending ten notes over three days is one round, not ten.

A copy-paste revision request template

Send this with every bounce:

Round 2 notes, please send by Friday:

1. Timestamp + what to change
2. Timestamp + what to change

This is revision 2 of 3 included in the quote. Additional rounds are $X.

The template does three jobs at once: it forces consolidated feedback, it labels the version, and it shows the remaining count without you having an awkward conversation. Clients who see “2 of 3” self-police.

What does a complete revision round look like, start to finish?

Worked example: one song, three rounds

Round 1: you bounce v1 at 16-bit/44.1 WAV, label it SongTitle_v1_2024-06-03, and send a preview-only link so the client can stream it without downloading. Feedback comes back consolidated in one place: vocals up 1 dB in the choruses, snare too bright. Round 2: you print SongTitle_v2_2024-06-06, note the changes in your version history, and send it with the same link structure; the client approves the vocal level but flags the low end. Round 3: SongTitle_v3_2024-06-09 fixes the low end and the client signs off. You deliver final masters plus dual-mono stems through the same branded portal, so every version of the song lives under one roof instead of scattered across a transfer service and a NAS. Three rounds, three labeled bounces, zero confusion about which mix is current, and the whole exchange fits in one thread your client can reopen a year later.

FAQ

How many mix revisions should I include for free before charging extra?

Two or three rounds is the common norm for mix and master work. The number matters less than writing the boundary into your quote before the first bounce leaves your studio: “Includes two revision rounds. Further rounds billed at $X per round.” Also define what counts as a round, so ten notes over three days is one round, not ten.

Is it okay to send mix revisions over SoundCloud private links?

It works for a quick listen, but you lose control of the details that prevent extra rounds. SoundCloud shows no version history, no revision labeling, and no consolidated feedback thread, so “the one from Tuesday” enters the conversation. A branded portal keeps every round in one place with preview-only links; a private link is fine for a hands-off client who never sends notes.

What bit rate should a client preview a mix at before final approval?

A 320 kbps-style stream is fine for judging balance, vocal level, and arrangement notes during rounds one and two. Final approval should happen on a 24-bit WAV at your session’s native sample rate, because lossy streams hide exactly what sign-off rests on: cymbal decay, low-level reverb tails, and top-end detail. The file they approve should be the file you deliver.

How do I ask a client for feedback on a mix without getting vague notes back?

Ask for timestamped comments at the moment they hear the problem, not a paragraph email afterward. “2:14 – snare too loud” takes five seconds and needs no interpretation. Send a short template with every bounce that lists the revision number, the deadline, and how many rounds remain. Pick one feedback channel per song and transcribe anything that arrives by text.

Should I send stems or a mix bounce when the client wants changes?

Send a stereo bounce. Revisions are an approval process, and the client only needs to listen and give notes. Stems earn their place when the client’s engineer will re-balance, edit for picture, or print alternate versions. If the deliverable list does not name stems, do not bounce them; they double your render time and invite unauthorized edits.