Compress images without uploading them anywhere
Drop in JPG, PNG, WebP or GIF files, choose WebP, JPEG or PNG output, set a quality level and an optional longest edge, then download smaller copies. Every pixel is processed in this tab with the Canvas API — there is no upload step, because there is no server to upload to.
Nothing has been processed yet. Add images and each one appears here with its original size, new size and the percentage saved.
PNG output ignores the quality slider because PNG is lossless. JPEG output flattens transparency onto white. Animated GIFs are reduced to their first frame. Files over 25 MB or 8000 px on the long edge are processed but may be slow.
How the compressor works
Three steps, no account, no upload
Add your files
Drag a selection onto the box above or click it to browse. Non-image files are ignored with a note, and anything over the batch limit is reported rather than silently dropped.
Choose format and size
The browser decodes each image, draws it onto a canvas at the target longest edge, and re-encodes it to WebP, JPEG or PNG at the quality you picked. Changing a setting re-runs the batch.
Compare and download
Each card shows the old and new dimensions, the old and new file size and the percentage saved. Download individually, or use Download all and allow multiple downloads if the browser asks.
What people use it for
Each guide below goes into the details
Converting photos to WebP
WebP is usually 25–35% smaller than JPEG at matched visual quality, and every current browser displays it.
JPEG vs WebP vs AVIF →Hitting a 100 KB upload limit
Resize first, then step the quality down. The order matters more than the number on the slider.
Get under 100 KB →Sizing product photography
One square master, four derived sizes, and a byte budget per slot keeps a catalogue consistent.
Product image sizes →Shrinking screenshots
Use lossless WebP for interface captures; JPEG turns text into mush at any setting worth using.
Screenshots and UI →Running batches
Fixed presets, protected originals, one encode per file, and a spot check of five images per folder.
Batch workflow →Keeping files private
What you actually give away when you upload an image to a compressor, and how to check a tool's claims.
The privacy cost of uploading →Guides
JPEG vs WebP vs AVIF
Which format to ship for photos, screenshots, logos and email — and where each one fails.
The privacy cost of uploading images
What happens to a file after it leaves your machine, and how to test whether a compressor really is local.
Getting an image under 100 KB
A five-step loop for hard file-size limits, with the arithmetic that makes it predictable.
Product photo sizes and file weight
A preset matrix for gallery, zoom, thumbnail and feed images, plus the export order that avoids double compression.
Why screenshots should not be JPEG
What block-based compression does to text and thin lines, and how to capture and publish UI imagery properly.
A batch compression workflow
Presets by destination, protected originals, chunked runs and a written record of what was applied.
Questions people ask
Are my images uploaded anywhere?
No. The page contains no upload code and no analytics beacons; the only files it requests are its own stylesheet and script. You can prove it by loading the page, disconnecting your network and compressing an image — it still works.
Which formats can it read?
Whatever your browser can decode: JPEG, PNG, WebP, GIF (first frame only), BMP, and AVIF in browsers that support it, plus SVG in most cases. A file the browser refuses to decode is reported on its card instead of failing silently.
Does the quality slider affect PNG output?
No. PNG is lossless, so the slider is ignored when PNG is selected. If a PNG comes out larger than the original, that is expected for photographic content — switch to WebP or JPEG.
Why did a compressed file come out bigger than the original?
Usually because the source was already heavily compressed and you re-encoded it at a higher quality, or because you chose PNG for a photo. The card warns you when the output grew, and lowering quality or switching format usually fixes it.