What this tool is for
Convert a browser-supported image into WebP when you want one modern format for web pages, apps, product catalogs, or downloadable assets.
How to use it
- Choose a JPG, PNG, WebP, or HEIC image up to 50MB.
- Select Process Image.
- Wait for browser-side decoding and WebP encoding.
- Download the WebP and inspect transparency and file size.
What happens to your image
GuavaPix decodes the source pixels locally and encodes a WebP image. PNG transparency is retained where the browser encoder supports it; source metadata is not copied.
Practical uses
- Standardize mixed website images as WebP.
- Optimize a PNG or JPG product catalog for the web.
- Create lighter app or landing-page assets.
- Convert an HEIC photo into a web-friendly format.
One format, different sources
The browser must be able to decode the source before it can create WebP. JPG sources remain opaque, while PNG sources can keep transparency. WebP is widely supported on the modern web but may be unsuitable for older offline software.
Important limitations
- Support for uncommon source formats depends on the browser.
- Very large images can exceed device memory.
- Animation is not preserved.
- Legacy editors may not accept the WebP result.
Frequently asked questions
Which source formats can I convert?
Common browser-supported images work, and HEIC is decoded with a local module when supported.
Will PNG transparency remain transparent?
Modern browser WebP encoders preserve transparent PNG pixels.
Should I use WebP for every image?
Use it for modern web delivery. Keep original files for editing and provide another format only when older compatibility is required.
Does WebP remove metadata?
The output is created from decoded pixels and does not copy the source file's metadata blocks.

