WebP Metadata Viewer
View WebP EXIF, XMP, ICC, software, author, and privacy metadata locally in your browser before publishing modern web images.
View Image Metadata
Analyze locally in your browser. Your image never leaves your device.
Supports JPG, PNG, WebP, HEIC, and TIFF. Analysis starts only when you click.
Verify modern web images before they ship
WebP improves delivery size, but converted files can still carry EXIF, XMP, ICC, author, software, or location metadata.
Modern chunk inspection
Check WebP EXIF, XMP, and ICCP chunks so performance conversion is not mistaken for privacy cleanup.
Final asset review
Inspect the WebP users will actually download, including CMS, build, CDN, and manually exported versions.
Creator context
Surface creator tools, editing history, color profile data, and content credential hints when readable metadata exists.
Audit the WebP output, not only the source image
A clean JPG source and a converted WebP output can have different metadata behavior.
Select the delivered WebP
Use the file from the same export, CDN, CMS, or build path that will reach users.
Check EXIF, XMP, and ICC
Review location, capture time, author, conversion software, color profile, and workflow fields.
Confirm the cleaned derivative
If cleanup is supported, analyze the downloaded WebP again before publishing or handing it off.
WebP metadata is reviewed in your browser
The selected WebP is processed locally for metadata viewing and supported cleanup. The page does not send the image to this site for analysis.
- Conversion to WebP does not automatically remove metadata from the source file.
- Content Credentials or C2PA-related fields may be reported when detected, but the tool does not validate signatures.
- Download the live served WebP and inspect that copy when a CDN rewrites images after upload.
WebP metadata questions
Answers specific to WebP chunks, conversion workflows, and publication checks.
Yes. Some converters preserve EXIF, XMP, or ICC data, so a WebP can still expose source-photo metadata.
Yes. The final served file is the one users receive, and CDN processing can preserve, remove, or rewrite metadata.
No. It can report related readable metadata when present, but it does not verify whether a credential or signature is authentic.
Export settings, image libraries, CMS plugins, and CDNs do not all follow the same metadata-preservation rules. Compare the actual WebP generated by each delivery path instead of assuming the source determines the final result.
No. Cleanup is offered only when the detected file and browser workflow support reliable original-format handling. When it is available, download the derivative and analyze it again to confirm the common readable fields.
Keep the final delivery file, the locally exported JSON report when a record is needed, and the context of the export or CDN path. That makes a later comparison more useful than a note about the source image alone.