How to Reduce Image File Size
Oversized images are one of the most common causes of slow page loads, email attachment failures, and CMS upload rejections. The good news: most images have a lot of room to get smaller without any visible quality loss. This guide walks through the process in order — tackling the biggest wins first, with free browser-based tools at each step.
Try the Image Optimizer free →
The problem
Images arrive oversized from cameras, design tools, and stock photo sites. A DSLR photo is typically 5000×3500 px and 8–15 MB. A screenshot might be 2880×1800 on a Retina display. Stock photos often come at maximum resolution "just in case." None of these need to be anywhere near that large for web use, email, or most CMS platforms — but they get uploaded as-is because there's no obvious step in the workflow that says "resize first."
The result: slow websites, rejected email attachments, and CMS platforms that hit their upload limits or quietly degrade your images server-side in ways you can't control. The solution is to take control of the optimization yourself before anything gets uploaded.
Step 1: Resize first
Resizing is almost always the highest-impact step. Most oversized images are simply too many pixels for how they'll actually be displayed. A 4000×3000 photo displayed at 800×600 on a webpage contains 25x more data than needed. No amount of compression makes up for carrying that many extra pixels.
The rule: resize to approximately 2x your display size. If an image appears at 800px wide on screen, 1600px wide source is enough for high-DPI (Retina) screens. Going beyond that wastes data with no visible benefit.
Use the Image Resizer to set exact pixel dimensions. It runs in your browser — no upload required.
Step 2: Choose the right format
The format you're using might be the wrong one for the job, and switching formats alone can cut file size significantly.
- Photos — JPG or WebP. Both are lossy formats designed for photographic content. PNG is the wrong choice for photos; it's lossless and will always produce larger files.
- Graphics, logos, illustrations with transparency — PNG or WebP. These need lossless compression to preserve sharp edges. JPG adds artifacts to hard lines and doesn't support transparency.
- Anything going on a website — WebP if browser support allows it. WebP is 25–35% smaller than JPG at equivalent quality, and supports transparency better than JPG.
Use the Image Format Converter to change formats, or read the WebP vs JPG comparison if you're unsure which to use.
Step 3: Compress
Once you have the right dimensions and format, compression is the next lever. For JPG and WebP, quality 75–85 is the practical sweet spot for most images. Below 70 you'll start seeing visible artifacts — blocky patterns in smooth gradients, rough edges on text. Above 90 the file sizes balloon with barely perceptible quality improvement.
For PNG, compression doesn't affect quality (PNG is lossless) — it only affects encode/decode speed. Most tools default to a reasonable level.
Use the Image Compressor to control quality level and preview the result before downloading.
Step 4: Convert to WebP
If the image is going on a website and you haven't already switched to WebP, this is an easy additional 25–35% saving on top of whatever you already achieved. WebP supports both lossy (for photos) and lossless (for graphics) compression, and handles transparency — so it covers almost every use case.
Use JPG to WebP for photos, or PNG to WebP for graphics and transparent images. Both run in your browser with no upload.
Quick reference: expected savings
| Technique | Typical savings | When to use |
|---|---|---|
| Resize dimensions | 60–95% | Image is larger than display size — do this first |
| JPG quality 85 → 75 | 30–50% | Photos; minimal visible quality difference |
| PNG → WebP lossless | ~26% | Graphics and icons with transparency |
| JPG → WebP lossy | 25–35% | Photos going on a website |
| Strip EXIF metadata | 5–20% | When location data and camera settings aren't needed |
| All steps combined | 80–97% | Maximum optimization before upload |
The "all combined" figure sounds dramatic but it's realistic for camera photos going to a website. A 10 MB RAW camera photo, resized to 1600px wide, compressed to quality 80, and converted to WebP can easily come out under 200 KB — a 98% reduction with no visible quality loss at web display sizes.
Built with vanilla HTML/JS. No frameworks, no backend, loads instantly.