Hit your exact KB target
A binary search across quality and dimensions converges on your target within a tight margin. Type 100 KB and the output lands at 100 KB, not 187 KB.
Got a form that caps uploads at 200 KB? Drop your image, type your target, click resize. The output lands inside the limit on the first try. No signup, no watermark, no server upload.
Drop one image to start
JPG, PNG, WebP, AVIF, HEIC, GIF, BMP, or TIFF. Up to 100 MB input. Pick a KB target inside.
A binary search across quality and dimensions converges on your target within a tight margin. Type 100 KB and the output lands at 100 KB, not 187 KB.
If your target is too aggressive for the input, the tool tells you the smallest size it could actually reach — instead of silently producing something bigger than asked.
A min-dimension floor protects against over-shrink. The tool will compress harder before it makes your portrait too small to print.
Drag a file in or tap to pick from your device. Works on JPG, PNG, WebP, AVIF, and HEIC. The file lands in this tab and stays there.
Tap a chip — 50 KB, 100 KB, 200 KB, 500 KB, 1 MB — or type a custom byte count. The tool reads it as your hard ceiling.
Watch the file size readout converge on your target. When it lands, click download. Original file untouched on disk.
Most embassy and consulate portals cap photos at 200 to 500 KB. Drop your headshot, pick the cap, the output lands inside the window without a re-shoot.
Admission portals enforce strict file caps — often 100 KB for the headshot. Hit the cap, keep the photo readable, move on with the application.
DMV, tax filing, license renewal, and other forms commonly cap at 50 to 200 KB JPG. The KB-target loop hits the cap exactly while preserving the document's legibility.
Bank KYC and verification portals vary by country and bank — 500 KB to 1 MB is common. Set the cap, the output is upload-ready in one click.
Indeed, Naukri, and similar platforms cap profile photos at 100 to 200 KB. Quality drops are visible — the binary search keeps it as high as the cap allows.
Some corporate mail servers cap attachments at 5 to 10 MB total. Resize a stack of receipts to a tight KB target each so the whole message fits under the limit.
JPG and WebP compress better than PNG for the same dimensions. If the target is small, pick JPG — PNG hits its limit fast.
For ID photos, 100 to 200 KB at JPG quality around 85 is a comfortable sweet spot — readable at print, small enough for any portal.
If the target is 20 KB or less, expect visible compression. Pick the highest quality the cap allows and accept the trade-off, or relax the target slightly.
HEIC iPhone photos hit small KB targets easily — the decoder converts to JPG cleanly and the binary search has plenty of room to work.
Set a min-dimension floor when the photo has to stay readable at print. The tool will compress harder before it shrinks below the floor.
Drop the file, type your target KB or tap a chip, and click resize. The compressor runs a binary search across quality and dimensions until the output falls inside your target window. The whole loop is automatic — you just set the ceiling.
The binary search converges to within roughly five percent of your target by default — so 100 KB usually lands between 95 and 100 KB. Tightening the tolerance is possible but trades convergence time for accuracy. The default suits every upload form we have tested.
PNG is a lossless format — its compression cannot give up quality, only redundant pixels. For aggressive KB targets the tool either reduces dimensions or asks you to switch to JPG or WebP, which can keep the dimensions and trade pixel accuracy instead.
Yes, easily, as long as you pick JPG, WebP, or AVIF. A typical phone photo hits 100 KB with mild compression at full resolution. For PNG, the tool reduces dimensions to fit, since lossless can't drop pixel data.
Yes, but expect visible compression. The tool will push quality and dimensions until the output crosses 20 KB. ID-photo work usually fits within 50 to 100 KB at acceptable quality — 20 KB is the lower edge of what most portals will accept.
If the binary search can't reach the target even at the lowest practical quality, the tool stops, shows you the smallest size it actually reached, and offers to relax the target or reduce dimensions. No silent fail, no false 'success' at a higher KB than you asked for.
No. The whole binary-search loop runs inside your browser tab using WebAssembly. The image transfer never leaves your machine — open the Network panel in DevTools and watch the transfer column stay at zero while the tool compresses.
Hitting a small KB target always means some quality loss — that is what compression is. The binary search keeps quality as high as the target allows, so the loss is minimal. For lossless output, pick PNG and let the tool reduce dimensions instead.
Browse every resize mode in one tool — pixels, percent, KB target, presets — with the full feature breakdown.
Resize by dimensions instead. The fast single-file flow for when you know the exact width and height.
Resize many images at once and download as a ZIP — useful when every photo in a batch has to fit under the same KB cap.
Larger MB targets for portals that cap by megabyte instead of kilobyte. Coming soon.
Presets tuned for phone photos, social posts, and email attachments. Coming soon.
Exact KB targets, binary-search accuracy, no signup. Drop one image to start.