Compress Image to Target KB

You've filled in your name, your address, your work history, and twelve fields of personal information. Then you reach the photo upload. 'File must be less than 100 KB.' Your photo is 3.8 MB. The form doesn't offer to compress it for you — it just refuses, and everything you typed is sitting there waiting while you go hunt for a solution.

The tool at the top of this page is that solution, built for exactly this moment. Drop the photo in, type the limit — 20, 50, 100, 200 KB, anything — and it lands on target. It works in your browser, so a document as sensitive as a passport photo or a signature never gets uploaded to anyone's server.

I help people through application portals for a living — school admissions, government programs, job boards — and the size-cap rejection at the final step is the single most common technical failure in the whole process. This page is everything I've learned about hitting exact file sizes, written down so the next one goes smoothly.

A modern phone camera produces a 4032×3024 image — about 12.2 million pixels — and stores it at 1.5 to 4 MB depending on format and scene detail. That's a display-quality asset, sized for printing and zooming. Meanwhile the form you're filling out displays your photo at 150 pixels wide in a corner of the page, and its engineers capped uploads at 100 KB because they're storing a hundred thousand of them.

Both parties are being reasonable; they're just optimizing for different worlds. Your camera captures for the future, the portal stores at scale. The compression tool is the diplomat between them — and the honest answer is almost always the same: shrink the image to roughly the size it will actually be displayed, and the byte target becomes easy.

• Exam and application portals — commonly 20 KB to 100 KB per image
• Government visa and lottery forms — the US Diversity Visa instructions, for example, ask for a square JPEG between 600×600 and 1200×1200 pixels, at most 240 KB
• Job board profile photos — typically 100 KB to 500 KB
• Classified listing sites and marketplace forms — 200 KB to 1 MB
• Email signatures and forum avatars — often 50 KB or less

1. 1

   Drop your image

   Drag in a JPG, PNG, WebP, or HEIC — the tool decodes any of them in the browser. If you're coming from an iPhone with HEIC files, there's no need to convert first; the tool reads the container directly.

2. 2

   Enter the target size

   Type the exact limit from your form — 20 KB, 100 KB, whatever the portal demands. You can also set a small safety margin, like aiming for 95 KB under a 100 KB cap, which protects you from portals that measure sizes slightly differently.

3. 3

   Allow resizing if the target is tight

   Small targets are physically impossible at full resolution. With resizing allowed, the tool can reduce dimensions as needed; without it, it will tell you when quality alone can't get there.

4. 4

   Choose JPG for photos, PNG for signatures

   The format matters more at small sizes than anywhere else. A photo compressed to 100 KB looks fine as JPEG and terrible as PNG; a signature or line drawing is the reverse.

5. 5

   Watch the search work

   The tool iterates — encoding, measuring, adjusting — and shows the convergence live: each attempt's quality, dimensions, and resulting size, until it lands under your target.

6. 6

   Download and verify

   Grab the file and check it against the form before you celebrate. The tool reports the final size precisely; the portal's number should match. If it doesn't, your margin was too thin — aim a few kilobytes lower.

JPEG compression has one main dial: quality, from 0 to 100. Turn it down, the file shrinks; turn it too far, faces become mosaic. What it doesn't have is a formula connecting quality to output size, because the relationship depends entirely on image content — a busy beach scene at quality 60 can out-size a blank wall at quality 80.

So the tool doesn't guess; it searches. Encode at quality 80, measure the result. Too big? Encode at 40. Too small now — the file is smaller than it needs to be, wasting quality? Encode at 60. Each iteration halves the remaining range, which is why this is called a binary search: five to seven rounds of encode-and-measure, each taking a fraction of a second on a typical photo, and the size converges on the target from above. It's the same technique used in performance tuning and calibration everywhere, because it's provably efficient — you never check more than a handful of candidates out of a hundred.

When even quality 20 can't fit — which happens with large resolutions and tight targets — the dimension fallback kicks in. The tool scales the image down proportionally and re-runs the search at the smaller size. The order matters: resize first, then optimize, because a resized image compresses differently and the search must start fresh. If you've ever compressed the same photo twice and gotten wildly different results, that's why.

Numbers from actual form-submission season, on real files. Sizes are as reported by the tool and confirmed by the receiving portals.

The search needed six iterations and one resolution step-down. At full resolution the file couldn't get under 100 KB even at quality 15; at 1024 pixels wide, quality 72 landed comfortably with room to spare. The portal displays this photo at about 200 pixels — the compression is invisible where it matters.

This one is the format lesson. Compressed as JPEG, the signature hit 18 KB but grew soft gray halos around every stroke — compression noise on a white background, the exact opposite of what a signature needs. As PNG, two extra kilobytes bought back every edge. Signatures, stamps, and line drawings always deserve PNG.

The margin story is worth telling: the first attempt targeted 240 KB exactly and produced a 239 KB file, which one test portal accepted and another measured as 240.3 KB and rejected. Aiming at 235 fixed it permanently. Thin margins at hard limits are how 11 p.m. submissions turn into 11:40 p.m. submissions.

These are the stable landing zones for a typical headshot, and you should read them as physics rather than policy: every kilobyte budget buys either pixels or quality, and past a point you're choosing which one to starve. A form that demands 20 KB is telling you, in its own way, that your photo will be displayed at stamp size.

