PK Systems PK Systems
Image Tools

Image Compressor

Squash JPG, PNG and WebP files smaller — visually identical, no upload.

Image Compressor

Drop images here or click to pick JPG, PNG and WebP. Multiple files supported. They stay in your browser.

All processing in your browser — no upload, no tracking.

75 works for the web. Lower for thumbnails; higher for prints.

Status

What this tool does

Re-encodes JPG, PNG and WebP files at a lower quality so they take less disk space, less bandwidth and load faster on web pages. The compression runs entirely in your browser using the standard canvas API — no upload, no tracking, no watermark, no quotas. Drop a single file or a hundred at once: each one is decoded, painted onto a canvas, and re-encoded at the quality you pick. The result table shows you the size before and after with a percentage saved per file, plus an overall total. When everything is done you can download files individually or grab a single ZIP. Quality 75 is the sweet spot for the web — typically 40-70% smaller than a phone-camera JPG with no visible difference. PNGs are re-encoded losslessly, but PNG sources can sometimes grow if the original was already optimised; we flag those in amber so you don't ship a worse file.

How to compress images

  1. Drop your images — JPG, PNG and WebP are accepted. Each file becomes a row in the queue showing its current size.
  2. Pick a quality — 75 is a great default for the web. Drop to 60 for thumbnails or chat; bump to 90 for prints. PNG output ignores quality (it's lossless).
  3. Hit Compress — Each file is decoded and re-encoded one at a time, locally on your device. Big files yield to keep the page responsive.
  4. Download — Use the per-row Download button, or grab everything as a ZIP. Files keep their original name with a -compressed suffix.

How the compression works

JPG and WebP files shrink by re-encoding the image with a stronger compression setting than the original used. Most camera and phone JPGs are saved at quality 92-98 — overkill for the web, where quality 75 looks identical on screen. PNG output is always lossless and ignores the quality slider, so PNGs of screenshots, logos and graphics stay perfectly sharp. As a useful side effect, the re-encode strips EXIF and ICC color profiles from the output, which is a small privacy win — no GPS, no camera serial, no editing-software signature carried along by accident. The savings panel shows the percentage of file size shaved off each image; if a row turns amber, the output is actually slightly larger than the source (rare, almost always on PNGs that were already heavily optimised) — in that case keep the original. Auto mode preserves your input format; pick a target like JPG to WebP for additional savings, since WebP at the same visual quality is typically 20-30% smaller.

Format and quality cheat sheet

JPG at quality 75 is the web default — small files, no visible artefacts on photos. WebP at quality 75 is typically 20-30% smaller than JPG at the same visual fidelity, and supported by every modern browser. PNG is lossless and best for screenshots, logos and graphics with sharp edges or transparency; quality is ignored. If a PNG source grows after re-encoding, leave it as is — the original was already well-optimised. Auto mode keeps the input format; pick a specific format to convert (e.g. JPG to WebP) for further savings.

Frequently asked questions

Are my images uploaded?
No. Everything happens locally on your device — your images never leave the browser, never travel to our servers, and are not stored, indexed, logged, or shared. The page works even if you go offline after it loads.
Why did my PNG get bigger?
PNG is lossless, so re-encoding cannot drop visual data — it can only reorganise the file. If your source was already well-optimised by a tool like pngcrush or Squoosh, the re-encode here may produce a slightly larger file. Those rows are flagged in amber — keep the original in that case.
What's the best quality setting?
75 for the web, 60 for chat thumbnails, 85-90 for prints, and 50 for absolute size constraints. Below 50 you start to see banding on skies and skin tones.
Why is WebP smaller than JPG?
WebP uses a more modern codec (VP8 / VP8L) with better entropy coding. At identical visual quality, WebP files are typically 20-30% smaller than JPG and are supported in every browser released in the last five years.
Will EXIF be preserved?
No. The re-encode drops EXIF, IPTC, XMP and GPS. That is usually a privacy win — no GPS, no camera serial, no editing-software signature — but if you specifically need to keep camera metadata, use a desktop tool that recompresses without re-encoding.
Is there a file size limit?
Only your browser's memory. Each photo allocates several megabytes of pixels while it's being processed. Phones comfortably handle a dozen 12 MP photos at once; desktops handle hundreds.