Yirinhana Tools

简体中文 · English · Español · Português · 日本語 · Deutsch

Shrink images so email and forms stop rejecting them

Résumé photos, insurance claims and school portals often enforce size caps that phone cameras ignore. Effective compression is an order of operations—dimensions, quality, then format—not a single desperate slider. This guide uses Image Compressor and related converters with checks you can see.

Target the real limit, not a rumour

Examples you will meet: roughly 100–300 KB for small ID-style photos, 1–2 MB for many application uploads, and around 25 MB for entire email messages including headers and encoding overhead. Organisation portals invent their own ceilings. Always prefer the number printed on the form. Weigh the file you will actually attach; screenshots of someone else’s success are not a specification.

Watch for dual constraints: “max 500 KB and max 2000 pixels wide.” Meeting only one rule still fails. Some forms count UTF-8 form fields toward a combined POST size; leaving headroom below the image cap avoids mysterious failures.

Three levers, in a sensible order

1. Reduce maximum dimensions before crushing quality. A 4000×3000 photo emailed at 1200 px on the long side is usually enough for on-screen review.

2. Lower JPG or WebP quality gradually and preview faces, hair edges and fine text at 100% zoom.

3. Change format when a PNG screenshot barely shrinks: convert to JPG or WebP, then compress.

4. Export derivatives once from a master. Opening and re-saving JPG repeatedly (generation loss) is how passport text becomes mush.

For screenshots with large flat regions, WebP or carefully tuned PNG may beat JPG. For noisy camera photos, JPG or lossy WebP usually wins. If text becomes fuzzy before you hit the size target, reduce dimensions again instead of another quality drop.

Using Image Compressor on this site

Open Image Compressor and add one representative image first. Set a max width that matches the form and a quality that still looks acceptable. Download and inspect. If the size is under the cap with readable detail, process the rest of the batch the same way. Prefer individual checks for ID photos; batch ZIP downloads for large sets of similar pictures.

Processing is local in the browser. The page assets still load over the network as described in Privacy.

After a successful sample, write down the exact width and quality you used so a future batch matches. When HEIC is the source, convert to JPG first, then compress—do not expect every compressor UI to accept HEIC directly on every browser.

When PNG will not budge

Lossless PNG of a photograph or detailed screenshot can stay stubbornly large. Run PNG to JPG for photos or PNG to WebP when the destination accepts WebP, then compress again. Keep the PNG master if you may need transparency or another edit later.

Animated or multi-layer sources should be flattened in an editor before compression if the tool reads only a single raster frame. Similarly, screenshots that include large browser chrome you do not need can be cropped first—fewer pixels beat another quality notch.

PDFs that are really stacks of photos

If “the PDF” is five phone pictures glued together, compress each image and rebuild with Image to PDF rather than fighting the PDF alone. When even that exceeds mail limits, split pages across messages using the split-for-email guide.

Keep a short log of width/quality settings next to the final files so a second submission months later matches the first. If a claims adjuster asks for a higher-resolution copy, regenerate from the master rather than enlarging a tiny JPG.

Related tools

Image Compressor for the size pass; PNG to JPG and JPG to WebP for format shifts; HEIC to JPG when the Camera Roll is still HEIC. Pair with the JPG/PNG/WebP chooser guide before you convert blindly.

Ferramentas relacionadas