Image Converter — PNG, JPG, WebP & AVIF online

Convert images between PNG, JPG, WebP and AVIF and set the output quality yourself. Batch-friendly, watermark-free, and processed in your browser.

About the Convert image format tool

Picking an image format is really a choice about what you are willing to trade. JPG throws away detail to get small files and cannot store transparency, which makes it right for photographs and wrong for logos. PNG keeps every pixel exactly and supports transparency, which makes it right for screenshots, diagrams and anything with sharp edges, and wrong for photographs — a PNG of a holiday snap can easily be ten times the size of the equivalent JPG for no visible gain.

WebP was designed to end that compromise. It does both lossy and lossless compression, supports transparency and animation, and typically produces files 25 to 35 percent smaller than JPG at the same perceived quality. Every current browser reads it. AVIF goes further still, often halving WebP again on photographic content, though it encodes more slowly and support outside browsers is thinner. For images going onto a website, one of these two is almost always the right answer.

The reason JPG and PNG remain unavoidable is everything that is not a browser. Upload forms, older desktop software, print services, some email clients and plenty of internal business systems still reject anything newer. That is the practical rule: WebP or AVIF when the file is destined for a web page you control, JPG or PNG when you are handing it to a person, a form, or a system you do not.

One conversion is safe; a chain of them is not. Going from JPG to PNG does not restore the detail the JPG discarded — it faithfully preserves the damage in a larger file. Going JPG to WebP to JPG loses a little each way. Whenever you can, convert from the largest original you still have rather than from whatever copy is nearest to hand, and you avoid the problem entirely.

How it works

1

Add your images

Drop in one file or several. PNG, JPG, WebP and AVIF are all accepted as input, in any mixture.

2

Choose the output format

Pick PNG, JPG, WebP or AVIF, and set the quality for the lossy ones. Higher quality means a larger file.

3

Download the converted files

Save the results. Originals are never modified, so you can convert the same file again to a different format.

Frequently asked questions

Which format should I actually use?
For photographs on a website, WebP. For photographs going anywhere else, JPG. For screenshots, logos, icons, diagrams or anything needing a transparent background, PNG — or WebP if it is web-bound, since WebP handles transparency too. AVIF is worth it when you are optimising a site aggressively and can accept slower encoding and narrower support outside browsers.
Will converting PNG to JPG lose transparency?
Yes. JPG has no concept of an alpha channel, so transparent areas have to become a solid colour — usually white or black — and there is no way to get them back afterwards. If your image has a transparent background and you need to keep it, convert to PNG, WebP or AVIF instead. All three support transparency.
Does converting improve image quality?
It cannot. Conversion changes how pixels are stored, not what they contain, so detail already lost to a previous compression stays lost. Converting a heavily compressed JPG to PNG produces a large file containing exactly the same visible artefacts. Quality can only be preserved or reduced, never recovered — which is why working from the original matters so much.
Why is my PNG so much bigger than the JPG was?
Because PNG is lossless: it stores every pixel precisely rather than approximating. That is superb for flat graphics with large uniform areas, which compress extremely well, but photographs are dense with fine variation and PNG has almost nothing to work with. If the image is a photograph, PNG is the wrong choice regardless of how good "lossless" sounds.
What quality setting should I choose?
Around 80 percent is the usual sweet spot for JPG and WebP — visually very close to the original at a fraction of the size. Between 60 and 75 is acceptable for thumbnails and background images. Above 90 you pay a lot of bytes for differences almost nobody can see. Compare the output before saving rather than trusting a number.
Why did I get a PNG when I asked for AVIF or WebP?
Encoding those formats is done by your browser, and not every browser build ships an encoder for every format even when it can display them. When the encoder is missing the tool falls back to PNG rather than failing silently or handing you a broken file. Updating your browser, or trying a current version of Chrome, Edge or Firefox, usually resolves it.
Are the files uploaded to convert them?
No. Decoding and re-encoding both happen on a canvas inside your browser tab, so images never leave your device. There is no upload queue, no account and no server-side storage, which also means no file-count limit beyond what your own machine can hold in memory at once.

Related tools