Guide · Browser-local · No upload

Compress an image under 100KB

Many uploads reject anything over 100KB. Here's how to hit that cap without guessing — and without uploading your photo to a cloud compressor.

  • Target size in KB (100KB or tighter)
  • Runs in your browser — no upload
  • Preview quality vs file size

Need an animated GIF smaller instead? Try the GIF Compressor.

Image Compressor

Same free browser tool as /image-compressor. Your file stays on this device.

No image? Try one of these

Your image stays on this device

Fogkits Image Compressor re-encodes with canvas in your browser. The original file is not sent to Fogkits servers for this tool — no account and no credits required to download.

  • No server upload
  • No credits for this tool
  • Free download

Why 100KB limits exist

Bandwidth caps — not a judgment of your photo

Forms, ticket systems, email gateways, and older CMS fields often cap attachments around 100KB–200KB. The limit is about bandwidth and storage, not whether your photo “looks good.” A phone selfie at full resolution can be several megabytes, so the file fails before anyone sees the image.

How to hit 100KB

How to hit 100KB without wrecking the photo

Set a KB target, optionally downscale, prefer JPEG/WebP for photos, and judge the preview — there is no magic lossless path to 100KB for a large image.

01

Open the compressor

Use the Fogkits Image Compressor below (or go to /image-compressor). Nothing is uploaded — compression runs in your browser.

02

Drop a still image

Add a JPG, PNG, or WebP. Typical limit: about 25 MB per file on desktops (lower on low-memory devices); up to 20 images per batch.

03

Set a 100KB target

Enter a target size of 100 KB (or start with the quality slider, then add a target). For stricter portals, try 50 KB with the same steps.

04

Optional max width

Set max width to 1920, 1280, 800, or 640 if resolution is part of why the file is heavy — fewer pixels often beats crushing quality alone.

05

Prefer JPEG or WebP for photos

Keep PNG only when you need lossless edges or transparency. Auto prefers WebP when the browser can encode it; force JPEG if the destination is picky.

06

Preview and download

Compare before/after. Download when the file is under 100KB and still acceptable for the job — there is no lossless path to 100KB for a large photo.

Quality vs size tradeoffs

Higher quality

Keeps more detail but may miss 100KB. Start higher, then lower only as far as the preview still works for the job.

Lower quality or a hard KB target

Shrinks the file further; fine detail can soften, and heavy JPEG compression can show banding. Preview before you download.

Max width first

Often the cleanest lever: fewer pixels usually beats crushing quality alone. Try 1280 or 800 when a form only needs a clear attachment.

Judge for your use case

An email thumbnail can tolerate more softness than a product hero. Stop when the preview is still acceptable — not when a spinner finishes.

JPG vs PNG for small uploads

Photos

JPEG or WebP usually reach 100KB more easily than a large PNG from a phone camera.

PNG

Lossless in the browser, so a big PNG may stay large — convert to JPEG/WebP when size is the blocker.

Auto output

Fogkits prefers WebP when the browser can encode it; force JPEG if the destination is picky about mime types.

Still on HEIC from an iPhone? Convert first with the HEIC to JPG guide, then compress to hit the size cap.

When to use GIF compress instead

This guide is for still images. Animated GIFs belong on the GIF Compressor — different controls (quality, frames, target size) and a different tradeoff. Don't force a GIF through the still-image compressor.

Compress an image under 100KB

Drop a JPG, PNG, or WebP on the Image Compressor, set a 100KB target, and download when the preview still looks good enough — free, browser-local.

  • Browser-local
  • No credits
  • Free download

Need an animated GIF smaller instead? Try the GIF Compressor.

Frequently asked questions

Can I compress to exactly 100KB?

You can set a 100KB target. The tool steps quality and width until the file fits or the aggressive passes finish — you may land slightly under the cap, not a guaranteed exact byte count.

Will quality look bad?

It can, if the source is large and 100KB is very tight. Preview first. If it looks too soft, raise quality slightly, increase max width only if you still fit, or accept that some destinations need a higher cap.

JPG or PNG?

For photos under 100KB, JPG or WebP. Use PNG when you need transparency or crisp UI graphics — and expect a larger file unless the image is already small.

Is it free / private?

Yes. Fogkits Image Compressor runs in your browser with canvas re-encode — free, no account, no credits for this tool, and the file is not uploaded to Fogkits servers.

Related image tools

All tools