Compress JPG

Add your JPG file (drag-drop or click "Add Images"), choose a compression preset (Maximum Compression is default and gives 60-80% reduction), then click Compress. Download results individually or as a ZIP. The entire process takes seconds.

Yes, JPEG is lossy—compression removes details. Maximum Compression is aggressive and you'll notice quality loss on close inspection. High Quality preset (quality 92) is imperceptible for most viewers. The more you compress, the more quality you lose, but our tool never returns a larger file than your original.

We use MozJPEG (Mozilla's encoder) which produces 3-10% smaller files than standard JPEG at the same visual quality. Unlike other tools, we process entirely in your browser—files never upload to a server. You get six compression presets, batch processing for 50 files, Target Size mode for exact limits, and no daily restrictions.

Use High Quality preset (starts at quality 92). It won't reduce size by much—typically 20-40%—but quality loss is imperceptible. You can't truly compress JPG "without losing quality" because JPEG is lossy. For lossless compression, you need PNG format.

Select Target Size preset, enter 100KB, then compress. Our binary search algorithm tries different quality levels (typically 2-3 attempts) and hits your target within 5% tolerance. If 100KB is unreachable even at lowest quality, enable Resize in optional settings to reduce image dimensions.

Yes, if the tool processes locally. We use browser-based WebAssembly—your files never leave your device. No upload to any server. Other tools upload files (privacy risk, especially for sensitive documents). We can't see your images because they only exist in your browser memory.

Nothing—same format, different file extension. Early Windows systems required three-letter extensions (.jpg), while Mac and Unix used .jpeg. Modern systems accept both. Our tool outputs .jpg files but handles .jpeg inputs identically.

Depends on the source. Uncompressed camera photos (4-8MB) can shrink 60-80% with Maximum Compression preset. Already-optimized images might only compress 10-20%. If an image is already at quality 75 and you try Maximum Compression, you'll see degradation but less size reduction. Our tool keeps your original if compression would make the file larger.

Use Maximum Compression preset or Target Size mode (aim for under 2MB per image). Most email providers limit total attachments to 25MB. If you're sending 10 photos, compress each to 200-300KB. Batch process all images at once, then download as ZIP.

Not truly. JPEG is inherently lossy—any decode-and-encode cycle loses information. High Quality preset (quality 92) is imperceptible to most viewers, but technically you're losing quality. For actual lossless compression, convert to PNG (much larger files) or use WebP lossless mode.

Select up to 50 files when you add images (Ctrl+Click or Cmd+Click to select multiple). We use 4-6 parallel Web Workers, so batches process simultaneously rather than one-by-one. Twenty images take about the same time as one. Download all results as a single ZIP file.

Optional. Enable "Strip Metadata" in settings to remove EXIF data (camera model, settings), GPS coordinates, timestamps, and copyright info. Typically saves 5-20KB. Color profiles are preserved for correct color display. Metadata stripping is useful for privacy (removes location data from photos).

Yes. Add a PNG file, and it converts to JPG during compression. Note: PNG supports transparency, JPG doesn't. Transparent areas become white background. If you need transparency, use PNG compression or convert to WebP.

Compress to an exact KB or MB limit. Choose Target Size preset, enter your requirement (e.g., 100KB for passport photos or 200KB for job applications), and compress. Our algorithm uses binary search—it calculates bits per pixel, estimates starting quality, compresses, checks result, then refines quality until your target is achieved within 5% tolerance.

No. We use WebAssembly for browser-based processing. Your images decode, compress, and encode entirely in your device memory. There's no XHR or fetch call to any compression endpoint. You can open DevTools Network tab and watch—zero file uploads. Works offline after page loads.