Skip to main content

Supported format

Remove metadata from WebP images

Inspect supported WebP EXIF and XMP in your browser before using an image in a disclosure. The file can also carry a colour profile, transparency and animation structures. ScrubMetadata distinguishes those structures from supported privacy metadata and checks the output independently. Review the report and processed image before releasing it.

WebP privacy fields and containers

WebP can carry EXIF and XMP inside its RIFF container, including authorship, identifiers or location where present. The same file can carry an ICC profile and separate transparency or animation structures. Inspect each type of structure; the container's feature flags alone do not describe every metadata value.

  • EXIF and XMP properties
  • ICC profile attributes
  • RIFF chunks, alpha and animation controls, and unknown private chunks

Supported WebP removal and checks

The supported path removes identified EXIF and XMP metadata and assesses other privacy containers before checking the output independently. Unknown chunks are recorded as unassessed, not assumed to be known private fields. Read the container and residual findings together, then open the processed image before deciding to disclose it.

WebP colour and animation structures

Image payload, alpha and declared animation chunks are treated as structural content. An independently assessed public ICC profile can remain for colour rendering, while a profile with private data needs a different disposition. The output must still pass its checks; retaining a colour dependency is not a universal fidelity guarantee.

  • The VP8 or VP8L image payload and VP8X structural header.
  • ALPH transparency and declared ANIM or ANMF animation structures.
  • An ICC colour profile only when independently assessed as public and structural.

WebP limits and unresolved findings

The RIFF size, chunk boundaries and padding must be consistent before the file can be assessed. Unknown chunks or malformed profiles cannot receive a known-field removal claim. Review their disposition and the processed output; the file extension alone does not prove every WebP variation, image size or animation has been verified.

  • The RIFF size, chunk boundaries and padding must be valid.
  • Unknown chunks cannot be described as identified privacy fields.
  • A private or malformed colour profile needs a different disposition from a public structural profile.
  • The workflow does not guarantee every image's fidelity, compression result or processing time.

Questions about WebP metadata

Is the WebP colour profile always privacy metadata?

No. The ICC assessor can identify a profile as a rendering dependency, direct privacy data or an unassessed structure. Those outcomes are reported separately.

Can animated WebP files contain ordinary metadata?

Yes. EXIF and XMP may coexist with animation chunks. The policy keeps declared frame and alpha structures while assessing the metadata containers; the final result must still verify.

An image selected by a publishing team

Representative scenario

A publishing team copies a WebP image into a rights-response draft. Inspect EXIF and XMP, then check how any ICC profile was assessed. Open the processed image and review transparency or animation where present before the authorised person decides whether the attachment can be included in the response.

How to review file metadata before disclosure

Process WebP files in your workspace

Supported WebP files are inspected and cleaned in your browser. Raw file bytes and raw metadata are not sent to ScrubMetadata servers, and only minimised evidence is recorded after processing.

  • Raw file processing stays local
  • Device-verified access
  • Accounts approved by a person
Request access

Already approved? Sign in

Remove WebP metadata in your browser · ScrubMetadata