When a form rejects your photo for being too large, the solution is either to compress it or to resize it — or both. People use these words interchangeably, but they describe completely different operations with different trade-offs. Using the wrong one first is a common reason you spend twenty minutes and still end up with a file that's too large or looks terrible.
What resizing actually does
Resizing changes the pixel dimensions of an image — the width and height measured in pixels. A 4000×3000 image resized to 2000×1500 has exactly one quarter the number of pixels it started with. Because it has fewer pixels to store, the file is smaller.
Resizing does not reduce quality the way compression does — a well-resized image looks just as sharp at its new smaller size. The trade-off is that it's now physically smaller: if the form needed an image of at least 2000 pixels wide, resizing it down past that point fails the requirement.
Use resize when: the form specifies exact pixel dimensions, or when the image is from a high-resolution camera (4000+ pixels wide) and just needs to be brought to a normal viewing size.
What compressing actually does
Compression keeps the pixel dimensions the same but encodes the image data more aggressively, storing it in fewer bytes. For JPEG images (the most common type), compression works by reducing color detail in areas where the eye is least likely to notice — smooth gradients, complex textures. At low compression levels this is invisible; at high levels you start to see blocky artifacts around edges.
Compressing a 4000×3000 image doesn't change the fact that it's 4000×3000 pixels — it just makes the file that holds those pixels smaller. The image still displays at the same size; it just takes up less disk space.
Use compress when: the form specifies a maximum file size in KB or MB, but doesn't have a strict pixel dimension requirement — or when the image is already at the right dimensions and just needs to be smaller.
PNG is a special case
PNG uses lossless compression — you can't reduce a PNG file's size the way you can a JPEG by adjusting quality. If someone tells you to "compress" a PNG, what they almost always mean is either: convert it to JPEG first (and then compress the JPEG), or resize the PNG's pixel dimensions. Saving a PNG at "lower quality" in most tools either does nothing or converts it to JPEG behind the scenes.
Which to do first when a file is too large
If the image is from a phone camera and is enormous (6000+ pixels wide, 5MB+), resize it down to something reasonable first — 1500–2000 pixels wide is usually plenty for form uploads. This single step often gets you 80% of the way to the target size.
If it's still too large after resizing, then compress it to hit the exact KB limit. Doing it in this order (resize first, then compress) gives you better quality at the target size than compressing a huge image down alone, because compression is less destructive when it has less work to do.
A concrete example
A form wants a file under 200 KB, no dimension requirement. Your photo is 5000×3800px at 4.5 MB.
- Resize only to 1500×1140px: file drops to roughly 600–900 KB. Still over the limit.
- Then compress to 200 KB: file hits the target, quality stays high because the image isn't fighting a huge original.
- Compress only without resizing: the tool has to compress an enormous image very aggressively to reach 200 KB — quality suffers more than it needed to.