To compress images for upload, re-encode them at quality 80, which returns a typical phone photo 60 to 80 percent smaller with no visible change. If a strict form wants less, reduce the pixel dimensions too, then convert to WebP. Every major destination publishes its cap, and this page lists them with the fastest route under each.
The levers themselves, quality, dimensions, and format, get the full treatment in my complete guide to compressing an image. This pillar is about the destinations. An inbox, a web page, a Word file, and a government portal each has its own ceiling and its own failure message, and the right move is slightly different at each one. I built the compressor these guides sit on top of, so every number below is either a published platform cap with its source linked at the claim, or a measurement from my own tool.
Why do email and upload forms limit image size?
The limits protect the infrastructure, not you. An email with a 40 MB photo attached does not fail politely on its own; it ties up the connection, times out, and retries until something gives up. Mail systems draw the line before sending starts, and web forms do the same to keep their storage and processing costs predictable.
Two details in the fine print catch more people than the headline numbers do. First, email caps apply to the whole message, not to each file. The limit covers the attachments plus the text and inline pictures around them, so four 7 MB photos break a 25 MB limit even though every one of them clears it alone. Second, your cap is not the recipient's cap. A message that fits under your provider's ceiling can still bounce off a stricter server on the receiving end, which is why the practical target sits well under the published number, never right at it.
Web forms add a third wrinkle: their limits are set per site, and they run far lower than email's. A form that accepts 2 MB is a generous one. Plenty of government and ID portals want a few hundred kilobytes, and some want less than one hundred. The fix is the same motion everywhere; only the target changes.
What are the real upload size limits?
Six published caps cover almost every upload you will meet: 25 MB on Gmail and Outlook.com, 20 MB on Outlook desktop with an internet account, 10 MB by default on Exchange work accounts, 33 MB on Outlook mobile for most account types, and whatever number a web form prints next to its upload button. The table and chart below put them side by side.
Email attachment size limits, sourced
The email attachment size limit is the wall people hit most, and the numbers are published. Gmail caps the message at 25 MB, and going over does not bounce the mail; Gmail uploads the file to Google Drive and inserts a link in place of the attachment (Gmail's attachment help). Outlook.com uses the same 25 MB for the whole message and offers OneDrive sharing for files up to 2 GB, which do not count toward the message limit at all (Microsoft's sending limits page).
Desktop Outlook is stricter. Internet accounts, meaning Gmail or Outlook.com addresses used in the desktop app, get 20 MB per message, and Exchange business accounts default to 10 MB, a number your admin sets and one that is often lower than you expect. The limit includes both the attachment and the email itself, and Microsoft is blunt about why the cap exists: it prevents your computer from continually trying to upload attachments that exceed the limits of most internet service providers (Microsoft's attachment size guidance).
Outlook mobile allows 33 MB on most account types and 20 MB on iCloud accounts, and it offers to compress or resize any image over 1 MB as you attach it, which is the one place in the email world where the fix is built into the failure (Outlook mobile's attachment docs).
| Destination | The cap | When you hit it |
|---|---|---|
| Gmail | 25 MB per message | The file becomes a Google Drive link |
| Outlook.com | 25 MB per message | Attachment refused; OneDrive sharing offered |
| Outlook desktop, internet accounts | 20 MB per message | The send fails until the message shrinks |
| Outlook desktop, Exchange | 10 MB by default | Admin-set, and often lower in practice |
| Outlook mobile | 33 MB, or 20 MB on iCloud | Images over 1 MB get a compress prompt |
| Web forms and portals | Set per site | Rejection, usually with the max in the error |
Where a phone photo lands on that scale
A phone photo runs about 4.5 MB straight off the camera, so five of them total 22.5 MB. That squeaks under Gmail's 25 MB with almost no room for the message around them, fails Outlook desktop's 20 MB outright, and lands at more than twice the 10 MB Exchange default. Compressed at quality 80, each photo comes back around 900 KB, so the same batch weighs roughly 4.5 MB and clears every cap in the table with room to spare.
That before and after is the whole argument of this page in one picture. The raw batch fails two of the five email routes; the compressed batch fits all of them without getting near a quality level anyone can see.
How do you compress images for upload?
Work the levers in order, quality first, dimensions second, format third, and stop the moment the file fits the cap. This is the fastest route to compress images for upload of any kind, and the same six steps cover email, forms, and everything between.
- Find the cap. Email caps are in the table above. For a web form, the maximum is usually printed next to the upload button, and when it is not, the error message after a failed attempt usually names it.
- Re-encode at quality 80. Drop the photo on the free compressor and leave the slider where it starts. That one pass returns a typical phone photo 60 to 80 percent smaller, and at quality 80 a photograph is visually lossless at normal viewing size.
- Read the live after size. Still over the cap? Pull the slider lower and watch the number drop until it fits. Re-compressing the same upload at a new quality or format never costs another image.
- Cut the pixel dimensions if quality alone cannot reach the number. A photo 4000 pixels wide headed for an inbox or a form is carrying pixels no screen there will show. Resampling to half the width leaves a quarter of the pixels, and the byte count falls with them. On a desktop, Preview's Adjust Size on a Mac and the Photos app's resize on Windows both do this without installing anything.
- Convert the format for the last stretch. WebP is typically 25 to 35 percent smaller than a JPEG of the same visual quality, and AVIF is often around 50 percent smaller at the cost of a slower encode. If the form only accepts JPG, stay in JPG and lean harder on steps 3 and 4.
- Inside a document, compress in place instead. Office's Compress Pictures command handles images already embedded in a file, and it has its own section below.
What happens to your file on the way through
Two useful things happen during that pass that you would otherwise do by hand. EXIF data, the hidden metadata block your camera writes into every file, including GPS coordinates, camera model, and the exact moment of the shot, is stripped by default, which matters more on uploads than anywhere else because you rarely control where an uploaded file ends up. And JPEG output is written progressive, so on a slow connection it renders in passes instead of loading top to bottom. The copy you upload to our servers is deleted within the hour.
The five-to-one rule for picking a lever
Divide the file size by the cap before you start. If the ratio is under five to one, the quality slider alone will get you there, because quality 80 takes a 4.5 MB phone photo to roughly 900 KB, a factor of five. If the ratio is bigger than five to one, no quality setting closes the gap on its own; cut the dimensions first and let the resize do the heavy lifting. That one division saves the trial and error that makes people give up on strict forms.
Should you resize or compress before uploading?
Compress first when the cap is in megabytes, resize first when it is in kilobytes, and expect to do both for the strictest forms. The two operations shrink different things: compression re-encodes the bytes while keeping every pixel, and resizing removes pixels outright.
| The cap says | Start with | Why |
|---|---|---|
| 10 MB or more | Quality 80 compression | A phone photo drops 60 to 80 percent in one pass |
| 1 to 10 MB | Compression, then resize | Quality gets close; a resize covers scans and PNGs |
| Under 1 MB | Resize, then compress | No quality setting squeezes 4000 pixels into kilobytes |
The trap between the two is the corner handle. Dragging an image smaller inside a message or a document changes the display size, not the file, and Microsoft's own troubleshooting page for Outlook.com says it directly: resizing how a picture looks does not reduce what it weighs, and the real fixes are compressing the file itself or sharing it as a cloud link (Microsoft's attachment troubleshooting).
Whichever order you use, work from the original and keep it. Lossy compression is a one-way door, and the day a different destination wants a different size, you want to start from the full file, not from last month's compressed copy.
Do email, web, and documents need different treatment?
Yes, because they fail differently. Email rejects you at a hard cap, the web punishes you quietly with load time, and documents swallow the bytes and balloon. The motion is the same; the target and the tooling shift.
Email: compress the batch, not the biggest file
The whole-message rule sets the target. Your byte budget covers every photo plus the text around them, so the count of attachments matters as much as any single file, and the batch math from the chart above is the habit worth keeping: five raw photos fail where five compressed ones fit. The email guide walks the attachment workflow step by step, including what the compress prompts on phones actually do to your picture.
The web: no cap, just slower pages
No form says no; the page just gets slower, and visitors pay the bill on every load. The discipline is to resize each image to the largest width the page actually displays, compress it, and serve WebP. The demo file on our home page makes the case in one pair of numbers: a 497 KB JPG becomes a 214 KB WebP at quality 80, which is 56.9 percent smaller with the same picture on screen. The website guide covers dimensions, formats, and the order to apply them.
Documents: compress inside the app
Images embed and travel with the file, which is how a deck of ten 4.5 MB camera shots becomes a 45 MB attachment before you have written a word. The fix lives inside Office: select a picture, open Picture Format, run Compress Pictures at the 220 ppi default, and tick the option to delete cropped areas of pictures, which discards the regions you cropped away but the file still secretly carries (Microsoft's Office picture guidance). The walkthroughs for PowerPoint, Word, and Excel cover each app's quirks.
Scans and TIFFs: the special case
A scanner hands you a TIFF, and a TIFF laughs at email caps. That format is its own problem with its own fix, covered in reducing a TIFF file's size.
What if the form wants the size in KB?
Kilobyte caps flip the order of operations: cut the pixel dimensions first, because no quality setting squeezes a full-resolution photo into tens of kilobytes, then compress the smaller image down to the number. This is the territory of government portals, job application sites, and ID photo systems, and a phone photo misses their targets by a factor of twenty or more.
Why resize comes first at KB scale
The related questions people search, compress image to 50KB, compress image to 100KB, compress image to 200KB, are all the same workflow with a different divisor. A 4.5 MB photo aimed at 100 KB needs a forty-five-fold reduction, and the five-to-one rule from above says quality alone covers a factor of five at best. Dimensions supply the rest: a resize to a third of the width leaves roughly a ninth of the pixels, and the byte count follows. Resize to about the size the form displays, then work the slider against the live number.
Artifacts and privacy: the two ID photo traps
Over-compression is visible, first as blocking in smooth areas like skies and backdrops, then as smeared faces, and on an ID photo that can get the upload rejected a second time for image quality. The pillar on compressing without losing quality maps where that floor is before you cross it. The second trap is quieter: the file off your camera carries EXIF metadata, including the GPS coordinates of where the shot was taken, which is not something an ID upload needs to disclose. We strip it by default. For the walkthroughs, see compressing an image for an upload form and compressing passport and visa photos to KB limits.
How do you prep a batch of photos for upload?
Compress every photo in the batch, not just the biggest one, because email caps count the whole message and a set of near-limit files fails together. Batch prep is one pass, not thirty.
You can drop up to 30 images at once on the compressor, up to 25 MB each, with no signup, and the same quality 80 pass runs across all of them. Check the total against your cap rather than each file alone; the five-photo example above is the arithmetic in miniature, and it scales linearly. If one straggler stays heavy, a scan saved as PNG usually, re-run just that file at a lower quality or convert it, since re-compressing never costs another image. iPhone photos saved as HEIC are the other straggler: convert them to JPG first with your phone or computer's built-in export, since most upload forms and the compressor both work in JPG, PNG, WebP, and AVIF.
The habit that pays longest: compress before you share, not after something bounces. When the small file is the one that leaves your hands, every app downstream gets it, and nothing recompresses your photo into mush later.
When should you send a link instead of an attachment?
When the recipient needs the original bytes, stop compressing and share a link. A photo going to print, a file a designer will edit, anything where the pixels themselves are the deliverable: compression that helps an inbox actively hurts those jobs.
The mail systems already have the escape hatch built in. Gmail switches an oversized attachment to a Google Drive link automatically, and Outlook.com offers OneDrive sharing for files up to 2 GB, which do not count against the message limit at all. Volume tips the same way: thirty vacation photos are a miserable set of attachments even compressed, and a single shared album handles them better.
The rule I use is short: compress when the image is meant to be looked at, link when the file itself is the point.
Where should you go next?
This page is the hub for destination problems, and each spoke goes deeper than a hub should. Pick the one that matches the upload in front of you.
- Compress images for email covers the attachment workflow end to end, caps, prompts, and phones included.
- Compress images for your website covers display widths, WebP, and the order to apply them.
- Compress an image for an upload form covers reading a form's stated max and hitting it on the first try.
The Office walkthroughs for PowerPoint, Word, and Excel, the TIFF guide, and the passport photo guide are linked in their sections above, and the sibling pillars on the complete method and on quality limits are one click from the top of this page.