Morphio
Menu

Is WebP lossless? It depends on the encoding mode

Is WebP lossless? WebP supports both lossy and lossless encoding. Lossless encoding preserves the pixel data represented by that encoding step; it does not recover detail already missing from the source. A .webp extension alone does not tell you which mode was used.

Choose a mode for the pixels you need to keep

Lossy encoding accepts changes to image data to reduce storage. Lossless encoding reconstructs its encoded pixels without that loss. The WebP specification defines the two bitstreams. Preprocessing and color conversion before encoding can still change the source representation.

For a PNG source, PNG to WebP is the relevant conversion direction. If exact pixel preservation is a requirement, verify the encoding path and output rather than treating “WebP” as a synonym for “lossless.” The linked conversion page does not provide a user-selectable lossless switch.

For an existing JPEG, previous compression has already determined the pixels you can decode. JPG to WebP cannot recover discarded texture or remove all previous artifacts. A later lossless file can preserve a damaged source just as faithfully as an undamaged one.

Is WebP lossless at the highest quality setting?

A high lossy quality setting is not the same operation as choosing lossless mode. Google’s cwebp documentation distinguishes lossy quality from the speed/compression tradeoff used in lossless mode. Its near-lossless preprocessing can adjust pixel values too. Its lossless encoding can also change invisible RGB values under fully transparent pixels unless exact preservation is requested. These are encoder behaviors, not controls offered by this guide. A matching number in two encoders is not a matched visual result.

There is no universal best setting for every photograph, screenshot and transparent icon. Keep one source at the same dimensions, create the candidate output, and inspect text edges, gradients, skin or fabric detail and semi-transparent borders. Compare at the intended display size and at a useful inspection zoom, then compare file bytes.

Use WebP compression for the current automatic size-reduction tool. It keeps the source’s lossy/lossless mode by default and retains the original if a valid candidate is not smaller. It has no quality slider, target-file-size field or resize control.

Choose the delivery format separately

A recipient may require a different image type regardless of how WebP was encoded. WebP to PNG supports a static output with transparency; WebP to JPG re-encodes a static image and flattens transparent areas onto a background.

For animated input, those static outputs use the first frame. A larger PNG or a new JPG is a delivery copy, not evidence of restored source quality. Keep the original when motion or the original encoding matters.

Bit depth, HDR, CMYK and print resolution

Google’s format FAQ describes lossy WebP as 8-bit YCbCr 4:2:0 and lossless WebP as RGBA; the lossless specification uses 8-bit channels. These are not native CMYK pixel encodings. A color profile describes interpretation but does not turn the stored pixels into a CMYK printing master.

These standard WebP encodings do not provide 10-bit or 12-bit HDR samples. Changing an SDR image into another extension does not create missing HDR highlight detail. If an HDR or print-color workflow is required, start from an appropriate source and verify the complete color-management path. This guide does not offer HDR reconstruction.

For printing, distinguish image pixel density, or PPI, from printer-dot density, or DPI. Changing a density label does not add image pixels or restore detail. Judge print suitability using the pixel dimensions and the physical size at which the image will be printed.

Progressive loading is a separate display question

The WebP FAQ distinguishes incremental decoding from progressive JPEG-style or interlaced PNG-style refresh. WebP can make decoded rows available incrementally, but the visible loading behavior also depends on the decoder and webpage. It is not an encoder-quality promise.

For page delivery and display choices, continue with WebP on websites. Keep loading behavior, transferred bytes and image quality as separate measurements.

Questions and answers

Encoding modes, source detail and file-size tradeoffs.