Skip to content

Make it small enough to email

Compress to 18 MB so it clears the usual 25 MB attachment limit with room to spare.

Input

Drag & drop an image or video

or click to choose

Images (JPG, PNG, HEIC, WebP, GIF, AVIF, BMP) and video (MP4, MOV, WebM, MKV, AVI, M4V and more)

What this tool decides

You pick a destination rather than a quality percentage. Drop a file and these five reorder by how well each one fits it, each with an estimated output size.

  • Put it on a web pageFor a blog or site. Scaled down to what actually gets displayedLong edge 1600px
    Quality 0.82
  • Send by email or chatSmall enough for attachment limits, and opens anywhereLong edge 1280px
    Quality 0.75
  • Post to social mediaKeeps the resolution, so it survives the platform’s own re-encodeLong edge 2048px
    Quality 0.85
  • As small as possibleWhen size wins. Quality will visibly dropLong edge 1024px
    Quality 0.60
  • Keep the qualityNo resizing at all — only the wasted bytes come offSize untouched
    Quality 0.92

Result

Nothing here yet

Why these settings

Gmail's attachment limit is 25 MB — but a 25 MB file will not attach. Mail encodes attachments as Base64 text on the way out, which inflates them by roughly 37%. What actually fits inside a 25 MB envelope is about 18 MB of original file.

That is why the target here is 18 MB. "It says 25 MB but it will not send" is this inflation, and Google itself describes the receiving side as "about 37% increase".

Above 25 MB, Gmail replaces the attachment with a Google Drive link. If the recipient can open a link, letting it do that keeps the quality far better than compressing.

25 MB is the Gmail and Outlook.com figure, not a universal one. Outlook for desktop defaults to 20 MB and Exchange Online to 35 MB, which administrators can change. Go smaller if the recipient is on a stricter server.

Common questions

Why does Base64 add 37%?
Mail bodies were designed to carry text, so anything that is not text — an image, a video — gets rewritten as text using Base64. That scheme turns every 3 bytes into 4 characters, which is 4÷3 ≈ 1.33x on its own. The mail standard also caps lines at 76 characters, and the line breaks push it to roughly 1.37x. The inflation only exists in transit; once the recipient saves the attachment it is back to its original size.
How do I find out what the recipient can accept?
Ask them. The limit belongs to the receiving server, not the sending one, so your Gmail can accept the message and their corporate mail server can still bounce it — sometimes without telling you. As a rough guide, plenty of internal mail systems cap around 10 MB. When you do not know and the file has to arrive, staying under 10 MB is the safe choice.
Split the file, or compress it?
Compress it. Splitting hands the recipient a reassembly job whose steps depend on the software they happen to use, and someone who is not technical simply stops at a folder full of parts. If the quality really cannot be reduced, a shared cloud link is far easier on the other person than a split archive.

Related purposes

Sponsored links