Compress & Upload
Quality at the floor and still rejected: is it 200KB or 2MB?
An application, a résumé portal, or an admin box says the photo is too large — or “200KB max.” You drag the quality slider to the left and export several times. Some pages never write a number, so you cannot tell whether they want 200KB or 2MB. The slider is about how mushy it looks. The field is about how heavy the file is.
An application form, a résumé portal, or an admin upload box comes back with file too large or 200KB max. You drag the quality slider to the left, export several versions, and it still fails. Worse: some pages never write a number, so you cannot tell whether they want 200KB or 2MB. Another nudge on the slider will not read that rule for you.
The slider answers how mushy it looks. The form asks how heavy it is. Hit that KB, then compress.
One “too large” — three different gates
The error is often one line. What you just tried, and what the field actually asked for, may not be the same job.
The table wrote a KB cap
“Max 200KB,” “500KB or less,” “must be ≤ 2MB” is a weight problem. Open Compress Image, switch to target size, and enter that number — leave headroom: if it is 200, enter 190. Some backends count headers or compress again.
It only asked for JPG
A transparent PNG or an iPhone HEIC can still bounce even when the KB looks small. Convert first with Convert Format. If the album is still .heic, follow the HEIC to JPG guide, then compress.
It also caps the width
Some backends want a longest side under 1920px and a KB cap. A 12-megapixel phone original stays heavy even at the lowest quality. Resize first, then hit the target KB.
Hit the number once — for the whole batch
Open Image8K Compress Image. Target KB can run as a batch: one ceiling on every file, each as its own result. Keep each original at or under 20MB. Decode and export stay in this browser — originals are never uploaded.
- Collect the files you will actually attach. JPG, PNG, WebP, or GIF — multi-select is fine. Still HEIC? Convert first, then come back. Keep each file at or under 20MB so the browser can finish.
- Switch to target size and leave headroom. If the limit is 200, 190 is safer. The tool balances quality under that ceiling — you do not walk 90 → 80 → 70 by hand.
- Huge pixels: resize first. A four- or five-thousand-pixel phone shot often goes mushy if you crush it as-is. Shrink the long edge, then compress once more.
- Download this batch and attach the new files. Confirm you are sending the export, not the original. Processing stays on this device.
Compress to a target KB locally
Target KB is about weight, not a contest for the lowest quality. One number can cover a batch; keep each file under 20MB; if the cap is 200, enter 190. ID scans stay on the device.
The file is light. The pack may still be incomplete
If the shop name is not on yet, stamp first with the text watermark guide, then compress — crushing first and marking after often smears the letters. If the same originals will go elsewhere, strip location with the guide to stripping GPS before sharing. A catalog that wants a white backdrop belongs in the white-background product photo guide. A form that wants one PDF is a merge, not a compress job — see the guide to merging images into one PDF.
Image8K compresses in your browser. Application photos, ID scans, and unpublished catalog shots stay on the device. There is no upload step to “process” the file.
What “ready to attach” usually means
Quality is already at the floor and the form still bounced it. See whether they wrote a KB, JPG only, or a width as well. Hit the number with target size, leave headroom, convert HEIC first, and resize huge pixels first. This step can run as a batch. Image8K does it in the browser — nothing is uploaded.
About compressing to a target KB
Can I compress a whole batch to the same KB?
Yes. Target size can run as a batch: one ceiling on every file, each as its own result — download singles or a zip. Keep each original at or under 20MB. That is a per-file cap, not a ban on batches.
I entered 200KB and the upload still failed. Why?
Leave headroom: if the limit is 200, enter 190. Some backends count headers or compress again. Also check you attached the export, not the original, and whether the field still wants JPG only or a max width.
The file is HEIC or a huge PNG. Should I compress first?
Not first. Convert HEIC to JPG, then hit the target KB. If the form wants JPG and you hold a transparent PNG, convert before you compress — the file often drops a lot. Very large pixels: resize first, then compress.
Are the original photos uploaded to a server?
No. Image8K compresses in your browser. The originals stay on the device and are never sent to a server — useful for application photos, ID scans, or unpublished catalog shots.