Convert and compress images to WebP, PNG or JPEG, in batches, without uploading anything. Useful for getting screenshots and photos down to a size that will not wreck your page load.
Three formats, and the right one depends on the content. WebP is the default because at the same visual quality it lands well under a JPEG of the same photograph, and every current browser reads it. JPEG is the fallback for somewhere that will not take WebP. PNG is lossless and belongs to screenshots, diagrams and anything with flat colour and sharp edges, where JPEG leaves visible ringing around text — and it is the only one of the three that keeps transparency.
Conversion and resizing here happen on a canvas inside your browser, so nothing is uploaded, and the quality slider is worth moving: for most photographs the difference between quality 90 and quality 75 is a file less than half the size and a change you have to look for. Metadata, including any GPS coordinates a phone recorded, does not survive the conversion — which is usually what you want before posting a picture.
Resizing is where most of the file size actually goes, and it is the step people skip. A photograph straight off a modern phone is 4,000 pixels or more across; displayed in a 800-pixel column, three quarters of that detail is discarded by the browser after it has been downloaded. Scaling the image to the size it will be shown at, and only then adjusting quality, cuts a file far more than any quality setting alone — and it does so without the smeared edges that aggressive compression leaves behind.
Quality settings are not linear and the top of the range is where the bytes hide. Moving from 100 to 90 typically removes a large fraction of the file and leaves a difference you have to hunt for; moving from 90 to 75 removes noticeably less and starts to show on flat gradients such as skies, where JPEG banding appears first. Below about 60 the artefacts stop being subtle. For photographs, somewhere between 75 and 85 is the usual sweet spot; for screenshots and diagrams no lossy setting is the right answer, and PNG is.
Metadata does not survive the conversion, and that is usually the point. A photograph taken on a phone carries EXIF data that can include the exact GPS coordinates where it was taken, the device model, and the timestamp — information that is invisible in the picture and travels with it when it is posted anywhere. Because the conversion here happens on a canvas in the browser, the output is pixels and nothing else. The trade-off worth knowing is that the orientation flag goes too, though the rotation it described is already baked into the pixels by then.
No. Decoding and re-encoding happen on a canvas inside your browser. The files never leave your computer, which also means there is no upload size limit beyond your available memory.
Usually because the source was already efficiently compressed and you converted at a high quality setting, or you converted a flat graphic from PNG to JPEG. The saving figure turns red when this happens — lower the quality or keep the original.
AVIF encoding is not offered because browser support for encoding it on a canvas is still inconsistent. AVIF input files can be read and converted to WebP, PNG or JPEG.