Resizing changes the number of pixels
Resizing means changing the width and height of an image. A 4000 × 3000 pixel photo resized to 800 × 600 contains far fewer pixels. Because there is less information to store, the file size drops dramatically, often more than compression alone can achieve. Resizing is the right choice when the final display size is much smaller than the camera output.
The downside is that you lose detail permanently. A 200-pixel-wide image cannot be enlarged back to 2000 pixels without looking blurry. Always keep the original full-resolution file somewhere safe and resize only a copy that you intend to upload.
Compression keeps the same pixels but stores them more efficiently
Compression reduces the amount of data needed to describe the existing pixels. JPG compression, for example, removes fine detail that the eye is less likely to notice. The image still has the same width and height, but the file is smaller. Compression is ideal when the dimensions are already close to what the destination needs.
Too much compression creates visible artifacts such as blocky edges, color banding in gradients, and ringing around text. The goal is to find the highest quality setting that still fits below 200KB, not the absolute smallest file at any cost.
Which should you do first?
The best workflow is to resize first and compress second. Start by cropping and scaling the image to the required dimensions. Then compress the result. If you compress first and then resize, you may apply compression to pixels that are about to be thrown away, wasting quality for no benefit.
| Action | What changes | Use it when | Main risk |
|---|---|---|---|
| Resize | Pixel width and height | The source is much larger than the required display or exact dimensions are specified | Permanent loss of fine detail |
| Compress | How pixel information is encoded | Dimensions are already suitable but file size is too large | Artifacts at very low quality |
| Resize, then compress | Both dimensions and encoding | A large camera image must meet a strict 200KB limit | Over-reducing both controls |
A practical decision tree
- Form requires exact dimensions → resize to those exact dimensions, then compress.
- File is large but dimensions are correct → compress only.
- File is large and dimensions are too big → resize first, then compress.
- Quality looks poor after compression → reduce dimensions slightly and compress again.
Understanding the difference between these two controls helps you reach 200KB without over-correcting. Use the right tool for the job and keep the original untouched for future changes. The complete 200KB workflow shows how to check the result before submitting it.