Compress an image to 50 KB
50 KB target preset, JPG output. The search tries quality 50 and up at full size, then shrinks pixels in 15% steps; the card shows what it took.
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 on your phone is megabytes. An ordinary 12 MP iPhone photo comes to 2 to 2.5 MB when you work it out from Apple's published figures, 40 to 50 times over, and the error message may say no more than file too large.
What wrecks the photo 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 the height and you keep a quarter of the pixels, so the same 50 KB is shared by far fewer of them.
This page opens with the 50 KB target (51,200 bytes) and JPG already selected. It looks for the highest JPEG quality, from 50 up, that lands under the line, and if none does, it starts shrinking pixels in 15% steps, searching again at each size. In a test of ours with a 12-megapixel photo in September 2026, the 50 KB target was met at 926 × 695. The result card tells you what happened and the exact size, so you know it 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. Max width (px) does: fill it in and the photo is resized before the search runs.
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 how far 51,200 bytes go depends on how many pixels share them. The page tries quality alone first, from 50 up; if quality 50 does not fit, the way down is fewer pixels. The table shows the budget per pixel for four common inputs.
| What you drop in | Pixels | Bytes per pixel at 51,200 bytes |
|---|---|---|
| 600 × 600 px headshot | 0.36 MP | 0.14 |
| 1000 × 1250 px portrait | 1.25 MP | 0.04 |
| 1920 × 1080 px screenshot | 2.07 MP | 0.025 |
| 4000 × 3000 px phone photo | 12 MP | 0.004 |
Set the width yourself instead of leaving it to the 15% steps
Pixel count grows with the square of the width, which is why a modest resize removes so many of them. 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. What each width leaves of a 12-megapixel frame:
- Portal displays the photo at 200–400 px: as a starting point, type 600 in Max width (px), then generate and check the card.
- Portal names exact pixels, 600 × 600 or 200 × 230: crop to the ratio on Crop image, resize to the number on Resize image, then compress here.
- Busy background: crop tighter. A patterned wall or a bookshelf behind a face takes bytes the face needs.
| Dimensions | Pixels | Share of a 12 MP frame |
|---|---|---|
| 2000 × 2500 | 5.0 MP | 42% |
| 1000 × 1250 | 1.25 MP | 10% |
| 800 × 1000 | 0.8 MP | 6.7% |
| 600 × 750 | 0.45 MP | 3.8% |
| 480 × 600 | 0.29 MP | 2.4% |
What happens after you click Generate, in order
Stage one is a binary search on JPEG quality between 50 and 96 at the original pixel size, keeping the highest quality whose file is at or under 51,200 bytes. If one fits, the pixels are untouched and the card shows target met.
Stage two runs when even quality 50 is too heavy. The image is redrawn 15% smaller with high-quality resampling and the same search runs again, up to sixteen times or until the longer side is down to 64 px. The first size where a quality fits wins, and the dimension tag on the card shows the old and the new size. As a last resort the page accepts a quality between 5 and 50 at the smallest size; if even that misses, you get that file with a smallest possible tag instead of a quiet failure. The guide how to reduce image file size walks through the stages.
Passed the 50 KB check and still rejected
Size may be the only rule the error message mentions without being the only one the portal checks:
- A pixel minimum, at least 600 × 600 say, that the automatic shrink just broke. Set the required width in Max width (px), or the exact frame on Resize image, before the search runs.
- 50 KB counted as 50,000 bytes. This page targets 51,200, so a card reading more than 48.8 KB is over that line; lower Max width (px) by about 10% and run it again.
- Format. The output here is a real .jpg, which settles HEIC, WebP and PNG originals in one pass.
- Face rules, if the portal has them: background, framing, headwear, shadows. No compressor fixes those.
Frequently asked questions
Will a photo straight from my phone fit in 50 KB?
Yes, but expect it to come back smaller in pixels. If quality 50 does not fit 51,200 bytes at full size, the page scales the photo down in 15% steps and prints the new dimensions on the card. To choose the width yourself, fill in Max width (px) before generating.
Why is the output smaller in pixels than what I dropped in, and can I stop that?
Because quality 50 was still over 51,200 bytes at full size, so stage two shrank it. To stay in control, type a width in Max width (px) before compressing; as a starting point we suggest 600–800 px for a headshot. The arrow on the dimension tag tells you whether stage two still ran.
The form wants at least 600 × 600 px and no more than 50 KB. Can I get both?
Set the pixels first. Crop to 1:1 on Crop image, resize to exactly 600 × 600 on Resize image, then compress here. At that size 51,200 bytes is 0.14 bytes per pixel; if the card shows target met and a single size on the dimension tag, you have both.
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). A portal that defines 50 KB as 50,000 bytes draws the line at what the card shows as 48.8 KB; if your result is above that, lower the width by about 10% and regenerate.
Will a screenshot or a scanned document stay readable at 50 KB?
JPEG is built for smooth photos, not hard edges, so text is where the loss shows first. Crop to the part that matters, generate, and read the smallest print in Compare before you upload. For a scanned page, fewer pixels across each line means less legible text, so do not let the width fall further than you have to.
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: if it carries its own, tighter cap, use the page for that target.
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. WebP gets the full quality search, but check that the portal lists it among the accepted formats.
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 a GPS position if your phone recorded one, is dropped from the output, which is what you want on a file handed to a portal.