Manage WordPress Image Sizes and Reclaim Disk Space

WordPress makes 7–12 resized copies of every image you upload, most never used. Disable the dead sizes, delete the orphaned files and reclaim disk space.

Upload one 3 MB photo to WordPress and you don’t get one file—you get seven, eight, sometimes a dozen. Thumbnail, medium, medium-large, large, the two larger sizes WordPress 5.3 added for high-density screens (1536 and 2048 pixels), a scaled copy, plus whatever your theme and plugins decided to register. Now multiply that by every image you’ve ever uploaded. On sites I’ve cleaned up, unused image sizes were quietly eating gigabytes—storage spent generating crops that nothing on the site ever displayed. Here’s how to take back control of what WordPress makes, and delete what it already made for nothing.

The essentials

  • WordPress core registers six sizes per upload (thumbnail, medium, medium_large, large, 1536x1536, 2048x2048), plus a scaled copy—your theme and plugins add more.
  • The module lists every registered size (core, theme, plugins) and lets you switch off the ones you never display.
  • Register custom sizes (width, height, crop) that also show up in the editor’s image dropdown.
  • Regenerate existing thumbnails per image, for a selection, or for the whole library one image per request so the server doesn’t time out.
  • Delete orphaned files from disabled sizes to reclaim space, and cap or disable WordPress’s 2560px auto-scaling.

How many image sizes is your site really generating?

More than you think: WordPress core registers six sizes per upload, your theme often adds two or three, WooCommerce brings its own, and some themes register ten or more. It’s entirely normal to find 12+ copies of every single image in wp-content/uploads, most of them for sizes no template on your site ever calls.

Want the real number? Open your uploads folder and count the files generated from any one photo. Multiply that by your media library size and you have a rough measure of the waste.

Here’s where each copy comes from and how to decide whether it earns its place on disk:

Image sizeWhere it comes fromWhen it’s actually usedKeep or cut?
Thumbnail, medium, largeWordPress coreWherever your theme inserts those sizesKeep the ones your pages display
Medium_large, 1536x1536, 2048x2048WordPress core (4.4 and 5.3)Offered to the browser so it picks the best file for each screen width and pixel density (srcset)Keep unless your theme never outputs responsive images
-scaled copy (longer side over 2560px)WordPress core (since 5.3)Caps oversized uploads inside contentCap or disable for print/hi-res work
Theme sizesYour active themeDepends on the templateCut the ones no template calls
WooCommerce / plugin sizesInstalled pluginsOnly if that plugin displays themCut when the plugin doesn’t need them
Custom size you registerYou, in the moduleInserted from the editor dropdownAdd only the ones you’ll use

The three “extra” core sizes aren’t dead weight by default: WordPress added medium_large in 4.4 for responsive images and the 1536 and 2048 sizes in 5.3 for high-density displays. Cut them and the browser has fewer files to choose from, so a phone downloads a larger image than it needs, or a retina screen gets a softer one.

How do you manage WordPress image sizes?

Enable the Image Sizes module and it lists every registered size with its likely source—core, theme or plugin—so you’re deciding with context. From there you disable the sizes nothing displays, register custom ones, regenerate existing thumbnails one image per request, delete the orphaned files left behind, and cap WordPress’s 2560px auto-scaling. Disk space comes back as the dead sizes go.

Activate the Image Sizes module in Blaminhor Essentials. Its settings list every registered size, labelled with a best-guess source—WordPress Core, Theme, Plugin or Custom—so you can see the full picture before changing anything.

Illustration: stacked orange rectangles of decreasing size, with folders, refresh arrows and small percentage tags around them. One image, many copies. In the module itself, every registered size is listed with its dimensions and where it’s registered—so you disable the dead weight with context, not guesswork.

Disable the sizes you don’t use

Switch a size to Disabled and WordPress stops generating it for new uploads. If nothing on your site ever displays a theme’s leftover slider or portfolio-thumb size, there’s no reason to keep creating it on every upload. Your originals and the sizes you keep are unaffected. Leave the three core responsive sizes alone unless you’ve checked how your theme outputs images.

Register custom sizes

Need a 600×400 cropped size for your blog cards? Add it right from the settings page with exact width, height and crop behaviour—and it also appears in the editor’s image-size dropdown, so you can actually insert it into content, not just register it in the background.

