How to send a screenshot that is too big to email

The attachment was rejected, so the obvious move is to compress it until it fits. For a screenshot that is usually the wrong move, because the thing you were trying to show is text, and text is exactly what compression destroys first. There is a better answer, and it also solves problems you had not counted as problems.

Why the limit bites sooner than the number says

Mail services publish a maximum attachment size, commonly around 20 to 25 MB. The number you can actually send is lower than that, because attachments are not sent as raw bytes. They are encoded into text so they survive a protocol designed for letters, and that encoding inflates them by roughly a third.

So a stated 25 MB limit is closer to 18 MB of real file, and it applies to the whole message rather than to each attachment. Three screenshots of six megabytes each is not comfortably inside a 25 MB limit, it is at the edge of it.

There is a second limit nobody mentions: the recipient's. Your message has to fit through their provider's maximum incoming size too, and theirs may be smaller than yours. A message that left your outbox successfully can still bounce at the other end, which is the most annoying version of this problem because it looks like it worked.

What compressing it costs you

Screenshots compress badly in the formats people reach for. JPEG was designed for photographs, where smooth gradients hide the artefacts it introduces. A screenshot is the opposite kind of image: hard edges, flat areas of colour, and small text with high contrast.

Those are precisely the features JPEG smears. Push the quality down far enough to hit an attachment limit and the error message you were trying to show becomes a grey suggestion of an error message. You have sent the file successfully and communicated nothing.

Scaling the image down has the same failure in a different shape. A screenshot at half size is a screenshot where the small print is gone. If the recipient has to ask you what it said, the compression did not work regardless of what the file size says.

Send a link instead

A link sidesteps the whole problem. The image is served at the quality you uploaded, so nothing is recompressed, nothing is scaled, and no attachment limit applies at either end. The message stays small enough to always deliver.

Screenshot Files gives you a share link for any screenshot in your library. The recipient opens it in a browser, on any device, without an account and without installing anything.

It also survives the things attachments do not. Chat apps rescale images on the way through. Mail clients recompress large ones. A link is a link in every channel, and it looks the same at the other end as it did when you sent it.

What a link gives you that a file cannot

This is the part that turns a workaround into an upgrade. Once a file has left as an attachment, it is out of your hands permanently. It sits in a mailbox you do not control and it is still there in a year.

A link stays yours. You can give it a lifetime of one day, seven days or thirty. You can put a password on it, so that a link forwarded to the wrong thread is not enough on its own. You can make it open only once, for anything meant for one person and one moment. And you can delete it, which stops it resolving immediately, whatever expiry it had.

None of that is possible with a file you already sent. Being able to change your mind after the fact is worth more than the attachment limit you were originally trying to get around.

If you do have to send a file

Sometimes a policy or a recipient requires an actual attachment. Two things help.

Crop first. Most oversized screenshots are oversized because they captured an entire 4K display to show one dialog box. Cropping to the part that matters often takes a file under the limit on its own, with no quality loss at all, and it makes the screenshot clearer at the same time.

Keep it in a format built for this kind of image. PNG and WebP handle flat colour and sharp text without smearing them. WebP in particular produces a much smaller file than PNG at the same visual quality on screenshots, which is why cloud copies here are stored that way.

And before you send anything, check what else is in frame. A screenshot cropped to the dialog is also a screenshot that no longer shows your browser tabs, your notification banners or the email address in your account menu.

Common questions

What is the actual Gmail attachment limit?

25 MB per message, which is roughly 18 MB of real file once encoding overhead is counted, and it covers everything in the message rather than each attachment separately. The recipient's incoming limit applies as well and may be lower.

Does the recipient need an account to open a link?

No. A share link opens for anyone who has it, plus the password if you set one. They do not sign up, install anything, or see the rest of your library.

Can I stop a link working after I have sent it?

Yes. Deleting the share link stops it resolving immediately, whatever expiry it was given. The screenshot itself stays in your library.

Will the image lose quality when I upload it?

Cloud copies are converted to WebP, a format designed to keep sharp edges and text crisp at a fraction of the size of a PNG. It is not the lossy smearing you get from pushing a JPEG down to fit an attachment limit.