How to Compress Images for WordPress (Faster Site)
13 June 2026
👉 Just need the tool? Convert JPG to WebP — runs in your browser, nothing uploaded.
Large, unoptimized images are one of the most common reasons WordPress sites feel slow. A single photo straight off a phone or camera can weigh several megabytes and be thousands of pixels wide, even though your theme may only ever display it at 800 pixels. The browser still downloads every one of those bytes. The good news: fixing this is mostly mechanical, and the biggest wins come from preparing images before they ever reach your media library.
Why upload-ready images beat plugins
WordPress automatically generates smaller “thumbnail” sizes, and optimization plugins can compress files for you on the server. Those tools help, but they have limits. A plugin still keeps your giant original around, the auto-generated sizes are often larger than they need to be, and server-side compression can tax your hosting or count against plan limits.
When you optimize first, you control exactly what gets stored. You upload a file that is already the right dimensions, already in an efficient format, and already compressed. Every copy WordPress derives from it starts from that smaller baseline. Fewer bytes in means fewer bytes out to every visitor.
Step 1: Resize to the size it will actually display
This is the step people skip, and it is usually the most impactful. Figure out the widest your image will ever appear:
- Full-width hero or featured image: around 1600–2000 px wide is plenty for most layouts, even on large screens.
- In-content images: typically your content column width, often 800–1200 px.
- Sidebar or thumbnail: a few hundred pixels.
Most modern themes serve different sizes to different screens using srcset, but you still want a sensible maximum. There is almost never a reason to upload a 6000 px file. Resizing it down to 1600 px can cut the file size dramatically before you have even compressed it, because you are literally discarding pixels nobody sees.
Step 2: Choose the right format
Format matters as much as dimensions.
- WebP is the practical default for the web today. It typically produces smaller files than JPEG at similar visual quality, it is supported by every current major browser, and it handles both photographs and graphics with transparency.
- JPEG remains a safe, universal choice for photographs when you want maximum compatibility or your workflow depends on it.
- PNG is best reserved for graphics that need crisp edges or transparency, such as logos, icons, and screenshots of text. It produces very large files for photographs, so avoid it there.
For most WordPress content, converting photos to WebP is the single easiest format change. WordPress has supported WebP uploads natively since version 5.8, so it should drop in without trouble on an up-to-date install. To convert in seconds, use Convert JPG to WebP and download a ready-to-upload file.
A note on AVIF: it can compress even more than WebP, and WordPress added native support in version 6.5. Browser support is strong but slightly less universal than WebP, so if you use AVIF it is worth confirming it behaves the way you expect on your site.
Step 3: Compress to a sensible quality
Compression trades a small amount of visual fidelity for a large drop in file size. For most photos, a quality setting around 75–85% is a good starting point: the file shrinks significantly while the difference is hard to spot at normal viewing sizes. Lower it further for background or decorative images; keep it higher for product shots or anything where detail matters.
The right setting depends on the image, so trust your eyes. Compress, view the result at the size it will actually display, and adjust if you notice blockiness or smearing. Keeping in-content images under a few hundred kilobytes is a reasonable target for most sites.
Because conversion runs entirely in your browser on SnapConvert, your images are never uploaded to a server while you work, which is useful peace of mind when handling client photos or anything you would rather not send across the internet just to shrink it.
A repeatable workflow
Put together, the routine is short:
- Resize the image to its maximum display width.
- Convert to WebP, or keep JPEG for photos where you need it.
- Compress to around 75–85% quality and check the result.
- Upload the finished file to WordPress.
After a few rounds you will know your common sizes by heart, and each image takes under a minute. You can run every step with the free tools in your browser.
The practical takeaway: the fastest image is the one that was already small before it reached WordPress. Resize to display size, convert to WebP, compress to taste, and upload that. Your pages will load lighter without you touching a single server setting.