Compress an Image Without Uploading It

Compress and resize images locally with the Image Compressor. The file is read by your browser and never uploaded.

The upload you did not see

Search for a free image compressor and most results work the same way: you choose a file, it is sent to a server, compressed there, and returned as a download. The interface says free and fast; it rarely says your file leaves your device.

For a holiday photo that may not matter. For a passport scan, a signed contract, a medical image, or an unreleased design, it changes the risk. Uploads can be retained, logged, or scanned, and you cannot verify what happens on the other side.

Local compression removes an entire class of risk: if the file never leaves the browser, there is no server copy to leak.

What local compression actually does

A browser can decode an image into pixels, redraw it at a smaller size, and encode it again as JPEG, WebP, PNG, or AVIF. That is the whole trick. The work happens on your CPU, inside the page.

The practical limits are your device's memory and the browser's encoders. A large photo can be processed on a laptop; a folder of raw camera files is a different job.

Decode: the browser reads the file you selected, without a network request.
Transform: resize, choose a format, and set a quality level.
Encode: the result is written back to a Blob you can download.

Note: You can verify the claim yourself: open DevTools, switch to Network, and compress a file. The only requests should be for the page's own code and assets.

Three common tasks, three different settings

The right settings depend on where the image is going. A file that looks fine on a large screen can still be too large for an email gateway. For a repeatable batch workflow, see batch image compression. If the image is headed for an email attachment, the email compression settings start from the recipient's size limits.

Email: JPEG or WebP, quality around 75-80, long edge about 1600-2000 px. Most inboxes do not need more.
Web: WebP at quality around 80, width matched to the layout, and a smaller size for mobile if the page uses srcset.
Forms: check the portal's pixel and byte limits first; JPEG is the safest default unless the image needs transparency, in which case PNG is the correct format.

Warning: Do not resize an image up. Upscaling adds bytes without adding detail.

Step by step in the browser

Open the Image Compressor.
Drop one or more images, or use the file picker.
Choose the output format: WebP for the web, JPEG for compatibility, PNG when transparency matters, AVIF only if the target browser supports it.
Set the quality and, if needed, a resize rule: original size, long-edge limit, percentage, or a width-by-height box.
Run the compression, compare the before and after size, and open the result once before downloading.
Download the files. Nothing is sent to a server at any point.

Note: If the output is larger than the input, keep the original. Re-encoding an already optimized file often adds bytes.

Quality, size, and the recompression trap

Quality 80 is a useful starting point, not a law. Photographs tolerate it well; screenshots with small text, line art, and images with sharp edges often need a higher setting or a lossless format. For the format comparison behind these defaults, see client-side image compression.

Every re-encode discards a little more information. Compressing the same photo five times produces a worse file than compressing it once from the original. Keep the original and regenerate from it when you need another size.

Judge visually, not by the byte count alone. Zoom to 100% and check text, faces, and gradients. A file that is 30% smaller but visibly soft is not a good trade.

When local compression is not enough

Very large images can exhaust browser memory, especially on phones. If the tab crashes, use a desktop tool or a command-line encoder for that batch.

AVIF output depends on the browser's encoder. If the format is unavailable, WebP is usually the next best choice; the page should tell you rather than silently produce a different file.

For a production site, compression is only one part of delivery. A CDN, correct cache headers, and responsive image sizes matter more than shaving the last few kilobytes.

FAQ

Q.Does local compression remove EXIF data?

A.A canvas-based re-encode usually drops metadata such as camera model and GPS coordinates, but the exact behavior depends on the encoder and the output format. If metadata matters, inspect the output with a dedicated tool instead of assuming.

Q.Why is the compressed file sometimes larger?

A.PNG screenshots, already optimized images, and files that are mostly noise can grow when re-encoded. Try WebP or JPEG, lower the quality slightly, or keep the original.

Q.Can I compress a PDF here?

A.No. This tool works on images. A PDF is a different container; use a PDF-specific tool and check whether it uploads the document.

References

MDN - Canvas API: https://developer.mozilla.org/en-US/docs/Web/API/Canvas_API
MDN - WebP image format: https://developer.mozilla.org/en-US/docs/Web/Media/Formats/Image_types#webp
W3C - PNG specification: https://www.w3.org/TR/png-3/
web.dev - Image optimization: https://web.dev/articles/image-optimization

Compress an image now

WebP, JPEG, PNG and AVIF output, batch and resize, all client-side.

Open Image Compressor

Keep the file on your device

Local compression is faster to verify than to trust. Open the network panel once, compress an image, and see for yourself that the file stays in the browser.

Use the Image Compressor for the next image you need to send; the original never leaves your device.