Three words get used interchangeably, and picking the wrong one is why people end up with beheaded portraits or unreadable screenshots.
Crop — Changes What's In the Frame
Cropping cuts pixels away from the edges. The remaining pixels are untouched, so nothing gets blurry — but content leaves the picture, and the aspect ratio usually changes.
Use it when: the composition is wrong, there's dead space around the subject, or a platform needs a specific ratio (1:1 avatar, 16:9 thumbnail, 3:2 print).
Resize — Changes the Pixel Dimensions
Resizing rescales the whole image, keeping all the content but changing how many pixels describe it. 4000 × 3000 → 800 × 600 keeps the same framing at a quarter of the width.
Use it when: a form states maximum dimensions, or you're serving a 4000 px photo into an 800 px slot. Downscaling is safe and even *looks* sharper on screen; upscaling is where quality dies, because the extra pixels are interpolated guesses.
Compress — Changes the File Size
Compression keeps the dimensions and reduces bytes, by discarding data the eye is least likely to miss (lossy) or by packing bytes more efficiently (lossless). Same pixel grid, smaller file, slightly less fidelity.
Use it when: the constraint is in KB or MB — an email attachment, a "max 200 KB" form, a slow-loading web page.
The Cheat Sheet
| The requirement says… | What you need |
|---|---|
| "must be square" / "16:9" | Crop |
| "max 1000 × 1000 px" | Resize |
| "under 200 KB" / "under 2 MB" | Compress |
| "photo must be 413 × 531 px" | Crop to ratio, then resize |
| Page loads slowly | Resize to display size, then compress |
The Correct Order
Always crop → resize → compress:
- Crop first, so you're not spending pixels on parts you'll throw away.
- Resize second, to the exact target dimensions.
- Compress last, to hit the byte budget — because compressing before resizing means the compression artifacts get rescaled too, and the second pass has to work harder.
Two Traps
- Resizing doesn't guarantee a small file, and compressing doesn't change dimensions. If a form enforces both pixels *and* kilobytes, you need two steps, not one.
- Never crop-then-upscale to hit a dimension target. If a portal wants 600 × 600 and your crop yields 400 × 400, go back to a larger original. Inventing pixels is the one operation that can't be undone by any later step.