Most online image compressors ask you to upload a file to a remote server, wait for processing, then download the result. That workflow is fine for public stock photos - and a bad fit for invoices, unreleased product shots, ID scans, or anything covered by a client NDA. Client-side compression flips the model: your browser reads the file with FileReader, redraws it on a Canvas, encodes JPEG, PNG, or WebP locally, and offers a download. Nothing is posted to an API. This guide explains when that approach wins, when a server tool still helps, and how to use quality and max-dimension controls without chasing a magic percentage.
Quick answer
Use a client-side compressor when the file must stay on your device. Use an upload tool when you need batch pipelines, exotic codecs, or server-side CDN rewriting. For everyday JPG, PNG, and WebP shrinking in the browser, open the free Image Compressor - drop a file, set quality and max edge, compare sizes, then download.
What client-side image compression actually does
In the browser, compression usually means decode → optional resize → re-encode. The Canvas API draws the bitmap at a chosen width and height, then toBlob or toDataURL writes a new JPEG, PNG, or WebP. JPEG and WebP expose a quality slider (roughly 10-100). PNG from Canvas is lossless, so quality does not apply. Max dimension caps the longest edge while keeping aspect ratio - useful when a 4000 px phone photo only needs a 1920 px web hero.
- File stays in memory in the current tab
- No account, no upload endpoint, no server log of your pixels
- You can verify in DevTools Network that compressing creates no request
- Output format can differ from the input (PNG screenshot → WebP, for example)
Client-side vs upload tools - a practical comparison
Upload tools win on heavy batch jobs, specialized codecs, and integrations that rewrite URLs after upload. Client-side tools win on privacy, speed for one-off files, and offline or locked-down networks. Neither replaces a proper build pipeline for a large site - but both beat emailing a 12 MB JPEG to yourself.
- Privacy: client-side keeps NDA and personal files local; upload tools trust a vendor
- Control: you see before/after size before you commit to a download
- Limits: browser Canvas has memory and format limits; servers can push larger batches
- PNG caveat: Canvas re-encoding can grow some PNGs - switch to JPEG or WebP when stats go the wrong way
When upload compressors are still the right choice
Choose a server optimizer when you need AVIF at scale, automatic responsive variants, or a CMS plugin that rewrites every upload. Marketing teams that already store assets in a trusted DAM may prefer that path. Just know that every upload is a policy decision - not only a quality slider.
How to shrink a photo in the browser without uploading
A simple workflow covers most web and email needs:
- Drop or paste a JPG, PNG, WebP, GIF, or BMP (respect the tool size cap)
- Pick JPEG for photos, WebP for a smaller modern file, PNG for lossless icons
- Set quality for JPEG/WebP (often 70-85 for heroes); leave PNG alone
- Set max dimension (1920 is a common web default) or 0 to keep original pixels
- Compare original vs compressed size, preview, then download
After you have a smaller file, you can resize for social presets with the Image Resizer, build a favicon pack with the Favicon Generator, or embed a tiny asset with the Image to Base64 Converter. Compress first when you plan to inline - smaller binaries mean smaller data URLs. For the tradeoffs of inlining itself, see Data URLs and Base64 Images.
JPEG, PNG, and WebP - quick format guide
- JPEG: best default for photos; quality slider controls the size vs artifacts tradeoff
- WebP: often smaller than JPEG at similar visual quality when the browser can encode it
- PNG: lossless; keep for sharp UI chrome, text screenshots, and transparency
- Transparency tip: exporting a transparent PNG as JPEG fills empty pixels (usually white)
Try it with a private file
Paste your own screenshot or product photo - that is the point of a client-side tool. Generative SERP widgets cannot safely hold your private bitmap. A local compressor can.
- Image Compressor - compress JPG, PNG, and WebP in the browser with quality and max dimension - nothing uploaded.
- Image Resizer - set exact pixels or social presets after you shrink file size.
- Image to Base64 Converter - turn a compressed file into a data URL when you truly need to inline.
Frequently asked questions
Is client-side compression as good as Squoosh or a CDN optimizer?
For everyday web sizes, Canvas JPEG/WebP is usually enough. Advanced tools may beat it on exotic codecs or multi-pass encoding. If privacy matters more than the last few kilobytes, stay client-side.
Why did my PNG get larger after compressing?
Canvas PNG does not preserve the original encoder settings. Photos saved as PNG often shrink more as JPEG or WebP. If the stats show growth, change format or lower quality.
Does quality work on PNG?
No. PNG from Canvas is lossless, so a quality slider does nothing useful. Use JPEG or WebP when you want a quality vs size tradeoff.
How do I prove nothing was uploaded?
Open DevTools → Network, compress a file, and confirm no new request carries the image body. The Image Compressor is built so FileReader and Canvas stay in the tab.
Compress without uploading
Open the free Image Compressor, drop a private file, set quality and max dimension, then download. Your pixels never leave the browser.