Image Format Converter
Convert images between PNG, JPEG, and WebP right in your browser. Pick a target format, tune quality, and download - nothing is uploaded.
- Free, no account
- No watermark
- No usage limit
About the Image Format Converter
Convert an image between PNG, JPG, WebP, and AVIF right here in your browser. Drop a file or a whole batch, pick the format you want, tune the quality if it's a lossy target, and download. It is free and instant, with no sign-up.
Most free converters either run your browser's built-in encoder, which works but leaves the files fatter than they should be, or they upload your image to a server you know nothing about. This one does neither, it runs the real encoders locally, the same MozJPEG, libwebp, and AVIF codecs the command-line pros install a toolchain to get, so the output holds up next to a proper CLI and your file never leaves your machine. It also opens iPhone HEIC photos your browser can't read on its own, and it exports AVIF, the two formats that make basic converters give up.
How to use
- Drop your images into the box, click to browse, or paste one straight from the clipboard. It reads PNG, JPG, WebP, AVIF, GIF, BMP, and iPhone HEIC/HEIF, and you can drop a whole batch at once to convert them together.
- Choose the format to convert to: PNG, JPG, WebP, or AVIF. All four are always available, since the tool brings its own encoders rather than relying on the browser's.
- Tune the quality for a lossy target. JPG, WebP, and AVIF each show a slider, and 80 to 90 looks clean while staying small. PNG hides the slider because it's always lossless.
- Rotate or flip if the shot came in sideways. One click each, and it's optional.
- Hit Convert. You'll see the old size next to the new size for every file. Download one, or grab the whole batch as a single ZIP.
It keeps your pixel dimensions, so what happens here is a change of format rather than a resize. For different dimensions, use the image resizer instead. No watermark, no queue, no daily cap. It does not work offline from a cold start, though, because each format's codec is fetched the first time you ask for it rather than arriving with the page. There are eleven of those files in the built site and they come to 9,955,568 bytes between them, which is exactly why they are not all shipped up front.
Why the output actually holds up
A lot of in-browser converters lean on whatever encoder the browser happens to ship. For a quick throwaway that's fine, but the files come out heavier than they need to be, and the browser can't touch AVIF or open a HEIC at all. This tool loads the real encoders instead. MozJPEG for JPG, libwebp for WebP, a genuine AVIF encoder, and oxipng for PNG, the exact tools people install a command line to get. They run on your own machine, so a JPG comes out as tight as MozJPEG makes it, a PNG gets losslessly squeezed by oxipng and lands smaller than most converters bother to make it, and AVIF is a real encode rather than a browser fallback.
And because every byte of that work happens locally, nothing is uploaded. The free upload-based converters ask you to hand your file to a stranger's server, which is a genuinely bad idea for a contract screenshot, an unreleased design, or a photo with your kid in it. Here the image never leaves your device. It even works on a locked-down work laptop where you can't install a thing.
Picking a format without overthinking it
For a website, WebP is the easy call. It compresses a photo noticeably smaller than JPG at the same visual quality, it keeps transparency, and every current browser reads it. If you're chasing a faster page or a greener Lighthouse score, converting your PNGs and JPGs to WebP is usually the single biggest win, since images are the heaviest thing on most pages.
Reach for JPG when the file has to open everywhere with zero fuss: an email attachment, a print shop, a marketplace listing, some fifteen-year-old desktop app. It's lossy and it can't hold transparency, but nothing on earth refuses to open it.
PNG is for logos, icons, screenshots, diagrams, anything with crisp text, hard edges, or a transparent background. It's lossless, so the pixels come back exact. One nice touch, the PNG runs through oxipng on the way out, so it lands smaller than the PNG most tools hand you, same picture with fewer bytes.
AVIF is the newest and the smallest, and it'll usually beat even WebP by a fair margin. Use it when you want the absolute lightest file and you know the destination reads AVIF (modern browsers do, plenty of older apps still don't). It encodes slower than the others because it works harder to shrink, so a big batch takes a moment.
And the job this tool does constantly, going the other way. Someone hands you a WebP or an AVIF and your CMS, your email client, or some old program flatly refuses it. Convert it down to JPG or PNG and it opens.
The traps that catch people
Three surprises worth knowing before you convert.
Convert a transparent PNG to JPG and that transparency has to go somewhere, because JPG has no way to store it. A lazy converter fills the see-through pixels with black and hands you a logo sitting on an ugly black block. This tool fills them with white instead, so you get a clean result you can actually use. If you need to keep the transparency, don't go to JPG at all, convert to PNG, WebP, or AVIF, all three hold an alpha channel.
Going from JPG to PNG does not make the image look better, and people expect it to. PNG is lossless, so it faithfully copies whatever the JPG currently shows, including any blur or blockiness already baked in. It freezes the current state, it can't bring back detail that's already gone. If a JPG looks rough, the only real fix is the higher-quality original.
The file can also come out bigger than it went in. Convert a photo to PNG and it'll usually grow, since lossless encoding can't pack photographic detail as tightly as JPG or WebP, and converting a tiny flat-color PNG to JPG can inflate it too. The before-and-after size sits right next to each file, so you'll never ship a worse one by accident. (If all you want is a smaller file in the same format, that's a compression job, and the image compressor is built for it.)
Frequently asked questions
Can I actually convert an iPhone HEIC photo here?
Yes, and that's the point of a lot of visits. Most browser-based converters can't open HEIC because the browser itself has no idea how to read it, so the file just fails to load. This one carries its own HEIC decoder, so a raw .heic straight off an iPhone loads and converts to JPG, PNG, WebP, or AVIF like anything else. If the HEIC holds several images, you get the main one.
How is the AVIF here different from other online AVIF converters?
It's a real AVIF encode running on your machine with a proper quality slider, not a file quietly shipped off to a server to be squeezed there. You get AVIF's full size advantage without uploading a thing. One heads-up: AVIF takes longer to encode than JPG or WebP because it does far more work to hit that smaller size, so a large image or a big batch won't be instant.
What if one file in a batch won't convert?
The rest still go through. Each image is processed on its own, so a corrupt file or a format the tool can't read fails by itself and drops into a short error list under the results, while every good file converts and shows up ready to download. One bad file never sinks the whole batch, so you're not stuck redoing forty images because the fifth one was broken. Fix or drop the ones that failed and move on.
What happens to my photo's GPS location and camera details?
They're removed. Converting keeps the pixels and drops the metadata, so the GPS coordinates, camera model, and timestamp don't ride along with the new file. That's good for privacy, you're not accidentally posting your home address inside a photo. Two small side effects: a shot that relied on an orientation flag can come out rotated, and a wide-gamut color profile is dropped so the image reads as standard sRGB. Both are fine for the web, but keep your original if it's headed to print.
My animated GIF turned into a single still frame. Why?
Because the conversion is a still-image job, so it captures one frame and not the motion. An animated GIF or animated WebP comes out as a single frozen picture. If you need to keep the movement, this isn't the right fit, use a dedicated GIF or video converter that understands multiple frames.
Is anything sent to a server?
No. Reading the file, converting it, and building the download all happen inside your browser. You can prove it: open the network tab and run a conversion. What goes out is a request for the codec that conversion needs, and your picture is not among the things that leave. That first request is the reason a converter with no connection at all gives you an error, and switching from JPG to AVIF later asks for a second one, because each format brings its own.