Regenerate existing thumbnails

Changing your size settings only affects future uploads, so regenerate the ones you already have to match. You can regenerate a single image from a row action in the Media Library, select many and use the bulk “Regenerate thumbnails” action, or run the module’s Regenerate Thumbnails tab for the whole library—it processes one image per request so a big library doesn’t hit a PHP timeout. Regenerating also removes the files of sizes you’ve since disabled—except any thumbnail still inserted in your content, which it keeps.

Clean up the orphaned files

This is where the disk space comes back. For the disabled sizes you select, the module goes through every image’s metadata and deletes those thumbnails, keeping any that is still inserted in a post’s content or in a page builder’s layout (Elementor, Beaver Builder, Oxygen, Bricks). It doesn’t see a theme’s featured-image display, widgets or custom fields such as ACF—so if those use a size you’ve disabled, check the pages yourself before cleaning up. On a site with thousands of images and a handful of unused sizes, that can reclaim a lot of space.

Control WordPress’s big-image scaling

Since WordPress 5.3, any image whose longer side exceeds 2560px is automatically shrunk and a -scaled copy replaces your original in content (the full-size original stays on disk). That’s sensible for most sites, but not if you upload print-ready or high-resolution photography. The module lets you turn that scaling off entirely—or, better, set your own maximum dimension instead of the fixed 2560px, so you keep control of quality without storing needlessly huge files.

How much disk space can you reclaim?

On a typical site with 1,000 images and four unused sizes, you’re storing up to 4,000 needless files—fewer if some uploads were too small for every size to be generated. Clearing them frees disk space, shrinks your backups, and speeds up any migration or restore; the benefit compounds every time the site is copied or archived.

Image Sizes pairs naturally with a database cleanup—together they trim the two things that bloat a WordPress site most: its media folder and its database.

Image Sizes is one of the 26 modules in Blaminhor Essentials—free and open-source on WordPress.org.

Download Blaminhor Essentials

– blaminhor

FAQ

Does disabling image sizes break responsive images (srcset)?

Not if you keep the sizes your theme actually uses. WordPress builds the srcset attribute from the sizes registered for an image, so disable only the ones nothing displays. The sizes you keep still populate srcset normally, and responsive images carry on serving the right file to each screen width.

Do lots of image sizes slow down my site?

Not the page a visitor loads directly—only the sizes your templates call actually get served. The real cost is generation and storage: every upload spends CPU making copies you never show, and they bloat your uploads folder, your backups and every migration. Cutting the dead sizes speeds all of that up.

Which image sizes should I keep and which are safe to delete?

Keep the sizes your active theme and pages display, and keep the core responsive sizes (medium_large, 1536x1536, 2048x2048) too: the browser picks among them for each screen width and pixel density. Safe to cut: theme or plugin sizes no template calls. When unsure, disable one size, check your pages still look right, then delete its orphaned files.

Will deleting sizes affect already-published posts?

Deleting a size's files only removes those specific crops; your originals and the sizes you kept stay intact. The cleanup keeps any thumbnail a published post still uses, so those posts are unaffected. Regenerate thumbnails first if you've changed dimensions, then spot-check a few older posts still display correctly.

Is it safe to disable WordPress image sizes?

Yes, as long as you only disable sizes nothing on your site actually displays. Disabling a size just stops WordPress generating it for new uploads; your originals and the sizes you keep are untouched. If you're unsure, disable one size, check your pages still look right, then clean up its old files.

How do I free disk space from unused image sizes?

Disable the sizes you don't use so WordPress stops creating them, then run the cleanup that deletes the orphaned files already on disk for those sizes. On a site with thousands of images and several unused sizes, that can reclaim gigabytes and makes every backup and migration faster.

What is the '-scaled' image in WordPress?

Since WordPress 5.3, any image whose longer side exceeds 2560 pixels is automatically shrunk and a '-scaled' copy replaces the original in your content; the full-size original stays on disk. If you upload print-ready or high-resolution photography you may want the full original kept, or a different cap. The Image Sizes module lets you turn scaling off or set your own maximum dimension.

blaminhor Building what's missing.

Comments