Image Compressor
Shrink JPG, PNG and WebP images in your browser — nothing is uploaded. Resize, convert to WebP, then download the result or get a link. No signup.
Need a link instead of a file?
Click Get a link on any result above and it appears here, hosted at a short-lived URL. Or drop an image straight into the box below.
Drag & drop an image here
or
or paste a screenshot (Ctrl/⌘+V)
Compress images without uploading them
Most online compressors send your images to a server. This one does the work in your browser tab, so private screenshots and client photos stay on your device. Drop one image or a whole batch, tune the quality, optionally cap the width, and download the smaller files.
How to get the smallest files
- Photos: choose WebP at quality 75–85. It is usually far smaller than the original JPEG.
- Screenshots and graphics: PNG to WebP is typically the biggest saving.
- Large images: set a max width (for example 1600 px) if the image will never be shown bigger than that. This tool never upscales.
- Already small? If the result is not smaller, you keep your original instead of a bigger file.
Automate it
For a folder of images, a pre-commit hook or CI, use the CLI: npx pixelvault-cli optimize ./images -r --format webp --max-width 1600. It runs locally with no account. See the docs or the image hosting API if you also want permanent CDN URLs.
Have an iPhone photo? Use HEIC to URL. Need a link for any image? Image to URL.
Image Compressor — FAQ
Are my images uploaded?
No. Compression runs entirely in your browser; the files never leave your device. They are only uploaded if you click "Get a link" on a result, and then only that one compressed image.
How much smaller will my images get?
It depends on the image. Photos usually shrink the most when converted to WebP or JPEG at quality 75-85, often by more than half. Screenshots and graphics saved as PNG typically shrink a lot as WebP. A file that is already well compressed may not shrink at all, and this tool keeps your original in that case rather than handing back a bigger file.
Will compression reduce the quality?
JPEG and WebP output are lossy: lower quality means a smaller file and more visible artifacts. Quality 80 is a good default for photos. PNG output is lossless, so it never changes pixels, but it saves less. Check the result before you replace an original.
What about EXIF and GPS data?
The image is redrawn in your browser and re-encoded, so embedded metadata such as camera details and GPS location is not normally carried into the compressed file. The photo's rotation is applied first, so it still displays the right way up.
Which formats work?
JPEG, PNG, WebP and AVIF in. JPEG, PNG and WebP out (browsers cannot encode AVIF, so an AVIF input is converted to WebP when you keep the format). GIFs, SVGs and iPhone HEIC photos are not handled here; use the HEIC to URL tool for HEIC.
Can I compress images from the command line or in CI?
Yes. The PixelVault CLI has an optimize command that does the same thing on your machine with no account: npx pixelvault-cli optimize ./images -r --format webp --max-width 1600 --out-dir ./optimized. It never writes a file bigger than the original and is safe to re-run in a hook.