Compress & upload
Quality slider at the bottom and still rejected? Hit a target KB — or convert/resize first
You dragged quality almost to zero and the form still said the image was too large. You are not even sure if they want 200KB or 2MB. This guide helps you decide: target-size compress, convert the format, or shrink the pixels first.
You dragged the quality slider almost to the floor. The signup form, the resume portal, or the admin panel still said image too large or please stay under 200KB. Worse: some pages never name a number — you do not know if they mean 200KB or 2MB. Another pass on the slider will not decide that for you.
Stop guessing with quality. Read what the form actually blocks, then pick one path: target KB, convert, or resize.
Three refusals that look the same
The error is often one line. The fix is not. Use the three scenes below as a decision, not a feature list:
The form wrote a KB cap
Copy like “max 200KB”, “under 500KB”, or “file must be ≤ 2MB” is a size problem. Open Compress, switch to target size, and type that number — leave a little headroom (200 → try 190).
It only says JPG
A PNG with transparency or an iPhone .heic can fail even when the KB looks fine. Convert to JPG first — the HEIC to JPG guide covers the phone case — then compress if the cap is still tight.
It also caps width
Some backends want “longest side under 1920px” plus a KB limit. A 12-megapixel phone shot stays heavy no matter how far you drag quality. Resize the sides first, then hit the KB.
How to hit the number in one pass
Open Image711's Compress tool. Decoding and export stay in your browser; the original is never uploaded. Target-KB mode can batch — drop a whole set, one target for every file. Keep each original ≤ 20MB.
- Drop one or many files: JPG / PNG / WebP / GIF. Multi-select is fine. If the file is still HEIC and the page will not open it, convert first, then come back.
- Switch to target size: type the form’s limit in KB. Leave a little slack — a 200KB rule is safer at 190. The tool balances look against that ceiling so you stop the 90 → 80 → 70 loop.
- Export and re-upload this batch: download singles or a zip. If the result looks muddy, the canvas is probably huge — resize, then compress again.
Target KB is a size match, not a quality contest. Leave headroom, batch the same number, keep each file under 20MB, and stay local so an ID scan never leaves the device.
When size is not the only rule
A resume photo that also needs a 1:1 or 1-inch frame should be cropped before you chase KB — the ID crop guide walks through that order. If you still need a name or logo on the file, add it with the watermark guide first, then compress; stamping after a heavy compress can smear the text. Format mismatches go through Convert.
The short version
Quality already at the bottom and still rejected: read whether they named a KB, a format, or a width. Hit the number with target-size compress, convert HEIC/PNG to JPG when they asked for it, resize huge pixels first. Batch the KB step; leave a little slack; do it locally.
About compressing to a target KB
Can I compress a whole batch to the same KB?
Yes. Target-size mode accepts multiple files and applies one KB ceiling to every image. Download singles or a zip. Keep each original around 20MB or under — that is the per-file cap, not a reason to skip batch.
I set 200KB and the upload still failed. Why?
Leave a little headroom — a 200KB rule is safer at 190, because some backends count headers or re-encode. Also check that you uploaded the new file, not the original, and that the form did not also demand JPG or a max width.
The file is HEIC or a huge PNG. Should I compress first?
No. Convert HEIC to JPG first, then hit the KB. A transparent PNG that the form wants as JPG should be converted before compress — size usually drops fast after that. Huge pixel width: resize the sides, then compress.
Are the original photos uploaded to a server?
No. Image711 compresses in your browser. The original stays on the device; nothing is sent to an upload backend for processing.