To compress images for WordPress, resize each photo so its longest side is 1600-2000 px before you upload it, then save it as WebP or JPEG at about 80% quality. That typically brings a phone photo down to somewhere between 150 KB and 500 KB, from 1.5 MB or more. Do those two things and you've fixed the problem behind most slow WordPress sites. The rest of this guide is the why, the edge cases, and what to do about the images you've already uploaded.
I'd resize first, every time. WordPress does some quiet things to oversized uploads that most people never notice, and none of them make the file small.
Compress your images → — runs in your browser, no upload.
WordPress image sizes at a glance (2026)
| Setting | What WordPress does |
|---|---|
| Scaling threshold | Uploads wider or taller than 2560 px get a scaled copy, used as the "full" size |
| Default generated sizes | Thumbnail 150 x 150, medium up to 300 x 300, medium_large 768 wide, large up to 1024 x 1024 |
| Upload limit | Set by your host's PHP config, the smaller of upload_max_filesize and post_max_size |
| WebP uploads | Supported since WordPress 5.8, if the host's image library supports it |
| AVIF uploads | Supported since WordPress 6.5, same host caveat |
| Our recommended upload | 1600-2000 px on the long edge, WebP or JPEG at 80%, typically 150-500 KB |
Sources: Make WordPress Core — Introducing handling of big images in WordPress 5.3, WordPress Theme Handbook — Featured Images & Post Thumbnails, WordPress developer reference — wp_max_upload_size()
The 2560px rule, and the -scaled files in your library
Open your Media Library and look at the filenames. If some end in -scaled.jpg, WordPress has been quietly resizing your uploads. Since version 5.3, every new image gets checked, and if its width or height is over 2560 px WordPress makes a smaller copy with a -scaled suffix. Your theme treats that copy as the full-size image. The original stays on the server, untouched, but nobody ever sees it.
Think of it like handing a poster to a print shop that only stocks one small paper size. They'll shrink it to fit, and they'll keep your original in a drawer, but the shrunk version is what goes on the wall.
So the 4032 px photo straight off your phone gets cut down to 2560 px no matter what. You paid the upload time, the storage and the server work for pixels that go in the drawer.
But here's the catch. 2560 px is where WordPress stops you, not where your images should be. A 2560 px copy, re-saved by your server, is still a heavy file. It can easily run past a megabyte. In our Resize tool tests a 2048 px copy of a phone photo at 92% quality was already 1.10 MB, and 2560 px is bigger again. If your theme shows the full-size image in a post (plenty do), that's what every visitor downloads. The fix is to upload something sensible so WordPress has nothing to scale.
If you'd rather WordPress didn't touch big uploads at all, the same announcement describes a big_image_size_threshold filter that changes or disables the limit. Honestly, I'd leave it alone. The threshold is a safety net. The real win is never hitting it.
What size should you upload?
Decide by where the image will appear, not by what the camera produced.
A blog post's content column is narrower than a laptop screen. Even a full-width hero on a 1920 px monitor needs 1920 px at most. So 1600-2000 px on the long edge covers any normal layout, including sharp high-density screens like a Retina display, and it stays under the 2560 px line on both sides whether the photo is wide or tall.
Here's what that does to file size. We ran an ordinary 12-megapixel phone photo (3024 x 4032 px, 1.62 MB JPEG) through our own Compress tool, using the same browser encoder the page uses:
Look at the first bar. Dropping the quality to 80% without touching the dimensions barely moved the file (1.62 MB to 1.61 MB). A phone photo is already a compressed JPEG, so re-saving it at a similar quality just re-saves the same information. The dimensions did the real work on this photo: 2000 px wide cut it by 70%, and 1200 px wide by 89%. Two more phone photos we tested lost 65-69% at 2000 px wide, so the pattern holds, even if the exact numbers move around.
One wrinkle worth spelling out, because it's the whole 2560 rule in miniature. That test photo is portrait. "2000 px wide" means 2000 x 2667, and 2667 is over 2560, so WordPress would still make a -scaled copy of it. For a portrait photo, set the height to 2000 instead. You get 1500 x 2000, which should come out smaller than 491 KB, and nothing for WordPress to do.
Resize first. Compress second. That's the lesson.
How to compress images for WordPress: the two-step workflow
- Resize so the long edge is 1600-2000 px. Open the Compress tool and drop the photo in. With the lock on, type the long side into the W box for a wide photo or the H box for a tall one. 2000 px is the safe default for a full-width hero or anything you want sharp on a high-density screen. 1600 px is plenty for a photo sitting inside a text column. If you only want the dimensions changed, the Resize tool does the same job at a fixed 92% quality.
- Pick the format and quality. Leave quality at the 80% default. Choose WebP if your host supports it (more on that below), JPEG if you're not sure. Check the compare view at 100% on a face or some text, then download.
Then look at the number under the preview. For a 2000 px photo you're expecting a few hundred kilobytes. If it's still over a megabyte, the photo has a lot of fine detail, so try 70%. Below that, check the compare view carefully before you commit.
Everything here happens in your browser. Nothing is uploaded to us, so a draft post with unreleased product shots, or a client's site you're building, stays on your machine until you upload it to WordPress yourself.
WebP, JPEG or PNG?
WebP, for almost everything. WordPress has accepted WebP uploads since version 5.8, as long as your hosting service's image library supports it. Google's own compression study found lossy WebP files 25 to 34% smaller than JPEGs at the same measured quality. Our single-photo test landed at 36%, a touch above that range, because we held the quality setting fixed rather than matching visual quality. Call it a quarter to a third off a typical photo, for free.
The one thing to check first is your host. Go to Tools, then Site Health, then the Info tab, and open Media Handling. If WebP isn't listed under supported formats, the upload will fail with an error. Upload JPEG instead, or ask your host to update their image library. And if you've got a pile of PNG or HEIC files from a phone or a designer, the image converter will switch them to WebP in the browser before you resize. Our WebP conversion guide has the fiddly details.
JPEG hasn't gone anywhere. A JPEG at 80% is a perfectly good blog photo, and every host supports it. On a shared host with an old image library, it's the no-drama choice.
What about PNG? Keep it for screenshots and logos. PNG is lossless, so the quality slider does nothing to it, and a photograph saved as PNG is enormous for no visible gain. Even for a screenshot, WebP usually wins: in our Compress tool tests a 62 KB screenshot came out at 25 KB as WebP at 80%. The only time I'd upload PNG is when I need a lossless file that some old tool has to open later.
AVIF is the newer option. WordPress added AVIF uploads in version 6.5, and in our format comparison it comes out smaller than WebP. But it depends on the same host-side support, and the WordPress team's own announcement points you to that Site Health page to confirm your server can handle it. If Media Handling lists AVIF, go for it. If not, WebP is the practical choice today. That comparison post covers when AVIF is worth the hassle.
Already have a library full of big images?
A browser tool fixes what you upload from now on. It can't reach into the 2,000 photos already sitting on your server, and I'm not going to pretend otherwise.
For an existing library, an image optimization plugin is the right tool. It can work through the whole library for you. The two jobs fit together: let a plugin clean up the backlog once, then resize new uploads yourself so the backlog never comes back.
Two more things for a cleanup. If you change the sizes under Settings, then Media, WordPress only applies them to new uploads, so you'd need to regenerate thumbnails for the old ones. And the biggest single win in most libraries is the featured image on your most-visited posts. Start there, by hand, with the two-step workflow above. Ten minutes on your ten busiest posts beats a week of background processing.
Why this matters for your Google rankings
Google's Core Web Vitals score the real loading experience of your pages, and the metric images affect most is Largest Contentful Paint. That's the time until the biggest visible thing on the page has rendered. Google's "good" threshold is 2.5 seconds or less at the 75th percentile of page loads, which means three out of four visits have to hit it.
And what's the biggest visible thing on most pages? An image. The 2025 Web Almanac found that an image is the LCP element on 76% of mobile pages. On a typical WordPress post that's your featured image or the first photo in the article. If it's a 1.6 MB upload, your LCP is in trouble before the rest of the page gets a say.
Shrinking that one image is the highest-return minute you can spend on site speed. Our guide to optimizing images for web speed covers the rest: lazy loading, srcset, and what a caching plugin can and can't do for you.
Hitting a specific file size
Sometimes you need a hard number rather than "a few hundred KB." A theme that chokes on featured images over 500 KB. A membership plugin with a 1 MB avatar cap. A host with a small upload limit you can't change.
The order of operations is the same: reduce the long edge first, switch to WebP second, drop the quality third. For a 100 KB target, start at 1200 px. Across three phone photos in our Compress tool measurements, 1200 px wide at 80% gave 159 to 231 KB. To get under 100 KB, go narrower (800-1000 px), lower the quality, or both, and watch the size readout until it drops below your target. The compress to a target size guide lists what each common cap looks like in practice.
On the upload limit itself: WordPress doesn't set it. Your host's PHP settings do, and the effective cap is whichever is smaller of two values, upload_max_filesize and post_max_size. If a photo is over the limit, don't fight PHP. Resize the photo.
Mistakes that keep WordPress sites slow
- Uploading straight from the phone. A 12-megapixel photo is about 3000 x 4000 px and typically 1.5-2 MB or more. WordPress scales it to 2560 px and still serves a big file.
- Lowering quality instead of size. Quality alone barely dents an already-compressed phone photo. The long edge is the lever.
- Letting a plugin do all the thinking. A plugin can only work with what you gave it. Upload sensibly and it has less to do.
- Saving photos as PNG. Lossless doesn't mean sharper. For a photograph it just means huge.
- Shrinking everything to 800 px to be safe. It'll look soft on today's high-density phone and laptop screens. Stay at 1600 px or more for anything you want to look sharp.
- Uploading WebP without checking the host. The upload fails with an unhelpful error. Check Site Health first.
The Bottom Line
To compress images for WordPress well, forget plugins and settings for a moment. What matters is what you upload. Resize every photo so its long edge is 1600-2000 px and save it as WebP or JPEG at around 80% quality. You'll typically land at a few hundred kilobytes per image, under the 2560 px scaling limit on both sides and small enough to keep your Largest Contentful Paint in the green. Do it before upload and WordPress has nothing left to fix.
Compress your WordPress images → — everything happens in your browser, so your photos never leave your device.
