| Field | What we found / documented |
|---|---|
| EXIF storage | Optional EXIF chunk in the RIFF container |
| XMP storage | Optional XMP chunk in the RIFF container |
| Consistency across tools | Less consistent than JPEG; many converters drop these chunks |
| Common use | Growing on the web for smaller file sizes; metadata support varies by tool |
WebP was designed primarily for smaller file sizes on the web, and its RIFF container format includes optional chunks for EXIF and XMP metadata, documented in Google's own WebP container specification. Support is optional at the format level, meaning an encoder can produce a fully valid WebP file with no metadata chunks at all.
In practice, many image converters and export pipelines that produce WebP do not carry over the source file's EXIF or XMP data, either because the tool does not implement it or because the conversion step discards it by default. A metadata-free WebP file is common and not by itself informative about the image's origin. Check any WebP file with our metadata viewer.
Questions this page answers
Does an empty metadata result mean the image is not from WebP?
No. A missing field can mean the metadata was never written, was stripped by an export or upload step, or was not inspected by this tool. Treat it as inconclusive, not as proof either way.
Does this page verify a specific image is from WebP?
No. It describes documented or observed behavior for WebP in general. To evaluate one file, inspect it with our metadata viewer and Content Credentials marker inspector and weigh the result alongside other context.