WebP provides superior lossless and lossy compression for images on the web, developed by Google.
Common Uses
Optimizing website images for faster loading
Reducing bandwidth usage for web assets
Creating animated images with better compression than GIF
WebP Conversion FAQ
What is a WebP file?
+
WebP is a today's image format that provides superior lossless and lossy compression for images on the web.
Does re-saving a WebP make it worse every time?
+
Yes, and that is the one thing worth knowing about the format. Each save re-runs the lossy encoder over an image that has already been through it, so artefacts compound — visible as blocking around text and haloes on hard edges after a handful of generations. Edit from a lossless master and export to WebP once, at the end, rather than repeatedly opening and re-saving the same file. WebP offers both lossy and lossless modes, with alpha transparency and animation available in either.
Why is so much web content delivered as WebP?
+
Because it was designed for exactly that job: small files, fast start, no plugin and no licence to worry about. That makes it excellent at delivery and unremarkable at everything else — editing tools, phone galleries and older devices frequently ignore it. Converting to a general-purpose format is what makes downloaded content usable off the web. WebP is typically 25-35% smaller than an equivalent JPG and far smaller than an animated GIF, with universal browser support since 2020.
What quality setting should I use when converting to WebP?
+
Somewhere between 80 and 90 for anything a person will look at. Below about 75 the artefacts start to show on skin, sky and any large flat area; above 95 the file grows quickly while almost nobody can see the difference. The setting is not a property of the image, it is a decision about this particular export — so choose it for where the file is going, and keep the original for the next time you need a different answer.
Do frame timing and looping survive converting a WebP?
+
Into another animation-capable format, yes — per-frame delays and the loop count are stored in the file and carried across. Into a still format only one frame survives, normally the first. Into video the loop flag has nowhere to go, because the player decides for itself whether to repeat. Check the playback speed afterwards when the frame rate changes: a fixed rate can only approximate variable per-frame delays.
Is WebP too new to be widely supported?
+
Less so every year, but the gap is real. Software support arrived quickly; hardware support only comes with new devices, and the phone, television or player in front of you may simply predate it. Where it is supported it is measurably better than the format it replaces, which is why it is worth converting into for delivery and worth converting out of for compatibility.
Is WebP tied to Google?
+
It came from Google and is published openly, with a specification anyone can implement and no licence fee attached — which is exactly why browsers adopted it so quickly. Using it does not involve any Google service. Support outside the browser is the real limit: plenty of desktop tools, phone galleries and televisions still do not read it. WebP is Google’s 2010 image format, built from the VP8 keyframe encoder and intended to replace JPG, PNG and GIF at once.
Can I use WebP directly on a web page?
+
Yes — every current browser renders it natively, so it needs no fallback copy and no conversion at publish time. The remaining question is weight rather than support: the same picture in a modern web format is frequently a third of the size at the same visible quality, which is worth doing on anything that appears above the fold.
Can I just rename the extension instead of converting WebP?
+
Almost never, and it is worth understanding why: the extension is a label, while the bytes inside are structured for one specific format. Renaming produces a file whose name promises something its contents do not deliver, and whatever opens it either refuses the file or misreads it. The one narrow exception is two formats that are genuinely the same container under different names — and even then a proper rewrap is safer than a rename.
Can I make a WebP bigger without it going blurry?
+
Only modestly. The pixels that were captured are all the detail there is: enlarging either interpolates, which softens edges, or uses an AI upscaler, which invents plausible detail that was never in the original. Both are fine for a step up of a third or so and neither turns a thumbnail into a poster. Start from the largest copy you have and resize down wherever the choice exists.
What happens to my WebP file after the conversion?
+
It is deleted automatically. The upload and the converted result stay on our servers for about 24 hours, which leaves time to download the result, and are then removed by an automatic cleanup. The transfer runs over HTTPS in both directions. Nobody reads the contents, nothing is indexed, and nothing is passed to anyone else.
How long does converting a WebP take?
+
Usually seconds. Small files are effectively instant, and the cases that take real time are the ones doing real work: a long recording that has to be re-encoded frame by frame, a scanned document going through character recognition, or a very large batch. Where a conversion only rewraps or repackages the existing data it stays fast no matter how big the file is, because nothing is being decoded.
