Convert an image to JPG,
PNG or WebP.

Converting between image formats

A conversion changes the container, not the picture. That single sentence explains most of the surprises people run into here: why a converted file can come out larger than the one they started with, why a blurry JPEG stays blurry when it becomes a PNG, and why a logo loses its transparent background on the way to JPG. Here is what each direction actually does, so you can pick the one you want rather than the one that sounds safest.

PNG to JPG

By far the most requested conversion, and usually the right one. A photograph saved as PNG is stored losslessly, which means every speck of sensor noise is preserved at full cost — a 3 MB PNG routinely becomes a 300 KB JPEG that nobody can tell apart. The one thing you give up is transparency: JPEG has no alpha channel, so anything transparent is filled with white before encoding. That is fine for photographs and wrong for logos.

JPG to PNG

This is the conversion that most often disappoints. PNG is lossless, but lossless means "preserves exactly what it is given" — and what it is given is a JPEG that has already thrown detail away. You get a bigger file containing the same compression artefacts, not a restored image. There is one good reason to do it anyway: you need transparency, or a tool down the line refuses to accept JPEG. Editing rather than archiving is the honest use case.

WebP to JPG

Compatibility, almost always. WebP is smaller and better, and it is also the format that an older photo printer, a corporate document system or an application form written in 2011 will reject without explaining why. Converting back to JPEG costs you a re-encode, so do it from the best source you have rather than from a copy that has already been through the loop twice.

JPG or PNG to WebP

The conversion worth doing if the destination is a web page. WebP is roughly 25–35% smaller than JPEG at matching perceived quality and it keeps transparency, so it replaces both of the older formats at once. Every current browser supports it. Avoid it only where the file leaves the web and lands somewhere you do not control — an email attachment, a print shop, a government upload form.

Why a converted file can get bigger

Two causes, and both are the format doing its job. Converting a photograph to PNG asks a lossless format to store millions of slightly different pixels, which it cannot do cheaply. Converting a flat graphic — a screenshot, a chart, a logo — to JPEG asks a photographic format to encode hard edges, which it does badly and expensively, adding a halo of fringing around every line of text into the bargain. Match the format to the picture: photographs to JPEG or WebP, flat graphics to PNG or WebP.

Converting is not compressing

This tool re-encodes once, at high quality, and leaves the dimensions alone. It is meant to answer "I need this as a PNG", not "I need this under 200 KB". If a form is rejecting your file for its weight rather than its extension, the compressor is the tool you want — it searches for the highest quality that still fits the limit you name, and reduces dimensions only when quality alone cannot get there. Converting first and compressing afterwards means two lossy passes where one would have done.