At 2 MB, JPG versus PNG is a footnote. At 100 KB it decides whether your upload looks professional or broken. The rule follows the content: photographs have thousands of smooth gradients, which JPEG's frequency-based compression handles brilliantly; drawings and text have flat regions and hard edges, which PNG's lossless approach preserves exactly.

JPEG quality runs 0–100, and the visual knee sits around 75 — above it, compression is essentially invisible; below 60, it announces itself. At small targets the tool will happily go lower because the form demands it, and there's no shame in a 40-quality 20 KB thumbnail. But know what you're buying: blocking on smooth areas, smeared fine detail, and color shifts in saturated regions.

The trap that ruins more photos than any tool is generation loss — compressing an already-compressed file. Take a 100 KB JPEG, run it through another compressor to hit 50 KB, and you've stacked two rounds of artifacts. Always start from the original file. If the original is gone and you must re-compress, expect visible damage; there's no algorithm that can restore what a previous encode already discarded.

• Compress once, from the original — every additional pass compounds artifacts
• When a form rejects 100 KB, don't re-compress the 100 KB file — go back to the source
• Keep your originals; the compressed file is a deliverable, not a replacement
• For printing, never use the form-size compressed version — print from the original at full quality

The images people compress to exact sizes are, overwhelmingly, identity documents: passport photos, signature scans, ID cards, certificate scans. These are the crown jewels of identity theft, and the majority of online compressors are server-side — your file uploads to their machine, gets processed, and downloads back with a promise attached about deletion.

A promise is not an architecture. This tool's compression happens entirely in your browser tab: the file loads into local memory, the binary search runs on your device, and the result is generated on your machine. Nothing transmits. In EU terms, that means no third-party processing of personal data — GDPR's concerns about lawful basis and processor obligations simply don't arise, because there is no processor.

For HR departments and school offices advising applicants, this is the detail worth repeating: the safest compressor for identity documents is the one that never receives them.

Some caps can't be met with quality, and the tool's honest response is to say so and resize. A few situations deserve special handling:

• 10 KB for a photo — only achievable at postage-stamp resolution. If a form demands this, it almost certainly expects a tiny avatar; comply, and don't expect the result to look like photography
• CMYK JPEGs — print-source files sometimes decode with inverted or washed-out colors in browser tools. Convert to RGB in a photo editor first, then compress
• 16-bit PNGs — the browser pipeline works in 8-bit color, so the output drops to 8-bit. For form uploads this is meaningless; for archival work, use desktop software
• Animated or multi-frame files — this tool outputs a single still image; a video thumbnail should be extracted first
• Screenshots of text at extreme compression — below 40 quality, glyphs melt. Switch to PNG, where text stays legible at much smaller sizes

Applicants, mostly, and the people who help them. Students uploading photos to university portals and scholarship forms. Job seekers fighting applicant-tracking systems with 500 KB caps. Immigrant families working through visa and lottery photo requirements with exact pixel and size specs. HR coordinators who field the 'the form rejected my photo' email forty times a season. Bookkeepers compressing receipt scans for expense systems that cap attachments.

The shared shape of the problem: a hard number, a deadline, and a photo that's twenty times over the limit. The tool turns the twenty back into one.

Plenty of forms don't stop at a size cap — they demand specific pixel dimensions too. The US visa and lottery photo specs ask for a square image between 600×600 and 1200×1200. Certain examination boards in other countries specify exact rectangles like 200×230 pixels. When a form names both dimensions and a size ceiling, the order of operations is fixed: set the dimensions first, then let the size search work within them.

• Square the image first if the form wants square — crop, don't stretch; a stretched face is the classic rejected-photo look
• Match the allowed range, not just the minimum — larger dimensions within the range give the size search more room to find a clean quality level
• Only then target the KB limit, with a small margin below the ceiling
• Resist the urge to sharpen after compression — sharpening artifacts at small sizes read as obvious editing to reviewers, and some portals flag them

One specific trap deserves naming: portrait forms that demand head height ratios. A passport-style spec of 'head between 50% and 69% of image height' is a composition requirement, not a compression one — no tool fixes it after the shoot. Shoot the photo right, then compress it right, in that order. The compression step is the only one this page can do for you, but it's also the only one that used to require guessing.

Rejections come in patterns. After enough of them, the patterns have names, and none of the three below is about the tool — they're about the details around it.

• Aiming exactly at the ceiling — a 100.0 KB file against a 100 KB limit is a coin flip depending on how the portal counts. Target 3–5% under, every time, and the coin flip disappears
• Renaming instead of converting — changing .png to .jpg in the filename does nothing to the file inside, and portals that check the actual format catch it instantly. Convert properly, always
• Compressing the wrong copy — the version with the right crop, the right background, and the right lighting is the one to compress. People get so focused on the KB number they forget the portal also has eyes

There's a fourth, dishonorable mention: compressing below a spec's stated minimum. Some portals reject files that are too small, because a 30 KB 'photo' looks like exactly the blurry mush it is. If a form says 10 KB minimum and 100 KB maximum, both edges are rules. Aim for the middle of the range, where quality still exists.

Hitting a size target is one stop in a longer journey for most applicants. These are the neighbors that get used in the same sitting.

• Image Compressor — quality-led compression when you want smaller files without a hard KB number
• JPG to PDF — turn form photos and scans into the single PDF most portals ultimately want
• PNG to JPG Converter — the format swap that makes PNG photos ready for JPEG-only portals