Shrinking Photos for Sharing: WhatsApp, Email, and 'Maximum Size 2 MB'

'Make it smaller' tempts people into iterating — compress, still too big, compress again — and every extra pass is a fresh lossy generation stacked on the last one's discarded data. The edge artefacts that appear on pass three are not the tool failing; they are the file's memory of the original being gone. One pass from the biggest clean version, aimed deliberately at the target, always beats a chain of guesses at the same destination.

Which means the workflow before any destination-specific advice: original file → resizer to the right dimensions → compressor to the right quality → check both numbers against the limit → done. One pass, ten seconds, and the result is the best version of that photo the destination can physically receive.

Email: attachments are read by gateways you never see, and the reliable targets are under 1 MB per image and under ~10 MB total. The pass that hits them: long edge 1600-2000 px (a photo read on a phone or a 7-inch laptop screen loses nothing at those dimensions), quality 82-85. A portrait or headshot for an email signature wants 400-600 px wide and about 80.

Forms with a stated cap — 'maximum 2 MB' on an application, 'under 500 KB' for a document upload — respect the number literally and check it twice: the file that leaves your machine at 1.95 MB can arrive at 2.04 after whatever the browser adds, and the gateway does not round in your favour. Land at half the stated maximum when you can, and the question disappears.

The combined-spec form (passports, exams, government portals) is the one people get rejected by: those define pixel ranges as well as weight ranges. Crop or resize to the pixel spec first — the compressor cannot invent dimension compliance, and an oversized-but-light file fails the same review as an underweight-but-huge one.

Chat apps have their own opinion: photo-mode sends are recompressed to roughly 100-200 KB whatever you started with, which is a good default for a screen photo and terrible for a scanned document or a form fill you need readable on the other side. The quality slider in the app does not reach that re-encode.

The escape hatch: send as a document. In WhatsApp, attach via 'Document' instead of 'Photos' and the original file arrives byte-for-byte — including its EXIF, which cuts both ways (the document route also delivers GPS, timestamps and device info; for a photo of your family it is exactly what you want for the first time the recipient asks when it was taken, and exactly wrong for a picture you would not want located).

The practical pattern: casual photos can go through the app's own compressor happily; anything with text, edges or evidential value goes as a document, optionally after your own one-pass resize to keep the download reasonable for the recipient's data plan.

Email a batch of holiday photos: 1600 px long edge in the resizer, quality 80 in the compressor, batch the twenty at once — 300 KB each and the thread survives.

Attach a CV photo or headshot to an application: crop to the form's pixel window, 200×200 px to 500×500 px is the usual band, quality 85, verify under the cap.

Scan of a signature or document where the reader will zoom: do not chase tiny bytes; grayscale, dimensions kept, quality high enough that 8 pt text stays crisp at 100% — that file is 200-400 KB and legible, versus a 60 KB one that fails the one job it has.

Photo for a print shop via email: the shop's stated format and size; when they say 'send the original', send the original — the two-step pass exists for screens, and paper pays a different tax.

The thirty seconds that save the rejection loop: open the reduced file's properties and read the two numbers the destination cares about — weight and dimensions — against the stated requirement. Where metadata matters (forms that check capture dates, legal attachments), confirm what survived the pass with the EXIF viewer; where privacy matters, that same check confirms the location data did not.

And one forward-looking habit: keep the originals. Every reduced file in this guide is reproducible from a master in seconds; the master is not reproducible from the reduced file, and the archive of shrunk JPEGs is where photo quality goes to die quietly (for the per-destination byte budgets, see the image file size guide).