Speed & performance · Guide
How to Fix "Properly Size Images" in WordPress
Short answer
To fix Properly size images in WordPress, serve each image at the size it is shown at, not at its full upload size. Pick the WordPress size that matches the display width, let srcset serve smaller files to phones, and re-run Lighthouse to confirm the warning is gone.
Key takeaways
- WordPress has added srcset and sizes to image markup since version 4.4, so the browser can pick a smaller file for a smaller screen.
- The default WordPress sizes are thumbnail at 150 by 150 pixels, medium up to 300 by 300 pixels, medium_large at 768 pixels wide, and large up to 1024 by 1024 pixels.
- Lighthouse fails the Properly size images audit when the rendered size is at least 4 KiB smaller than the actual image file.
- A 300 pixel wide slot needs a 600 pixel file on a 2x screen, because the file width is the display width times the pixel density.
- Changing a size in Settings then Media only affects new uploads, so older images need new files or regenerated sizes.
What does “properly size images” mean in WordPress?
A properly sized image is one whose file width matches the width at which it is shown, after allowing for the screen pixel density.
An image shown at 400 pixels wide does not need a 4000 pixel file. The extra pixels still download, even though the visitor never sees them at that size.
Web.dev puts the point plainly: an image that looks fine can still waste data and hurt page speed when it was never scaled down before upload.
WordPress adds to the problem when you pick Full Size for a small slot. The full file then travels to every visitor, including phones on slow connections.
How do you find the images that are too large?
Run Lighthouse on the page and open the Properly size images result, which lists each oversized image with its possible saving in KiB.
Open the page in Chrome, open DevTools, run the Lighthouse Performance audit, then look under Opportunities. Each listed image shows how much data a smaller file would save.
Chrome for Developers explains the rule: Lighthouse compares the rendered size with the actual size, counts the device pixel ratio, and fails the audit when the rendered size is at least 4 KiB smaller than the actual size.
That 4 KiB cut-off matters as of November 2026. A tiny gap is ignored, so you can focus on the images with real savings first.
Start with the largest saving on the page that carries the most traffic. Fixing one hero image often clears more bytes than fixing ten small icons. For a wider view of page weight, see how to fix Avoid enormous network payloads in WordPress.
What sizes does WordPress create when you upload an image?
WordPress saves the original file and creates smaller copies, so you can pick a copy that fits the slot instead of serving the original every time.
Learn WordPress states that an upload saves four versions: the original plus thumbnail, medium and large copies. Themes and plugins can add more sizes on top of those four.
The defaults, as of November 2026, are thumbnail at 150 by 150 pixels, medium up to 300 by 300 pixels, and large up to 1024 by 1024 pixels. Medium and large are maximums, so a photo keeps its shape inside those limits.
Learn WordPress gives two plain examples. A medium copy can be 300 by 200 pixels, and a large copy of the same photo can be 1024 by 683 pixels. The numbers change with the shape of the photo.
| WordPress size | Default limit | Typical use |
|---|---|---|
| Thumbnail | 150 by 150 pixels | Small squares, lists and avatars |
| Medium | Up to 300 by 300 pixels | Narrow columns and small cards |
| Medium_large | 768 pixels wide | A middle step for phones and tablets |
| Large | Up to 1024 by 1024 pixels | Wide article images |
| Full Size | Original upload | Only when the slot really needs it |
The medium_large size is 768 pixels wide with no height limit, according to WordPress Developer Resources. It is a middle candidate for responsive delivery, not a choice you pick by hand in most cases.
How do you work out the right width for each image?
Measure the slot in CSS pixels, then multiply by the pixel density you want to serve, so a 400 pixel slot needs an 800 pixel file on a 2x screen.
First, find the display width. In Chrome DevTools, select the image in the Elements panel and read its rendered size. That number is the slot width in CSS pixels.
Next, allow for sharp screens. A 2x screen packs 2 physical pixels into each CSS pixel, so it needs twice the file width to stay sharp. A 3x screen needs three times the width, but the gain is small for most photos.
Use this simple table as a starting point.
| Display width | File width for 1x | File width for 2x |
|---|---|---|
| 300 pixels | 300 pixels | 600 pixels |
| 400 pixels | 400 pixels | 800 pixels |
| 768 pixels | 768 pixels | 1536 pixels |
| 1024 pixels | 1024 pixels | 2048 pixels |
Cloudflare Images docs give the same maths in a different form: with a dpr value of 2, Cloudflare sends a 600 pixel image for a 300 pixel container. Its dpr setting tops out at 2, which fits the 2x target above.
Do not aim for 3x on every image. The file grows fast, and most visitors will not see the extra detail.
Fixing the main image on the page, often the largest contentful paint element, gives the clearest gain. See how to improve LCP in WordPress for that step.
How do you pick the right WordPress size in the editor?
Select the image block, open Resolution in the block settings, and pick the smallest size that is still at least as wide as the slot.
The Image block offers Resolution choices that may include Full Size, Large, Medium and Thumbnail, depending on your theme and the size of the uploaded image, according to WordPress.org documentation. Pick Large for a wide article image and Medium for a narrow column image.
Follow these steps for an image already in a post.
- Open the post in the block editor and click the image.
- Open the block settings on the right and find Resolution.
- Pick the smallest size that covers the slot width at 2x, using the table above.
- Save the post and view the live page.
- Check that the image still looks sharp on a phone and a desktop screen.
If the slot is 800 pixels wide on desktop, Large at 1024 pixels is a fair pick. If the slot is 300 pixels wide, Medium at 300 pixels is too small for a 2x phone, so Large is the safer pick there.
Do not drag the resize handles to shrink a Full Size image and leave it at that. The handles change how the image looks on the page, not which file the browser downloads. The file stays large unless you change the Resolution or replace the file.
How does srcset and sizes choose the file for each visitor?
WordPress adds srcset and sizes to the image markup, and the browser uses those two attributes to pick the smallest file that still looks sharp on that screen.
Since WordPress 4.4, native responsive images have been supported by adding srcset and sizes attributes to the image markup it generates, according to WordPress Developer Resources. You do not switch this on in Settings, because it works behind the scenes.
The srcset attribute lists the files WordPress made, each with its width in pixels. The sizes attribute tells the browser how wide the image will be shown at each screen width.
WordPress uses a default sizes value equal to (max-width: image-width) 100vw, image-width, as stated in the same developer handbook. In plain terms, the image fills the screen width up to its own width, then stays at that width.
As a guard, WordPress caps the largest file it offers in srcset at 2048 pixels by default, through the max_srcset_image_width filter. That cap stops a huge original from being offered as a responsive candidate.
Web.dev shows the same pattern in plain HTML: a srcset list of 300w, 600w and 1200w files, with a sizes list that gives 33vw on wide screens, 50vw in the middle, and 100vw on narrow screens. The browser picks from that list before layout is done.
Keep width and height on every image. Web.dev states that the browser uses those two numbers to work out the ratio and reserve the right space, which stops other content from jumping when the image loads. That jump is layout shift, covered in how to fix CLS in WordPress.
How do you resize an image before you upload it?
Resize the file to the largest width it will ever be shown at, times 2 for sharp screens, before you upload it to the Media Library.
Start with the slot width from the step above. A content image shown at 768 pixels wide needs a file no wider than 1536 pixels for 2x screens. A full-width hero shown at 1200 pixels wide needs a file no wider than 2400 pixels.
Use an image editor on your computer to resize the file, then save a fresh copy. Keep the original full-size file on your computer in case you need a larger crop later.
Web.dev suggests ImageMagick for this job and gives a plain command for scaling a file to fit within 200 pixels wide by 100 pixels tall. The same idea works at any size: set the target width, keep the shape, and save the result.
Upload the resized copy to WordPress, not the camera original. A phone photo can be 4000 pixels wide or more, and WordPress will still make smaller copies, but the original stays on your server and can still be picked by mistake.
Check the file size after resizing. A smaller pixel count should give a smaller file, and that is the saving Lighthouse reports. If the file is still large, compression is the next step, not a larger file.
How do you fix images you already uploaded?
Replace the oversized file with a resized copy, pick the right WordPress size in the editor, then regenerate thumbnails if you changed a size setting.
Work through the flagged images one page at a time, starting with the pages Lighthouse lists first.
- Open the page, note each flagged image and its display width.
- Resize a copy of each image on your computer to the target width from the table above.
- In the Media Library, replace the file or upload the resized copy and swap it into the post.
- Set Resolution to the smallest size that still covers the slot at 2x.
- Save, clear any page cache, then re-run Lighthouse.
If you changed the numbers in Settings then Media, remember that the change only affects new uploads. Older images keep their old files until you rebuild them.
A thumbnail regeneration plugin can rebuild the missing sizes for older uploads. Pick one from the WordPress.org plugin directory, run it on a few images first, and check the pages before you run it on the whole library.
For a full speed check after the image fixes, work through how to speed up WordPress.
For the wider Core Web Vitals picture, see how to pass Core Web Vitals in WordPress.
How do you check that the fix worked?
Re-run Lighthouse on the same page and confirm that the Properly size images item is gone, then check the image by eye on a phone and a desktop screen.
Run the same Lighthouse Performance audit you ran at the start, on the same page and the same device type. The audit should no longer list the images you fixed.
Web.dev gives the same advice in one line: once you have resized all your images, re-run Lighthouse to verify that you did not miss anything.
Check the live page in a browser, not only in the editor. Open it on a phone width and a desktop width, and look for blur, stretch or cropping. A sharp image at both widths means the file width and the slot width now match.
If Lighthouse still lists an image, read its saving in KiB. A small remaining saving may come from a theme image, a logo or a widget image that you have not resized yet. Fix those next, in order of saving size.
What mistakes should you avoid?
The most common mistake is shrinking the image on screen while leaving the Full Size file in place, because the browser still downloads the large file.
Avoid these traps.
- Picking Full Size for every image, even for a 300 pixel slot.
- Using CSS width alone to shrink a large file, with no change to the file itself.
- Uploading camera originals at 4000 pixels wide and letting the theme pick the size.
- Changing Settings then Media and expecting older images to change too.
- Serving a 1x file to a 2x phone and calling the blur a theme fault.
- Removing
widthandheightfrom the markup, which lets content jump as images load.
Each of these leaves the same warning in place. Fix the file, pick the size, then re-check with Lighthouse.
Frequently asked questions
What is a good target width for a WordPress featured image?
Use the widest slot where the image appears, times 2 for sharp screens. If the slot is 768 pixels wide, a 1536 pixel file covers 2x screens. If the slot is 1200 pixels wide, a 2400 pixel file covers it. Pick the WordPress size that meets that target, and check the image on a phone and a desktop screen before you move on.
Does WordPress resize images on its own?
Yes, in part. WordPress creates thumbnail, medium, medium_large and large copies when you upload an image, and it adds srcset and sizes so the browser can pick a smaller file. It does not resize the original file to match your slot, and it does not stop you picking Full Size for a small image. You still need to pick the right size.
Why does Lighthouse still flag an image after I resized it?
The live page may still serve the old file from cache, or the editor may still point at Full Size. Clear the page cache, check the Resolution setting on the image block, and view the page source to see which file is served. Then re-run Lighthouse on the same page. If the saving is under 4 KiB, Lighthouse will not flag it.
Should I serve a 3x file for the sharpest phones?
No, for most images. A 2x file is sharp on most high-density screens, and a 3x file adds a large amount of data for a small visible gain. Use 2x as your target for photos and hero images. Reserve larger files only for a full-width image where blur would be easy to see.
Do I need a plugin to fix properly size images?
No, not for most sites. WordPress already creates the smaller sizes and adds srcset and sizes. You can fix most warnings by resizing files before upload and picking the right Resolution in the editor. A regeneration plugin helps only when you changed size settings and need older images rebuilt.
Sources
- Serve images with correct dimensions web.dev
- Responsive images web.dev
- Responsive Images WordPress Developer Resources
- Properly size images Chrome for Developers
- Managing Settings: Media Learn WordPress
- Image block WordPress.org
- Image Optimization features Cloudflare Docs
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
