ID scans, verification photos, the 100KB ceiling. Target preset, drop and compress.
Bank account opening, government portals, platform identity verification - single-page ID uploads often cap at 100KB. Scanner defaults produce 1-2MB PNGs. The target is preset to 100KB here; document text stays sharp with room to spare at this size.
Click to choose / drag & drop / Ctrl+V paste, multi-select supported
JPG / PNG / WebP / GIF (resize only), up to 50MB each, up to 20 files
KB or less
Adjustable 10-2000KB; preset fits ID documents
JPG for documents: PNG scans auto-flatten to white and shrink by more than half.
Your images are compressed inside this device's browser - nothing is uploaded and it works offline. Target size and format live only in this browser's localStorage; switching devices or clearing site data loses them. "Clear my data" in the footer wipes them.
Queue is empty - drop ID scans or document photos in, each one gets its own pass/fail badge.
Three steps
Feed drag signatures or scans onto the bench (multi-select fine); each file's size shows up in the queue instantly.
Set target is preset to 20KB, adjustable; JPG recommended, switch to PNG only for transparent icons.
Take results arrive per file: green ✓ badge plus the real size in the file name; for IDs, zoom in on small print and stamps once.
Facts & limits
Input
JPG / PNG / WebP / GIF; up to 50MB each; animated GIFs get resize-only (no frame compression); transparent PNGs are flattened to white when output as JPG
Output
JPG / WebP / PNG / Smart (PNG→WebP, others keep their format); file names carry target and actual size, e.g. photo-20kb-19KB.jpg
Key parameters
Target preset to 100KB (range 10-2000KB); binary-search quality 0.30-0.96, up to 8 rounds; auto proportional downscale to 85% when it does not fit, up to 6 steps
Processing
Browser-local Canvas encode/decode, no upload, no account; settings live in this device's localStorage (nothing written on first load), images never touch disk
Limits
Up to 20 files per run, 50MB each; queued one by one, a single failure never blocks the batch
Known limits
Dense fine-print contract scans may miss 100KB (red badge shows minimum); lossless PNG often misses tiny targets; HEIC unsupported - iPhone users convert to JPG first
FAQ
Will small print on my ID scan stay readable at 100KB?
Yes. ID text is much larger than A4 fine print: a 1000-1200px long edge at JPG quality 65-80 usually lands at 60-90KB, and even the smallest address line reads cleanly. The honest test: download the result and zoom to 200% on the issuing-authority stamp - if the stamp is crisp, the text is too.
Does 100KB hurt the machine-readable zone (MRZ) on passports?
Barely, but verify once. The two MRZ lines are the highest-contrast content on any passport, and JPEG treats those regular strokes kindly; at a 100KB target the binary search usually settles at quality 60-85 with the MRZ still sharp. If a downstream OCR must read it, zoom through those bottom two lines before you submit.
Mixed ID photos and scans - which output format?
JPG for both. Photos are JPG natively; PNG scans convert with an automatic white flatten (ID scans are already white, so nothing is lost). Unless a system explicitly demands PDF, a 100KB JPG is the most compatible format across government and financial portals.
IDs are sensitive. Is this page safe?
That is exactly why this tool exists: decode, compress, download - all inside this device’s browser, no upload endpoint, works offline (unplug the network and try). ID images never touch disk or localStorage; only the target and format preference persist locally, wipeable from the footer. Not convinced yet? Run a vacation photo through first and watch the flow.
What if the scan will not fit 100KB?
After 6 automatic downscale steps it still misses only when the source is a noisy re-photographed color page. Three fixes usually suffice: switch PNG to JPG, scan in grayscale or 300dpi instead of 600dpi, and crop away the desk around the document. The page shows a red honest badge with the minimum reached - it never pretends success.
Are my ID scans uploaded to a server?
No. Decode, compress and download all happen inside this device’s browser - no upload endpoint, and it works offline with the cable pulled. ID images never hit disk; only target and format settings sit in localStorage, one click in the footer clears them.