Skip to content
OptiMedia

Image compressor for PNG, JPG and WebP

Reduce image size without an upload step: your browser decodes each file, re-encodes it at the quality you choose and hands back the smaller version — plus the exact bytes it saved.

  • Batch as many images as you need
  • Before/after slider on the real output
  • Download single files or one ZIP
  • 0 bytes uploaded — verify in DevTools

Compress, compare, download

Drop files below. The ad space is the only thing on this page that talks to a third party — your images never do.

Drop images here, or click to choosePNG · JPG · WebP · GIF · AVIF · BMP — up to 40 MB each, as many as you like. You can also paste from the clipboard.Nothing is uploaded: compression runs in this tab

Compression settings

Quality: 75%
5% · smallest100% · best quality
Web-ready: visually identical for photos at a fraction of the size.

Your before/after preview appears here

Add an image and you get the comparison slider, the exact bytes saved and a download button per file — plus one ZIP for the whole batch.

  • 0 bytes uploaded

    Canvas and OffscreenCanvas do the work inside your tab — there is no server to receive a file.

  • PNG · JPG · WebP output

    Convert between formats, resize and re-encode in one pass, then download per file or as a ZIP.

  • Batch for free

    No file-count limit and no size paywall: everything a desktop tool charges for, running locally.

Compression guide

How to get the smallest image that still looks right

How much smaller will a compressed image really be?

It depends on the source, and anyone promising a fixed percentage is guessing. A 4 MB phone photo exported as PNG typically lands between 250 KB and 700 KB as WebP at 75% quality. A screenshot of flat UI shrinks far less as PNG but 60–80% as WebP. An already-optimised JPEG might only save 5–20%, and the tool will tell you so instead of pretending.

The results table shows the exact byte count before and after, plus the percentage saved per file, so you can decide with numbers rather than optimism.

Choosing a quality setting that survives zooming

Quality 75 is the default because it is where the curve flattens: below it, gradients start to band and text edges soften; above it, file size climbs quickly for differences most people cannot see. Use 85–95 for product photography and screenshots of dense interfaces, 50–65 for thumbnails, hero backgrounds and anything behind a text overlay.

Always check the before/after slider at full width before publishing — you are looking at the actual output, not a preview render.

Resizing usually saves more than compressing

A 6000 px wide photo displayed at 1200 px is carrying five times the pixels it needs. Set a maximum dimension and the file drops dramatically before any quality trade-off is applied, because you are removing data nobody ever sees.

The maximum-dimension presets cover the common cases: 1920 px for full-width web images, 1600 for blog heroes, 1200 for email attachments and 800 for thumbnails.

How it works

Browser-native compression, start to finish

Four steps, all of them inside your device. The heavy lifting is done by createImageBitmap, OffscreenCanvas and the WebP/JPEG encoders your browser already ships.

  1. 1. Drop your files in

    Drag and drop PNG, JPG, WebP, GIF, AVIF or BMP images — or pick them from the file dialog. Files are read with the browser's File API, straight from disk into memory.

  2. 2. Pick format, quality and size

    Choose WebP for the smallest web-ready files, JPEG for maximum compatibility, or keep the original format. The quality slider and the max-width presets decide how aggressive the compression is.

  3. 3. Compress in your tab

    Each image is decoded, optionally resized on a canvas and re-encoded at the quality you asked for. Processing is single-threaded per file so the tab stays responsive — no queue, no worker farm, no waiting for a server.

  4. 4. Compare and download

    Drag the before/after slider to check quality, read the exact bytes saved, then download files individually or grab the whole batch as a single ZIP archive.

Privacy by architecture

Nothing is uploaded — and you can verify it

Privacy claims are cheap, so this one is falsifiable: the app has no upload code path at all.

  • The upload step simply does not exist

    There is no POST route, no S3 bucket and no signed URL in this app. Open DevTools → Network, compress a 5 MB photo and watch the request list stay empty apart from the page itself.

  • Your files live in a blob URL

    Images are held as in-memory objects and blob URLs that the page creates and revokes. Close or reload the tab and they are gone — nothing survives, because nothing was stored.

  • Metadata is dropped, not kept

    Canvas re-encoding writes a fresh file, so EXIF geolocation and camera metadata are not carried over. That also means you should keep your own copy of the original when metadata matters (copyright fields, for example).

Image compression FAQ

Sizes, formats, metadata and limits — answered without the marketing maths.

How much smaller will my images get?

Photos typically shrink 60–90% when converted to WebP at 75% quality, screenshots and flat graphics 40–80% with PNG kept lossless or converted to WebP, and already-optimised JPEGs 5–30%. The results table shows the exact bytes saved per file, and if re-encoding would make a file bigger the tool keeps your original instead.

Should I choose WebP, JPEG or PNG?

Use WebP for websites and email attachments: smallest files, supported by every current browser. Use JPEG when the destination is picky about formats (older CMS uploads, print shops). Use PNG when you need lossless pixels and transparency, and accept that it will not shrink much unless you also resize.

Does the compressor remove EXIF metadata?

Yes. Re-encoding through a canvas writes a fresh file with no EXIF block, which means GPS location and camera details are dropped — good for privacy, but if you rely on copyright or lens metadata, keep your original file.

Can I compress many images at once and download them together?

Yes. Drop in as many files as you need, they are processed one after another with a progress indicator, and the “Download all (.zip)” button produces a single archive built in your browser with the same file names (plus a -compressed suffix).

Can I hit an exact target file size?

Not directly — the honest way is to lower the quality slider or set a smaller maximum dimension and watch the result, then re-compress with different settings using the “Re-compress with these settings” button. That keeps the tool deterministic instead of pretending to guess a target size.

Does it work offline?

Once the page has loaded, yes: there is no API call during compression, so you can go offline and keep processing images. That is the same reason nothing can be logged or retained on a server.

More free tools in the hub

  • WebP converter

    Convert any PNG or JPG to WebP at the quality you pick: typically 60–80% smaller than PNG with no visible difference.

    Open tool

  • PDF compressor

    Shrink PDFs in the browser with three compression levels or a lossless pass. Scans, contracts and decks, without uploading a thing.

    Open tool