WordPress adds -scaled to an image file name when the upload is more than 2560 pixels wide or tall: it keeps your original, makes a smaller copy that fits inside 2560 by 2560, and uses that copy as the “full” size. The cleanest way to avoid it is to resize images to 2560 pixels or less before you upload, so WordPress has nothing to scale. OpticBatch from Automata Labs does that for a whole folder at once on your Windows PC, with Max Width and Max Height limits, a quality slider, and originals that are never overwritten.
Size a whole folder of photos for WordPress before you upload, locally on Windows.
Get it from Microsoft
Why does WordPress rename my image to -scaled?
Because of the “big image” handling added in WordPress 5.3. The WordPress core team’s announcement explains the reason: many uploads are photos straight from a phone or camera, and “A photo taken with an average modern smartphone is easily over 5MB in file size.” To deal with that, WordPress detects big images and generates “a web-optimized maximum size” of them.
The current WordPress source code, in wp-admin/includes/image.php, says it plainly in a comment: “Append “-scaled” to the image file name. It will look like “my_image-scaled.jpg”.” So a file called beach.jpg that is too big becomes beach-scaled.jpg in your Media Library.
What is the WordPress big image threshold?
It is 2560 pixels by default. The big_image_size_threshold reference on WordPress.org describes it this way:
- “If the original image width or height is above the threshold, it will be scaled down.”
- “The threshold is used as max width and max height.”
- “The scaled down image will be used as the largest available size.”
- The default value is 2560.
Two details are easy to miss. First, the check is “above” the threshold, so an image that is exactly 2560 pixels on its longest side is not scaled. Second, either side counts. A tall portrait photo that is 1800 pixels wide but 3200 pixels tall will still be scaled.
What happens to my original image?
WordPress keeps it. The 5.3 announcement says “the original image file is stored in the uploads directory and its name is stored in another array key in the image meta array: original_image,” and that a function called wp_get_original_image_path() was added so developers can always find it.
The source code adds another useful detail: the -scaled suffix “doesn’t affect the sub-sizes names as they are generated from the original image (for best quality).” In other words, WordPress still processes the large original to make thumbnails and medium sizes, and the server keeps both the original and the scaled copy.
What does WordPress do with each kind of upload?
This table summarizes what the current core code does when an image is uploaded with the default settings.
| Your upload | What WordPress does | File name you see |
|---|---|---|
| Both sides 2560 pixels or less | Keeps the file as the full size and makes sub-sizes | beach.jpg |
| Either side above 2560 pixels | Scales a copy to fit 2560 by 2560, uses it as full size, keeps the original | beach-scaled.jpg |
| 2560 or less, but the camera’s EXIF orientation says it should be rotated | Saves a rotated copy and uses it as the full size | beach-rotated.jpg |
| A site has an output format mapping set for that file type | Converts the file on saving, without adding a suffix | beach with the new extension |
For a sense of scale, a 6000 by 4000 pixel camera photo would be scaled to about 2560 by 1707 pixels, keeping its proportions.
You may see older forum notes saying PNG files are never scaled. The current core function we read today applies the threshold check without a PNG exception, so test with your own site rather than relying on older advice.
Can I turn off -scaled images in WordPress?
Yes, with code. The WordPress reference says “Returning false from the filter callback will disable the scaling,” and the 5.3 announcement gives the one-line example:
add_filter( 'big_image_size_threshold', '__return_false' );You can also return a different number to raise or lower the threshold. That usually goes in a small plugin or your theme’s functions file. The trade-off is that with scaling turned off, a huge upload becomes the full-size image that themes and blocks can link to or display. If you do not manage code on your site, or you want small files on the server in the first place, resizing before upload is simpler.
How do I resize photos before uploading to WordPress?
Do it in one batch, on your own PC, before the files reach the Media Library. With OpticBatch:
- Drop the folder of photos you plan to upload.
- Choose Max Width and Max Height and set both to 2560, or smaller if your theme never shows images that large. The aspect ratio lock keeps every photo in proportion, so portrait and landscape shots both fit inside the box.
- Pick the output format. OpticBatch converts between JPEG, PNG and WebP, so you can also produce WebP files for a lighter page.
- Set the quality with the slider from 1 to 100. OpticBatch shows a live estimate of the file size savings before you run the batch.
- Run it and upload the results. Your originals are never overwritten, and if one file in the batch is corrupted, OpticBatch flags it and keeps processing the rest.
Because every exported image is at or under 2560 pixels on each side, WordPress has nothing to scale, so no -scaled file is created. Everything happens locally, with no uploads to an online converter, no forced account and no telemetry. That matters when the photos belong to a client or show products that are not public yet.
Resize and convert thousands of images locally, and never overwrite an original.
Get it from Microsoft
What size should I use if 2560 is more than my theme needs?
2560 is a ceiling, not a target. Many layouts never show an image anywhere near that wide. If your content area or hero images are smaller, a lower Max Width keeps files lighter while WordPress still makes its usual sub-sizes from what you upload. Check your theme’s widest image and add some headroom for high-density screens.
For more on WordPress image prep, see bulk resize WebP for WordPress before upload, optimize WordPress media outside the Media Library, exact dimension batch resizing, and a fast local bulk image resizer for Windows 11.
Frequently asked questions
Is it bad that WordPress made a -scaled image?
No. It is WordPress protecting your pages from very large images. It does mean the server stores both the original and the scaled copy.
Will an image that is exactly 2560 pixels be scaled?
No. WordPress scales an image only when its width or height is above the threshold.
Where is the original image after scaling?
Still in your uploads folder. WordPress records its name in the image metadata as original_image.
Why did my photo get -rotated instead?
WordPress rotates images whose EXIF orientation says they should be turned, and saves the result with a -rotated suffix.
Does OpticBatch upload my photos anywhere?
No. It processes images locally on Windows 10 and Windows 11, with no forced account and no telemetry.
Try OpticBatch
Get OpticBatch from the Microsoft Store. It is a one-time purchase with no subscription, and the Store listing shows the current price.
Get every image under the WordPress threshold before it ever reaches the Media Library.
Get it from Microsoft
WordPress is a trademark of the WordPress Foundation. Microsoft and Windows are trademarks of the Microsoft group of companies. OpticBatch is not affiliated with or endorsed by either.
Last updated 21 October 2026. Published by Automata Labs, a software company in Canada.