Reduce Image File Size: 8 Practical Ways

By SwiftPDF Team · Updated 2026-08-19 · 3 min read

A 12 MB phone photo attached to an email. A 4 MB hero image slowing a webpage to a crawl. An upload form rejecting your perfectly good picture. Image bloat is everywhere — and almost all of it is avoidable.

These eight techniques stack: apply them in order and you'll routinely cut image sizes by 80–95% with no visible difference.

1. Resize to the dimensions you need

The single biggest win. A 4000×3000 phone photo displayed at 800×600 carries 25x more pixels than necessary. Resize to the largest size it will actually be viewed at — 1920px wide is plenty for full-screen web use, 800px for in-content images.

Resizing is pure math: halving each dimension quarters the pixel count. No quality judgment required.

2. Dial quality to 80–85%

For JPG and WebP, the quality slider is the fidelity dial. 80–85% is the magic zone for photos: visually indistinguishable from 100% at a fraction of the size. Going from 100% to 85% often halves the file; going from 85% to 60% saves less and starts showing artifacts.

3. Choose the right format

Photos as PNG is the classic blunder — converting to JPG or WebP can cut 80% instantly. Screenshots of text should stay PNG (JPG smudges edges). For web, WebP beats JPG by another 25–35%. Match the format to the content before touching anything else.

4. Strip metadata

Phone photos carry EXIF data: GPS coordinates, camera settings, thumbnails. Stripping it saves tens of kilobytes and protects your privacy — most converters and 'save for web' exports do this automatically.

5. Crop ruthlessly

The pixels you delete are the cheapest bytes you'll ever save. Tighten compositions, remove dead space, and reconsider whether that 16:9 photo needs to be 16:9 at all.

6. Use progressive/interlaced encoding for web

Progressive JPGs and interlaced PNGs render in stages — blurry-to-sharp — which feels faster on slow connections and is marginally smaller. Most export tools offer it as a checkbox.

7. Consider AVIF for maximum squeeze

When every kilobyte counts, AVIF compresses better than anything else mainstream. Encoding is slower and support slightly patchier than WebP, so reserve it for hero images and bandwidth-critical pages.

8. Know your targets

• Web content images: under 200 KB each, hero images under 500 KB
• Email attachments: total under 10 MB to be safe
• Social uploads: platforms recompress anyway — send good quality and let them handle it
• Print: don't downsize aggressively; 300 DPI at final print size is the floor

Automating it for teams

If image optimization is a recurring team task rather than a one-off, stop doing it by hand. Build it into the pipeline: CMS plugins that compress on upload, build scripts running sharp or ImageMagick, or a shared export preset in your design tool with the right dimensions, format and quality baked in.

Set a team standard and write it down — 'content images max 1600px wide, WebP at 82%' — so nobody has to make the decision per image. Consistency beats perfection here; a good default applied everywhere outperforms heroic optimization applied sometimes.

Related guides

Frequently asked questions