Ever noticed a file in your Media Library ending in -scaled.jpg and wondered where it came from? You didn’t create it — WordPress did. It’s part of a built-in feature called the big image threshold, and most site owners have never heard of it, even though it’s been quietly resizing their uploads for years.

Here’s what it does, why it exists, and the choice AWP gives you if you’d rather manage it yourself.

What the big image threshold actually does

Since WordPress 5.3 (released in 2019), any image you upload that is larger than 2560 pixels on its longest side gets automatically scaled down before WordPress finishes processing it.

So if you upload a photo straight from a modern smartphone or DSLR — say, 6000×4000 pixels — WordPress will:

1. Create a scaled-down version, no larger than 2560px on the longest side.
2. Use that scaled version as the new “full size” image going forward.
3. Keep your original, un-scaled upload as a backup file, with -scaled added to its filename.
4. Generate all the usual thumbnail sizes (medium, large, etc.) from the new scaled version.

The result: the image that actually gets used across your site — in blog posts, product pages, galleries — is the 2560px version, not the original file you uploaded.

Why WordPress added this

Before this feature existed, it was extremely common for people to upload massive, camera-original images straight into a post — sometimes 4000px, 6000px, or wider — without resizing them first. WordPress would dutifully generate thumbnails from that giant file, but the “full size” version stayed enormous.

If that full-size image ever got used on the front end (in a theme, a lightbox, a featured image area), visitors could end up downloading a multi-megabyte file for something displayed at a fraction of that size on screen. That’s slow for visitors and wasteful of server storage and bandwidth.

Capping uploads at 2560px was a sensible default: it’s large enough to look sharp even on high-resolution displays, but small enough to avoid the worst-case scenario of truly oversized originals being served to visitors. It’s WordPress trying to protect site owners from a mistake they didn’t know they were making.

The “-scaled” file and the quirks it causes

The -scaled naming convention is simple once you know what it means:

• photo.jpg — your new “full size” image (max 2560px), the one WordPress actually uses.
• photo-scaled.jpg — your original, untouched upload, kept as a backup.

This is generally a good compromise: you don’t lose your original file, but your site doesn’t serve it either. Still, it causes a few quirks that catch people off guard:

• The original is dead weight. The -scaled file sits in your uploads folder and Media Library, taking up storage, but it’s never used on the front end unless you specifically dig it out (for example, to re-edit the photo in higher resolution).
• “Why is my image smaller than the file I uploaded?” If you check image dimensions after upload and they don’t match your original, this is why — you’re looking at the scaled version, not your source file.
• It only applies to raster formats. The threshold affects JPEG, PNG, and similar formats; it doesn’t apply the same way to other file types.
• It’s a one-time decision at upload. WordPress makes this call the moment you upload the file. There’s no per-image toggle in the media editor — it’s a global setting.

None of this is a bug. It’s WordPress doing exactly what it was designed to do: stop enormous originals from being served to visitors. But it also means the 2560px cap is applied the same way to every image on your site, regardless of where or how large that image actually displays.

The choice AWP gives you

This is where AWP’s Images module comes in. WordPress’s big image threshold is a reasonable one-size-fits-all default, but it isn’t the only way to manage upload sizes — and for many sites, it isn’t the most precise one.

AWP lets you disable WordPress’s built-in 2560px threshold and hand that responsibility to AWP’s own Max Dimensions setting instead. Once you do, every image you upload is resized by AWP according to the dimensions you choose — not WordPress’s fixed default.

The trade-off is straightforward:

• WordPress’s default (2560px threshold): simple, works out of the box, no configuration needed. But it’s a fixed number that may be larger or smaller than what your site’s design actually needs.
• AWP’s Max Dimensions setting: you decide the ceiling — whether that’s 2560px, 1920px, or any value that matches how images are actually displayed on your site. This gives you consistent, predictable output dimensions across your whole Media Library, set once, applied automatically at upload time.

If your theme never displays images wider than 1800px, for instance, letting every upload cap out at 2560px means you’re still storing and processing more pixels than you’ll ever show. Setting AWP’s Max Dimensions closer to your real display width means smaller files, less storage used, and one less discrepancy to think about between “what I uploaded” and “what my site serves.”

This local resizing at upload time works independently of AWP’s cloud-assisted optimization (which handles right-sized, responsive AVIF delivery per device based on how your live pages actually render). Together, they cover both ends of the problem: sensible dimensions going into your Media Library, and the best format and size going out to each visitor’s device.

Getting it right for your site

The big image threshold is one of those quiet WordPress defaults that works fine for most people, most of the time — which is exactly why so few site owners know it exists. Understanding it means you’ll no longer be surprised by -scaled files in your Media Library, and you’ll know why the “full size” image isn’t always the file you actually uploaded.

If you want more control than the fixed 2560px default offers, AWP’s Max Dimensions setting is a simple way to take over that decision — matching upload sizing to how your site actually displays images, rather than relying on a one-size-fits-all number.