Compress Image to 100KB Online — No Upload

Nawal Shrestha — Sun, 04 Oct 2026 03:58:14 +0000

Visa portals, exam forms, and job applications all ask for the same thing: a photo under 100KB. Most compressors hand you a quality slider and wish you luck — you export at 60%, check the size, re-export at 50%, check again. Five guesses later you land at 97KB with a photo that looks worse than it needed to.

There's a better way: name the size, and let the tool find the best quality that fits it. Type 100, get ≤100KB, done — with your file never leaving your device.

Why 100KB limits are everywhere

Government and university portals process millions of files. A hard per-file cap keeps storage costs and database rows predictable. A phone photo today is 3–8MB, so "under 100KB" means shrinking it to roughly 2% of its original size.

Common places you'll hit this limit:

Visa and passport applications — photo and signature uploads, often capped at 100KB or even 50KB
Exam and university admission portals — scanned documents and photos with per-file caps
Job applications — resume portals that reject oversized profile photos
Scholarship and KYC forms — ID scans that must stay small but readable
Banking portals — document uploads for account opening or loans

The cap persists because the bottleneck is storage and database row size, not your internet speed. Faster broadband didn't move it; it won't move soon.

What 100KB actually looks like: quality vs size

People imagine 100KB means a ruined photo. It depends entirely on dimensions. Here's the relationship, roughly, for a typical phone photo saved as JPEG:

Source dimensions — Quality 85 — Quality 60 — Quality 40
4000×3000 (12MP) — ~2.5 MB — ~1.2 MB — ~600 KB
2000×1500 — ~700 KB — ~350 KB — ~180 KB
1200×900 — ~280 KB — ~140 KB — ~75 KB
800×600 — ~130 KB — ~65 KB — ~35 KB
Illustrative — actual sizes vary with image complexity. Noisy, detailed photos run heavier.

The takeaway: 100KB is mostly about resolution, not the quality slider. A 1200×900 photo at quality 60 hits ~140KB; drop to 800×600 and you're comfortably under 100KB at decent quality. Anyone telling you to "just lower the quality" on a 12MP original is giving bad advice — resize first, then compress.

Type 100, get ≤100KB: how target-size mode works

In SnapShrink you type 100 into the target-size box and the engine does the search for you:

Drop your image at https://getsnapshrink.com/app/. JPG, PNG, WebP, and GIF accepted.
Type 100 as the target size in KB and pick your output format (WebP is smallest for photos — but check portal acceptance below).
Binary search on quality. The engine encodes at quality 95, then 50, then narrows the range — about 8 encodes — to find the highest quality that lands at or under 100KB.
Downscale fallback. If even quality 5 overshoots, the image scales down in ×0.9 steps (never below 320px) and the search repeats.
You get the result with before/after sizes shown. On the rare image where 100KB is truly unreachable, it reports the best effort it managed instead of failing silently.

It all runs in a background worker in your browser tab, so the page stays responsive. A standard 5MP phone photo typically finishes in under 3 seconds.

Which format will the portal accept?

This is where people get burned. You compress a beautiful 80KB WebP, upload it, and the portal rejects it — not for size, but for format. Older government and banking portals often accept only JPEG (sometimes only JPG, not even PNG).

Your image — Best format — Why
Photo / camera shot — WebP or JPEG — Smallest at a given quality; WebP usually wins ~25%
Screenshot / graphic with text — PNG or WebP — Keeps edges sharp
Scan of a document — WebP or JPEG — Text stays readable far below 100KB in grayscale
Signature on white background — PNG or JPEG — Tiny anyway; JPEG safest for old portals
Rule: when in doubt, JPEG. It's the universally accepted format. Use WebP only when you've confirmed the portal takes it — or when the file is for your own site, not someone else's form.

Compress a batch to 100KB

A passport photo, a signature scan, a supporting ID — drop them all at once. SnapShrink's bulk image compressor (https://getsnapshrink.com/bulk-image-compressor/) applies the 100KB target to each file individually, because every image needs a different quality level to hit the same cap. When the batch finishes, download everything as one ZIP.

