A 100 KB image limit is usually not about compression. It is about dimensions. A 4,000-pixel photo squeezed into 100 KB will look like a watercolor painting; the same photo at 1,200 pixels can look sharp and still fit comfortably. The order of operations matters more than the quality slider.
This is the workflow for a form, a job portal, a marketplace listing or an email signature that insists on a small file.
Why the file is big in the first place
An image file is roughly a function of three things: the number of pixels, the amount of detail, and the format. A 12-megapixel photo has 12 million pixels; each one needs bits to describe its colour. Compression finds patterns and throws away some detail, but it cannot make 12 million pixels cost the same as 1 million.
A screenshot of text is different. It has large flat areas and sharp edges, so PNG can compress it efficiently. A photograph of a forest has fine detail everywhere, which is why JPG exists and why a 100 KB target is harder.
Do the maths before the slider
Ask what the image is actually for. A profile photo displayed at 200 — 200 pixels does not need to be 3,000 pixels wide. A marketplace image shown at 800 pixels does not need 4,000. A print image needs 300 DPI at the final print size, which is a different calculation.
For a web or form image, a longest edge of 1,200—1,600 pixels is usually plenty. For a thumbnail, 400—600 pixels. For a full-width hero on a high-density screen, 2,000 pixels may be justified — but then 100 KB is an aggressive target and WebP is a better bet.
Resize first
Use the image resizer to set the longest edge to the size the recipient actually displays. Keep the aspect ratio locked unless the form specifies exact dimensions. Do not upscale: a 600-pixel image enlarged to 1,200 pixels has no extra detail and will only be a larger file.
If the form requires an exact pixel size (many passport and visa forms do), crop to the required aspect ratio first, then resize. Check the face position and head size requirements for official photos; those rules are stricter than a file-size limit.
Pick the format
| Image | Best format | Why |
|---|---|---|
| Photograph of a person, product or landscape | JPG | Small, widely accepted, good for smooth detail |
| Screenshot of text or a UI | PNG | Sharp edges, no JPG artifacts around letters |
| Logo or icon with flat colours | PNG or SVG | Lossless edges; SVG if a vector source exists |
| Transparent product cut-out | PNG or WebP | JPG will fill transparency with a solid colour |
| Modern website image | WebP | Smaller than JPG/PNG at similar quality |
If you have a photographic PNG, convert a copy to JPG with PNG to JPG before compressing. A PNG photo is often several times larger than a good JPG and will fight you all the way to 100 KB.
Compress in steps
Start at a moderate quality — around 80—85 for JPG — and check the file size. If it is close, lower the quality in small steps rather than jumping to 20. The Image to 100KB tool automates the search, but it is still worth looking at the result.
For screenshots, do not use JPG unless the form forces it. JPG turns crisp text into a halo of artifacts, and the file may not even be smaller than a well-optimized PNG. If the screenshot has photographic content and a 100 KB limit, consider converting to JPG at a reduced dimension, or using WebP if the recipient accepts it.
Special cases
- Screenshots of text. Crop to the relevant area first. A full-screen screenshot with 70% empty space is wasting pixels. PNG at the cropped size may be surprisingly small.
- Logos. Use PNG or SVG, not JPG. If the logo must be a JPG for a portal, flatten it against white at the final size and accept some edge softening.
- Transparent PNGs. Decide what the background will be before converting. A transparent logo placed on a white form should be flattened to white; a transparent product shot on a dark site should be flattened to that dark colour.
- Product photos. Resize to the marketplace—s recommended dimensions, then compress. Many marketplaces re-encode uploads anyway, so an overly aggressive source compression is lost quality for no benefit.
- Scanned documents. A 100 KB scan of a full page is usually unreadable. If the form demands it, scan at a lower resolution and in grayscale, and check that the text is still legible. For a PDF, compress the PDF rather than converting each page to an image.
Check the result properly
- Look at it at 100%. A thumbnail hides artifacts. Zoom in on faces, text and edges.
- Check the file size in the file manager. The browser—s estimate can differ from the saved file.
- Check the dimensions. A 100 KB file that is 4,000 pixels wide may still be rejected by a form with a pixel limit.
- Upload it to the actual form. Some portals reject images for reasons that have nothing to do with size — colour mode, aspect ratio, file extension, or a maximum dimension.
- Keep the original. If the compressed copy looks bad, you want the source back.
Common mistakes
- Compressing before resizing. You spend quality on pixels the recipient will never see.
- Re-saving the same JPG repeatedly. Each save loses a little more. Work from the original, not the last compressed copy.
- Using the lowest quality immediately. Start moderate; stop when the image is still acceptable.
- Converting a transparent PNG to JPG without a background. The transparent area becomes black or white; sometimes both, depending on the tool.
- Upscaling a small image to meet a pixel requirement. It adds file size, not detail. Start with a larger source.
- Ignoring the form—s exact requirements. File size, pixel dimensions, aspect ratio, format and colour mode are separate rules.
The short version
Resize to the dimensions the recipient actually uses, choose JPG for photos and PNG for screenshots and graphics, compress in moderate steps, and inspect the result at 100%. A 100 KB image can look good; it just cannot be a 12-megapixel photograph at full size. The limit is a hint that the image was never meant to be that large in the first place.