SparkCore
Large uploads? Automatically resize after upload
Photographers and marketers upload large source files; Spark delivers web-ready variants.
In short
- A large upload only becomes a problem when visitors have to download it.
- WordPress scales very large images down to 2560 pixels on its own, but that is not compression.
- A generous upload limit in MB says nothing about how fast your pages load.
Upload limit vs. file size
Compression helps even if your limit in MB is still generous: visitors download less.
Why does uploading large images in WordPress slow down your site?
The upload itself only costs you time. The problem starts when that heavy image sits on a page. Every visitor then pulls in a large file, especially on mobile. That hurts the Largest Contentful Paint. It is good at 2.5 seconds or less. A hero of several megabytes rarely reaches that on a slow connection. Photographers and marketers also often upload source files straight from the camera or the design tool. Those are made for print, not for your screen.
- Source files are made for print, not for the web.
- A heavy hero image slows LCP the most.
- Mobile visitors feel the difference first.
What does WordPress itself do with large images on upload?
WordPress automatically scales very large uploads down to a maximum of 2560 pixels. This is called the big image threshold. The original file is kept. WordPress also creates smaller sizes for themes and blocks. That helps, but it is not a complete solution. An image of 2560 pixels can still weigh several megabytes. The dimensions are smaller, but the file is still not lean. For that you need real compression.
Upload limit or file size: what is the difference?
The upload limit decides how large a file may be when uploading. You set it on your server. The file size on the page is something else. It decides how much a visitor has to download. A high limit solves an upload error but does not make your site faster. A low limit does force your team to use smaller files. That feels strict and causes hassle. A smarter approach is a generous limit and then automatic reduction, so nobody has to think about it.
- The limit is about the upload, not the page.
- A higher limit does not make your site faster.
- Reducing after upload saves your team hassle.
How do you control the size of uploads in WordPress?
First agree on the maximum dimensions your team uploads. For most sites that is the width of the largest spot on the page. Then let processing run automatically. Spark Media Optimizer puts this in a background queue, so uploading stays smooth. PDFs and PowerPoint files from the media library go through the same queue. That way your visitors get web-ready files, even when the uploader does not think about it. It works on new uploads and on what is already there.
Frequently asked questions
WordPress scales very large uploads down to 2560 pixels and keeps the original. That is a dimension, not a file size. The resulting file can still be heavy.
No. A higher limit only allows larger files. For speed, what the visitor downloads is what counts. So reduce and compress the images that end up on your pages.
It does not have to be. WordPress keeps the original for large uploads. Spark Media Optimizer works with safe copies and lets you roll back. Always check this for any tool you use.