How to Compress an Image to a Specific Size (in KB)

By Ankit Vachhani · Updated June 20, 2026

Sooner or later, almost everyone runs into an upload form that rejects a photo for being "too large" — not in dimensions, but in kilobytes. Government portals, job sites, admissions forms, and visa applications are notorious for capping uploads at oddly specific numbers like 20 KB, 100 KB, or 200 KB. Your phone, meanwhile, happily produces 3–8 MB photos by default. Getting from one to the other without your photo turning into a blurry mess of JPEG artifacts is a real skill, and this guide walks through exactly how to do it.

Why "file size" and "dimensions" are different problems

It's easy to assume that a smaller photo (fewer pixels) automatically means a smaller file, but that's only half true. File size in kilobytes depends on both the pixel dimensions and the compression quality applied when the image was saved. A tiny 400×400 image saved at maximum quality can still be several hundred KB, while a much larger 2000×2000 image saved at aggressive compression can be tiny. This is why simply cropping a photo smaller in an editor often doesn't hit a form's exact KB limit — you need to control compression directly, not just pixel count.

The fastest way: compress to an exact target

The most reliable method is to let a tool do the trial-and-error for you. Our free Compress Image to an Exact Size tool repeatedly re-encodes your image at decreasing quality levels until the output lands under the KB number you specify — so instead of guessing a quality percentage, you just tell it the target:

1. Open the tool and drag in your JPG, PNG, or WebP file.
2. Type your target size in kilobytes — for example, 100 for a 100 KB limit.
3. Let it process. It shows you the original size next to the new size so you can confirm the result actually fits before you download.
4. Download the compressed file and upload it to the form that needed it.

Everything runs locally in your browser tab. The photo is never sent to a server, which matters a lot when the image in question is a passport photo, an ID scan, or another sensitive document.

Prepare the image first — it makes a huge difference

Compression alone can only do so much before quality visibly degrades. If you resize and clean up the source image first, you'll land on your target size with far less visible loss:

• Downscale oversized photos. A modern phone photo can be 4000×3000 pixels — overkill for a form that displays the image at 200×250. Use the Resize Image tool to bring it down to something reasonable (1000–1500px on the long edge is plenty) before you compress. Fewer pixels means less data to compress, so you keep more quality per kilobyte.
• Switch to JPG for photographs. PNG is a lossless format built for screenshots and flat-color graphics — a poor choice for photos, since it can't discard detail the way JPG can. Converting a photo with our PNG to JPG converter can shrink the file by 60–80% before any further compression happens.
• Convert HEIC photos from iPhone first. iPhones save photos as HEIC by default, and many upload forms reject that format outright regardless of size. Run it through our HEIC to JPG converter first, then compress the resulting JPG to your target KB.
• Strip hidden metadata. Photos carry invisible EXIF data — camera model, GPS coordinates, timestamps — that adds extra weight and can be a privacy concern too. Our EXIF removal tool clears that out in one step before you upload a photo of yourself anywhere.

Format trade-offs: JPG vs PNG vs WebP

Not all formats compress the same way, and picking the right one changes what's achievable:

• JPG uses "lossy" compression built for photographs — it discards detail the eye barely notices, which is exactly what you want for a small file size, and it's accepted almost everywhere.
• PNG is lossless, so it never gets genuinely small for a photo — reducing PNG size mostly means reducing color depth, which looks worse than JPG at the same size. Save PNG for text, diagrams, and logos, not photos.
• WebP often compresses smaller than JPG at equal quality, though some older portals don't accept it. Convert with JPG to WebP to compare, but keep a JPG fallback on hand.

Troubleshooting: why is my file still too big?

If compression won't get you under the limit, pixel dimensions are almost always the culprit. A tool can only lower quality so far before an image turns blocky, and beyond that point it stops shrinking meaningfully. When that happens, resize the image smaller first — a 3000px-wide image compressed to 20 KB looks far worse than a 600px-wide image compressed to that same 20 KB, simply because there's less detail to throw away. For passport or ID-photo rules that also specify exact pixel dimensions, use a dedicated passport photo tool to size and crop correctly before compressing to the required KB limit.

Common size targets you'll run into

Different forms tend to cluster around a handful of familiar numbers: 10–20 KB for tiny signature or thumbnail boxes, 50 KB for many exam and recruitment portals, 100 KB and 200 KB for standard photo/document uploads on job and government sites, and 1–2 MB for general-purpose uploads like resumes or portfolio images. Whatever the number, the same workflow applies — resize if needed, pick the right format, then compress to the exact KB figure.

Frequently asked questions

Will compressing to a smaller KB size ruin my photo's quality?

Some quality loss is inevitable once you push below a certain file size, but it's usually far less noticeable than people expect — especially if you resize the image down to sensible dimensions first. Most quality complaints actually come from compressing an oversized image too aggressively rather than from the compression process itself.

What's the difference between "compress to a percentage" and "compress to an exact KB size"?

Percentage-based compression (like "70% quality") gives you no guarantee about the resulting file size — a detailed photo at 70% quality might still be huge, while a simple image at 70% quality might be tiny. A KB-target tool works backward from your goal, testing quality levels until the output actually lands at or under your specified size, which is far more useful when a form has a hard limit.

Can I compress multiple photos to the same size at once?

Our current tool processes one image at a time so you can verify each result individually, which matters when precision counts — like ID photos where you want to confirm the crop and quality before submitting. For batches of similar photos, running each through the same target size only takes a few seconds per file.

Is it safe to compress sensitive documents like ID cards or passports online?

Yes, as long as the processing happens in your browser rather than on a remote server. Whiztools' compression tools run entirely client-side using your browser's own processing power — the image data never leaves your device, so there's nothing to upload, store, or intercept.