1 Choose your PNG and AVIF files
opens the file picker natively. Calling .click() on a display:none input is refused by Safari and by some Chrome configurations, so the input stays in the layout: visually hidden, still focusable, and reachable by keyboard. There is no JavaScript in that path at all. --> Drop PNG and AVIF pictures here or click to browse — .png, .avif, identified by their contents AVIF is also accepted when your browser can decode it. Output remains WebP. AVIF sequences give only the first decoded image. The browser canvas makes an 8-bit SDR copy: color or HDR may change, metadata is left out, and the file may be larger. Your original file stays unchanged.
2 Lossless, or smaller
Either way the transparency comes across — WebP has an alpha channel just as PNG does, so nothing has to be flattened onto a background.
3 Convert them
Cancel stops before the next file. An encoder already running finishes, and completed files remain available.
# PNG to WebP The same picture, often a third off, with the see-through parts intact. > Convert PNG and AVIF images to WebP in your browser, losslessly or smaller still. Transparency is kept either way. Nothing is uploaded, there is no account, and it works offline. This is an interactive browser tool at https://abox.tools/png-to-webp/. Files are processed on the device running that browser. Any deliberate sharing or optional network feature is described on the page. What follows is its written explanation; open the address to use it. ## Your pictures are **processed in your browser**. No processing upload. The converting runs in your own browser, on your own hardware. Every browser has written WebP since 2020, so the encoder was already on your machine before you arrived — there is nothing to download and nothing to wait for. That is why this page can promise what it promises: there is no network feature on it at all, and no server on the other end to send a picture to. - ✗ No upload - ✗ No account - ✗ No size limit - ✓ Works offline - ✓ Open source ## How to convert a PNG to WebP 1. **Choose your PNG and AVIF files.** Drop them onto the picker or select them by hand. Every file is identified by its first bytes rather than by its name, so a file that is really a JPEG is turned away with a line saying so rather than converted into a copy of itself. A row that has see-through parts says so, because that is the part people are most worried about losing. 2. **Pick lossless, or pick smaller.** Lossless keeps every solid pixel the PNG had and still comes out smaller — the right answer for screenshots, diagrams, logos and anything with text in it. Smaller turns on a quality slider and is the right answer for photographs, where nobody can see the difference and the saving is enormous. 3. **Press “Convert”, and read what it says it did.** Each result gives the new size and how it compares, and then says which coding the browser actually wrote — lossless, or lossy at the quality you chose. That line is read out of the finished file rather than repeated back from the setting. 4. **Download, one at a time or all at once.** One file gives you a download button; two or more give you a zip of the lot as well. Files that share a name get a number added before the extension, so nothing quietly replaces anything else in the archive. ## The longer version [The same picture, a third smaller, with the transparency intact](https://abox.tools/guides/convert-png-to-webp/): WebP is smaller than PNG even without losing anything - and far smaller if you let it. Which of the two you want depends on what is in the picture. What each mode does, what it saves, and how to convert without uploading. ## Also in the box - [AVIF to JPG](https://abox.tools/avif-to-jpg/): The format websites save now, in the one everything has always taken. - [ID Photo Maker](https://abox.tools/id-photo/): Choose a supported country and document. Published rules and guidance are marked. - [Image Stacker](https://abox.tools/stack-images/): Average a steady burst, take the median for a clear background, or lighten a night-sky sequence. - [Image Redactor](https://abox.tools/redact-image/): What you cover is deleted from the file, not covered up in it. ## Questions ### Is my picture uploaded anywhere? No. The file is read, decoded and written by your own browser on your own hardware. This tool has no network feature of any kind — it never fetches anything and never sends anything — and the page's `Content-Security-Policy` names every address it may contact, none of which belongs to this site. ### Does the transparency survive? Yes, in both modes, and that is the main reason people convert a PNG to WebP rather than to a JPEG. WebP has a real alpha channel, so a logo with a see-through background arrives with a see-through background — there is no colour to pick and nothing gets flattened. The row for each file says whether it has any transparency in it before you convert, and the result says the transparency came across. ### What is the difference between lossless and smaller? Lossless means every solid pixel in the WebP is the pixel the PNG had, and the file is smaller anyway — usually by a fifth to a third, because WebP's lossless coding is simply better than PNG's. The one footnote is about half-transparent pixels, and it has a question of its own below. Smaller means WebP's lossy coding, which throws away detail you were unlikely to notice and can take a photograph to a tenth of its size. The rule of thumb: anything with text, flat colour or sharp edges wants lossless, and photographs want the other one. ### You say “every solid pixel”. What about the half-transparent ones? They can shift very slightly, and it is a canvas that does it rather than WebP. A browser stores a picture on a canvas with its colour already multiplied by its transparency, and that multiplication cannot be undone exactly — the fainter a pixel is, the less of its original colour survives the arithmetic. Every browser-based converter has this property, including this one, because the canvas is how the picture gets from one format to the other. \ \ What it means in practice: a pixel that is fully solid comes through bit for bit, and so does one that is fully invisible. In between, the colour stored underneath can move — measured here at up to 63 out of 255 on pixels that are less than a quarter opaque, and at most 4 on the rest. You cannot see any of it, because the pixels whose colour moves most are the ones showing least of it: a nearly-invisible pixel contributes nearly-invisible colour whatever number is stored in it. The anti-aliased edge of a logo is the only place this exists at all, and it looks the same afterwards. \ \ If you need a PNG kept as an exact archival copy, keep the PNG. If you need one to look identical and weigh a third less, that is what this does. ### How do you know it was really lossless? Because the finished file is read back and checked, rather than the setting being repeated to you. A WebP stores its pixels in one of two chunks — `VP8L` for the lossless coding and `VP8` for the lossy one — and this page looks at which chunk came out and says so on the row. It has to work that way: a canvas has no lossless flag, so asking for it means asking for the top of the quality range and trusting the browser to take the hint. Every current browser does. This page checks anyway. ### Will a WebP actually open everywhere? On the web, yes — Chrome, Edge, Firefox and Safari have all shown WebP since 2020, so there is no longer a fallback to think about for a website. Away from the browser it is patchier: Windows and macOS both preview them now, but some older desktop software, a few upload forms and a lot of e-readers still will not take one. If you are converting for something that refuses a WebP, you want the [WebP to JPG](https://abox.tools/webp-to-jpg/) converter, which is this tool pointed the other way. ### Why is my PNG so big in the first place? Because PNG is lossless and photographs are not compressible that way. A PNG is excellent for a screenshot or a logo, where large areas repeat, and terrible for a photograph, where almost nothing does — a phone photo saved as a PNG is routinely ten times the JPEG of the same picture. That is exactly the case where the lossy setting here earns its place. If the file needs to come in under a particular figure, the [Image Compressor](https://abox.tools/compress-image/) takes a target size rather than a quality. ### Does it keep the date, camera and location? No. The picture is drawn onto a canvas and a canvas holds pixels and nothing else, so any metadata around them is left behind. [EXIF Viewer & Remover](https://abox.tools/exif-editor/) reads and edits JPEG, PNG and WebP metadata without re-encoding their pictures. For AVIF, it shows available EXIF as read-only and cleans by converting the first decoded image to a new PNG; color or HDR may change. ### Can it do a whole folder at once? Yes. Drop in as many as you like — there is no limit on the number or the size, because there is no server paying for them. Each one gets its own row and its own download, and two or more give you a zip of the lot with the total saving at the top. ### Is it free, and do I need an account? It is free, and there is no account, no sign-in, no trial and no watermark. The site carries advertising, which is what pays for it; the ads are not given anything about your pictures. ### Does it work offline? Yes. Load the page once, then disconnect from the internet and it keeps working exactly as before. That is also the strongest proof available that nothing is being uploaded: a converter that sent your files away to be processed would stop the moment you unplugged, and this one does not. ### Can I also convert AVIF pictures? AVIF is also accepted when your browser can decode it. Output remains WebP. AVIF sequences give only the first decoded image. The browser canvas makes an 8-bit SDR copy: color or HDR may change, metadata is left out, and the file may be larger. Your original file stays unchanged. ## How the privacy claim is verifiable - **Processing happens in this browser.** This tool processes input and results inside your browser. Its processing code does not upload them for processing. Content-Security-Policy restricts permitted resources and connection destinations, but allowed hosts can still receive requests: the policy does not inspect payloads and alone cannot prove that nothing is sent. Compare the source with the requests for the operation you use, or complete that local operation while disconnected. - **The transparency survives, which is the usual reason people ask.** WebP has an alpha channel exactly as PNG does, so a logo with a see-through background comes out with a see-through background and there is no colour to choose and nothing to flatten. That is the difference between this page and the [WebP to JPG](https://abox.tools/webp-to-jpg/) one next door, which has to ask, because a JPEG has no alpha channel at all. - **Lossless is checked, not claimed.** A canvas has no switch for lossless WebP — the browser picks the coding from the quality it is handed, and every current one writes the lossless coding at the top of the range. That is engine behaviour rather than a guarantee in the specification, so this page does not take it on trust: every file it writes is read back, and the row tells you whether the bytes are really the lossless coding. If a browser ever stops honouring it, you will be told on the day instead of finding out later. - **What a canvas does not carry across.** The picture is decoded and drawn onto a canvas, and a canvas holds pixels and nothing else, so any text chunks, ICC colour profile or XMP block in the PNG do not survive. The pixels do — that is what lossless means here — but the metadata around them does not. [EXIF Viewer & Remover](https://abox.tools/exif-editor/) reads and edits JPEG, PNG and WebP metadata without re-encoding their pictures. For AVIF, it shows available EXIF as read-only and cleans by converting the first decoded image to a new PNG; color or HDR may change. - **What Google loads, and what it is not given.** The ad and measurement scripts come from Google, and the donate button from Buy Me a Coffee. None of them is handed anything about your pictures. Every line that reads, decodes or writes a file is served from this origin and listed in the repository. - **It works offline.** Load the page once and disconnect from the network, and the tool is unchanged. That is the simplest proof of all: a converter that sent your pictures away to be converted could not possibly manage it. **Check it yourself.** None of the above has to be taken on trust. This page is generated from the templates and config in the repository by a build script you can read and run yourself, and the result is committed to the `dist` branch — so you can diff what is served against what a build of the sources produces: https://github.com/A-Box-of-Tools/website The files worth reading first are `config/site.toml` for the Content-Security-Policy, and `src/shared/image-convert.js` for the conversion — in particular `encodeWebp`, which writes the file and then reads its own RIFF chunks back to find out whether the browser really wrote the lossless coding it was asked for.
How to convert a PNG to WebP
- Choose your PNG and AVIF files. Drop them onto the picker or select them by hand. Every file is identified by its first bytes rather than by its name, so a file that is really a JPEG is turned away with a line saying so rather than converted into a copy of itself. A row that has see-through parts says so, because that is the part people are most worried about losing.
- Pick lossless, or pick smaller. Lossless keeps every solid pixel the PNG had and still comes out smaller — the right answer for screenshots, diagrams, logos and anything with text in it. Smaller turns on a quality slider and is the right answer for photographs, where nobody can see the difference and the saving is enormous.
- Press “Convert”, and read what it says it did. Each result gives the new size and how it compares, and then says which coding the browser actually wrote — lossless, or lossy at the quality you chose. That line is read out of the finished file rather than repeated back from the setting.
- Download, one at a time or all at once. One file gives you a download button; two or more give you a zip of the lot as well. Files that share a name get a number added before the extension, so nothing quietly replaces anything else in the archive.
The longer version
The same picture, a third smaller, with the transparency intact WebP is smaller than PNG even without losing anything - and far smaller if you let it. Which of the two you want depends on what is in the picture. What each mode does, what it saves, and how to convert without uploading.
Also in the box
Questions
Is my picture uploaded anywhere?
No. The file is read, decoded and written by your own browser on your own hardware. This tool has no network feature of any kind — it never fetches anything and never sends anything — and the page's Content-Security-Policy names every address it may contact, none of which belongs to this site.
Does the transparency survive?
Yes, in both modes, and that is the main reason people convert a PNG to WebP rather than to a JPEG. WebP has a real alpha channel, so a logo with a see-through background arrives with a see-through background — there is no colour to pick and nothing gets flattened. The row for each file says whether it has any transparency in it before you convert, and the result says the transparency came across.
What is the difference between lossless and smaller?
Lossless means every solid pixel in the WebP is the pixel the PNG had, and the file is smaller anyway — usually by a fifth to a third, because WebP's lossless coding is simply better than PNG's. The one footnote is about half-transparent pixels, and it has a question of its own below. Smaller means WebP's lossy coding, which throws away detail you were unlikely to notice and can take a photograph to a tenth of its size. The rule of thumb: anything with text, flat colour or sharp edges wants lossless, and photographs want the other one.
You say “every solid pixel”. What about the half-transparent ones?
They can shift very slightly, and it is a canvas that does it rather than WebP. A browser stores a picture on a canvas with its colour already multiplied by its transparency, and that multiplication cannot be undone exactly — the fainter a pixel is, the less of its original colour survives the arithmetic. Every browser-based converter has this property, including this one, because the canvas is how the picture gets from one format to the other.
What it means in practice: a pixel that is fully solid comes through bit for bit, and so does one that is fully invisible. In between, the colour stored underneath can move — measured here at up to 63 out of 255 on pixels that are less than a quarter opaque, and at most 4 on the rest. You cannot see any of it, because the pixels whose colour moves most are the ones showing least of it: a nearly-invisible pixel contributes nearly-invisible colour whatever number is stored in it. The anti-aliased edge of a logo is the only place this exists at all, and it looks the same afterwards.
If you need a PNG kept as an exact archival copy, keep the PNG. If you need one to look identical and weigh a third less, that is what this does.
How do you know it was really lossless?
Because the finished file is read back and checked, rather than the setting being repeated to you. A WebP stores its pixels in one of two chunks — VP8L for the lossless coding and VP8 for the lossy one — and this page looks at which chunk came out and says so on the row. It has to work that way: a canvas has no lossless flag, so asking for it means asking for the top of the quality range and trusting the browser to take the hint. Every current browser does. This page checks anyway.
Will a WebP actually open everywhere?
On the web, yes — Chrome, Edge, Firefox and Safari have all shown WebP since 2020, so there is no longer a fallback to think about for a website. Away from the browser it is patchier: Windows and macOS both preview them now, but some older desktop software, a few upload forms and a lot of e-readers still will not take one. If you are converting for something that refuses a WebP, you want the WebP to JPG converter, which is this tool pointed the other way.
Why is my PNG so big in the first place?
Because PNG is lossless and photographs are not compressible that way. A PNG is excellent for a screenshot or a logo, where large areas repeat, and terrible for a photograph, where almost nothing does — a phone photo saved as a PNG is routinely ten times the JPEG of the same picture. That is exactly the case where the lossy setting here earns its place. If the file needs to come in under a particular figure, the Image Compressor takes a target size rather than a quality.
Does it keep the date, camera and location?
No. The picture is drawn onto a canvas and a canvas holds pixels and nothing else, so any metadata around them is left behind. EXIF Viewer & Remover reads and edits JPEG, PNG and WebP metadata without re-encoding their pictures. For AVIF, it shows available EXIF as read-only and cleans by converting the first decoded image to a new PNG; color or HDR may change.
Can it do a whole folder at once?
Yes. Drop in as many as you like — there is no limit on the number or the size, because there is no server paying for them. Each one gets its own row and its own download, and two or more give you a zip of the lot with the total saving at the top.
Is it free, and do I need an account?
It is free, and there is no account, no sign-in, no trial and no watermark. The site carries advertising, which is what pays for it; the ads are not given anything about your pictures.
Does it work offline?
Yes. Load the page once, then disconnect from the internet and it keeps working exactly as before. That is also the strongest proof available that nothing is being uploaded: a converter that sent your files away to be processed would stop the moment you unplugged, and this one does not.
Can I also convert AVIF pictures?
AVIF is also accepted when your browser can decode it. Output remains WebP. AVIF sequences give only the first decoded image. The browser canvas makes an 8-bit SDR copy: color or HDR may change, metadata is left out, and the file may be larger. Your original file stays unchanged.