Convert Image

Because that is sometimes the correct answer. PNG is a lossless format, so converting a JPEG to PNG normally produces a file several times bigger — nothing has gone wrong, that is simply what the two formats are. This tool does what you asked and tells you exactly how much the size changed, rather than handing back your original and pretending it converted anything. If your goal is a smaller file, the Compress Image tool is the one you want.

It survives in WebP and PNG, because both support an alpha channel. JPEG has none at all, so if you pick it for a transparent image we warn you before converting and fill the background with white — black is what you get if the browser is left to decide, and it looks like a bug rather than a trade-off.

WebP for anything going on the web: it compresses harder than JPEG, keeps transparency, and every current browser displays it. JPEG for photographs headed somewhere older, or into software that cannot read WebP. PNG for logos, graphics, and anything that needs transparency with no loss at all.

Yes, if your browser can decode them — Safari opens HEIC, and current browsers open AVIF. The tool uses your browser's own decoder, so any format it can display it can convert. Output is limited to WebP, JPEG and PNG, because those are the three a canvas can write.

Never. The output has exactly the dimensions the input had. Changing resolution is the Resize tool's job, and folding it in here would mean your converted file differs from its source in two ways instead of one.

It is removed. Re-encoding strips all attached metadata, including GPS coordinates and camera model. That is useful if you are publishing the image, but worth knowing if you need to keep that data.

No. Everything happens inside your browser — the image never leaves your device, and there is no daily usage limit.

Yes. Choose any number of images (up to 20, and up to 200 MB combined), and we convert them all to the same format, one at a time, inside your browser — the results come back as a single ZIP archive. Each image is processed on its own and its result shows up the moment it finishes — converted or excluded, with the reason.

Each image is decoded on its own, so decode memory never grows with the batch — but every image's output accumulates in memory before the archive is built. Converting a batch to PNG can legitimately come out several times larger than the input (the same reason a single file can grow, above), so this cap is set lower than other tools on the site to keep things running smoothly on any device.

The preview shown represents only the first image in the batch, as a reference to confirm your settings look right before running the whole batch — the same settings apply to every image, but each one's actual result depends on its own content.