How to Reduce Video File Size for Sending (Email, WhatsApp, Discord)

Most guides that cover this topic give you one instruction: compress your video. That's incomplete. There are actually two different problems that look identical from the outside, and the fix for one can make the other worse if you don't know which problem you have.

Problem one: the file is above the platform's hard size limit and simply won't send. Email has this. Discord (free) has this. Problem two: the platform accepts the file but silently re-encodes it at low quality before delivery, so the recipient gets a degraded copy. WhatsApp has this. iMessage has a version of this. Understanding which problem applies to your situation changes what you should do entirely.

The Short Answer — Skip Straight to Your Platform

If you're in a hurry, here's the bottom line for each platform before the explanation.

Why Phone Video Files Are So Large

Modern smartphones record video at bitrates that were unimaginable five years ago. An iPhone 15 Pro shoots 4K 30fps HEVC at around 60–75 Mbps in standard mode, and in ProRes — which some people accidentally leave on — it records at up to 200 Mbps. That is the same bitrate as a professional broadcast camera. A 90-second clip in standard 4K from an iPhone weighs in at roughly 700 MB–1 GB. ProRes takes it to 2–3 GB for the same clip.

Those bitrates exist because phones are designed to record first and compress later — the high bitrate preserves as much quality as possible for editing. They were never intended to be the final delivery format. When you try to send a raw phone video, you're sending a production file, not a delivery file. The compression step people skip is the one that was always supposed to happen.

I took a 90-second clip recorded on an iPhone 15 at 4K 30fps. The iCloud export came in at 1.1 GB. Here is what happened at each compression step:

• 4K H.264 CRF 23: 112 MB — still too large for email or Discord
• 1080p H.264 CRF 24: 43 MB — fits Nitro Basic, too large for email
• 1080p H.264 CRF 27: 22 MB — fits email with a little room
• 720p H.264 CRF 26: 11 MB — fits Discord free with room to spare
• 720p H.264 CRF 29: 7.4 MB — fits Discord free comfortably

Watched on a phone: the 720p CRF 29 version and the original 4K file are indistinguishable at arm's length. The difference only becomes apparent on a 4K reference monitor at 100% zoom — which is not how anyone watches a video someone sent them.

Resolution Is Your Biggest Lever

Codec settings and quality sliders get most of the attention. But resolution is almost always the single largest factor in file size, and it's the one step most people are afraid to touch because they think it means a blurry video.

A 4K video contains four times as many pixels as a 1080p video. A 1080p video contains over twice as many pixels as a 720p video. If the person on the other end is watching on a phone — which they almost certainly are — they are viewing at a screen resolution that tops out at 1080p on a large phone and 720p on most mid-range models. Sending them 4K pixels that their screen will never actually render is paying 4× the file size for zero visual benefit.

My honest take: drop to 720p first, before touching anything else. It is the single step with the best file size reduction to quality tradeoff for the use case of "sending a video to someone." If the output still doesn't fit, then lower the CRF. If it still doesn't fit, try 480p. Do it in that order.

The one exception: if the recipient specifically needs the high resolution — a client reviewing footage for a production, someone who will edit it further, someone displaying it on a large TV — then resolution matters. For casual sharing, 720p is the right answer almost every time.

WhatsApp: The Platform That Mangles Your Video

WhatsApp is the most frustrating platform on this list because it has a problem people don't expect: it re-encodes your video before delivering it to the recipient, regardless of whether the file would have fit without re-encoding.

When you pick a video from your gallery and send it through WhatsApp's standard video picker, WhatsApp compresses it — at settings you have no control over, targeting a low bitrate that prioritises fast delivery over quality. The recipient sees a degraded copy. This happens whether your video is 10 MB or 500 MB. The re-encoding is not optional when you use the video path.

If you want to use the standard video path — for example, because you want the recipient to be able to stream it inline rather than download a file — then compress the video yourself first before sending. If WhatsApp is going to re-encode your video, give it the best possible source file to work from. A video you've already compressed to a clean, low-artifact encode at a reasonable bitrate will survive WhatsApp's re-encoding better than a massive, bloated phone recording will. You're not beating WhatsApp's compression — you're limiting the damage it can do.

I tested this directly. Sending the same 90-second clip via WhatsApp's gallery picker produced a 5.2 MB file on the recipient's end that looked noticeably soft and blocky in fast-motion segments. Sending the same clip at 720p H.264 CRF 26 (11 MB) via the Document path delivered an 11 MB file that looked clean. The quality difference was obvious.

Discord: The 8 MB Wall

Discord's 8 MB attachment limit for free accounts is a genuinely small number. To put it in context: at decent quality, 8 MB gives you roughly 60–90 seconds of 480p video, or 20–35 seconds of 720p. If your clip is longer than that, compression alone will not save you at watchable quality — something else has to give.

Unlike WhatsApp, Discord does not re-encode anything. What you upload is exactly what the recipient downloads. That is good news because it means your quality settings matter and will be preserved. It is also unforgiving — if your file is 8.1 MB, it will not send and there is no workaround short of getting it below the limit.

For clips you need to get under 8 MB, the correct approach in order of priority:

