Convert Images to WebP
Turn JPG, PNG and more into WebP right in your browser. Batch, with a live size readout — or name the KB you need and let it find the quality.
Up to 50 at once
Drop a whole folder in. Most converters that run locally do one file at a time.
Hit an exact size
Need it under 150 KB? Type the number and the quality is tuned for you.
Five input formats
JPG, PNG, GIF, BMP and AVIF, mixed together in the same batch.
Nothing is uploaded
The conversion runs in this tab, and we check your browser can really do it.
In short: This tool handles image to WebP conversion inside your browser, in batches of up to 50, starting from JPG, PNG, GIF, BMP or AVIF. You can drive it with a quality slider or simply name a target size in KB and let a binary search find the quality that fits. Transparency comes through intact. Before anything else it checks that your browser can actually encode WebP — because some cannot, and they fail silently.
Why WebP Makes Pages Faster
At the same visual quality, a WebP is typically 25 to 35 percent smaller than the equivalent JPEG, and WebP’s lossless mode is around 26 percent smaller than PNG. That gap is the entire case for image to WebP conversion — on a web page, bytes are time.
Images are almost always the heaviest thing a page downloads, which makes them the first place to look when a site feels slow. Converting an image to WebP is one of the few optimisations that costs nothing in effort and is measurable immediately: the same picture, visibly the same, a third fewer bytes. A JPG to WebP conversion on a photo-heavy page is often the single biggest win available.
That matters beyond impatience. Largest Contentful Paint — the metric Google uses to judge how quickly a page becomes useful — is very often decided by a single hero image. Shrink that image and you move the number that search engines actually look at.
Browser support is no longer the question
WebP was the format everyone hedged against for a decade. That period is over: every current browser displays WebP, and the share of visitors who cannot is now smaller than the share who cannot run JavaScript. Fallbacks are optional rather than mandatory.
When it is not worth it
A small icon at 4 KB will not become meaningfully smaller, and a PNG to WebP conversion on flat colour that is already close to optimal gains little. The returns concentrate in photographs and large decorative images, which is also where the page weight is.
Hit a File Size, Not a Quality Number
A quality value is a setting on the encoder. A file size is what your page budget is actually written in. This tool lets you name the second one and works out the first, which is the part of image to WebP conversion that other tools leave to you.
Everyone converting an image to WebP for a website has a number in their head, and it is almost never a quality level. It is "the hero image should be under 200 KB", or "the whole gallery has to fit in a megabyte". Yet nearly every tool that will convert to WebP — including the ones running locally in your browser — hands you a quality slider and leaves the arithmetic to you.
Switch to target size, type the KB you need, and the converter searches for the highest quality that still fits: eight encodes, halving the range each time, all in this tab. You get the best-looking file that satisfies your constraint rather than a guess that you then have to check.
What the search actually does
It encodes at the top quality first — if that already fits, nothing is sacrificed. Otherwise it bisects: try the midpoint, keep it if it fits and aim higher, discard it and aim lower if it does not. Eight rounds narrows a 5–98 range to within one, which is finer than the difference you could see.
When the target cannot be met
A 4000-pixel photograph will not fit in 50 KB at any quality, and the tool says so rather than silently handing you something that misses. When that happens the answer is resolution, not compression — an image displayed at 800 pixels carries five times the pixels it needs.
A practical starting budget
For most content sites, a hero image under 200 KB and in-body images under 100 KB keeps a page comfortable on a phone connection. Set that as the target, convert to WebP in one batch, and you have a page weight you chose rather than inherited.
Choosing a Quality Level
If you would rather set quality directly, the useful range is narrower than the slider suggests. Below about 60 the artefacts become obvious; above about 92 the file grows quickly for differences almost nobody can see.
Between 80 and 90 is where most web images belong. That is where WebP does what it is known for: a JPG to WebP conversion at 85 lands noticeably smaller than the JPEG it came from with nothing visibly given up.
Photographs tolerate it well
Soft gradients and sensor noise hide compression artefacts, which is exactly the case lossy formats were designed for. Quality 82 on a photograph is usually indistinguishable from the original at any size a browser will display it.
Text and flat colour need more
Screenshots, diagrams and anything with lettering pick up halos around hard edges — the same failure mode as JPEG. Keep those above 90, or leave them as PNG where the edges stay exact.
The readout is the real answer
Move the slider and the tool encodes your first file for real and reports the size. Content matters more than the setting here: a photograph and a screenshot at the same quality can land at wildly different sizes.
Not Every Browser Can Make a WebP
Reading a WebP and writing one are different capabilities. Every current browser can display WebP, but WebKit — the engine behind Safari — still gives web pages no way to encode one. And when a browser cannot produce the format you asked for, it does not raise an error. It quietly gives you a PNG instead.
That silence is the problem. The file arrives with the name you expected, the extension you expected, and completely the wrong contents. Upload it to your site and you have shipped a PNG wearing a WebP label: bigger than the JPEG you started with, and no faster at all.
So before you add a single file, this tool encodes a one-pixel canvas and checks what actually came back. If the result is not really a WebP, the page says so and stops — no upload area, no convert button. It is a blunt outcome, and it is a much better one than an image to WebP conversion that produces a folder of files that look right and are not.
What to do if you land on that message
Open the page in Chrome, Edge or Firefox and you can convert to WebP normally. There is no setting to change in Safari; the encoder simply is not exposed. If you are on an iPhone or iPad, note that every browser there uses WebKit underneath, so switching browsers on the device will not help.
Why other converters do not warn you
Most tools that run in the browser simply call the encoder and trust the result. Some go further and list Safari as supported, which is true for reading WebP and not for writing it. The check costs three lines; it is mostly that nobody thought to look.
Lossy Only — and Why That’s Usually Fine
WebP has a lossless mode, but browsers do not expose it. Everything this tool produces is lossy WebP, and we would rather say so than let you assume otherwise.
Producing lossless WebP requires libwebp, which in a web page means shipping a few hundred kilobytes of WebAssembly to every visitor before they convert anything. On a site whose whole argument is that pages should be light, that is a trade we are not willing to make.
In practice it costs you very little. Lossy WebP at quality 80 to 90 is the right choice for photographs anyway — that is the case the format was built for, and lossless would produce a much larger file for a difference you could not see.
When you genuinely need lossless
Logos, icons, diagrams and screenshots that will be scaled or edited later deserve exact pixels. For those, PNG remains a good answer and is already well compressed for flat colour — a PNG to WebP conversion would buy you less than you think. If a PNG is heavier than you would like, compressing it is more useful than converting it.
How to Convert Images to WebP in 3 Steps
The whole image to WebP conversion happens on your own machine, so there is no upload, no queue and no waiting on a server. Your original files are never modified.
- 1
Add your images
Drag in up to 50 files at once — JPG, PNG, GIF, BMP and AVIF can be mixed in the same batch.
- 2
Set a quality, or a target size
Move the slider and watch the real output size, or switch to target size and type the KB your page budget allows. This is the step that decides what the WebP will weigh.
- 3
Convert and download
Each file shows its before and after size. Take them one by one or grab everything as a single ZIP.
Pro tip — Resize before you convert. An image displayed at 800 pixels but stored at 4000 is carrying twenty-five times the data it needs, and no quality setting recovers that.
Note — The size readout is measured on your first file. It is a real encode, not an estimate, so it is safe to plan a batch around it.
What About Transparency and Animation
Transparency comes through
WebP has an alpha channel, so a PNG to WebP conversion keeps a transparent background intact. This is one of the reasons WebP replaced both JPEG and PNG in a lot of workflows rather than just one of them.
Animation does not
WebP supports animation, but browsers cannot produce an animated one from a canvas. An animated GIF dropped here comes out as a still image of its first frame. If you need an animated WebP, that job needs a dedicated encoder and this is not it.
Your Files Never Leave This Tab
Local processing is common for image to WebP conversion, which is how it should be. This one is local too, including the encoder check that runs before you add anything.
You can verify it in about ten seconds: load the page, turn off your Wi-Fi, and convert a file. It still works, because there was never anything to send.
In-Browser vs Upload-Based Converters
Local processing is no longer the differentiator when you convert to WebP, so here is where the tools actually diverge.
| Aspect | This converter | Other tools |
|---|---|---|
| Target file size in KB | Yes, binary search | Only on upload-based tools |
| Checks the browser can encode | Yes, before you start | No — fails silently |
| Batch limit | 50 files, free | Squoosh does one at a time |
| Input formats | JPG, PNG, GIF, BMP, AVIF | Varies |
| Where conversion happens | Your browser | Mixed |
| Lossless WebP | No — see below | Server-side tools can |
The honest gap in that table is the last row: tools with a server can run libwebp and produce lossless WebP, and we cannot. For photographs it does not matter. For flat-colour graphics that need exact pixels, PNG is usually the better destination anyway.
Complete PDF Tool Suite
Discover our comprehensive collection of PDF tools designed to handle all your document needs
PNG to PDF
Bind PNG images into a single, print-ready PDF
JPG to PDF
Convert JPG images to PDF format
Merge PDF
Combine multiple PDF files into one
Compress PDF
Reduce PDF file size efficiently
PDF to PNG
Convert PDF pages to PNG images
PDF to JPG
Convert PDF pages to JPG images
PDF to Text
Extract text content from PDF files
Split PDF
Split PDF into separate pages
Edit PDF
Edit and annotate PDF documents
Organize PDF
Organize and rearrange PDF pages
Rotate PDF
Rotate PDF pages and save permanently
Page Numbers
Add page numbers to PDF with live preview
Watermark PDF
Add a text watermark to PDF with live preview
HEIC to JPG
Convert iPhone HEIC photos to JPG
Delete PDF Pages
Remove unwanted pages and download a clean PDF
Extract PDF Pages
Save selected pages as a new PDF or separate files
Sign PDF
Draw, type, or upload a signature and place it on any page
Resize PDF
Change page size to A4, Letter, or custom dimensions
Crop PDF
Trim margins, drag-select, or auto-crop white space
Flatten PDF
Make forms read-only — keep text searchable or lock to image
PDF Metadata
View, edit, or strip author, title, dates and other metadata
Grayscale PDF
Convert to grayscale or black & white to save colour ink
Extract Images from PDF
Pull embedded photos out of a PDF and save as PNG or JPG
WebP to PDF
Convert WebP images to a PDF, merge many into one file
Protect PDF
Add an open password to your PDF, entirely in your browser
Unlock PDF
Remove a known password or restrictions from a PDF, in your browser
HEIC to PDF
Convert iPhone HEIC photos to PDF
AVIF to PDF
Convert AVIF images to PDF
TIFF to PDF
Convert TIFF images and scans to PDF
BMP to PDF
Convert BMP bitmap images to PDF
OCR PDF
Make a scanned PDF searchable, entirely in your browser
Redact PDF
Permanently remove sensitive text from a PDF, in your browser
Compress Image
Shrink JPEG, PNG and WebP in batch, entirely in your browser
Resize Image
Change image dimensions in batch, with presets, in your browser
PNG to JPG
Turn PNG images into JPG, batch, with the size shown before you download
JPG to PNG
Turn JPG images into PNG, batch, with optional transparent background
WebP to JPG
Turn WebP files into JPG, batch, with every frame of an animated WebP
WebP to PNG
Turn WebP into PNG with transparency intact, or knock a solid background out
Image to WebP
Turn JPG, PNG and more into WebP, batch, or hit an exact size in KB
Image to WebP — Frequently Asked Questions
Everything people ask before converting their first batch.
Can I compress an image to a specific size in KB?
Yes — switch to target size mode and type the number. The converter runs a binary search across quality values and returns the highest quality that still fits your limit. Among the tools that convert to WebP locally, this one is unusual in offering it at all.
How much smaller will the WebP be?
Typically 25–35% smaller than the equivalent JPEG at the same visual quality. Photographs gain the most, so a JPG to WebP conversion on a gallery pays for itself immediately. Small icons and flat graphics that are already well compressed gain very little.
Why does it say my browser cannot create WebP?
Safari and older browsers have no WebP encoder available to web pages. They fail quietly rather than erroring, so an image to WebP conversion there would hand you files named .webp with PNG inside. The tool checks first and stops rather than giving you those. Chrome, Edge and Firefox all work.
Does a PNG to WebP conversion keep transparency?
Yes. WebP has an alpha channel, so a transparent PNG stays transparent. This is one of the reasons WebP can replace both JPEG and PNG rather than only one of them.
Can I make an animated WebP from a GIF?
Not here. An animated GIF comes out as a still of its first frame. Browsers cannot produce animated WebP from a canvas. That job needs a dedicated encoder, and this tool would rather say so than quietly drop your frames.
Is the output lossless?
No. Browsers only expose lossy WebP encoding. Lossless would require shipping libwebp as WebAssembly to every visitor, which contradicts the point of making pages lighter. For photographs, lossy at quality 80–90 is the right choice anyway.
Do my files get uploaded anywhere?
No. The conversion and the encoder check both happen in this tab. Load the page, disconnect from the internet, and convert a file. It still works, because nothing was ever sent.
Do I still need a JPEG fallback for WebP in 2026?
For most sites, no. Every current browser displays WebP. The share of visitors who cannot see a WebP is now smaller than the share running with JavaScript disabled. Keep a fallback only if your analytics show a meaningful audience on very old software.
Related tools
Other things you may want to do with the same images, all in your browser.
- Resize an image — do this first — dimensions save far more than quality ever will.
- Compress an image — when you need the original format kept rather than converted.
- WebP to JPG — the way back, for anything that needs to open outside a browser.
- WebP to PNG — the way back with transparency intact.
- PNG to JPG — a smaller file without leaving the formats everything accepts.
- JPG to PNG — when you need lossless or a transparent background.
Convert your images to WebP now
Drop in up to 50 files, name a target size if you have one, and see the result before you download. Image to WebP conversion runs entirely in this tab — nothing is uploaded.
Convert to WebP