Compress JPEG Files
JPEG is the most common image format on the web, but camera photos and high-quality exports are often 3-15MB — far too large for fast page loads, email, or social media uploads. Pixotter compresses JPEG files with adjustable quality, letting you find the perfect balance between file size and visual fidelity. Processing happens entirely in your browser. Your photos never leave your device.
When to Compress JPEG
- Website images — Google recommends images under 100KB for fast page loads
- Email attachments — Most email providers limit attachments to 10-25MB total
- Social media uploads — Platforms re-compress large images, often with worse quality than you'd choose
- E-commerce products — Product photos need to load fast on mobile without sacrificing zoom quality
- Blog posts — Each unoptimized hero image can add 2-5 seconds to page load time
JPEG Quality Guide
90-100: Near-lossless. Minimal size reduction (10-20%). Use for archival or professional print.
75-89: The sweet spot for most uses. 50-70% size reduction with differences invisible to most viewers. Recommended for web, email, and social media.
50-74: Noticeable quality loss on close inspection. 70-85% size reduction. Acceptable for thumbnails and previews.
Below 50: Visible artifacts. Only use when file size is critical (under 20KB targets).
When to Compress JPEG Files
JPEG is the most common image format on the web, and also the most common reason pages load slowly. A photo straight from a DSLR or modern smartphone sits at 3–5MB. That's fine for archiving — it's a problem for everything else.
Website performance. Unoptimized JPEGs are the single biggest cause of slow page loads. A hero image should land under 200KB; content images under 100KB. A 4MB photo in a WordPress blog post burns three to four seconds of load time on a mobile connection. Google's Core Web Vitals score that against you.
Email. Most providers cap attachments at 25MB. A batch of ten vacation photos at 4MB each exceeds that before you hit send. Compressing first means the email actually arrives.
E-commerce. Amazon recommends product photos under 1MB. Oversized images increase bounce rate — shoppers don't wait. Compress and resize every product photo before upload; the conversion impact is measurable.
Social media. Instagram, LinkedIn, and Twitter re-compress any image that exceeds their thresholds — and their algorithms are aggressive. Pre-compressing to your target quality means you control what the output looks like, not the platform.
Local storage. A photo library of 10,000 images at 4MB each is 40GB. Batch compression at quality 80 cuts that to 8–12GB with no visible quality change.
How JPEG Compression Works
JPEG compression is lossy by design. Understanding how it works helps you make smarter tradeoffs between file size and visual quality.
Discrete Cosine Transform (DCT). The encoder divides your image into 8×8 pixel blocks, then converts each block from pixel values into frequency components — similar to how audio compression works. High-frequency components represent fine detail and sharp edges. Low-frequency components represent broad color areas. The quality setting controls how aggressively the high-frequency data is discarded.
Quality parameter (1–100). At quality 80–85, JPEG typically achieves 60–70% file size reduction versus quality 95, with no perceptible visual difference on screen. Below quality 60, you start seeing blocky artifacts, especially around sharp edges and text. Below quality 40, the image looks degraded to any viewer.
Chroma subsampling. Human eyes are more sensitive to brightness than color. JPEG exploits this by storing color at lower resolution than brightness. The 4:2:0 mode (used by most JPEG encoders at quality settings below 90) discards half the color data in both dimensions. You almost never notice it. It saves roughly 33% on top of DCT compression.
Progressive vs. baseline. A baseline JPEG loads top-to-bottom, one row at a time. A progressive JPEG loads in passes — first a low-resolution version of the whole image, then progressively sharper. For web use, progressive feels faster even when the total bytes are identical. Progressive encoding also typically saves 2–8% on file size.
EXIF metadata. Every camera embeds metadata in JPEGs: GPS coordinates, camera model, lens, aperture, shutter speed, timestamp. This data adds 5–50KB per image and, more importantly, leaks location data if the photo was taken on a phone. Stripping EXIF is good practice before any public-facing upload.
Re-compression risk. Every time you open a JPEG and save it at a lower quality, you add another generation of artifacts on top of the existing ones. Always compress from the original high-quality source, never from an already-compressed copy.
JPEG Compression Tools
| Tool | Type | Quality Control | Batch | Privacy | Speed | Cost | Best For |
|---|---|---|---|---|---|---|---|
| Pixotter | Browser-based | Quality slider | Yes, unlimited | Files never leave device | Instant | Free | Web optimization with privacy |
| TinyPNG | Cloud-based | Automatic | Yes (20 files free) | Uploaded to servers | 2–5 sec/file | Free tier / $25+/yr | Simple compression, no config needed |
| Squoosh | Browser-based | Quality slider + preview | No (1 file at a time) | Files never leave device | Instant | Free | Side-by-side quality comparison |
| ImageMagick | CLI tool | Full control | Yes, unlimited | Local | Fast | Free (Apache 2.0) | CI/CD pipelines, scripting, automation |
| Photoshop | Desktop app | Full control | Yes (via Actions) | Local | Medium | $20.99/mo (Creative Cloud) | Professional editing workflows |
Notes on the table:
- TinyPNG's free tier limits you to 20 files per session and 5MB per file.
- Squoosh is excellent for evaluating quality tradeoffs before committing to a setting — but you have to process files one at a time.
- ImageMagick is the right choice if you're compressing hundreds of images in a build pipeline. Pixotter handles the browser workflow.
JPEG Quality Settings Guide
| Quality Setting | Typical File Size (1000px wide) | Visual Quality | Best Use Case |
|---|---|---|---|
| 95–100 | 300–500KB | Indistinguishable from original | Print, archival, source files |
| 80–90 | 100–200KB | Excellent — no visible artifacts at normal viewing distance | Website hero images, portfolio, e-commerce |
| 60–75 | 50–100KB | Good — minor artifacts visible on zoom | Blog content images, thumbnails, social media |
| 40–55 | 25–50KB | Acceptable — visible artifacts on close inspection | Low-bandwidth previews, aggressive mobile optimization |
| Below 40 | Under 25KB | Poor — obvious block artifacts | Avoid for anything customer-facing |
The 80–85 range is the practical sweet spot for most web use. You get 60–70% file size reduction from a quality-95 source, and the visual difference is imperceptible on screen. Start there and only go lower if your file size target requires it.
Tips for Best Results
- Start at quality 80. Reduce from there only if the file size target isn't met. Don't go below 60 for anything public-facing.
- Resize before compressing. A 4000×3000 image scaled to 1200×900 and then compressed at quality 80 will be dramatically smaller than the original compressed at quality 80 at full resolution. Both steps matter. Pixotter's resize tool handles both in one pass.
- Strip EXIF metadata. Cuts 5–50KB per image. Removes GPS data from photos taken on phones. Always strip before uploading user-generated content to a public page.
- Use progressive encoding for web. Better perceived load time, marginally smaller file. No downside for browser delivery.
- Batch-process e-commerce photos with identical settings. Consistent quality settings produce visual consistency across a product catalog. Mixed settings look unprofessional.
- Compress from the original, every time. Never re-compress an already-compressed JPEG. Start from the RAW or the highest-quality export you have.
- Check the result at 100% zoom. Zoom to 100% after compressing. Blocky artifacts around text or sharp edges at 100% zoom are a sign you've gone too far.
Frequently Asked Questions
What quality setting should I use when compressing a JPEG?
For web images — hero images, blog photos, product images — start at quality 80. At that setting, a typical photo compresses 60–70% from a quality-95 source, and the difference is invisible on screen. If 80 still produces a file that's too large for your target, drop to 70. For thumbnails and preview images, 60–70 is fine. Avoid going below 40 for anything a customer or reader will actually see.
If you're unsure, use Pixotter's quality slider and compare the output at 100% zoom before downloading.
Does compressing a JPEG reduce quality?
Yes — JPEG is a lossy format. Compression permanently discards some image data. The question is whether that loss is perceptible.
At quality 80 and above, the discarded data consists of high-frequency detail that human vision doesn't pick up at normal viewing distances. The practical answer: at quality 80, compressing a photo looks lossless even though technically it isn't.
One important rule: always compress from the original high-quality source. Each generation of JPEG compression stacks artifacts on top of existing ones. A quality-80 copy of a quality-80 copy looks noticeably worse than a quality-80 copy of the original.
What's the difference between JPEG and JPG?
Nothing. They are the same file format. The `.jpg` extension originated in early Windows operating systems that enforced a three-character extension limit, so `.jpeg` was shortened to `.jpg`. Modern operating systems handle both. The format, the compression algorithm, the file structure — all identical.
How do I compress a JPEG without losing quality?
Strictly speaking, you can't. JPEG is lossy by definition. But there are two practical approaches:
Lossless JPEG optimization — tools like jpegtran and MozJPEG can re-encode existing JPEGs without touching the image data (just stripping metadata and optimizing the file structure). This gets you a 5–15% size reduction with zero quality change. It only works if you're starting from an already-compressed JPEG source.
Compress at quality 80+ — technically lossy, but the removed data is imperceptible to human vision. For the practical purpose of "looks identical but loads faster," quality 80–85 from a high-quality original achieves that.
For absolute lossless compression with significant size reduction, convert to WebP — WebP supports true lossless encoding at file sizes 20–30% smaller than lossless PNG.
Can I compress multiple JPEG files at once?
Yes. Pixotter supports batch compression — drop any number of files, set your quality preference, and download everything at once. There's no file count limit.
If you're processing hundreds or thousands of images (e.g., a product catalog migration), a CLI approach with ImageMagick or a build tool integration is worth setting up. But for most web workflows, browser-based batch compression handles the job.
See our guide on how to reduce image size in bulk for batch workflow patterns.
Should I use JPEG or WebP for my website?
WebP is the better format for new websites. At equivalent visual quality, WebP files are 25–35% smaller than JPEG. Browser support sits above 97% as of 2026. There's no meaningful compatibility reason to prefer JPEG for web delivery.
Where JPEG still makes sense:
- Email attachments (WebP support in email clients is inconsistent)
- Print workflows (WebP isn't accepted by most print services)
- Legacy systems and platforms that haven't added WebP support
For a detailed breakdown, see Best Image Format for Web.
Is it safe to compress JPEG photos with personal content using an online tool?
With Pixotter, yes. Pixotter processes images entirely in your browser using WebAssembly — no file is ever uploaded to a server, and no data leaves your device. Your photos remain on your machine throughout the process.
Most other online compression tools upload your files to a remote server for processing. That's worth knowing before you compress photos that contain sensitive content, faces, or location data. If privacy matters, use a client-side tool or compress locally with a desktop application.
How It Works
Drag and drop one or more JPEG images. Batch processing handles up to 20 files at once.
Adjust the quality slider (1-100). For web use, 75-85 typically cuts file size by 60-80% with no visible difference.
Download individual files or grab them all as a ZIP. Use the before/after slider to verify quality.