Job portals, government forms, and forums cap uploads at 1MB. Shrink any photo under the limit with no visible quality loss — free, private, in your browser.
Drag & drop or click to upload
JPG, PNG, WebP up to 50MB
Geek check: open DevTools → Network tab — 0 bytes of your data uploaded.
Target size: 1 MB per image — quality adjusts automatically.
Files are processed locally and never uploaded.
Drop your photo into the compressor above — this page targets 1MB automatically.
The tool iteratively re-encodes until the file lands under 1MB.
Download the result and upload it to your form — check it looks right first.
A huge number of upload forms — job applications, visa and government portals, university submissions, forum avatars, marketplace listings — cap attachments at 1MB (sometimes 2MB, sometimes 500KB). A modern phone photo is 3–8MB, so almost every upload from a phone hits the wall on the first try.
The limit exists because these backends store millions of uploads and display them at modest sizes. They don't need your 12-megapixel original — and neither does the person reviewing your application on a laptop screen.
Here's the math that makes 1MB comfortable: a 1920px-wide JPEG at 80% quality — sharp on any screen — typically weighs 300–600KB. Even a detailed photo rarely needs the full megabyte. The compressor aims just under the cap, so you keep maximum quality while sailing through the upload validator.
Resolution matters more than the quality slider. If your photo is 4000px wide, downsizing to 2000px alone can cut the file to a quarter of its size with zero perceptible change at display size. The tool handles the iteration; you just download.
Don't compress the only copy of a photo you might print. Print needs resolution — a 4×6 inch print at 300 DPI wants roughly 1800×1200 pixels, which fits in 1MB, but anything larger doesn't. Always keep the original; compress a copy for the upload.
Also watch for forms that demand exact dimensions (passport photos, ID uploads) rather than just a size cap. For those, resize to the required pixels first, then check the file size — the order matters, because resizing changes everything downstream.
Some portals recompress uploads themselves — badly, with no preview, and sometimes after you've already waited through a slow upload. Doing it yourself means you see the result before submitting, and you keep a copy of exactly what the reviewer will see.
Doing it locally has a second advantage: ID photos, certificates, and application documents never touch a third-party server. The compression happens on your device; the only upload is the final file to the form you chose.
Not visibly, for screen use. A 1920px photo at 1MB holds far more detail than any upload form displays. You'd only notice a difference pixel-peeping at 100% zoom or printing large — and you should keep the original for that anyway.
Almost always. Phone photos are massively over-specified for uploads: downsizing the resolution plus smart re-encoding typically cuts 70–90% of the weight. The tool iterates automatically until the file lands under the 1MB target.
Use the targeted sibling pages: compress-image-to-100kb for the 100KB case. The same tool powers all of them — only the size target changes.
JPG for photos (smallest at good quality), PNG only if you need transparency or crisp text/lines. Note that some older government portals only accept JPG — when in doubt, JPG is the safe choice.