Tutorial

How to Compress JPEG File Size

Phone cameras and DSLRs produce multi-megabyte JPEGs by default. Here is a practical, browser-only way to shrink JPEG file size without uploading your photos to a third-party server.

Why JPEG files get so large

JPEG is already a compressed format, but “compressed” does not mean “small enough for every use case.” A modern phone photo can be 3–12 MB. That is fine for archival storage and bad for email attachments, CMS uploads, product galleries, and portals with hard byte caps.

File size grows with resolution, noise, fine detail, and how aggressively the camera encoded the original. Re-saving at a lower quality, resizing to the display size you actually need, or converting to a more efficient web format are the three levers that matter.

What you will use

This tutorial uses SnapShrink, a client-side compressor that runs in Chrome, Edge, Firefox, and Safari. Images are read with the File API and encoded in a Web Worker. Nothing is posted to SnapShrink servers. If you prefer a deeper privacy explanation, see the privacy policy.

Step 1 — Open the tool

Go to getsnapshrink.com/app/. There is no signup wall. You should see a drop zone, quality controls, an optional Target KB field, and an output format picker.

Step 2 — Drop your JPEG (or a batch)

Drag one .jpg / .jpeg file onto the drop zone, or multi-select a folder of photos. Mixed batches with PNG and WebP are fine too; this guide focuses on JPEG workflows.

Files over 50 MB are skipped with a clear message so the rest of the batch can continue. Corrupt files are likewise skipped rather than crashing the run.

Step 3 — Choose how you want to shrink the file

Option A: Quality slider

Pick JPEG as the output format and lower the quality until the before/after size looks right. This is the classic approach. It works, but you may iterate a few times if you have a hard size limit.

Option B: Target KB (recommended for caps)

Type a number such as 200 or 100 in Target KB. SnapShrink searches for the highest quality that keeps the output at or under that size. If you specifically need a visa or portal photo under 100KB, use the dedicated flow on compress image to 100KB.

Option C: Convert to WebP

If the destination accepts WebP, set output to WebP. You often get a smaller file at similar visual quality. The WebP converter landing page covers PNG/JPG → WebP in more detail.

Step 4 — Compress and inspect

Click Compress. Each image shows its original size, new size, and ratio when finished. Check faces, text overlays, and product edges at 100% zoom before you ship the file. If something looks too soft, raise the target slightly or start from a resized (but still sharp) source.

Step 5 — Download

Download a single file, or use Download all as ZIP for a batch. The ZIP is built in the browser. First 10 images per session are free; a one-time $9 license removes the quota if you compress regularly.

Tips that shrink JPEGs further without wrecking them

• Resize first when the display size is known. A 4000px-wide hero that shows at 1200px on the site should not start life at full camera resolution.
• Crop empty space. Borders and unused background still cost bytes.
• Avoid repeated re-saves of the same JPEG. Each lossy pass adds artifacts. Prefer one careful encode from the original.
• Use progressive JPEG only if your stack needs it. SnapShrink focuses on size and privacy; host requirements vary.
• Batch product shots together. The bulk image compressor applies the same settings across a folder and returns a ZIP.

JPEG vs PNG vs WebP for file size

Photos almost always belong in JPEG or WebP. PNG shines for screenshots, UI, and graphics with sharp edges or transparency. If you started with a PNG photo export, converting to JPEG or WebP will usually cut the size dramatically. If you started with a camera JPEG, staying in JPEG or moving to WebP are the common paths.

A worked example: email-ready product shot

Suppose you have a 4MB JPEG from a product shoot and need it under 300KB for an email campaign. Open SnapShrink, drop the file, type 300 in Target KB, keep JPEG output if the ESP rejects WebP, and compress. Confirm the before/after panel shows ≤300KB. If skin or fabric looks soft, try resizing the source to the email template width first (for example 800px), then re-run target mode — you often regain quality because fewer pixels must fit inside the same byte budget.

For a Shopify or WooCommerce gallery, process the whole folder with the bulk compressor, set WebP when the theme supports it, and download a ZIP. Keep originals elsewhere; only ship the compressed set to the CMS.

Phone workflow

On iPhone Safari or Android Chrome, tap the drop zone, pick from Photos or Files, set quality or a target, and download. iOS HEIC is typically handed to the browser as JPEG via the system picker, so you do not need a separate converter. For hard portal caps on mobile, the same Target KB field applies — see reduce image size to 100KB when the form is that strict.

How this compares to desktop editors

Photoshop, Affinity, and Lightroom export dialogs also shrink JPEGs well. SnapShrink is for the moments when you do not want to open a full editor: quick portal uploads, batch web exports, or a privacy-sensitive file you refuse to upload to a hosted compressor. Squoosh remains a strong single-image alternative with deep codec controls; SnapShrink trades some of that depth for batch + target-KB speed.

Common mistakes

• Uploading passport or client photos to a random “compress online” site when a local tool exists.
• Cranking quality to the minimum and wondering why skin tones band.
• Ignoring the portal’s required format (some still reject WebP).
• Compressing already-tiny thumbnails and expecting miracles.

FAQ