How do I compress an image to exactly 100 KB (or any specific size)?

Switch to Target Size mode and type the number — 100 KB, 500 KB, 1 MB, or anywhere between 5 KB and 5 MB. The tool runs a binary search over quality settings to find the highest-quality version that fits under your limit, then if quality alone can't get there, it starts reducing the image's width in steps until it does. Results typically land at or just below the target. If the image genuinely can't reach your target without becoming unusable (very common with tiny signature-image limits like 20 KB), the tool will tell you and give you the smallest version it could produce.

Is the image I upload actually sent somewhere?

No. The entire compression happens inside your browser tab. Your file is read into local memory, re-encoded using the browser's native image codec, and offered back as a download. We don't operate a server-side compression service — there's nothing on our end that your file passes through. You can verify this by opening the browser's network tab while compressing: there are no outbound requests for your image data.

Which output format should I pick for my use case?

For web pages and modern browsers, pick **WebP** — it's typically 20–30% smaller than JPG at equivalent visual quality and is supported in Chrome, Firefox, Safari, and Edge. For email attachments, government portal uploads, or anywhere compatibility with ancient software matters, use **JPG** — it's the universal lingua franca of photos and nothing will refuse it. Keep the original format (don't convert) when the receiving system specifically expects that format.

My PNG didn't shrink or got bigger — what went wrong?

PNG is a lossless format, which means there's no quality level to lower — the browser can only re-encode the same pixels, and if your original PNG used a smart indexed palette, re-encoding it as 32-bit RGBA can actually bloat the file. If you need a smaller PNG specifically, use the width/height slider to reduce dimensions. If PNG isn't a hard requirement, convert the output to WebP or JPG — a photograph compressed as JPG will typically be 5–20× smaller than the same photograph as PNG.

Does compressing a photo remove GPS location data and other EXIF metadata?

Yes, as a side effect of how the compression works. Every mode decodes the image to raw pixels, redraws it on a canvas, and re-encodes — a round-trip that strips EXIF, GPS coordinates, camera make and model, capture time, ICC colour profiles, and XMP metadata. If removing EXIF is the actual goal (for example, before posting a photo publicly), the dedicated EXIF Remover tool does it faster and without re-encoding the image's pixels, preserving the original quality.

What file formats does this accept?

JPG (.jpg, .jpeg), PNG (.png), and WebP (.webp) as inputs. HEIC (iPhone format) isn't supported directly — convert the HEIC to JPG first using the HEIC to JPG tool, then compress. AVIF isn't supported either, mostly because browser encoder support for AVIF is still inconsistent. For GIF compression, use a dedicated GIF tool — this one treats GIF as a flat image and doesn't preserve animation.

Will the compressed photo still be good enough to print?

Depends on how aggressive you went and what size you're printing. For a 4×6 inch photo print at 300 DPI, you need an image at least 1200×1800 pixels at reasonable quality (quality 85+ in Custom mode) — Auto mode's defaults generally preserve enough detail for small prints but may show artifacts if you print at poster size. If print quality matters, work from the original and only compress the copy headed to the web/email.

Can I compress multiple images at once?

Not in this tool — it processes one image at a time. For batch compression, open several browser tabs with this tool and run them in parallel, or use a desktop utility like ImageOptim (Mac) or FileOptimizer (Windows) for folder-level batch work. We may add a batch mode here based on usage.

Image

Image Compression

Compress images to reduce file size while maintaining quality. Supports JPG, PNG, WebP. Runs on your device — nothing is uploaded, nothing is stored.

Drop your image here

Up to 25MB - PNG, JPG or WebP

Compression Mode

Output Format

Compressed image will appear here

Image Upscaler

Upscale and enhance images 2x with an on-device AI super-resolution model. Increase image resolution for free, privately, with no upload.

Image

Image Captioner

Generate a descriptive caption and ready-to-use alt text for any image with an on-device AI model. Great for accessibility and SEO. Free, private, no upload.

Image

Depth Map Generator

Generate a depth map from any image with an on-device AI model. Grayscale or colormap output, downloadable PNG. Free, private, no upload.

Image

About Image Compression

Compress JPG, PNG, or WebP images to a smaller file size — right in your browser, with no upload and no size cap. Drop in a photo up to 25 MB and the tool re-encodes it on your own device, giving you back a smaller version in seconds. Perfect for getting past an email attachment limit, slipping under a government portal's 100 KB cap, speeding up a slow website, or saving space before you back up your photo library.

Four compression modes handle the common cases. **Auto** picks a sensible quality based on how large the source is — the right choice for everyday photos where you just want a smaller file. **Aggressive** maximises savings for cases where loading speed matters more than finest detail (web content, email attachments). **Custom** gives you the quality slider directly if you want to fine-tune. **Target size** is the mode most people actually need: type a specific number like 100 KB or 500 KB, and the tool automatically binary-searches for a quality setting that fits under your limit — if quality alone can't do it, it progressively reduces the width until the file squeezes in.

Everything runs on your own device using the browser's built-in image encoder, so there's no queue to wait in, no account to create, no hidden file size cap, no "premium" to upgrade to, and no watermark on the output. The compression is lossy for JPG and WebP (that's what makes them small) and lossless for PNG.

Why this runs on your device

The honest reason to compress images locally instead of on a server comes down to what people actually use these tools for. Most of the time it's a vacation snapshot that nobody will scrutinise. But the single most common real-world use of a "compress image to 100 KB" search is uploading a scanned Aadhaar card, PAN card, passport, driver's license, academic transcript, or digital signature to a government or application portal — documents you absolutely should not be handing to a random web service in exchange for a smaller copy of them, no matter how clean the UI looks. Speed is the other factor. Uploading 20 MB to a server so it can hand you back 200 KB is the slowest possible way to perform an operation that your own laptop finishes in about one second. On a weak network — which is exactly the kind of connection you're usually on when a file is too big to send in the first place — the upload will time out or stall before anything happens. Compressing locally sidesteps all of that: the processing starts immediately, the output appears without ever leaving your device, and the only limit is your own hardware.

How to use Image Compression

Drop a JPG, PNG, or WebP image onto the page, or click to pick one. The file size can be up to 25 MB.
Choose a compression mode: Auto for general use, Aggressive for maximum shrinking, Custom to drive the quality slider yourself, or Target Size to hit a specific KB number.
Optionally change the output format (keep original, JPG, WebP) and cap the maximum width — reducing the width is often the single biggest file-size win for web content.
Preview the before/after side by side to check that quality is still acceptable, then download the compressed file. The result is yours, no watermark, no account required.

Limitations and trade-offs

The compression uses the browser's built-in encoder, which is a general-purpose tool rather than a specialist. A dedicated pipeline built on MozJPEG, oxipng, or guetzli will typically reach a slightly smaller file at the same visual quality. For production web assets where every kilobyte matters, use a build-time optimiser (ImageOptim, Squoosh CLI, imagemin) instead. For form uploads and attachments, this tool is more than enough.
PNG files barely benefit from compression here, and can occasionally come out slightly larger than the input. PNG is already a lossless format with no quality dial to turn, and the browser's canvas-based decode-re-encode cycle doesn't know anything about the original's palette, bit depth, or filter strategy — an indexed-palette PNG comes back as full 32-bit RGBA. To genuinely shrink a PNG, resize its dimensions or convert the output to WebP or JPG (lossy formats can be dramatically smaller for photographic content).
All compression modes strip the file's metadata as a side effect of re-encoding through a canvas: EXIF data, GPS coordinates, camera make and model, capture date, ICC colour profiles, and XMP are all discarded. This is usually a privacy win, but if you need to preserve capture metadata (for archival, legal evidence, or wide-gamut colour accuracy), compress with a desktop tool that supports metadata-preserving encoding instead.
The tool processes one image at a time — there's no batch mode or ZIP output here. The file size cap is 25 MB per image, which comfortably covers phone photos and most DSLR output but will reject medium-format RAW conversions. The browser's encoder runs on the UI thread, so a very large image will briefly freeze the page while it works.

Frequently asked questions

Related tools