This beats the one-by-one loop most online tools force on you, and it eliminates the rename-and-organize step — the ZIP keeps your filenames.

Compressing from a phone

Identical process in Safari on iOS and Chrome on Android: tap the drop zone, pick from camera roll or files, type 100, download. The file lands in Downloads, ready to attach.

One iOS wrinkle: phone photos are typically HEIC. Safari converts HEIC to JPEG automatically through the file picker, so SnapShrink receives a JPEG and processes it normally. No manual conversion needed.

Why "no upload" matters for document compression

Passport photos, ID scans, and visa applications contain biometric data. Uploading those to a third-party compressor — even one promising deletion — creates a data trail: how long the server actually retains the file, who can access it, what their breach notification obligations are. You have no visibility into any of that.

SnapShrink processes images with the browser's Canvas API and a Web Worker. The bytes never leave your device.

Verify it yourself — don't take my word for it:

Open the tool (https://getsnapshrink.com/app/) and press F12 → Network tab.
Compress a photo.
Look for file uploads in the network log.

There are none. Thirty seconds, and you've confirmed what no privacy policy can prove for a server-side tool. For documents this sensitive, "trust us" isn't good enough — testable beats promised.

SnapShrink also strips EXIF metadata (GPS coordinates, device info, timestamps) automatically during compression. Your ID photo shouldn't ship your location history to a portal database.

Step by step: compress to 100KB

Open the SnapShrink tool (https://getsnapshrink.com/app/) — no signup, no install.
Drag in your photo (or pick files with the button).
Type 100 in the target-size field. Choose JPEG if the portal is old or unspecified; WebP if confirmed accepted.
Hit Compress, then download. The file is ≤100KB and ready for the portal.

First 10 images per session are free. If you process documents regularly, one $9 payment unlocks unlimited use — no subscription.

Troubleshooting: when the image won't reach 100KB

Genuinely impossible cases are rare but real. A 320×320px photo that's already 110KB at quality 1 in JPEG has nowhere left to go. In that situation:

Switch to WebP — usually smaller than JPEG at the same dimensions (if the portal allows).
Crop tighter — border whitespace costs bytes, especially in JPEG.
Resize to the portal's minimum — if it says "minimum 200×200px", try exactly 200×200.
Grayscale for documents — some portals accept it, and it compresses far more efficiently.
Check the EXIF — a 50–200KB metadata payload on an unprocessed phone photo is dead weight; stripping it alone can close the gap.

SnapShrink always reports the actual output size, so you know exactly where you stand instead of guessing whether a rejection was the size, the format, or the portal being slow.

FAQ

Is my photo uploaded to a server?
No. Compression happens entirely in your browser. Open DevTools → Network while compressing — zero file uploads. That's the whole point.

What if my image can't reach 100KB?
Rare, but possible with very detailed images at small dimensions. You'll see the smallest size achieved ("best effort") instead of a silent failure.

Which browsers work?
Chrome, Edge, Firefox, and Safari handle WebP encoding natively. If yours can't encode WebP, the tool says so and you pick JPEG or PNG instead.

Is there a file size limit?
Files up to 50MB accepted. Larger files are skipped with a clear message; the rest of the batch keeps going.

Can I compress multiple images to 100KB at once?
Yes — drop the batch, set the target once, download a ZIP. Each image is processed individually to hit the same cap.

JPEG or WebP for a 100KB target?
WebP preserves more quality at 100KB, but old portals may reject it. JPEG when unsure; WebP when confirmed.

How is this different from Squoosh?
Squoosh is excellent for single-image manual tuning. SnapShrink is built for two things Squoosh doesn't do: batch processing and target-size mode — type the cap, get there automatically. One image with pixel-perfect control: Squoosh. A stack of documents with a size cap: SnapShrink.

DEV Community: Nawal Shrestha