Compress an image to 20KB.
This page is preconfigured for strict 20KB uploads: JPG output, Auto target search, and an 800px dimension cap so small form photos and icons can reach the limit more reliably.
Local processing. Measurement, resizing, encoding, and ZIP creation happen in this tab; selected images are not sent to imgrove. Privacy details
How to use Compress Image to 20KB
- Crop the source to the face, signature, or mark the destination actually needs; blank background still consumes pixels.
- Drop the cropped JPG, PNG, or WebP into the 20KB page and keep Auto, JPG, EXIF removal, and the 800px cap for the first pass.
- Check both target met and the preview: eyes, edges, or signature strokes must remain identifiable at the displayed size.
- If the result is unreadable, try a 600px cap after a closer crop; if detail still fails, confirm whether the destination permits 30KB or 50KB.
How it works
- Auto mode first tests browser JPEG quality at the 800px cap, then reduces pixel dimensions only if the smallest quality pass is still above 20KB.
- The success state is byte-based: the final blob must be at or below 20,480 bytes after any requested JPEG EXIF data is accounted for.
Formats and limits
| Input | A tightly cropped JPG, PNG, or WebP portrait, signature, or small mark. |
|---|---|
| Default output | JPG, Auto target, 800px maximum side, 76% manual fallback. |
| Byte rule | At or below 20,480 bytes; the result labels target met or explains the failure. |
| Transparency | JPG flattens transparency onto white; use WebP or PNG only when the destination accepts it. |
| Metadata | Removed by default because EXIF competes directly with the 20KB pixel budget. |
| Batch | Up to 30 related files; successful multi-file jobs download as one ZIP. |
Real failure cases
- If a face becomes blocky, crop closer before lowering dimensions; compression cannot preserve detail that has too few pixels or bytes.
- If signature strokes disappear in JPG, try WebP when accepted or start from a clean, high-contrast scan without wide white margins.
- If a portal rejects a target-met file, check its separate pixel, format, filename, and minimum-size rules rather than compressing again blindly.
Example result to verify
| Reference input | 600x800 synthetic portrait PNG used by the browser regression suite. |
|---|---|
| Preset | 20KB, JPG, Auto, 800px cap, EXIF removed; manual fallback starts at 76%. |
| Tested result | Downloadable image/jpeg blob at or below 20,480 bytes with target met and output dimensions reported. |
| Human check | Eyes, face outline, or signature strokes must still be recognizable; otherwise crop closer or use a larger permitted limit. |
Best for
- Tiny ID portraits, signature previews, and legacy upload boxes with a hard 20KB ceiling.
- Testing whether a tightly cropped face or mark remains recognizable after extreme compression.
- Removing EXIF bytes before a file enters a privacy-sensitive application form.
What you get
- A JPG capped at 20,480 bytes when the browser can preserve a practical image at that budget.
- An 800px maximum side, Auto target search, 76% manual fallback, and metadata removal as the page defaults.
- A before/after report that exposes final bytes, pixels, quality, compression ratio, and target status.
Before you download
- 20KB is an extreme budget for a full phone photo; crop unused background before sacrificing the face or signature.
- Fine signature strokes can break up in JPG, while PNG may stay above 20KB; compare the preview instead of trusting bytes alone.
- When a portal also specifies exact pixels, resize first because reaching 20KB does not prove the dimensions are accepted.
20KB workflow for tiny portraits and signatures
A 20KB limit is not a normal photo-optimization target. It leaves so few bytes that subject isolation and pixel dimensions matter more than a high quality-slider value, so this page starts conservatively and makes the quality loss visible.
- Default configuration. 20KB target, JPG output, Auto search, 800px maximum side, 76% manual fallback, and EXIF removal. Auto searches from the highest usable quality and shrinks dimensions only when quality alone cannot fit.
- Real task. Use it for a tightly cropped portrait, signature preview, or small identity mark when the receiving form explicitly rejects anything above 20KB.
- Browser regression sample. The test suite loads a 600x800 synthetic portrait PNG and requires a downloadable JPG no larger than 20,480 bytes, a target-met result, reported output dimensions, and removed metadata.
- 20KB-specific recovery. Crop empty background first, then reduce the longest side toward 600px. For broken signature strokes, test WebP if accepted; for a JPG-only portal, move to a larger allowed byte limit instead of hiding unreadable output.
- Verification. File size is only one requirement. Reopen the download, confirm the face or mark is recognizable, and use Image Size Checker if the portal also publishes width, height, format, or DPI rules.
Next steps
- Passport Photo - prepare a centered portrait before the extreme 20KB pass.
- Resize Image by Dimensions - meet an exact portal width and height before compression.
- Image Size Checker - verify bytes, pixels, MIME type, and metadata on the downloaded result.
- Compress Image to 30KB - retain more fine detail when the receiving form permits a 30KB ceiling.
Questions about Compress Image to 20KB
Why is 20KB harder than an ordinary image compression job?
A 20KB file must pay for dimensions, color variation, encoding overhead, and any metadata from the same tiny budget. Full phone photos usually need both a close crop and fewer pixels.
What should I inspect on a 20KB portrait?
Check the eyes, face outline, and boundary between the subject and background at the size the portal will show. A target-met badge does not guarantee usable identity detail.
Why did my signature look worse as JPG?
JPEG is efficient for photos but can soften thin dark strokes against white. Remove excess margins and try WebP if allowed; PNG may preserve strokes but often cannot fit under 20KB.
Should I keep EXIF on a 20KB image?
Usually no. Camera and GPS metadata consumes bytes without improving the visible form upload. Keep it only when the destination explicitly needs that metadata.