Image Too Large? The Right Order to Shrink Pixels Then Quality
When an image exceeds an upload limit, first tell which gate it hits — resolution or file size — then apply fixes in the right order.
Two gates: pixel count vs file size
Upload failures distinguish "resolution too large" from "file too large". The former means fewer pixels; the latter means lower quality or a leaner format. Do both, smallest-first: resize, then compress.
Resizing first lets the encoder work on a smaller canvas, so the same quality value yields a smaller file. Reverse the order and the gain mostly disappears.
Where the quality slider stops mattering
Around 80 is the practical threshold: above it, file size climbs while the image looks the same; below it, blocking artifacts appear. Flat-color screenshots tolerate lower values; people photos should stay above 75.
Check text edges at 100% zoom after compressing — jagged edges mean you went too far; step back 5-10 points.
Switching format often beats pushing the slider
WebP runs 25-35% smaller than JPG at similar quality and supports transparency — ideal for web delivery. For recipients on older software, stick with JPG.
PNG-to-JPG drops transparency; lay down a background color first. Details in the PNG/JPG guide.