How to Compress Images Without Uploading Them Anywhere

Every “compress your image online” site does the same thing: upload your photo to a server, run it through MozJPEG or pngquant, and hand back a smaller file. You do not need the server. Those exact codecs compile to WebAssembly, which means compression runs in your tab — same results, no upload, no size limits, no queue. Here is how to do it properly.

Why browsers can do this

The image compression world runs on a small set of open-source engines: MozJPEG for JPEG, libwebp for WebP, libavif for AVIF, oxipng for PNG. All of them have WASM builds. A browser compressor downloads the codec (a few hundred KB, cached forever), then your images are decoded and re-encoded locally using your device’s CPU. Quality and file sizes match the command-line tools because they are literally the same code.

Format selection in 30 seconds

• Photos → WebP or AVIF. AVIF is 20–50% smaller than JPEG at the same quality; WebP has the broadest device support. Modern browsers handle both.
• Screenshots / graphics with flat color → PNG or WebP lossless.Text and sharp edges survive lossless compression; JPEG smears them.
• Need universal compatibility → JPEG. Every platform since 1995 opens it.
• Logos and simple icons → SVG. Vector beats all of them; do not rasterize what could be vector.

Step-by-step

• 1. Drop your images. Batch processing is local, so there is no penalty for dragging in a whole folder. No file-size caps because nothing is uploaded.
• 2. Pick quality. For WebP/AVIF, quality 70–80 is visually indistinguishable for photos and 40–70% smaller. For JPEG, quality 75 is the historic sweet spot. Zoom to 100% on the preview to judge.
• 3. Set dimensions. Resizing is the single biggest saving most people miss. A 6000 px phone photo used at 1600 px wide can shrink 5× before you even touch quality settings.
• 4. Strip metadata. EXIF location, camera data, and thumbnails add 20–200 KB per file. Local tools can remove it — that is a privacy win too, since GPS coordinates live in there.
• 5. Download. Files save directly to disk; original files on your device are never overwritten unless you choose to.

Quality settings that actually work

A few battle-tested presets:

• Web/blog images: WebP, quality 75, resize to 1600 px max width.
• E-commerce product photos: AVIF quality 65 plus a JPEG fallback — under 200 KB per image is easy.
• Email attachments: JPEG quality 70, 1200 px wide — a 6 MB photo becomes ~400 KB.
• Archival: Keep a lossless original; only compress the copy you publish.

The privacy angle (yes, for images too)

Uploaded images retain EXIF data until the server strips it — GPS location, device serials, sometimes edited history. That data lands in server logs you will never see. Local compression removes or preserves metadata under your control, and the photo itself never leaves the machine. Sensitive scans, ID photos, legal documents: compress them locally out of habit.

Batch workflows

Because processing is local, batch runs cost nothing and never hit a rate limit. Drag in 200 wedding photos or a folder of product shots; modern multi-core WASM handles several images in parallel, and your laptop fans spinning up is the only “server load” involved.

Wrapping up

Image compression is the perfect first local-AI-adjacent habit: the tooling is mature, the results are identical to cloud services, and the friction — upload progress bars, 25 MB caps, account walls — simply disappears. Open the image compressor in the matrix, drop in a photo, and watch a 5 MB JPEG become a 400 KB AVIF without a single byte leaving your computer.