Image Converter
Convert between PNG, JPEG, WebP and AVIF, one image or a whole batch. Output formats are checked against what your browser can actually encode, so you never get a mislabelled file.
Related tools
How to convert an image
- Add your images. Drag them onto the box above or click to browse. JPG, PNG, WebP, AVIF, GIF and BMP are all accepted as input.
- Pick an output format. Formats your browser cannot encode are disabled rather than silently substituted.
- Set the quality for lossy formats, and choose how transparency is handled if the target format does not support it.
- Convert and download. Each row shows the size change. Save images individually or download the batch as a ZIP.
Nothing is uploaded. Everything runs in your browser.
When you would need this
Making a website faster. Converting JPEG and PNG assets to WebP or AVIF typically cuts image weight by a third or more with no visible difference. Images are usually the largest thing on a page, so this is among the highest-impact changes available.
Getting a file accepted. Plenty of systems accept only JPEG or PNG. Photos from a modern phone may arrive as HEIC or WebP, and forms reject them without explaining why.
Removing transparency. A logo with a transparent background dropped onto a white document looks fine until it is placed on something coloured. Converting to JPEG with a chosen background makes the result predictable.
Preparing images for print or documents. Some software handles JPEG and PNG reliably and everything else erratically. Converting first avoids surprises.
Reducing file size without resizing. When dimensions must stay the same, changing format is often the only saving available — and going from PNG to WebP can be substantial.
The four formats at a glance
| JPEG | PNG | WebP | AVIF | |
|---|---|---|---|---|
| Compression | Lossy | Lossless | Both | Both |
| Transparency | No | Yes | Yes | Yes |
| Best for | Photographs | Screenshots, logos, line art | Almost everything | Photographs where size matters most |
| Relative size | Baseline | Much larger for photos | 25–35% smaller than JPEG | Up to 50% smaller than JPEG |
| Browser support | Universal | Universal | All current browsers | All current browsers for display |
| Encoding speed | Fast | Fast | Fast | Slow |
The pattern worth internalising is that JPEG and PNG solve opposite problems — JPEG throws detail away to make photographs small, PNG keeps every pixel exactly so graphics stay sharp. Using either on the wrong content produces a bad result: a photograph as PNG is enormous, a screenshot as JPEG is visibly smeared around the text.
WebP is notable because it removes that choice. It does lossy and lossless in one format, supports transparency in both modes, and is smaller than the format it replaces in either case. For most work today the honest answer is to use WebP and stop thinking about it, keeping JPEG and PNG for the specific cases where compatibility demands them.
Tips for converting well
Understand what each format is for. JPEG compresses photographs efficiently and cannot store transparency. PNG is lossless and supports transparency, which makes it right for screenshots and line art and wasteful for photographs. WebP does both jobs well and is smaller than either. AVIF compresses hardest of all but encodes slowly and is not universally supported for output.
Do not convert lossy to lossy without a reason. Every lossy re-encode discards a little more. Converting JPEG to WebP is worth it for the size saving, but converting back and forth repeatedly accumulates damage. Work from the highest-quality original you have.
Converting a photo to PNG will inflate it. PNG is lossless, so it must store every pixel exactly — a photograph saved as PNG is routinely several times larger than the JPEG it came from, with no visible benefit. Convert to PNG only when you need transparency or exact pixel fidelity.
Choose the background colour deliberately. When flattening transparency into JPEG, the default white suits most cases. If the image will sit on a dark background, black avoids an obvious white halo. If neither works, keep transparency by converting to PNG or WebP instead.
Use WebP as the default for the web. Every current browser supports it, it handles both photographs and graphics, it supports transparency, and it is meaningfully smaller than the alternatives. Keep JPEG or PNG only when something specific requires them.
Check one image before converting a batch. Formats behave differently depending on content. Convert a single representative image, look at the result at full size, then apply the same settings to the rest.
Limits and requirements
Available output formats depend on your browser. Encoding support differs from display support — a browser can often show AVIF without being able to create it. Unavailable formats are disabled rather than silently substituted, because the underlying API returns a PNG for an unsupported type without reporting an error.
Transparency cannot survive a conversion to JPEG. The format has no alpha channel. Transparent areas are filled with the colour you choose.
Metadata is not carried across. Re-encoding drops EXIF, including timestamps, camera settings and GPS coordinates.
Animated GIFs lose animation. Only the first frame is converted, producing a still image.
HEIC is not supported as input. Photos in Apple's HEIC format cannot be decoded by most browsers. Set your iPhone camera to "Most Compatible" to capture JPEG instead, or export a JPEG copy first.
Memory is the constraint. Each image is decoded to raw pixels at roughly four bytes per pixel, so a 50-megapixel photo occupies around 200MB while processing. Split very large batches on a phone.
Privacy: how this tool handles your images
Your images never leave your device. When you add a file, your browser decodes it into memory, re-encodes it in the format you chose, and hands the result straight back. There is no upload, no server-side processing and no copy on our infrastructure.
Format conversion is one of the most common reasons people reach for an online tool, and it is also one of the most casual — the file feels like a technicality rather than something private. But the images being converted are photos of documents for an application, product shots for a business that has not launched, screenshots containing account details, pictures of family. The ordinary way to convert them online means uploading a full-resolution copy, GPS coordinates and all, to a company you have never heard of.
You can check this rather than trusting it. Open your browser's developer tools, switch to the Network tab, and convert an image — nothing carries your file. Or load this page, disconnect from the internet, and convert anyway. It still works, because everything needed is already running on your machine.
Frequently asked questions
Are my images uploaded to convert them?
No. Conversion happens in your browser using the image codecs built into the browser itself. Nothing is transmitted or stored by us. You can verify this by opening your browser's developer tools, switching to the Network tab, and converting an image — no request carries your file.
Which format should I choose?
For photographs on a website, WebP is the pragmatic default — every current browser supports it and it is typically twenty-five to thirty-five percent smaller than JPEG at matching quality. AVIF is smaller still, often halving a JPEG, but encodes more slowly and is not supported everywhere. Use PNG for screenshots, logos, diagrams and anything with sharp edges or transparency. Use JPEG when the file must open in older software or be accepted by a system you do not control.
What happens to transparency when I convert to JPEG?
JPEG has no alpha channel, so transparent areas must be filled with a solid colour. You can choose white or black; white is the usual choice and is the default. If transparency matters, convert to PNG, WebP or AVIF instead — all three support it. A logo designed for a dark background will look wrong flattened onto white, so pick the background that matches where the image will be used.
Why is AVIF sometimes unavailable?
Because not every browser can encode AVIF, even though most can display it. The tool tests what your browser can genuinely produce and hides the options it cannot. This matters because the underlying browser API does not report failure for an unsupported format — it silently returns a PNG instead, which would hand you a file named .avif that is really a PNG. Hiding the option is more honest than producing that.
Does converting reduce quality?
It depends on the direction. Converting to PNG is lossless and loses nothing. Converting to JPEG, WebP or AVIF is lossy and discards some detail, though at 85% quality the difference is not normally visible. Converting a lossy image to another lossy format re-compresses it, so a JPEG converted to WebP loses a little more on top of what the JPEG already lost. Convert from the highest-quality original you have.
Can I convert PNG to JPG to make it smaller?
Yes, and for photographs the saving is usually dramatic — often ninety percent or more, because PNG stores photographic data very inefficiently. For screenshots, logos and line art the opposite applies: converting to JPEG produces visible fringing around text and sharp edges, and often is not much smaller. Keep those as PNG, or use WebP, which handles both cases well.
Can I convert several images at once?
Yes. Add as many as you like and they are all converted with the same settings. Save them individually or download the batch as one ZIP. If two source files would produce the same output name — a.png and a.jpg both becoming a.webp — the names are automatically made unique rather than one silently overwriting the other.
Is EXIF metadata carried across?
No. The image is decoded to raw pixels and re-encoded, which does not transfer metadata — so the output has no EXIF, no GPS coordinates and no camera information. That is usually welcome when publishing images. If you need those details preserved, keep your original file.