Take a photo on almost any modern phone and you’ll get an image somewhere around 4000×3000 pixels. A photo from a DSLR or mirrorless camera can easily be larger — 6000×4000 pixels or more isn’t unusual. Upload that straight into WordPress, and the plugin dutifully stores every one of those pixels, forever, even though the widest your blog post column or product image will ever display is maybe 1200 to 1600 pixels.

That mismatch — between what you upload and what a web page actually needs — is one of the most common, least-noticed sources of a bloated, slow-loading WordPress site. A “Max Dimensions” setting is the fix. This post explains what it does, why it matters, and how to think about setting a sensible limit for your own site.

The problem: your originals are bigger than your page

When you upload an image in WordPress, the plugin generates a set of resized copies — thumbnail, medium, large, and so on — for use in different contexts. But by default, it also keeps the original file at full resolution, exactly as it came off your camera or phone.

That original often isn’t used directly on the front end, but it still sits in your uploads folder taking up disk space. Depending on your hosting plan and theme, it can also end up referenced directly in certain contexts (linked media, some page builders, certain themes’ “full size” image options) — and when that happens, visitors can end up downloading several megabytes of image data to fill a space that’s a few hundred pixels wide on their screen.

A few consequences of leaving originals uncapped:

• Wasted storage. A media library of a few hundred full-resolution photos can easily run into gigabytes, most of which is pixel data no browser will ever render.
• Slower backups. Every backup, whether it’s a full site backup or an offsite sync, has to move that same oversized image data around, again and again.
• Bandwidth risk. If an oversized original ever does get served to a visitor — directly, through a broken theme setting, or through a plugin that doesn’t respect WordPress’s generated sizes — that visitor pays for it in load time and (on mobile data) actual bandwidth cost.
• A false sense of “already optimized.” Compressing a 6000-pixel-wide JPEG to be smaller in file size still leaves you with 6000 pixels of unnecessary resolution. File-size compression and dimension control solve two different problems.

None of this is about image quality on the page — a correctly displayed photo can look identical whether its source file was 6000 pixels wide or 1800. It’s about not paying, in storage and bandwidth, for resolution nobody will ever see.

What a Max Dimensions setting actually does

A Max Dimensions setting puts a ceiling on the original file itself at the moment it’s uploaded. You set a maximum width and/or a maximum height — commonly somewhere in the 1600–2000 pixel range — and any image wider or taller than that limit gets automatically downscaled to fit inside it.

Two details make this safe to use without a second thought:

• Aspect ratio is always preserved. The resize fits the image proportionally within your width and height limits — it never stretches or squashes it, and it never crops content out. A 4000×3000 landscape photo capped at 1920px wide comes out as 1920×1440 — same shape, smaller file.
• It only affects images that exceed the limit. A photo you upload at 1200×800 is already inside a 1920×1920 cap, so it passes through untouched. The setting only steps in for images that are genuinely oversized for web use.

The result is straightforward: nothing you ever need for display gets removed, but the enormous excess resolution that phones and cameras produce by default is trimmed down to something reasonable before it ever takes up long-term storage.

How to pick a sensible maximum

There’s no single right number, but a few landmarks help:

• Full-bleed hero images and large feature photos rarely need to exceed about 1920 pixels wide, even on today’s large monitors — and with responsive images, the browser is only ever requesting a size appropriate to the visitor’s screen, not the absolute original.
• Blog content images embedded in a text column are usually displayed well under 1000 pixels wide. If your site is mostly text with occasional in-post photos, you can often set a lower cap.
• WooCommerce product galleries with zoom are the main case where you might want to keep a larger maximum (2000–2500px), since zoom features rely on extra source resolution to show fine detail.
• When in doubt, 1920px on the long edge is a safe, widely used default. It comfortably covers full-width layouts on standard desktop monitors without keeping camera-native resolution around for no reason.

If you’re not sure what your theme actually displays images at, a quick check of your page in a browser’s “inspect element” view (looking at the rendered width of your largest image container) will tell you the real number to aim for.

How AWP’s Max Dimensions setting works

AWP’s Images module includes a Max Dimensions setting that applies this automatically, locally, on your own server, at upload time. You set a maximum width and/or height in pixels — AWP ships with a sensible 1920×1920 default — and from that point on, any newly uploaded image that exceeds those limits is downscaled proportionally to fit, exactly as described above. Leaving either field at zero skips the cap on that axis if you only want to constrain one dimension.

This runs as part of the same upload pipeline as AWP’s other Images module features — AVIF conversion and EXIF metadata stripping — so a single upload gets resized, cleaned of unnecessary metadata, and converted to an efficient format in one pass, with no manual steps. AWP also keeps things consistent behind the scenes: it automatically turns off WordPress’s own “big image” auto-scaling threshold when your Max Dimensions cap is active (so the two don’t work against each other), and it disables any registered image size that’s larger than your configured maximum.

It’s worth being clear about scope: this setting works on new uploads going forward, not a retroactive resize of everything already in your media library. If you have years of oversized originals already stored, Max Dimensions prevents the problem from growing further, starting the moment you turn it on.

This is separate from AWP’s optional personalized optimization, where the AWP Exchange Server looks at your page’s public output and works out the best display size for each device, and the plugin then serves right-sized, responsive AVIF variants — without touching your original files at all. Max Dimensions, by contrast, is a simple, permanent, local housekeeping step on the originals themselves: a small setting that keeps your media library from quietly filling up with resolution nobody on your site will ever actually see.