WebP Converter

Convert images to WebP for lighter pages, or bring a WebP back to PNG or JPG.

Runs on your deviceImagesWorkingNo account needed

What this tool does

WebP Converter works in three directions, chosen with a radio button. Convert to WebP re-encodes a JPG, PNG, GIF or BMP as WebP; WebP → PNG writes a lossless PNG; WebP → JPG writes the format the widest range of software can open. Each file is decoded, drawn onto a canvas at its full pixel size and encoded again, so the output has exactly the dimensions the input had.

The quality slider, 82 by default, is handed straight to the browser's own WebP or JPG encoder. There is no separate lossless-WebP switch, and what a particular browser does at the very top of the range is that browser's decision rather than a setting exposed here — so treat WebP output as lossy and pick a high number for screenshots, logos and anything carrying text. Quality is ignored when the output is PNG, which is lossless by definition.

Conversion happens inside this browser tab. The page reads each file, redraws it on a canvas and hands back a download; nothing is transmitted, and once the page has loaded the conversion itself needs no network connection. The cost of that route is that a canvas returns pixels and nothing else: EXIF, GPS tags and embedded ICC colour profiles are absent from the output, and only one frame survives, so an animated WebP or GIF converts to a single still image.

The input list is whatever browsers can decode — JPG, PNG, WebP, GIF, BMP and SVG, plus AVIF on recent versions — and that is a real limit, not a preference. HEIC photos taken on an iPhone, TIFF scans and camera RAW files have no browser decoder at all; the tool names the problem instead of failing vaguely, and points HEIC files at HEIC Converter, which does that job on the server. An SVG is rasterised at whatever pixel size the browser resolves for it, which is the size the file declares when it declares one; anything the browser hands back with no measurable size is refused rather than guessed at.

How to use it

  1. Add your images. JPG, PNG, GIF, BMP or WebP, and several at once if you like. Each file is converted as its own job with the same settings, and more than one result gives you a ZIP button as well as individual downloads.
  2. Pick a direction. Convert to WebP, WebP → PNG or WebP → JPG. The last two write that format from whatever you feed them, so they are named for the job people arrive wanting rather than restricted to WebP input.
  3. Set the quality. The slider applies to WebP and JPG output and is ignored for PNG. Push it well above the default for line art and screenshots, where lossy artefacts appear around text long before they show in a photograph.
  4. Choose a background if the output is JPG. JPG has no alpha channel, so transparent pixels are painted with the colour you pick — white unless you change it. WebP and PNG output keep transparency and leave the setting unused.

Processing & privacy

Runs on your device. Your file is processed directly in this browser.

Common use cases

Cutting page weight

Every current browser reads WebP, so replacing a page's JPG and PNG assets with WebP is usually the largest saving available without touching the layout or the markup.

A WebP something refuses to open

Older design software, a few CMS uploaders and some print services still reject the format. Convert WebP to PNG or JPG and the picture arrives at the same pixel dimensions, though the byte count moves with the new encoding.

Screenshots for a wiki or a ticket

PNG screenshots are heavy to host. Converting to WebP at a high quality keeps the text readable, and the result panel reports the before and after byte counts so you can check the saving rather than assume it — in a batch those figures describe the last file converted, while every row lists its own output size.

Keeping a transparent logo

An alpha channel survives both the trip to WebP and the trip back to PNG. Only WebP → JPG has to flatten it, and then the background colour is yours to choose.

Questions

Are my images uploaded?
No. WebP Converter decodes and re-encodes each file inside this browser tab using the canvas encoder, so nothing is sent anywhere and there is no server copy to delete, because none is ever made.
Why was I told the browser cannot write WebP?
Because it could not. Canvas quietly falls back to PNG when it cannot produce the format asked for, so the tool checks what the encoder actually returned and refuses it rather than handing you a PNG with a .webp name. Current browsers all write WebP; a very old one may not.
Does it keep transparency?
Converting to WebP keeps it, and WebP → PNG keeps it. WebP → JPG cannot, because JPG has no alpha channel — those pixels are filled with the background colour before encoding.
Will an animated WebP stay animated?
No. Only the first frame is decoded, so an animated WebP or GIF comes out as one still image. APNG Converter is the tool for moving images; it converts between APNG, GIF and animated WebP on the server.
Is EXIF or colour profile data preserved?
No. Re-encoding from canvas pixels drops camera fields, GPS coordinates and any embedded ICC profile. That is welcome when you want the metadata gone, and a genuine problem for a wide-gamut photograph that depends on its profile — convert that one with software that carries the profile through.
Should I use AVIF instead?
AVIF usually encodes smaller at a comparable quality, but fewer browsers can write it and older ones cannot display it. AVIF Converter offers that trade; WebP remains the safer default for anything a stranger will open.
Can I resize or crop while converting?
No — the output always has the input's pixel dimensions. Resize Image changes dimensions, Crop Image trims them, and Image Compressor works to a quality or a file-size target, with optional maximum dimensions.

Related tools