Short answer, from a measurement and not a guess: in a plain WordPress, 1.75× the photos you upload. We uploaded 5 phone-sized photos, 8.7 MB in total, and WordPress wrote 39 files taking 15.3 MB to wp-content/uploads.
The surprise is where the extra goes: 84% of it comes from just three large copies of each photo. The thumbnails people worry about are almost nothing.
When you upload an image, WordPress keeps your file and then writes smaller copies of it, one per registered image size. With no plugins and the default theme, there are six sizes. And if the photo is wider or taller than 2560 pixels, WordPress also writes a -scaled copy, 2560 pixels on its longest side, and uses that as the "full size" image on your pages. Your original stays on disk next to it.
Here is every file, added up over the five photos. The copies are JPEG, like the photos we uploaded.
| File | Size in pixels | Total for 5 photos |
|---|---|---|
| Your original | as uploaded | 8.7 MB |
-scaled | 2560 longest side | 2.2 MB |
2048x2048 | 2048 longest side | 2.1 MB |
1536x1536 | 1536 longest side | 1.2 MB |
large | 1024 longest side | 587 KB |
medium_large | 768 wide | 346 KB |
medium | 300 longest side | 70 KB |
thumbnail | 150×150, cropped | 38 KB |
| All files | 15.3 MB |
The copies add 6.6 MB on top of the originals. The -scaled, 2048x2048 and 1536x1536 files are 84% of that. They exist so that large and high-density screens get a sharp image through srcset, which is a fair reason, but it is worth knowing they are the bill.
| Photo | Pixels | Original | Files in WordPress | On disk |
|---|---|---|---|---|
| Cat | 4000×2667 | 1.6 MB | 8 | 2.8 MB |
| Forest | 2560×1705 | 1.4 MB | 7 | 2.8 MB |
| Mountain | 4000×2383 | 1.5 MB | 8 | 2.7 MB |
| Valley | 4000×2670 | 1.8 MB | 8 | 3.1 MB |
| Milky Way | 4000×2669 | 2.4 MB | 8 | 3.9 MB |
The forest photo is exactly 2560 pixels wide, so WordPress didn't make a -scaled copy of it: one file fewer. It still ended up as large on disk as the cat, because its detailed texture makes every copy heavier.
GD or Imagick barely matters. WordPress uses one of two image libraries, depending on what your hosting has installed. We ran the test with both: 15.3 MB with Imagick (1.75×), 15.7 MB with GD (1.80×).
Our photos are not your photos, and your theme and plugins may add sizes of their own: each one is another file for every image you upload. To see your real numbers:
wp-content/uploads folder. Over SSH: du -sh wp-content/uploads.find wp-content/uploads -type f | wc -l, then divide by the number of items in your Media Library.wp media image-size lists every registered size.Three things move the number, each with a cost:
-scaled copy, and your original stops being several megabytes of pixels nobody sees.intermediate_image_sizes_advanced filter can stop WordPress from making the 1536x1536 and 2048x2048 copies. Large and high-density screens then get a smaller image, or the full one.-scaled copy. Returning false from the big_image_size_threshold filter does it, and then your full original becomes the "full size" image served on your pages.None of these touches images you already uploaded, and none changes the format: the copies stay JPEG.
We sent the same five photos to Easydoor, on the same day. It keeps your original as you uploaded it and makes five WebP versions in the WordPress sizes (a 150×150 cropped thumbnail, and 300, 768, 1024 and 2560 pixels), then the same sizes in AVIF, a newer format, about a minute later. It doesn't make the 1536 and 2048 copies, and never enlarges an image.
The honest result: Easydoor stores about the same amount. 53 files and 14.5 MB, or 1.66× the photos, against 15.3 MB in WordPress: −5%. It skips two large copies but keeps every size in two formats, and those roughly cancel out. All of it counts toward your Easydoor space (why used space is larger).
What changes is where it lives and what your visitors download:
| Size | WordPress JPEG | Easydoor WebP | Easydoor AVIF |
|---|---|---|---|
thumbnail | 38 KB | 26 KB (−31%) | 28 KB (−25%) |
medium | 70 KB | 57 KB (−19%) | 61 KB (−13%) |
medium_large | 346 KB | 323 KB (−7%) | 345 KB (0%) |
large | 587 KB | 553 KB (−6%) | 592 KB (+1%) |
| 2560 px | 2.2 MB | 1.9 MB (−15%) | 2.0 MB (−11%) |
The gain is biggest in small images and modest in the 768 and 1024 sizes that pages show most. Added up, AVIF came out heavier than WebP at every size on these photos, which is why Easydoor doesn't sell it as the lighter format: you choose, per site, between Automatic (AVIF for browsers that open it, WebP for the rest) and WebP only. The format lab shows where each format wins.
photo-1518791841217-8f162f1e1131, photo-1441974231531-c6227db76b6e, photo-1470071459604-3b5ec3a7fe05, photo-1506744038136-46273834b3fb, photo-1519681393784-d120267933ba.wordpress:7.1.0-apache, PHP 8.3.33), fresh install, the default Twenty Twenty-Five theme, no plugins active, default settings (JPEG quality 82, big_image_size_threshold 2560). Uploaded with wp media import (WP-CLI 2.12.0), which runs the same server-side code as an upload in the Media Library, once with Imagick (ImageMagick 7.1.1-43) and once with GD (bundled 2.1.0). Every file was weighed in bytes on disk.Easydoor is a WordPress plugin and a service: you upload in the Media Library as usual, and your images are stored, turned into WebP and AVIF and served from Easydoor instead of your hosting. Every account starts on the free plan, with no credit card.