Image guide
JPG vs PNG vs WebP
JPG, PNG, and WebP solve different problems: photo compression, exact pixels and transparency, and small web assets. The right choice follows from where the file is going, not from which format sounds newest.
The sizes below come from one 1,400 x 788 photo (264 KB JPEG) exported at 92% quality in this site's browser converter, so the source pixels and the encoder stay the same across all three formats.
Recommended tool
Open Convert ImageMeasured on the same photo
Same pixels, three outputs: JPG 264 KB, WebP 212 KB, PNG 2.07 MB.
WebP came out about 20% smaller than JPG here, and PNG was roughly 7.8 times the JPG size: a browser-canvas PNG stores every pixel without photo compression. A dedicated PNG optimizer can shrink that number, but on photographs PNG still loses to JPG and WebP.
Treat this as one sample, not a guarantee. The gap widens on large detailed photos and narrows on flat graphics, so re-run your own file through the converter before you rely on a target size.
Use JPG for photos that must open anywhere
JPG compresses gradients and natural detail well, and it is the format every upload form, phone, email client, and print shop accepts.
It has no transparency, and each re-save discards a little more detail, so keep the original and export once from it.
Use PNG for transparency and sharp edges
PNG keeps every pixel exact, which is what screenshots, logos, UI captures, and transparent cut-outs need.
On photographs the file grows fast: 2.07 MB for the same 1,400 px photo above. If a portal caps uploads at 200 KB or 1 MB, a photo is rarely a good fit for PNG.
Use WebP for website images, with a fallback
WebP gives the smallest file of the three for photos and illustrations on the web: 212 KB against 264 KB for JPG on the test photo.
It is not accepted everywhere. Government upload portals, older desktop software, and some print workflows still ask for JPG or PNG, so confirm the accepted formats before converting.