Skip to main content

Image Compression Guide

Hit a KB or MB Cap — Iterate, Do Not Guess

Forms print 50KB, 200KB, 500KB, or 1MB. The slider estimates weight. Exact bytes on one click are rare. Pixels first if quality collapses.

Quality slider estimates size — iterate to hit 20KB–1MB caps. Convert HEIC first; resize if quality bottoms out before the target.

Loading image compressor…

Prefer the main tool? Open our free image compressor to compress image files locally in your browser.

Written by Safaat Rahman Siham, Founder & Developer at Convertify4u. Contact us.

Portals lie in two directions: they reject 201KB when the label said 200KB, and they display MB when they mean MiB. Work under the cap with a little headroom. This page is the iteration loop: drop JPEG/PNG/WebP, lower quality, check the estimate, download, confirm in the OS, submit. Tiny ID stills (20–50KB) almost always need a smaller pixel box. A 4000px face cannot become 20KB without looking like a stamp. Image Resizer to ~600–800px on the long edge, then encode. 100–200KB is the usual job-application and LMS zone. 500KB–1MB is comfortable for most photographs if you already resized. HEIC will fail many government pickers even at 50KB — convert to JPEG first. PNG photographs will miss tiny caps; switch to JPEG. We do not lock an exact byte count with a binary search encoder. We give you a fast local loop so you stop before the deadline.

Caps are policy; the slider is an estimate

20KB and 50KB: government ID photos, some visa scans. Expect aggressive downscale plus JPEG. 100KB, 150KB, 200KB: universities, HRATS, licensing boards. 300KB and 500KB: friendlier still. 1MB: scholarships, some immigration PDFs that still panic at 5MB Camera stills. If quality bottoms out before the number, you are fighting pixel count, not the slider. Crop to the face if the form is a portrait. Do not upscale a tiny still hoping the portal “wants more pixels” while also demanding 50KB — those requirements conflict; follow the byte cap and the official pixel spec separately (resizer + this loop).

How it works

  1. 1

    Write down the cap and the pixel spec if any

    Some forms want 200KB and 600×600. Hit pixels with Image Resizer, then come here for bytes.

  2. 2

    Encode, check estimate, download, verify in the OS

    Do not trust only the on-page number if the portal is pedantic. Finder/Explorer properties are the judge.

  3. 3

    If mush appears before the cap, shrink the long edge

    Halving dimensions quarters area. Then a milder quality often beats a crushed 4000px JPEG.

Use cases

Aggressive ID caps

20KB or 50KB. Small JPEG, small box, no PNG photo.

Common application portals

100–200KB headshots and certificates as stills.

Larger but still capped uploads

300KB, 500KB, 1MB — milder quality, still not a Camera original.

Verify before Submit

OS file size in KB or MB, matching the unit the form printed.

Problems we solve

Submit button that only says “too large”

Iterate until you are under, with headroom. Portals round unkindly.

Chasing exact bytes

Estimates, then a download check. We do not binary-search to 200000 bytes on one click.

Quality gone, cap missed

Resize, then encode again from the original, not from the mushy download.

Trust, speed & privacy

Local ID stills

Application photos stay in the tab. WASM, no Convertify4u copy.

Fast retries

Seconds per pass so a deadline is the portal, not our queue.

Any modern browser

Same loop on a phone or a library PC.

Frequently asked questions