WordPress Image Size Lab
Drop an image in. See every copy WordPress will make of it.
Runs in your browser. Nothing is uploaded.
Drop an image here
or click to choose one
Your file is read in your browser and never uploaded. We set no file size limit and no daily quota, because there is no server to pay for. A very large image can still be more than your browser can handle.
About the WordPress Image Size Lab
See the exact files WordPress makes from your image: every size, the crop it applies, the -scaled copy and the file count, worked out in your browser.
The lab works out every file WordPress would write for your image with its default sizes, or with WooCommerce's three sizes added: which sizes it makes, which it skips because the image is too small, where a crop cuts, and whether a -scaled copy is added. The sizing runs in your browser, and your image is not uploaded anywhere.
Worked example: a 3000 × 4000 portrait photo
Input
A JPEG photo, 3000 x 4000 px (portrait)
Default WordPress sizes, no plugins What the lab shows, shortened (file sizes and the per-size notes left out)
WordPress will not serve this image. It will serve a smaller copy.
WordPress will write 6 new files
thumbnail 150 × 150 hard crop · 25% of your image is thrown away
medium 225 × 300
medium_large 768 × 1024
large 768 × 1024 Same dimensions as medium_large, so WordPress writes one file for both.
1536x1536 1152 × 1536
2048x2048 1536 × 2048
-scaled 1920 × 2560 - thumbnail is the only default size that crops. To make a 150 × 150 square from a 3000 × 4000 photo, WordPress keeps the middle 3000 × 3000 and cuts 500 px from the top and the bottom, so a head near the top edge can be lost. That is the 25% the lab reports.
- medium, large, 1536x1536 and 2048x2048 are boxes: the image shrinks until it fits inside, keeping its shape. A portrait therefore comes out 225 × 300 in the 300 × 300 medium box. The WordPress image sizes cheat sheet lists every default size with its box and crop setting.
- medium_large is 768 px wide with no height limit, so it is 768 × 1024 here. The large box (1024 × 1024) gives the same 768 × 1024, so WordPress writes one file for both sizes, and the lab counts 6 new files for 7 entries. When we uploaded this size of photo to WordPress 7.1.4 (PHP 8.3, GD, WordPress Playground, 2026-11-16), both sizes pointed at the same file name, and the upload left 7 files on disk: these 6 and the original.
- The longest edge, 4000 px, is over 2560, so WordPress adds a -scaled copy that fits inside 2560 × 2560 and serves it whenever a page asks for the full size. The original stays on disk, and the other sizes are made from it. The -scaled image checker shows how to raise or remove that limit.
When to use it
- Before you remove sizes to save disk space, to see which files your uploads really get and which sizes end up sharing one file.
- When a thumbnail cuts off part of a photo, to see exactly which part the centre crop keeps.
- When an image looks soft on the page, to check whether a -scaled copy is what the page is showing.
Sizes WordPress skips
WordPress does not enlarge images. A size is skipped when the image already fits inside that size's box, and also when the result would be within 1 px of the original on both sides. In our test uploads (WordPress 7.1.4, PHP 8.3 and GD in WordPress Playground, 2026-11-16) a 301 × 200 upload got no medium file for the second reason, and a 769 × 500 upload got no medium_large. An image that is too small on one side only still gets the size: a 2000 × 120 upload got a 300 × 18 medium. A narrow image is cropped on one side only: a 120 × 400 upload got a 120 × 150 thumbnail. The lab marks each skipped size and says why.
The code it gives you
The PHP panel writes code for the two options you can tick: a filter on intermediate_image_sizes that stops the 1536x1536 and 2048x2048 sizes, and a big_image_size_threshold filter that turns the -scaled copy off. Paste it into a child theme's functions.php or a small plugin. Both only change uploads made after the code is active. For an image that already has a -scaled copy, upload it again; regenerating thumbnails did not remove the copy in our 2026-11-06 test (WordPress 7.1.4 with WP-CLI 2.12.0 and Regenerate Thumbnails 3.1.6).
Sources
- WordPress Code Reference: add_image_size()
- WordPress Code Reference: image_resize_dimensions()
- WordPress Code Reference: wp_create_image_subsizes()
- WordPress Code Reference: big_image_size_threshold hook
- WordPress Code Reference: intermediate_image_sizes hook
- WordPress Code Reference: WP_Image_Editor::get_default_quality()
Limits
- The file sizes are your browser's own encoding. WordPress uses GD or Imagick on your server, at quality 82 for JPEG and 86 for WebP by default, so real files will differ.
- The dimensions were checked against WordPress 7.1.4 with GD. We did not test Imagick, or the browser-side image processing that WordPress 7.1 uses for uploads made in the block editor on HTTPS sites and on localhost.
- Plugins and themes that register their own sizes or filter the size list change the result. The lab includes WooCommerce's default sizes as an option, but it cannot see your site.
- Crops are centred, which is what WordPress does for the thumbnail. A focal-point plugin, or a size a theme registers with another crop position, would cut differently.
Guides for this tool
- WordPress Thumbnail Sizes: Why One Photo Becomes 8 Files
WordPress turns one large photo into up to 8 files: the original, a -scaled copy and 6 sizes. We tested 28 popular themes, WooCommerce and Elementor.
- WooCommerce Product Image Size: Defaults and How to Change
WooCommerce product image sizes: the three defaults, where to change them, why catalog thumbnails crop badly, and how to regenerate old product images safely.
- Why WordPress Adds -scaled to Images and How to Stop It
WordPress adds -scaled to uploads over 2560px. Raise or turn off big_image_size_threshold, then regenerate or re-upload. Measured on WordPress 7.1.4.
- Stop WordPress Compressing Your Images at 82%
Raise the WordPress JPEG quality default of 82 with one filter, regenerate the thumbnails already stuck at 82, and know when PNG is the better fix.
- Why Your WordPress Uploads Folder Is So Large
Your WordPress uploads folder is too large because one big photo becomes up to 8 files, plus theme sizes. Deregister unused sizes, then regenerate.
- WordPress Featured Image Size: 1200×630 + How to Find Yours
WordPress featured image size: 1200×630 px suits link previews, but your theme may crop it. Find the size your theme displays and upload at 2× its width.
- Why WordPress Images Look Blurry After Upload, and the Fix
Blurry after upload? Check whether WordPress capped the file at 2560px or served a too-small size, then fix it. Includes a regenerate test on WordPress 7.1.4.
Reference
- WordPress Image Sizes Cheat Sheet
Every size WordPress registers, what crops, and what to actually upload
Related
Other tools you might need
FAQ
Questions
What image sizes does WordPress actually create?
On a default install, six sizes: thumbnail (150 × 150, cropped), medium (fits in 300 × 300), medium_large (768 px wide), large (fits in 1024 × 1024), 1536x1536 and 2048x2048. An upload over 2560 px also gets a -scaled copy, and sizes bigger than the image are skipped. Themes and plugins can register more; WooCommerce 11.2.2 adds three.
Why is my image blurry after uploading to WordPress?
A common cause is the -scaled copy. Since WordPress 5.3, an upload wider or taller than 2560 px gets a copy that fits inside 2560 × 2560, and WordPress serves it whenever a page asks for the full-size image. The original stays on the server, and WordPress makes the other sizes from it. A page can also look soft when the theme shows a size smaller than the space it fills. Drop your image into the lab to see which files it gets.
Are the file sizes this tool shows accurate?
The dimensions and crops follow WordPress 7.1.4's own rules: the lab uses a port of WordPress's resize code, and it matched 15 test uploads on WordPress 7.1.4 with PHP 8.3 and GD (WordPress Playground, 2026-11-16). The file sizes are estimates, because your browser does not use the same encoder as your server. WordPress uses GD or Imagick and saves JPEGs at quality 82 by default.