Compress Image to 5KB — Free, Fast & Private
Five kilobytes is five thousand bytes, and it has to hold an entire picture. Before you aim at it, be sure you need to be under 5 KB rather than over it — because on the Indian forms that mention 5 KB at all, it is usually the smallest file they will take, not the largest.
What fits in 5 KB — measured on this page
We dropped five real files on the compressor above and kept what it handed back. 5 of 5 came out under 5 KB; 4 were made smaller in pixels to get there, because past a point the bytes can only come from pixels.
| File | Before | After, on this page | Under 5 KB? |
|---|---|---|---|
| 12 MP phone photo | 4032 × 3024 px · 3.73 MB | 639 × 479 px · 3.70 KB | Yes |
| Portrait / headshot | 3264 × 4653 px · 2.25 MB | 621 × 885 px · 4.29 KB | Yes |
| Scanned handwritten page | 3349 × 4281 px · 2.17 MB | 684 × 874 px · 4.62 KB | Yes |
| Scanned signature | 2041 × 617 px · 109.1 KB | 1306 × 395 px · 4.76 KB | Yes |
| Screenshot (PNG) | 1280 × 800 px · 88.1 KB | 1280 × 800 px · 4.88 KB | Yes |
Measured 2026-10-06 in Chromium 145.0.7632.6 with this page’s own settings. The photos are public-domain and CC0 files from Wikimedia Commons; the screenshot is our own. Sizes read as the tool shows them (1 KB = 1,024 bytes); the target itself is 5,000 bytes, which is under 5 KB on either reading.
Who actually needs a file this small
Genuine under-5 KB jobs are mostly outside government forms: a favicon-sized logo for an email signature, an avatar for a forum or chat profile that caps uploads tightly, a thumbnail embedded in a document or a database row, a placeholder image that should arrive before anything else on a slow page. In those cases nobody checks a floor, and the only question is how much of the picture survives.
Forms are a different matter. The table shows where 5 KB lands against the bands that mention it, every figure read from the exam body’s or issuing authority’s own document.
| Upload | Band | A 5KB file is… |
|---|---|---|
| GATE photograph | 5–600 KB | exactly on the floor — the riskiest place to be |
| GATE signature | 3–300 KB | inside, near the bottom |
| CTET signature | 3–30 KB | inside, near the bottom |
| PAN card photo | 4–200 KB | inside, just above the floor |
| Aadhaar photo | 4–100 KB | inside, just above the floor |
| SSC / IBPS signature | 10–20 KB | too small — under the 10 KB floor |
| Indian passport photo | 10–100 KB | too small — under the 10 KB floor |
Read the right-hand column carefully. No row in it asks you to get below 5 KB. Every band that contains 5 KB has plenty of room above it, and several common ones (the bank and SSC signatures, the passport photo) start well above it. If you landed here because a form rejected your file as too large, check its stated maximum against this table before compressing further: you may be fixing the wrong end.
The 5KB floor trap, in arithmetic
GATE asks for a photograph of 5–600 KB. This page’s target counts a kilobyte as 1,000 bytes, so its 5 KB target means a file of at most 5,000 bytes. A system that counts a kilobyte as 1,024 bytes reads that same file as 4.88 KB, and its 5 KB floor as 5,120 bytes. A file that is “exactly 5 KB” by one convention is under the floor by the other.
So for GATE, do not use this page. Aim comfortably inside the band — the GATE photo tool targets it directly. The same reasoning applies to PAN and Aadhaar: a 4 KB floor leaves only a sliver between it and a 5 KB file, and a photo that someone has already squeezed hard can slip under it. A file below a floor is rejected just as surely as one above a ceiling, and the target on this page is a ceiling only — the tool never pads a file upwards.
What 5,000 bytes buys at real pixel counts
An uncompressed colour pixel takes three bytes, one each for red, green and blue. GATE’s smallest permitted photo, 200 × 260, is 52,000 pixels, so raw it would be 156,000 bytes. Squeezing that into 5,000 bytes leaves 0.096 bytes — 0.77 bits — per pixel, about one 31th of the raw size.
Scale up to GATE’s largest allowed photo, 530 × 690 or 365,700 pixels, and the same budget is 0.014 bytes (0.11 bits) per pixel — one 219th of raw. The PAN upload, 213 × 264 or 56,232 pixels, would get 0.089 bytes per pixel.
Those fractions explain everything you will see. JPEG stores an image as 8 × 8 blocks, and on a budget this far under a byte per pixel it can afford little more than each block’s average colour plus a hint of its main edge. Faces go soft, fine hair becomes a smudge, and the 8 × 8 grid itself starts to show in flat areas like a white background. Fewer pixels means more bits for each one — which is why, at this size, a smaller picture usually looks better than a bigger one forced into the same bytes.
How this compressor reaches 5KB
It works in a fixed order. First it lowers JPEG quality at your image’s full size, step by step, looking for the highest quality that fits under 5,000 bytes. Only when even the lowest quality still misses does it reduce the pixel dimensions, and when it does, it tells you and shows the new width and height. At 5 KB, a large phone photo will almost always end up resized — the measured table near the top of this page shows what happened to each sample file.
You will usually get a cleaner result by doing the resize yourself first. Crop tight to what matters, then set the dimensions to whatever the destination displays — an avatar shown at a small square on screen does not need a camera’s worth of pixels. Use crop and resize before you compress, and the quality step has more room to work with.
Keep it JPEG. PNG is lossless and at this budget it can only hit the target on simple graphics, by cutting colours; a photograph does not survive that. JPEG has no transparency, so a logo with a transparent background will come out on a solid one — for a tiny logo that must stay transparent, a PNG with few colours may beat it.
Everything happens in your browser. The image is never uploaded, so the face in your avatar or ID photo stays on your device.