WebPJSON or WebP

webpmux GUI

Inspect WebP mux structure or create byte-preserving copies with EXIF-only or all standard metadata chunks removed.

Browser LocalNo signupBatch supported
WEBP WORKFLOW05.OPTIMIZE

Choose files to begin.

Perform focused container-level operations through a webpmux-style interface while image and animation payloads remain byte-for-byte intact. Inspection produces JSON; removal modes rebuild RIFF bounds and feature flags after omitting only the selected metadata chunks.

How to use webpmux GUI

  1. Choose still or animated WebP files and select an inspection or metadata-removal operation.
  2. Run the operation locally; image payloads are never decoded for container-only changes.
  3. Review the report or validate the rebuilt WebP before replacing any delivery copy.

What this tool is good at

Read-only mux inventory
Focused EXIF removal
Standard metadata cleanup
No pixel or frame re-encoding

When to use webpmux GUI

Debug mux operations with evidence

Inspect a WebP container or create a focused delivery copy without EXIF-only or without EXIF, XMP, and ICC metadata while retaining image and animation chunks. Work from the selected WebP's actual bytes, dimensions, or decoded pixels instead of assuming that an extension, filename, or one successful preview proves the underlying implementation.

Prepare a repeatable developer handoff

Inspection produces JSON; removal modes report removed bytes and return a rebuilt WebP with corrected RIFF length and feature flags. Keep the generated asset, report, markup, or command beside a ticket or publishing change so another developer can reproduce the decision and verify the exact inputs.

Keep unreleased assets private

Inspect campaign media, client images, product artwork, and internal fixtures in the current browser tab without creating an image-processing upload or remote conversion job.

How to choose the right settings

01

Match settings to the consuming system

Inspect a WebP container or create a focused delivery copy without EXIF-only or without EXIF, XMP, and ICC metadata while retaining image and animation chunks. Confirm filename conventions, layout widths, codec availability, metadata policy, and quality requirements in the real CMS, build pipeline, browser, or command-line environment.

02

Verify generated output, not only controls

Inspection produces JSON; removal modes report removed bytes and return a rebuilt WebP with corrected RIFF length and feature flags. Open downloaded images, read the complete report, or review generated code before publishing; a convenient default cannot know every repository path, responsive layout, or compatibility rule.

03

Keep the source as the authority

This browser interface does not execute the webpmux binary, add arbitrary chunks, recover deleted metadata, remove identifying pixels, or strip unknown proprietary chunks. Store the untouched WebP until every derivative or integration change has been tested and accepted.

Practical workflow and output details

A chunk parser copies retained byte ranges directly and the metadata utility omits only the selected standard FourCC records without decoding pixels. Processing uses browser APIs, bounded typed-array parsing, Canvas, or local Blob generation. No selected image bytes are submitted to PicConverters for processing.

This browser interface does not execute the webpmux binary, add arbitrary chunks, recover deleted metadata, remove identifying pixels, or strip unknown proprietary chunks. The page states this boundary explicitly so a local convenience tool is not mistaken for a full codec debugger, perceptual quality lab, shell runtime, deployment system, or irreversible source-of-truth editor.

Format behavior and limitations

This interface implements the named browser-safe operations directly and does not execute the webpmux command-line binary.

Removing all standard metadata omits EXIF, XMP, and ICCP while retaining unknown chunks, pixels, animation controls, and compressed frame data.

Frequently asked questions

Will animation remain animated?

Yes. Container removal modes copy ANIM, ANMF, and image payload chunks unchanged.

Can it add arbitrary chunks?

No. This release limits the GUI to inspection and carefully bounded metadata removal.

Is removal reversible?

No. Keep the source because deleted chunks cannot be reconstructed from the cleaned copy.

Related WebP tools