Image converter: PNG, JPG and WebP.

Convert images between PNG, JPG and WebP, one or many at a time, and compare each file’s size before and after. It runs in your browser, so your images are never uploaded.

Choose imagesor drop them here

Convert to

PNGJPGWebP

Quality 85%

Runs in your browser. Nothing you add here is uploaded or stored.

How to convert an image

Choose your images, or drop them on the box above. You can add several at once.
Pick the format to convert to: PNG, JPG or WebP.
Set the quality for JPG or WebP, from 40% to 100%. It starts at 85%; lower settings make smaller files with more visible compression. PNG is lossless, so it has no quality setting.
Convert, then download each file. The list shows every file’s size before and after.

A few things to know:

Transparency. PNG and WebP keep transparent areas. JPG can’t store transparency, so transparent areas become white.
Size and name. Images keep their width and height, and their file name with the new extension: hero.png becomes hero.webp.
Input. Besides PNG, JPG and WebP, you can add other images your browser can open, such as GIF. Animated images are saved as a single still frame.
Metadata. Each image is redrawn from its pixels, so metadata such as camera details and GPS location isn’t copied to the new file.
Browser support. If your browser can’t save a format, the tool says so instead of saving a different one. Try another format or browser.

Use WebP for faster pages with Codex

Images are usually the heaviest part of a page. A WebP file is usually noticeably smaller than a JPG of similar quality, and far smaller than a PNG photo, and all major browsers display WebP. Converting before the images go into your project is the easiest speed-up there is.

Convert before you commit. Convert hero photos, screenshots and the images you generated for a design to WebP at 75–85% quality, check that they still look right, and put them in your project’s image folder, such as public/images.
Keep PNG where it matters. If WebP blurs fine lines or small text in a graphic, keep that one as PNG. Logos and icons are usually best as SVG.
Automate large batches. This tool is quickest for a handful of images. For dozens, ask Codex to add a conversion step to your build instead.

Then tell Codex to use the new files:

Switch to WebP images

Use the WebP images in [public/images] for [the landing page]. Replace every reference to a PNG or JPG with its .webp file, give every <img> a width and height so the layout doesn't shift while it loads, and lazy-load the images below the first screen.

Frequently asked questions

Is the image converter free?

Yes. There is no sign-up, no watermark and no daily limit.

Are my images uploaded?

No. Your browser reads, redraws and saves each image on your device. Converted files stay in the page’s memory until you convert again or close the tab. The site only counts that the tool was used, never what you put in.

Is WebP better than PNG or JPG?

For most images on a website, yes. WebP files are usually smaller than JPG at a similar quality, and unlike JPG, WebP supports transparency. JPG is still the safest choice for email or older software that can’t open WebP, and PNG keeps every pixel exactly, which matters for some screenshots and graphics.

Why is my converted file bigger?

Converting a JPG or WebP to PNG usually makes it bigger, because PNG stores every pixel without lossy compression. A very high quality setting can also make a WebP or JPG larger than the original. For a smaller file, choose WebP or lower the quality.