How to Shrink Photos for Email and Upload Limits
The form already told you the number. It was in the error, or in the help page, or in a host's PHP default that nobody printed on the form. The job is to land under that number without turning the sky into blocks. Shorten the long edge first. The quality slider is the second move, and it is the one people make too early.
Read the number on the form before you touch the slider
"Too large" is not one limit. Gmail's help page documents an attachment limit of 25 MB. Outlook.com's help page documents 20 MB. A school portal, a visa form, a job site, or a WordPress install will name its own cap in the error, often 2 MB, 5 MB, or 10 MB. PHP's stock upload_max_filesize is 2 megabytes until the host raises it, so a photo that opens fine in your mail can fail on a contact form that never states a number. Write down the number you have to beat. Then make a file that lands under it with room to spare.
Room to spare matters because the file on disk is not always the size on the wire. Mail attachments are commonly encoded as Base64, which uses four characters for every three bytes. A 15,000,000-byte JPEG is about 20,000,000 bytes once encoded, before headers. A photo that looks safely under a 20 MB ceiling at 18 MB on disk can still bounce. Leave a margin of roughly a third on mail, and a smaller margin on a web form that uploads the raw bytes. If you are attaching several photos, add them up. The limit is usually on the message, not on each file.
This is a different job from publishing a hero image. A web page wants a file near 100–200 KB at the right pixel size, which is the subject of Compressing Images for Core Web Vitals. A mailbox wants "under the cap, still a photo." Do not drive the slider to 40 to hit a mail limit you could have hit by shortening the long edge.
Dimensions move the size more than the slider does
A 24-megapixel camera frame, 6000 × 4000, holds 24,000,000 pixels. An email preview and a form thumbnail do not display that. A long edge of 1600 pixels is 1600 × 1067 if you keep the 3:2 frame, which is about 1.7 million pixels, under a tenth of the original count. A long edge of 1920 is still only about 2.5 million pixels. The full arithmetic, and why you resize before you re-encode, is in Resizing vs Compressing.
JPEG file size does not shrink by the same ratio as the pixel count, because the camera file is already compressed and because flat skies compress more than foliage. The direction is reliable: a multi-megabyte camera JPEG, resized to a 1600-pixel long edge and saved again around quality 80, is usually a mail-sized file. I will not quote a single kilobyte target as if every photo behaved the same. Look at the size the studio prints next to the preview, and look at the file after it lands in your downloads folder. Those two numbers are the ones that count.
| Cap you read on the form | Where to start | If you are still over |
|---|---|---|
| About 10 MB, or a 25 MB mailbox with several photos | Long edge 2400 px, JPEG quality 80–85 | Drop the long edge to 1920 before you drop quality below 75. |
| 5 MB | Long edge 1920 px, JPEG quality 80 | Long edge 1600. Check the download's byte size, not the camera's. |
| 2 MB (common on PHP defaults and older portals) | Long edge 1600 px, JPEG quality 75–80 | Long edge 1280. One photo per upload if the form allows it. |
| Under 500 KB, "thumbnail" or "avatar" | Match the stated pixels (often 400–800) | Quality 70 is plenty at that size. Below that, blocks show up in the sky. |
These are starting points for photographs, not a guarantee. A night shot full of grain and a page of scanned text do not compress the same way. Scanned documents that are already PDFs should go through the PDF Suite, using the preset guidance in How to Shrink a PDF Locally, instead of being photographed again as a JPEG of the screen.
Do it in Image Studio
- Drop the photo on the home page. If the phone gave you HEIC and the image does not appear, export a JPEG from the Photos app first. The studio decodes what the browser can decode, which is JPEG, PNG, WebP, and GIF as a single frame. It does not decode camera RAW.
- Crop only if the form asked for a shape (a square headshot, for example). Otherwise leave the frame alone so you are not throwing away the subject to save bytes.
- Set the long-edge pixels in the width or height box and keep the other side in proportion. If you type both numbers and they do not match the crop's aspect, the export is stretched. There is no separate "lock ratio" checkbox in the current studio.
- Open Compress & Preview. Choose JPEG unless the form explicitly accepts WebP. Many mail clients and government portals still do not. Set the slider to 80.
- Read the compressed size in the preview. If it is under the cap with margin, download. If it is over, reduce the long edge and look again. Drop the slider only after the dimensions are honest.
- Confirm in the downloads folder. The preview size is the blob the browser just encoded. The attachment size your mail program shows may be the Base64 size. Use the folder figure as the file, and the one-third margin for mail.
The new file will not contain the photo's GPS tag. That is a side effect of painting a new image, and it is what you want before a photo goes to a stranger. It is explained in What Leaves Your Browser. Keep the camera original. The download is a copy for the form, named with the pixel width so you can tell the 1600-pixel version from the 1280-pixel one.
Several photos, one message
If you are sending a set, repeat the same width and the same slider so the set looks consistent. The studio remembers crop, size, format, and quality per thumbnail. The ZIP button packs them as simplycompress_batch.zip. A ZIP counts as one attachment, which helps when the limit is "one file," and it hurts when the person on the other end is on a phone and only needed to look at the pictures. Prefer separate JPEGs under the cap when the receiver has to preview them. Use the ZIP when the receiver asked for a bundle. The per-image details are in Batch Compress and Export a ZIP.
Do not put a dozen full-size camera files in one ZIP and hope the mailbox accepts it. Zip compression barely shrinks JPEGs, because the JPEG is already compressed. A ZIP of ten 8 MB photos is still about 80 MB. Resize first, then zip if you zip at all.
When the portal recompresses, and when it refuses the type
Some sites decode your upload and save their own JPEG. Sending them a quality-95 giant does not preserve your quality; it wastes the attempt and can trip the cap. Send the resized file. If the portal then looks soft, the damage happened on their side. You cannot fix their encoder. You can avoid handing them a 6000-pixel file that they downscale badly.
If the form says "JPG or PNG" and rejects WebP, believe it. The studio's WebP is for pages you publish, not for a file input you do not control. PNG of a photograph will often be the largest of the three choices and is the wrong way to sneak under a cap. PNG is right when the upload is a scan of text or a screenshot and you can still meet the number at a sensible pixel size.
iPhones still default to HEIC. A form that says JPEG will reject the HEIC even when the byte count is tiny. Convert once, to a resized JPEG, and upload that. Sending the HEIC through a mail client that silently converts it is how people end up with a second, worse recompress they never looked at.
Frequently Asked Questions
Why did a file under the limit still bounce?
Mail attachments are often Base64-encoded, which uses four characters for every three bytes. An 18 MB JPEG can become roughly 24 MB on the wire. Leave about a third of the stated limit as margin, and add the sizes if you are attaching more than one file.
Should I send WebP by email?
Only if you know the recipient's client opens it. Many mail apps and upload forms still want JPEG. Use WebP for a website you control, and JPEG for a mailbox or a portal.
Will zipping the photos get me under the cap?
Not if the photos are already JPEGs. Zip barely shrinks them. Resize each photo, then zip only if the recipient asked for one bundle. A phone user who needed to look at the pictures would rather have separate JPEGs.
The form rejected my iPhone photo even though it was small. Why?
The camera default is often HEIC. A form that says JPG will reject HEIC regardless of size. Export a JPEG, resize it, and upload that file.
Make a JPEG that fits the form
Set the long edge, export JPEG, and check the byte count before you attach it.
Open Image Studio