I've lost count of how many times someone has emailed me asking the same thing: "How do I get this photo under 100KB?" Usually it's for a government form, a job application, or a university portal that was apparently designed in 2004.

So I ran the numbers. I took 50 photos from three different phones (iPhone 15, Pixel 8, Galaxy S24) and compressed each one at every quality setting from 100 down to 10. Here's what I actually found.

The 100KB Problem Is Usually a Resize Problem

Here's the thing most guides won't tell you: if you're trying to squeeze a 4032x3024 iPhone photo down to 100KB using compression alone, you're going to destroy it. That's a 12-megapixel image. Even at JPEG quality 20, it'll still be around 180KB. And it'll look terrible.

The real move is to resize first, then compress.

A 1200x900 photo at quality 75? That's about 85KB. And it looks perfectly fine for any web form or document upload. A 800x600 version at quality 80? Around 52KB. Still sharp enough to read text on a document scan.

The formula I use: Resize to the smallest dimensions the platform will accept, then set JPEG quality between 72-80. In my testing, quality 72 is where compression artifacts start becoming visible on close inspection. Below 65, they're obvious.

My Actual Test Results

I tested with a typical iPhone 15 photo (4032x3024, 3.2MB original):

Resize ToQuality 90Quality 80Quality 72Quality 60
4032x3024 (original)1.8MB820KB540KB310KB
2000x1500480KB210KB145KB89KB
1200x900195KB92KB68KB42KB
800x60098KB48KB36KB23KB

See that? At 1200x900 and quality 80, you're already at 92KB. That's your sweet spot for most use cases. No visible quality loss at normal viewing distance.

Format Matters More Than You Think

I keep seeing people use PNG for photos and wondering why the file is 8MB. PNG is lossless. It's for screenshots, logos, and graphics with sharp edges. For photos, it's almost never the right choice.

Quick comparison of the same 1200x900 photo:

If whatever you're uploading to accepts WebP, use it. It's 25-30% smaller than JPEG at the same visual quality. I built the imagemochi converter specifically because I was tired of needing to bounce between three different tools for this.

Compress to an exact file size

Drop your image, set a target size. It processes in your browser — nothing gets uploaded.

Try Compress Tool

The Government Portal Problem

Government portals are the worst. Indian visa applications want photos under 100KB but exactly 2x2 inches at 300 DPI. Korean immigration wants under 200KB but at specific pixel dimensions. The US passport portal wants under 240KB in JPEG only.

Here's my approach for these: resize to the exact pixel dimensions they specify first, then adjust quality until you're under the limit. Don't go below quality 70 — some portals will reject images that look too compressed.

I actually ended up building specialized tools for the most common requirements (passport photo, 100KB compressor) because the combination of exact dimensions + file size limits is so specific.

Batch Compression: The E-Commerce Scenario

If you're compressing one or two photos, any tool works. But I had a user last month who needed to compress 200 product photos for a Shopify store. All under 100KB. All maintaining consistent quality.

For batch work, consistency matters more than squeezing out every last kilobyte. Pick one quality setting (I'd say 75 for product photos), one max dimension (1200px wide is standard for e-commerce), and apply it uniformly. Your product pages will look coherent, and every image will be well under 100KB.

One More Thing: Check Your Metadata

Modern phone photos carry about 20-50KB of EXIF metadata — GPS coordinates, camera model, timestamps, lens info. Stripping metadata alone can shave 10-15% off a file. Plus, if you're uploading to a public form, you probably don't want your GPS coordinates in there anyway.

Our Compress tool handles this (re-encoding a JPEG strips most metadata automatically).