Image to WebP Converter
Convert PNG, JPG and JPEG images to WebP instantly with adjustable quality, batch conversion, previews and one-click downloads.
- Free
- No signup
- Browser-based
- Fast processing
- Batch conversion
Drag & drop images here
or
PNG • JPG • JPEG • WebPWebP for the web, PNG for lossless, JPG for maximum compatibility.
Caps the longer side. Smaller images are never enlarged.
JPG has no alpha channel, so transparent pixels must be filled.
No images yet. Drop PNG, JPG, JPEG or WebP files above to begin.
Supported conversions
Every conversion listed here is implemented and runs in your browser. Nothing else is offered.
- PNG → WebP
- JPG → WebP
- JPEG → WebP
- WebP → PNG
- WebP → JPG
- PNG ⇄ JPG
Batch conversion, quality control, resizing and per-file download are available for all of them. GIF and BMP files are accepted where your browser can decode them; an animated GIF converts as a single frame.
.webp — which is exactly what the previous version of this page did.Converting images to WebP
What is WebP?
WebP is an image format created by Google for the web. It supports lossy and lossless compression, transparency and animation, and is designed to produce smaller files than PNG or JPEG at comparable visual quality. Every browser in current use displays it.
How do I convert PNG to WebP?
- Drop your PNG files onto the upload area, or press Select images.
- Leave Convert to set to WebP.
- Adjust the quality slider — 80 is a sensible default.
- Press Convert images.
- Download each file, or use Download all for a ZIP.
How do I convert JPG to WebP?
Identically. The tool accepts .jpg and .jpeg alongside PNG and WebP, and you can mix formats in one batch — each file's original format is shown on its card so you can see what is converting to what.
Does converting to WebP always reduce file size?
No, and any tool that promises it is wrong. WebP is usually smaller for photographs, but re-encoding an already-optimised file or a flat graphic with few colours can produce something larger. When that happens this tool says "Output is 12% larger" rather than reporting a saving.
Is WebP lossless?
The format supports both lossy and lossless encoding. The browser's canvas encoder that this tool uses produces lossy WebP only — quality 100 is the top lossy setting, not lossless. For genuine lossless WebP you need a command-line encoder such as cwebp -lossless. There is deliberately no "lossless" switch here, because it could not be honoured.
PNG vs JPG vs WebP
| Format | Transparency | Typical use | Compression |
|---|---|---|---|
| PNG | Yes | Graphics, logos, screenshots | Lossless |
| JPG | No | Photographs | Lossy |
| WebP | Yes | Web images | Lossy or lossless |
The single most practical difference is the transparency column. A photograph has no transparency, so JPG and WebP compete purely on size and quality. A logo or a UI screenshot usually does, which rules JPG out entirely unless you are willing to flatten it onto a background.
Image formats, quality and page speed
PNG to WebP conversion
PNG stores every pixel exactly. That is ideal for a logo with hard edges and terrible for a photograph, where the file ends up several times larger than a lossy format would need. Converting photographic PNGs to WebP is where the biggest savings live — a screenshot of a photo saved as PNG can easily drop by 80% or more.
Flat graphics are a different story. A two-colour icon is already tiny as a PNG, and a lossy WebP of it may be larger as well as slightly blurred around the edges. Check the reported size before replacing the original: this tool shows both numbers precisely because the answer varies.
Transparency carries across cleanly. WebP has a full alpha channel, so a PNG with a soft shadow or an anti-aliased edge converts without the halo you would get from flattening onto a background.
JPG and JPEG to WebP conversion
.jpg and .jpeg are the same format; the two extensions are a historical accident from the 8.3 filename era. Both are handled identically here.
Converting JPG to WebP means re-encoding lossy data with a different lossy codec. Detail already discarded by the JPEG encoder cannot come back, and a second lossy pass discards a little more — this is generational loss, and it is why converting the same file back and forth repeatedly degrades it. Convert from the highest-quality source you have, once.
In practice a WebP at quality 80 from a good JPG source is typically 25–35% smaller at visually equivalent quality. That is a genuine win for a web page, and not worth doing to an archive of family photos where the original JPGs are the masters.
WebP to PNG and WebP to JPG
The reverse direction matters more than people expect, usually because something downstream cannot read WebP — an older design tool, a print service, a marketplace upload form.
WebP to PNG is lossless as a conversion, but it cannot restore what a lossy WebP already threw away. You get a PNG that looks exactly like the WebP did, at a considerably larger file size. That is the right trade when you need compatibility, and the wrong one if you were hoping to recover quality.
WebP to JPG runs into the alpha problem. JPEG has no transparency, so the transparent pixels must become something. This tool detects transparency, tells you it found it, and asks for a colour — because a logo that silently arrives on a black background is a genuinely annoying way to discover the limitation.
Choosing a quality setting
The quality number is not a percentage of anything and does not map linearly to file size or to perceived quality. It is an encoder parameter, and the relationship differs per image.
- 50 — visibly soft on detailed photographs; fine for a large blurred background.
- 75 — a reasonable floor for photographic content on a web page.
- 80 — the default here, and a good general choice.
- 90 — for images with text, screenshots or sharp edges, where artifacts show first.
- 100 — the top lossy setting. Files grow sharply for very little visible gain, and it is still not lossless.
The most useful habit is to convert one representative image at two or three settings and look at them at full size before committing a whole batch.
Resizing while converting
Resizing usually saves more bytes than any amount of quality tuning. A 4000px-wide photo displayed in a 800px column is carrying sixteen times more pixels than the page can show, and no codec fixes that.
Aspect ratio is locked by default. Type a width and the height follows; type a height and the width follows. If you set both with the lock on, the image is fitted inside those bounds rather than stretched to them, because that is the only reading of "keep aspect ratio" that does not distort. Unlocking is possible and deliberately requires a click.
The presets cap the longest edge, which handles portrait and landscape correctly in one setting, and never enlarge an image that is already smaller — upscaling adds bytes and invents detail.
Transparency and backgrounds
Whether an image is transparent is checked by sampling its alpha channel rather than by trusting the file extension, since plenty of PNGs are fully opaque. When transparency is found the card says so, and the background control appears only when it is actually needed — converting to JPG.
Previews sit on a checkerboard so transparent areas read as transparent rather than as white, which matters when you are deciding whether a background colour is required at all.
Metadata and orientation
Browser-based conversion through the Canvas API discards metadata. EXIF fields — camera model, exposure, timestamps and any GPS coordinates — do not survive. For publishing to the web that is usually a benefit, and it is worth knowing that stripping location data from photos is a side effect you get here for free. If you need the metadata preserved, this is the wrong kind of tool.
Orientation is handled separately and correctly. Photos from phones often carry a rotation flag rather than rotated pixels, and a naive converter produces sideways images. Here the image is decoded with orientation applied, so the rotation is baked into the output pixels and the result stays upright even though the EXIF tag itself is gone.
Batch conversion and memory
Decoding a large image allocates width × height × 4 bytes — a 6000×4000 photo is roughly 96 MB as raw pixels before any encoding. Starting fifty of those at once is how a browser tab runs out of memory.
So the queue processes a few images at a time, releases each canvas as soon as its blob exists, and revokes object URLs when files are removed or the page is closed. Progress reflects genuine completions, not a timer.
WebP and page speed
Smaller images mean fewer bytes over the network, which usually helps. But image size is one input to page speed among many: a render-blocking script, a slow server response or a large font can each dominate.
For Core Web Vitals specifically: converting the LCP image to WebP can improve Largest Contentful Paint, because a smaller file finishes downloading sooner. It does nothing for Cumulative Layout Shift unless you also set explicit width and height attributes so the browser can reserve space, and nothing whatsoever for Interaction to Next Paint, which is about JavaScript. Measure before and after rather than assuming.
Using WebP on a website
The safest pattern is a <picture> element with a fallback. Browsers that understand WebP take it; anything else quietly uses the JPG, with no JavaScript involved:
<picture> <source srcset="image.webp" type="image/webp"> <img src="image.jpg" alt="Example image" width="1200" height="800"> </picture>
Keep the width and height attributes on the img. They cost nothing, and without them the browser cannot reserve space and your layout shifts as each image arrives.
Privacy
Everything here happens in the page. Files are read with the File API, decoded and drawn to a canvas, encoded to a blob and offered as a download. No request carries your image anywhere, nothing is logged, and closing the tab is all the cleanup required.
That is worth caring about for images specifically. A screenshot of a dashboard, a scanned document, a photo with location data in it — all of these routinely get dropped into online converters, and most of them upload.
Common conversion problems
- The output is larger. The source was already well compressed, or it is a flat graphic. Try a lower quality or keep PNG.
- Transparency turned black. You converted to JPG. Choose a background colour — this tool asks first.
- The photo is sideways. A converter that ignored EXIF orientation. Not an issue here.
- The file will not open elsewhere. Something in your pipeline does not read WebP. Convert back to PNG or JPG.
- The image looks soft. Quality set too low, or an upscale. Raise the quality; never enlarge.
- The browser stalls on a big batch. Very large images consume real memory. Convert in smaller groups.
Frequently asked questions
What is WebP?
WebP is an image format developed by Google for the web. It supports both lossy and lossless compression as well as transparency and animation, and it is designed to produce smaller files than PNG or JPEG at comparable visual quality. Every current browser can display it.
How do I convert PNG to WebP?
Drop your PNG files onto the upload area or use Select images. Leave the output set to WebP, adjust the quality slider if you want, then press Convert. Each result shows its new size next to the original, with a Download button.
How do I convert JPG to WebP?
Exactly as for PNG — the tool accepts .jpg and .jpeg alongside PNG and WebP. Add the files, keep WebP as the output format, set a quality and convert. You can mix PNG and JPG files in the same batch.
How do I convert JPEG to WebP?
JPEG and JPG are the same format with two common extensions, so the process is identical. Files ending .jpeg are accepted and converted the same way, and the output is named with a .webp extension.
Can I convert WebP to PNG?
Yes. Add your WebP files and change the output format to PNG. PNG supports transparency, so any transparent areas in the source are preserved.
Can I convert WebP to JPG?
Yes. Change the output format to JPG. Because JPG has no alpha channel, if any of your images contain transparency the tool asks you to choose a background colour and fills the transparent areas with it rather than picking one silently.
Does WebP reduce file size?
Usually, but not always. WebP typically produces smaller files than PNG for photographs and than JPEG at similar quality, though the result depends on the image content and the quality setting. Re-encoding an already well-optimised file can make it larger — when that happens this tool says the output is larger rather than reporting a saving.
Is WebP smaller than PNG?
For photographic content, almost always and often dramatically, because PNG is lossless and stores every pixel exactly. For flat graphics, logos and screenshots with few colours the gap narrows and PNG can occasionally win. The tool shows the actual numbers for your file.
Is WebP smaller than JPG?
Generally yes at comparable visual quality, though the margin varies with the image and the encoder. The browser's built-in WebP encoder is not the most aggressive available, so results here may differ from a command-line tool such as cwebp.
Is WebP better than PNG?
For most web imagery, yes — smaller files with transparency support. PNG remains the better choice when you need guaranteed lossless output, when you are editing and re-saving repeatedly, or when a tool in your pipeline does not read WebP.
Is WebP better than JPG?
For the web, usually: smaller at similar quality, and it supports transparency, which JPG cannot. JPG is still the safer choice for maximum compatibility with older software, cameras and print workflows.
Does WebP support transparency?
Yes. WebP supports an alpha channel in both its lossy and lossless modes, which is one of its main advantages over JPG. Converting a transparent PNG to WebP keeps the transparency.
Does JPG support transparency?
No. The JPEG format has no alpha channel at all. Any transparent area has to be filled with a solid colour, which is why this tool asks you to choose one before converting a transparent image to JPG.
Is WebP lossless?
WebP supports both lossy and lossless encoding. However, the browser's canvas encoder used by this tool produces lossy WebP only — quality 100 is the highest lossy setting, not lossless. If you need true lossless WebP, use a command-line encoder such as cwebp with its lossless flag.
What quality should I use for WebP?
80 is a good default for photographs and is what this tool starts with. Drop to 60–70 for large background images where fine detail does not matter, and raise to 90 for images with text or sharp edges. Compare a few settings on your own image rather than trusting a single number.
Does conversion reduce image quality?
Converting to WebP or JPG is lossy, so some information is discarded — how much depends on the quality setting. Converting to PNG is lossless, but a lossy source cannot regain detail it never had, so a WebP converted to PNG will not look better than the WebP did.
Can I convert multiple images at once?
Yes. Select or drop as many files as you like and press Convert. They are processed a few at a time rather than all at once, which keeps memory use bounded, and the progress indicator reports genuine completion rather than an animation.
Can I download all converted images at once?
Yes. Download all packages every converted image into a single ZIP that is built in your browser. If ZIP creation is unavailable, the files are downloaded individually instead.
Can I resize images while converting?
Yes. Resize by a custom width or height, by percentage, or by capping the longest edge to a preset such as 1920px. Aspect ratio is locked by default, so nothing is stretched unless you deliberately unlock it.
What do the resize presets mean?
They cap the longest edge of the image. A 1920px preset applied to a 3000×2000 photo produces 1920×1280; applied to a portrait 2000×3000 it produces 1280×1920. Images already smaller than the cap are left alone rather than being enlarged.
Are my images uploaded to a server?
No. Decoding, resizing, encoding and downloading all happen in your browser using the Canvas API. No network request carries your image data, and nothing is stored once you close the tab.
Can I use this tool offline?
Once the page has loaded, conversion needs no network at all, so an already-open tab keeps working without a connection. Loading the page fresh does require the network.
Does conversion keep EXIF metadata?
No. Browser-based conversion through the Canvas API discards metadata such as EXIF, including camera settings and any GPS coordinates. That is often desirable for privacy, but if you need to keep the metadata you will need a tool that copies it across explicitly.
Will my photos be rotated incorrectly?
No. Images are decoded with the orientation flag applied, so a portrait photo from a phone converts the right way up. Because the rotation is baked into the pixels, the result stays correct even though the EXIF orientation tag itself is not carried over.
How large an image can I convert?
There is a 30 MB per-file limit and a warning for images beyond roughly 40 megapixels, because very large canvases can exhaust browser memory. This is a browser constraint rather than a policy — a desktop application will handle bigger files.
What happens if two files have the same name?
The second gets a numbered suffix — image.webp, then image-1.webp — so one download cannot overwrite another in your downloads folder.
Which formats can I upload?
PNG, JPG, JPEG and WebP are fully supported. GIF and BMP are accepted where your browser can decode them, and animated GIFs convert as a single frame. Anything the browser cannot decode fails with a clear message rather than producing a broken file.
Why did my file get larger after conversion?
Usually because the source was already well compressed, or because a flat graphic with few colours was re-encoded with a lossy codec. Try a lower quality, or keep PNG for logos and screenshots. The tool tells you plainly when the output is larger instead of showing a saving.
Does WebP improve website speed?
Smaller images reduce transfer size, which usually helps — but page speed depends on the whole page. If your slowest element is a render-blocking script or a large font, converting images will not fix it. Measure before and after rather than assuming.
Does WebP improve Core Web Vitals?
It can help Largest Contentful Paint when the LCP element is an image, because a smaller file arrives sooner. It does nothing for Cumulative Layout Shift unless you also set width and height attributes, and nothing at all for Interaction to Next Paint.
How do I use WebP on my website?
Use a picture element with a WebP source and a JPG or PNG fallback, and the browser picks whichever it supports. All current browsers take the WebP, and older ones fall back automatically without any JavaScript.
Is this converter free?
Yes. Free, no sign-up, no email address, no watermark and no per-file charge.
Related image tools
More ToolAdda image utilities that run entirely in your browser.
This converter runs entirely in your browser using the Canvas API. Your images are never uploaded, nothing is logged, and everything is discarded when you close the tab. Browser-based conversion removes metadata such as EXIF information, and WebP output uses the browser's lossy encoder — quality 100 is its highest lossy setting, not WebP lossless. File sizes shown are measured from the actual encoded output.