1. Drop resolution to 720p or 480p first. This is usually enough to bring most short clips under 8 MB.
2. Lower CRF to 28–32. Quality will decrease slightly but the video will still look reasonable on a Discord embed playing at small size.
3. Trim the clip. If you're sending a 3-minute clip, consider whether 30–60 seconds of the most relevant part would serve the same purpose. A 30-second 720p clip at CRF 28 should come in under 4 MB.
4. Paste a link instead. Google Drive, Dropbox, Streamable, and WeTransfer all allow larger files and are widely accepted in Discord. A file-sharing link in a chat is a completely reasonable alternative — don't spend an hour compressing when a 10-second upload to WeTransfer solves the problem.

Email: The 25 MB Myth

Gmail, Outlook, and Yahoo all advertise a 25 MB attachment limit. The number you should actually be targeting is closer to 18–19 MB.

Email attachments are encoded in a format called MIME base64 when transmitted — a standard that converts binary data to ASCII text for safe transport through email servers. Base64 encoding increases the size of the data by approximately 33%. A 19 MB video file becomes a roughly 25 MB email attachment in transit. Mail servers that enforce a 25 MB limit measure the encoded size, not the raw file size. A file that appears to be 23 MB in your file manager will frequently bounce.

I've watched too many people target 24 MB and have their attachment rejected. Target 18 MB if you want the video to reliably arrive.

For anything longer than about 2 minutes at 720p, email attachments are the wrong tool entirely. The correct approach is:

• Upload to Google Drive, iCloud, Dropbox, or WeTransfer
• Generate a share link
• Paste the link into the email body

WeTransfer's free tier handles files up to 2 GB with no account required. It is the fastest option for a one-time send. Google Drive is better if the recipient needs long-term access or will edit the file.

Which Codec to Use When Sending

For all three platforms — email, WhatsApp, Discord — the answer is H.264 in an MP4 container. Every device made in the last decade plays H.264 MP4 without issues. It embeds and previews correctly in Discord, plays inline on WhatsApp, and opens without needing additional software after downloading from email.

H.265 is roughly 40% more efficient at the same visual quality, which sounds appealing. But H.265 is still not universally supported for inline playback. Some Windows versions don't play it without a paid codec pack. Some older Android devices struggle with it. Discord's inline player has inconsistent H.265 support. For sending to an unknown recipient — which is almost always the case with email — H.264 is the right choice. The slightly larger file size is the price of compatibility.

Audio: Keep It Simple

Audio rarely contributes much to the total size of a short video — typically 3–8% — but misconfigured audio does add up over longer clips.

• AAC at 128 kbps stereo is correct for virtually all consumer video. Indistinguishable from uncompressed at normal listening levels through phone speakers or earbuds.
• 96 kbps AAC is genuinely fine for speech-only content — voiceovers, screen recordings with narration, phone call recordings. Save yourself a few MB on a long clip.
• Drop surround sound if your source has it. A 5.1 audio track on a video you're sending over WhatsApp adds file size that will be downmixed by the recipient's device anyway.

The one thing not to do: leave audio at a very high bitrate (256 kbps, 320 kbps) while aggressively compressing the video. High audio bitrate does not compensate for low video quality — it just costs you MB you could spend on keeping the video CRF lower.

When Compression Won’t Save You

Sometimes the honest answer is that what you're trying to do isn't physically possible at acceptable quality. If you need to get a 20-minute video under 8 MB for Discord free, no compression settings will produce a watchable result. A 20-minute 480p video at a bitrate low enough to hit 8 MB would look like a moving thumbnail.

The same applies to email. A 10-minute 1080p video will not fit in an 18 MB attachment at any quality level worth watching. Trim the clip to the relevant section, or send a link. If neither is acceptable, compress to the limit and accept that the recipient will get a lower quality version than you intended — and be upfront with them about that.

Recommended Settings by Use Case

Skip the theory — here is what to actually use:

Frequently Asked Questions

What is the actual video file size limit for Gmail?

Gmail's stated limit is 25 MB, but email attachments are base64-encoded in transit, which adds roughly 33% to the transmitted size. A 19 MB video file becomes approximately 25 MB on the wire. Most mail servers enforce the limit on the transmitted size, not the file size. Target 18–19 MB to be safe — a 23 MB video file will frequently bounce even though it's technically under 25 MB.

Does WhatsApp compress videos when you send them?

Yes, when you send through the standard video/gallery path, WhatsApp re-encodes the video at a lower bitrate before delivery. The recipient gets a degraded copy regardless of how good your original was. To bypass this, send the file as a Document instead — tap the attachment icon, choose Document, and navigate to your video file. WhatsApp sends Documents without re-encoding, up to 2 GB.

What is Discord's video file size limit?

8 MB for free accounts. Nitro Basic raises this to 50 MB. Nitro raises it to 500 MB. Discord does not re-encode attachments — what you upload is exactly what the recipient downloads. If your compressed video is still over 8 MB after dropping to 720p and CRF 30, the only options are to trim the clip shorter or share a file-hosting link instead of a direct attachment.

What resolution should I use when compressing video for sending?

720p is the right default for most situations. It is indistinguishable from 1080p when viewed on a phone at arm's length, and the file size difference is substantial — typically 40–60% smaller than 1080p at the same CRF. The only reason to keep 1080p is if the recipient specifically needs it for professional review or further editing. For casual sharing, 720p is the correct target.

Can I send a video larger than 25 MB by email?

Not as a direct attachment through Gmail, Outlook, or Yahoo — all three enforce the limit and bounce files that exceed it. The correct approach for larger files is to upload to Google Drive, Dropbox, WeTransfer, or iCloud and paste the share link into the email body. WeTransfer handles files up to 2 GB on the free tier with no account required and is the fastest option for a one-time send.