Quality first, then edges, then we stop
A typical 3MB phone photo to 400KB usually finishes in the quality search. Pixels stay the same; the encoder just works harder.
A 4000-pixel-wide export aimed at 50KB will not get there on quality alone. The long edge steps down and we search again. That is expected, not a bug, and the page will say the image was resized.
A 20KB cap on a huge, noisy photo can still fail. We return the smallest file we made and mark it best effort. The byte count on screen is the real one — we do not quietly go over the cap.
Chips are shortcuts, not the whole product
20KB through 5MB are one-tap presets. 87KB or 1.4MB still belong in the box. We do not publish a URL for every number; that would be a hallway of near-duplicate pages. Use this hub, or the 200KB and 500KB pages when those limits have their own story.
How it works
- Switch to target size and type a number, or tap a chip.
- We search quality so the file stays at or under the cap.
- If quality is not enough, dimensions shrink. If it still cannot fit, you get a best-effort file and a clear note.
Frequently Asked Questions
Why 1024 instead of 1000?
Windows file properties use 1024. Some web forms use 1000 and then bounce a file that looks like 199KB on your desktop. The 5% checkbox is for that mismatch.
The original is already smaller than my number.
We leave it alone and say so. Re-encoding would only hurt it.