// compress images in the browser, nothing uploaded
Free browser-based image compressor. Compress JPEG, PNG, and WebP images client-side with adjustable quality. No upload to server, no sign-up required.
Click or drag & drop images
JPEG · PNG · WebP · GIF — max 20 filesNo images yet
Upload up to 20 images at onceDrag and drop or click to select up to 20 JPEG, PNG, WebP, or GIF images at once.
Adjust the quality slider, pick an output format, and optionally set a max dimension to resize large images.
Click Compress All, then download each file individually or grab all at once as a ZIP archive.
A free browser-based image compressor that uses the HTML Canvas API to re-encode images at a lower quality. Supports JPEG, PNG, and WebP output, optional proportional resizing, batch processing of up to 20 files, and ZIP download — all 100% client-side, nothing is uploaded to a server.
No. This tool uses the browser's Canvas API to read, re-encode, and compress your images entirely on your device. No image data is ever sent to any server — not even for processing. The files stay in your browser's memory only for the current session. This makes it safe for confidential, proprietary, or personal images.
For most web images, a quality of 75–85 produces an excellent balance of file size reduction and visual quality. For thumbnails or small previews, 60–70 is acceptable. For print-quality or archival images, use 90+. PNG output ignores the quality slider since PNG uses lossless compression — use JPEG or WebP for the best compression ratios.
JPEG is lossy and produces the smallest files for photographs — ideal for photos with no transparency. PNG is lossless (quality slider has no effect) and preserves transparency — best for logos, icons, and screenshots with sharp edges. WebP supports both lossy and lossless compression with better efficiency than JPEG and PNG, and is supported in all modern browsers.
PNG uses lossless compression, so re-encoding a PNG as PNG may produce a larger file than the original if the original was already well-optimized. To reduce PNG size, convert to JPEG or WebP (lossy), or use a dedicated lossless PNG optimizer. For JPEG inputs, very high quality settings (95+) may also produce a slightly larger output.
Yes. The max dimension field sets an upper limit on both width and height. If your image is 3000×2000 and you set max dimension to 1200, the output will be 1200×800 — proportionally scaled so neither dimension exceeds 1200px. Images already smaller than the limit are not upscaled.
GIF files can be loaded, but the output will not be an animated GIF — the Canvas API reads only the first frame. For animated GIFs, use a dedicated GIF optimizer. Converting a static GIF to WebP or JPEG with this tool will typically produce a much smaller file than the original GIF.
Images are typically the largest assets on a web page. Unoptimized images slow down page load times, increase bandwidth costs, and hurt Core Web Vitals scores — all of which affect both user experience and search engine rankings. Compressing images before uploading them to a website, CMS, or CDN is one of the simplest and highest-impact optimizations available.
This tool handles the compression entirely in your browser using the HTML Canvas API — no server round-trip, no account, no file size limits beyond what your browser can handle. It is suitable for quick one-off compressions as well as batching up to 20 files at once.
Choosing the right format is as important as the quality setting. JPEG is the go-to for photographs and images with gradients — its lossy algorithm handles continuous-tone imagery efficiently and produces small files. PNG should be used for images with transparency, sharp edges, text overlays, or flat colors — its lossless algorithm preserves every pixel exactly. WebP is a modern format that outperforms both: it supports both lossy and lossless modes with 25–35% smaller files than equivalent JPEG or PNG, and is fully supported in all modern browsers since 2020.
If you are optimizing for the web and file size is the priority, WebP at quality 80 is almost always the best choice. For compatibility with older systems or email clients that may not render WebP, JPEG at quality 80 is the safe fallback.
This tool draws your image onto an HTML <canvas> element and then calls canvas.toBlob() or canvas.toDataURL() with the target MIME type and quality value. The browser's built-in image encoder re-encodes the pixel data at the specified quality, producing a new compressed file. The quality parameter (0–1 internally, shown as 1–100 in the UI) controls the degree of lossy compression for JPEG and WebP. For PNG, no quality parameter applies — the output is always lossless, but the canvas re-encoding may still produce a different (sometimes smaller, sometimes larger) file than the input depending on the original encoder used.