Image Dimensions vs. File Size: Why Your Upload Keeps Getting Rejected

A phone photo is 1.2MB and gets rejected as "image too large." That sounds like a file-size problem, so the instinct is to compress it — except compressing doesn't touch the actual thing the form is checking. The photo is 4032×3024 pixels, and the form's limit is 2000px wide. Two completely different measurements share one error message, and picking the wrong fix wastes a round trip.

Two counters, two units

"Max 2000px wide" counts pixels — the width and height of the image grid, independent of how it's encoded. "Max 500KB" counts bytes on disk — how much storage the file takes up, which depends entirely on compression. These aren't correlated the way people assume. A 4000×3000 photo can be a lean 200KB JPEG at moderate quality or a bloated 8MB file at near-lossless quality — same pixel grid, wildly different byte count. Conversely, a small 300×200 image saved as an uncompressed PNG can weigh more than a huge, heavily-compressed JPEG. Dimensions and file size move independently; one number never tells you the other.

Why phones trip the dimension check specifically

Modern phone cameras shoot 12–48 megapixels, which works out to 4000–8000px on the long edge. Most upload forms — profile photos, marketplace listings, form attachments — cap incoming images around 1500–2000px, because nothing on a screen displays wider than that anyway; storing more is wasted space on their end. So a camera-fresh photo almost always exceeds a dimension cap, regardless of how well it's compressed. That's the specific reason "image too large" so often hits phone photos that look perfectly reasonable in file size.

Each error needs a different fix

Changing pixel dimensions and changing file size are two separate operations, done by two separate tools. Image Resize rewrites the pixel grid itself — enter a width or height and leave the other field at 0, and it computes the missing side from the original aspect ratio so nothing comes out stretched. This is what fixes a "max 2000px" rejection.

Image Compressor does the opposite: it leaves the pixel grid untouched and re-encodes the same dimensions at a lower JPEG quality, running a binary search until it lands the sharpest result under a target you pick — 100KB, 200KB, 500KB, or 1MB. This is what fixes a "max 500KB" rejection. One consequence worth knowing: the output is always a JPG, so a transparent PNG logo gets its transparent pixels flattened onto white — for anything that needs to stay transparent, compression is the wrong tool regardless of the size target.

Resizing usually shrinks the file too, since fewer pixels means less data to store — but it won't hit an exact KB number on purpose. Compressing never changes the width or height at all, only the encoding.

When a form checks both

Some forms cap dimensions and file size at once. The order matters: resize first, then compress. A 6000×4000 phone photo squeezed straight down to 100KB shows visible blocking, because that much detail can't fit in that small a budget without heavy quality loss. Resize the same photo to 1600px wide first, and compressing it to 100KB afterward produces a noticeably cleaner result — the same byte budget just has far less detail left to discard.

The gotcha: shrinking is nearly free, enlarging isn't

Making an image smaller means discarding pixels you no longer need — the remaining ones are still real, captured detail, so the result stays sharp. Making an image bigger is a different operation entirely: there's no extra detail to reveal, so the software has to invent new pixel values by interpolating between the ones that exist. That's why an upscaled photo looks soft around edges and text no matter which tool does it — the information was never captured in the first place. The practical rule: always resize down from the highest-resolution original you have, and treat upscaling to hit a minimum-dimension requirement as a last resort, since the extra pixels are fabricated, not recovered.

Next time an upload bounces, check which word is in the error. "Resolution," "dimensions," or a number followed by "px" means resize. "Size," "KB," or "MB" means compress. Seeing both means resize first.