Compress an image to 50 KB
50 KB target preset, JPG output. A tight headshot fits at full size; a phone photo fits after an automatic shrink, and the card shows the new pixel size.
Your images
Settings
Generated images
- Nothing uploaded
- Free, no sign-up
- Strips EXIF
- Batch files
Exam registration, a student ID card portal, a licensing board, a visa form that wants a passport-style photo: the field says JPG, 50 KB maximum, and the picture from your phone is 3.8 MB, about 75 times over. Those limits were written when a 50 KB photo was a normal photo, and the error message rarely says more than file too large.
The good news is that a head-and-shoulders shot on a plain background is the easiest image there is to compress. What wrecks it is the order of operations: dragging quality down on a 4,000-pixel-wide photo that the portal will display at 300. Halve the width and you keep a quarter of the pixels and roughly a quarter of the bytes, with no visible loss at the size anyone will ever view it.
This page opens with the 50 KB target (51,200 bytes) and JPG already selected. It looks for the highest JPEG quality that lands under the line, and only if none does, it starts shrinking pixels in 15% steps. The result card tells you which of the two happened and the exact byte count, so you know the file will pass before you leave.
How it works
Three steps from a phone photo to a file the portal accepts, with the target already dialed in.
Drop in the photo
Drag it onto the page, click to pick it from your camera roll or desktop, or paste with Ctrl+V. Several files at once are fine. An iPhone HEIC works too: the first one fetches a decoder of about 1 MB, and the photo itself stays on your device.
Keep JPG, skip the slider
The settings panel shows JPG lit on the format bar and the 50 KB target applied. The quality slider does nothing on this page, since the target search chooses the value, and there is no width box either: if you need a specific pixel size, set it on Resize image first.
Generate, read the tag, download
Click Generate images. Each card reads old size → new size with a target met tag, or smallest possible if 50 KB was out of reach, plus a width × height tag (with an arrow from the original size when the image had to shrink). Compare opens a before/after slider; Download saves one file, the .zip button saves them all.
What fits in 50 KB as-is, and what has to shrink
JPEG spends bytes on detail, and a face on a plain wall has little of it per pixel. A 12-megapixel phone photo is the exception: even at the lowest quality this page tries, it stays at several hundred kilobytes, so the only way down is fewer pixels. Typical first-run results:
| What you drop in | What the page does | Card reads |
|---|---|---|
| 600 × 600 px headshot, 180 KB JPG | Quality search only, lands near quality 75 | 47 KB, target met, no size tag |
| 1000 × 1250 px portrait, 400 KB | Quality search, ends near quality 45; visibly soft | 49 KB, target met |
| 4000 × 3000 px phone photo (JPG or HEIC), 3.8 MB | Quality 5 still too big, so several 15% shrinks | 50 KB at roughly 800–1,100 px wide; a busy scene gets smallest possible |
| 1920 × 1080 screenshot with text, PNG | Re-encoded as JPG at very low quality | Under 50 KB, but small text smears |
Shrink the width first; it beats lowering quality every time
Bytes track pixel count, and pixel count grows with the square of the width, which is why a modest resize does more than a brutal quality cut. The automatic shrink is a rescue, not a plan: it moves in fixed 15% steps and stops at the first fit, so it can leave the photo wider than needed or narrower than the portal's minimum. Rough sizes for a head-and-shoulders JPG at quality 80:
- Portal displays the photo at 200–400 px: type 600 into the max width box on Resize image, then compress here. Quality stays above 70 and nothing shrinks.
- Portal names exact pixels, 600 × 600 or 200 × 230: crop to the ratio on Crop image, resize to the number, then compress. Stage one finishes the job, so the dimensions survive.
- Busy background: crop tighter. A patterned wall or a bookshelf behind a face eats bytes the face needs.
| Dimensions | Pixels | Approx. size at quality 80 |
|---|---|---|
| 2000 × 2500 | 5.0 MP | 600 KB |
| 1000 × 1250 | 1.25 MP | 150 KB |
| 800 × 1000 | 0.8 MP | 95 KB |
| 600 × 750 | 0.45 MP | 55 KB |
| 480 × 600 | 0.29 MP | 35 KB |
What happens after you click Generate, in order
Stage one is a binary search on JPEG quality between 5 and 96, up to twelve encodes, keeping the highest quality whose file is at or under 51,200 bytes. If any fits, the pixels are untouched and the card shows target met.
Stage two runs only when even quality 5 is too heavy. The image is redrawn 15% smaller with high-quality resampling and re-encoded at quality 72, up to ten times, down to about a fifth of the original width. The first size that fits wins and the card adds a width × height tag. If the tenth shrink still misses, you get that file with a smallest possible tag instead of a quiet failure.
Passed the 50 KB check and still rejected
Size is the only rule the error message mentions and rarely the only one it checks:
- A pixel minimum, at least 600 × 600 say, that the automatic shrink just broke. Resize to the required frame first so stage one finishes without touching it.
- 50 KB counted as 50,000 bytes. This page targets 51,200, so a card reading 50.4 KB can bounce; take 10% off the width on Resize image and run it again.
- Format. The output here is a real .jpg, which settles HEIC, WebP and PNG originals in one pass.
- Face rules: plain light background, face centered, no hat, no heavy shadow. Those checks are done by a person or a model, and no compressor fixes them.
Frequently asked questions
Will a photo straight from my phone fit in 50 KB?
Yes, after an automatic shrink. A 12-megapixel JPG is too heavy even at the lowest quality, so the page scales it down in 15% steps, usually landing between 800 and 1,100 pixels wide, and prints the new dimensions on the card. For a portal that displays the photo at a few hundred pixels, that is more than enough.
Why is the output smaller in pixels than what I dropped in, and can I stop that?
Because quality alone could not reach 51,200 bytes, so stage two shrank it. To stay in control, resize to 600–800 px wide on Resize image before compressing; at that size a headshot fits in stage one and keeps its dimensions.
The form wants at least 600 × 600 px and no more than 50 KB. Can I get both?
Yes, if you set the pixels first. Crop to 1:1 on Crop image, resize to exactly 600 × 600, then compress here. A face on a plain background at that size lands around 45 KB at quality 70 or better, so the page never needs to shrink it.
Is the result exactly 50 KB, and which 50 KB?
Under, never over: the search keeps the highest quality at or below 51,200 bytes (50 × 1,024), so cards typically read 46–50 KB. A portal that defines 50 KB as 50,000 bytes may reject a 50.4 KB file; shave 10% off the width and regenerate.
Will a screenshot or a scanned document stay readable at 50 KB?
A 1080p screenshot fits as JPG but small text goes fuzzy, because JPEG is built for smooth photos, not hard edges. Crop to the part that matters; a full screenshot cannot fit 50 KB as PNG, so keep JPG. A letter-size scan should stay at least 1,000 px wide, which at 50 KB means a tight crop and grayscale.
Can I run my photo and my signature scan in one batch?
Yes: drop both in and download the pair as a .zip. Check the signature field first, though. Those usually carry a tighter cap, 10–20 KB is common, and for that the 20 KB page is the right rung.
Should I switch the output to PNG or WebP?
Only if the portal rejects JPG. PNG has no quality setting, so the page goes straight to shrinking pixels and a photo ends up a few hundred pixels wide. WebP compresses well but many application portals refuse it. Almost every ID photo upload expects JPG.
It is an ID photo for a government or school form. Does it get sent anywhere?
No. The decoding, the quality search and the resizing all run in your browser's canvas, and the file never leaves your device. The EXIF block, including the GPS position and time your phone recorded, is dropped from the output, which is what you want on a file handed to a portal.