Image WebP Converter
Drop images into the area above and conversion starts immediately. Move the quality slider to convert again, then check each card for output size and savings before downloading one file or the whole ZIP.
The picker is intentionally broad. Conversion starts with formats your browser can read, while files such as HEIC or TIFF that the browser cannot decode are explained per card.
Up to 20 MB · all image extensions attempted · WebP outputready to use.
- Visible firstKeep the input and result positions clear.
- Results firstPut the main number up front and keep the process secondary.
- Less to askNo sign-up or extra information before using the tool.
Decide quality, read the result cards, and keep your originals
Converting to WebP means re-saving an image the browser has already decoded into the WebP format. This page never sends your files to a server; it uses only the File API and the canvas toBlob flow. That suits blog thumbnails, shop product photos and CMS uploads, where file size must drop but on-screen quality must hold.
The flow is short. Conversion starts the moment images are added, and changing the quality converts the same files again at the new value. You make the decision in the cards below: each one shows output size, savings against the original, a status, and its own Download button.
What this tool does and does not do
This is a format converter rather than a plain compressor: it rewrites the output as WebP. JPGs become WebP photos, while PNG and BMP become WebP images that keep their alpha channel.
It does not edit or resize the original. If you also need smaller pixel dimensions, use the resizer; if you want to keep the format and only shrink the file, use the compressor.
Why conversion starts on its own
By the time a file arrives, every value the tool needs is already set. The output format is fixed to WebP and quality has a default, so there is no reason to make you press one more button.
Changing quality re-runs the conversion when you release the slider. While you drag, only the number updates, so a batch of large images is not re-encoded at every intermediate value.
Choosing 60, 75, 80 or 90 percent
Quality is the only variable you set here. Use the list below as a starting point and confirm with the savings and preview on each card.
- Around 60% — list thumbnails and quick share images where fine detail does not matter
- 75-80% — most web photography, including blog body images and secondary product shots
- Near 90% — hero product shots, portfolio work, and images containing text or a logo
- What breaks first at low quality — letter strokes, skin gradients, and wide flat areas such as sky
How to read a result card
The thumbnail sits on the left, the file name with original size and dimensions in the middle, and the status plus the Download button on the right. The lower line puts output size and savings side by side at the same height.
On a wide screen the cards sit two per row, which makes comparison quick. Save the cards with a solid saving and a clean preview; for any card that reports an increase, lower the quality and look again or keep the original.
Batches and the ZIP flow
Drop twenty-odd product thumbnails or article images at once and the queue tracks each file separately. One failure does not block downloads for the files that succeeded.
When you want everything, ZIP all packages the successful results in one archive. Clearing failed and larger-than-original cards before you build the ZIP keeps the download tidy.
Local conversion without uploads
Your current browser reads and converts the images. Because nothing is uploaded for conversion, the risk profile differs from server-side converters.
Working in the browser also means inheriting its limits. Very large images and long queues depend on device memory and processing speed.
Why HEIC, HEIF and TIFF fail
The file picker deliberately accepts HEIC, HEIF and TIFF so you do not have to hunt for a file twice. That permissiveness is not a promise that the format converts.
Real conversion begins only after the browser decodes the image. When it cannot, that card shows an error while the other files continue. The same file may behave differently in Safari, Chrome and Edge.
Animation in GIF, APNG and SVG
Canvas-based saving usually stores the single frame the browser painted. Full GIF or APNG animation and scripted SVG behaviour should not be assumed to survive.
If an animated banner or sticker has to keep moving, play the downloaded file before treating it as final. When you only need a static key image, this behaviour works like frame extraction.
Worked example: four product images
Say you add three JPG photos and one PNG logo for a product detail page. Read the cards produced at the default 80% first.
If the three photos dropped 30-60% and look unchanged at a glance, they are ready to save. If the PNG logo softened or barely shrank, compare again at 90%; when there is still no gain, keep the original PNG.
Checklist before downloading
Four checks prevent almost every redo.
- No failed card is left in the queue
- Output size on the card really is smaller than the original
- Text, faces, product edges and transparent areas survived the preview
- The originals are kept somewhere rather than deleted immediately
Where WebP fits and where it does not
Separating distribution copies from archive copies makes the decision easy.
- Good fit — blog body images, product thumbnails, CMS media uploads, images shared in chat
- Good fit — anywhere a smaller file at the same on-screen quality speeds up loading and uploading
- Poor fit — camera originals, layered working files, and sources you will colour-grade later
- Poor fit — print-ready deliverables that must not pass through lossy compression again
Browser technology behind the page
The core is the File API for reading local files and the toBlob flow that exports a canvas as a WebP blob. On start-up the page encodes a 1x1 canvas to check that this browser really returns WebP, and it refuses to convert when it does not.
Supported formats, alpha handling and the speed of large images all depend on the browser implementation.
Frequently asked questions
What does this WebP converter do?
It re-saves images your browser can read, such as JPG, PNG and AVIF, as WebP files. Nothing is sent to a server; the conversion finishes inside the browser you are using.
Do I have to press a convert button?
No. Conversion starts as soon as images are added, using the selected quality. Changing the quality converts the same files again at the new value.
Which quality percentage should I use?
Start around 60% for small thumbnails, 75-80% for ordinary web photos, and near 90% for product or portfolio shots where detail matters. Decide from the savings and the preview shown on each card rather than the number alone.
Are my images uploaded to a server?
No. The images you pick are read and converted to WebP by your current browser. This tool does not upload them for conversion.
Do HEIC, HEIF and TIFF convert?
You can select them, but success is not guaranteed. Conversion only runs when your browser can decode the format; files it cannot read stay in the queue as per-card errors.
Is GIF, APNG or SVG animation preserved?
Not reliably. Canvas conversion often stores only the static frame the browser painted. If motion matters, play the downloaded file before treating it as final.
The output is larger than the original. Why?
Heavily compressed JPGs and very small PNGs gain nothing from being re-encoded and can grow. When a card reports an increase, lower the quality and compare again or keep the original file.
Can I download several files at once?
Yes. After conversion, take individual files with the Download button on each card, or save every successful result together with ZIP all.
Can I use PNGs with transparent backgrounds?
Yes. WebP supports an alpha channel, so transparent areas survive the conversion. Very low quality can roughen the edges, so compare logos and icons at a higher setting.