Archives

How to Shrink Files for Email

"File too large" — and the email won't send. A familiar wall. The first instinct is to zip it, but with photos and videos that barely helps. Let's look at where the real mail limits are, why an archive doesn't always save you, and which four methods actually shrink a file for sending.

A white external drive with a USB cable on a grey background, black-and-white photo — an image of transferring files
There are four different ways to shrink a file for sending. The key is picking the right one for your file type. Photo: Pexels

The real limits of mail and messengers

Before compressing anything, it helps to know exactly what you need to fit under. Limits vary by service, and that's often the root of the problem:

ServiceAttachment limitOver the limit
Gmail25 MBAuto-link to Google Drive
Outlook / Hotmail20 MBAuto-link to OneDrive
Yahoo Mail~25 MBCloud link
Telegramup to 2 GBFile sent in full
WhatsAppup to 2 GBFile sent in full

The key takeaway: mail limits are strict and small, while messengers are far more generous. But there's a hidden trap — these numbers don't refer to the file size you see on disk.

Why a file "fattens up" 37% in email

Here's why a "24 MB" file won't go through Gmail's 25 MB limit. Attachments are encoded before sending over the mail protocol, and that encoding grows the size by about 37%. So the limit is measured against the "inflated" size, not the original.

In practice this means: a 20 MB file on disk becomes roughly 27 MB in the email and no longer fits in Gmail. The safe attachment ceiling is around 18 MB on disk, so there's headroom after encoding. And the second trap is the recipient's limit: if you send from Gmail (25 MB) to Outlook (20 MB), the message is capped by the smaller limit.

Leave headroom

Don't squeeze a file right up to the limit. Aim for about 18 MB on disk for email — then neither the +37% encoding nor the recipient's stricter limit will catch you out.

Method 1: compress the file itself

The most underrated and yet most effective route is to shrink not the "packaging" but the file itself. And here it matters what you're sending, because archiving behaves differently with different data types.

Photos. A phone shot easily weighs 5–12 MB, and a few of them already blow past the limit. Wrapping them in a ZIP is nearly pointless — JPG is already compressed. The real gain comes from lowering resolution and quality: a 4000×3000 photo is overkill for email or a messenger; 1600 pixels on the long side is plenty, and the size drops several times over. How to do it without visible loss is in the guide compress images without losing quality, and specifically for the format — compress JPG.

PDF documents. A heavy PDF is almost always heavy because of the images inside. Re-compressing them shrinks the file several times over with no loss of readability — details in how to reduce PDF file size.

Video. Here an archive won't help at all — MP4 is already compressed by a codec. You need to re-encode the video (lower bitrate/resolution): see how to compress video.

A simple rule

Already compressed (photos, video, music) — compress it as a source, don't archive it. Not yet compressed (documents, spreadsheets, text) — an archive is fine. Why this is so is unpacked in the article on lossless compression.

Method 2: split the archive into volumes

Sometimes a file can't be compressed (say it's a large installer or a database) but has to go by email. Then splitting the archive into volumes saves you: the archiver divides it into parts of a set size — say 18 MB each — and you send them in several emails.

1

Create an archive with volumes

In 7-Zip or WinRAR, when creating the archive choose "Split to volumes, size" and set, for example, 18 MB.

2

Get a set of parts

You'll get files like archive.7z.001, .002 and so on. Each fits into an email separately.

3

Send and explain reassembly

The recipient needs to download all parts into one folder and open the first — the archiver reassembles them. Without one part, the extraction fails.

The method works but is clunky: the recipient needs an archiver and some care. For most everyday tasks the next option is more convenient.

A server tower under blue light — cloud storage for files
The cloud removes the mail-limit question: instead of the file, you send a link to it. Photo: Pexels

Method 3: a cloud link

For truly large files the best route is not to attach them at all. Upload the file to the cloud (Google Drive, OneDrive, Dropbox) and send a link. Mail limits become irrelevant: the email is tiny, and the recipient downloads the file whenever it suits them.

The best part is that mail services do this automatically. If an attachment in Gmail is over 25 MB, it offers to upload it to Google Drive and inserts a link; Outlook does the same with OneDrive. So often there's nothing to set up — just attach the big file and accept the offer.

For a file just over the limit it's simpler to compress. For a very large one, a link is more reliable. Split volumes are the last resort, when you can't compress and the cloud isn't available.

What to choose for your situation

Let's fold it into a clear decision:

  • Photos, screenshots, a PDF, a video just over the limit → compress the file itself. Fast, and the recipient opens the attachment immediately.
  • Many document files → collect them into a ZIP (text and spreadsheets compress well) and split into volumes if needed.
  • A very large file (hundreds of MB, video) → a cloud link. It doesn't depend on limits and doesn't burden the recipient.
  • Recipient on a messenger → send it directly: Telegram and WhatsApp accept up to 2 GB.

Compress your files right now

FormatZ shrinks and converts images, documents and other formats right in your browser — no install, no sign-up. Often a single compression is all it takes for the email to go through.

Open all converters

The main takeaway is simple: before battling the limit, look at the file type. Already-compressed media shrinks by re-encoding the source, not-yet-compressed documents shrink in an archive, and giant files aren't sent as attachments at all but as a link. And if you're curious why JPG and video so stubbornly refuse to shrink in a ZIP — that's a separate and intriguing topic: lossless compression.

Gmail is 25 MB per message, Outlook is 20 MB. An important subtlety: the limit is measured after encoding for transmission, which inflates the file by about 37%. So a 20 MB file on disk becomes roughly 27 MB in the email and may not go through. The safe attachment ceiling is around 18 MB on disk.
It depends on the file type. Archives compress documents, spreadsheets and text well. But photos (JPG), video (MP4) and music (MP3) are already compressed — ZIP or 7z will shave off only a few percent. For media it's far more effective not to archive but to compress the files themselves: lower the resolution and quality of a photo, or re-encode the video.
Three routes. First, compress the file itself (photo, PDF, video) — often that's enough. Second, split the archive into volumes of the required size and send them in parts. Third, and most convenient for big files, upload the file to the cloud and send a link; Gmail and Outlook do this automatically via Google Drive and OneDrive.
For files just over the limit it's simpler to compress: the recipient opens the attachment right away, with no extra clicks. For truly large files (hundreds of megabytes, video) a cloud link is better — it doesn't depend on mail limits, and the recipient downloads when convenient. Messengers like Telegram and WhatsApp also accept up to 2 GB.
Two common reasons. First, attachment encoding adds about 37% to the size, so a file right at the edge of the limit can exceed it. Second, the recipient's limit: you send from Gmail (25 MB) to Outlook (20 MB), and the message is capped by the smaller limit. Leave headroom: keep the attachment within about 18 MB on disk.