Convert Images to WebP
Turn PNG and JPG into WebP in bulk, and see the real size change.
Encoding happens in this tab — no upload, no file capBatch-convert PNG and JPG to WebP with a quality you choose
or drag & drop them here, or paste one from your clipboard (Ctrl+V). Drop as many as you like — no file cap, no size cap.
PNG · JPG · WebP · GIF · AVIF
JPEG has no alpha channel. If the source image has transparency, those areas are filled with this colour (white by default) and the result says so. Nobody should discover their logo went out on a black background.
Lossless keeps every pixel (quality 1 — the only lossless lever a browser encoder exposes). It is a real alternative to PNG, but on noisy images it can come out larger than the original: the table below reports the actual bytes, never a promise.
Results
Choose your images and every file shows up here with its original size, its new size and the real difference — including when the output is bigger.
How it works
Everything runs in your browser: images are never uploaded, there is no account, no queue and no daily limit. Re-encoding also drops the original EXIF metadata, location included.
About converting images to WebP
Select or drop as many PNG, JPG or GIF files as you like and each one comes back as a .webp, converted in this tab by your browser’s own encoder. There is no per-file cap, no daily quota and no queue, because there is no server doing the work and no marginal cost per image to ration. Files are processed one after another, each with its own download, and the ceiling is your device’s memory and patience — a folder of small graphics is instant, a hundred 24-megapixel photos is a coffee break.
A quality control sits on top of that, because converting in bulk at some unknown fixed setting is how sites ship images that are smaller and visibly worse. Pick a quality, convert, and each file reports its real byte count before and after — the actual delta, not an estimate. That readout exists because the saving is not guaranteed. Measured with this very encoder, a PNG of random noise came out larger as a WebP than it went in: 58,192 bytes against 58,020. Google’s own tooling concedes the same: Android Studio’s converter offers to skip files whose encoded version would be larger than the original.
The awkward truth about lossless, since people arrive looking for exactly that: this page cannot produce true lossless WebP. The browser API it is built on takes a format and a quality number, which MDN describes as applying to “file formats that support lossy compression (such as image/jpeg or image/webp)”. There is no switch for WebP’s separate lossless mode, so treat everything here as lossy even at the top of the slider. For genuine lossless WebP, use cwebp with its lossless flag, Squoosh, or Android Studio, which documents switching to lossless automatically at quality 100 when minSdkVersion is 18 or higher. The gain is real: Google puts lossless WebP about 26% below the same PNG.
Second honest limit: converting an already-compressed JPEG re-compresses it. Google’s 25–34% figure against comparable JPEG describes encoding both formats from the same original, not re-encoding a JPEG that already went through a lossy pass. Doing that adds a fresh generation of loss over the old one: usually invisible at high quality, very visible at low quality, especially on flat colour and text. Convert from your masters when you have them. Note what this tool is not: a format converter with a quality dial is not a target-file-size compressor. “Get this under 50 KB” means searching over quality with a re-encode per attempt — a different algorithm, and a different page.
What you get is bytes off the wire, not a ranking bonus. WebP is Google’s own format, Chrome’s Lighthouse audit recommends modern formats over JPEG and PNG, and caniuse puts WebP at roughly 96% of global browser usage, so a fallback is cheap insurance rather than a necessity — the block below has the picture element. Transparency survives, since WebP carries alpha in both modes. Three things do not: an animated GIF converts as its first frame only, EXIF and ICC data are dropped by the canvas round trip (good for privacy, bad if you need copyright metadata), and WebP tops out at 16,383 pixels per side. Everything stays on your machine, which with unreleased product photos is the difference between a workflow and a leak.
How to actually serve WebP, and where not to bother
Converting the files is the easy half. The half that decides whether visitors see your images is how you reference them. The pattern below is the one MDN documents: the browser examines each source element’s srcset, media and type attributes and picks a compatible image, skips any source whose type it does not support, and if nothing matches — or the browser does not understand picture at all — it loads the img src instead. That last clause is what makes it safe to ship.
<picture>
<source srcset="hero.webp" type="image/webp">
<img src="hero.jpg" alt="Describe the image here"
width="1200" height="630" loading="lazy" decoding="async">
</picture>| Where the image is going | Convert to WebP? | Why |
|---|---|---|
| A website you control | Yes | This is the case WebP was designed for. Lighthouse flags oversized JPEG and PNG and recommends modern formats; the fallback above covers the small remainder of browsers. |
| An Android app’s resources | Yes — but not with a web tool | Android Studio does it in place: right-click an image file or a folder and choose Convert to WebP. Lossless and transparent WebP need API level 18 or higher, lossy needs 14, and 9-patch files are skipped automatically. |
| An email newsletter | No | Mail is rendered by mail clients, not by browsers, and the picture fallback you rely on for the web is not something you can count on there. Stay with JPEG or PNG. |
| A file someone else must open | No | Older desktop software and non-subscription Office releases still refuse .webp. If a colleague has to open the file, send PNG or JPG — that is the reverse trip, and it has its own page. |
| Print, or anything going to a press | No | Print workflows want CMYK and embedded ICC profiles. A canvas re-encode is sRGB and drops the ICC profile, so keep TIFF or high-quality JPEG for print. |
| An image that must hit an exact KB limit | Not here | A hard size budget needs a search over quality with a re-encode per attempt, not a single fixed setting. Convert here first if the format is the goal; use a target-size compressor if the number is. |
One last thing worth internalising, because it is the difference between an honest conversion and a superstition. WebP is smaller than the JPEG or PNG that the same source would have produced — Google measures 25–34% against comparable JPEG and about 26% against PNG for lossless — but it is not smaller than every file it meets. Google’s own Android tooling ships a checkbox to skip images whose WebP would come out larger, which tells you how routine the exception is. So convert, look at the two numbers this page prints for each file, and keep whichever one is actually smaller. That is a two-second habit that quietly beats any claim on a converter page, including ours.
FAQ
Does using WebP hurt SEO?
No. WebP is Google’s own image format, and Chrome’s Lighthouse performance audit recommends AVIF and WebP over JPEG and PNG for exactly this reason. There is no ranking penalty for the container — what search engines care about is that the page loads fast and the image is described properly. So keep the descriptive filename, keep the alt text, keep the image in your sitemap, and serve a fallback with the picture element so that no visitor sees a broken image. The format change is a performance change, not a magic ranking lever.
Will WebP break older browsers?
Very rarely now. caniuse puts WebP at about 96% of global browser usage — Chrome from 32, Firefox from 65, Edge from 18, iOS Safari from 14 — and MDN notes that macOS support requires Safari 14 with Big Sur or newer. The safe pattern costs three lines: a picture element with a WebP source and a JPG or PNG in the img fallback. MDN describes the rule that makes it work: a source whose type the browser does not support is skipped, and if no source matches, the img src is used.
Can I get true lossless WebP from this page?
No, and no browser-based canvas converter can. The encoding API accepts a quality number for lossy formats and exposes no lossless mode for WebP, so even at maximum quality you are getting the lossy encoder. For genuine lossless output use cwebp -lossless, Squoosh, or Android Studio, which documents switching to lossless automatically at quality 100 when minSdkVersion is 18 or higher. Google puts lossless WebP at roughly 26% below the equivalent PNG, so it is worth the extra tool when you need it.