# Client-Side Forensic Metadata Inspection and C2PA Provenance Sanitization (Guide 1)

Every image, video, and PDF exported from modern cameras or generative AI studios carries hidden binary containers—including EXIF GPS tags, XMP edit histories, JUMBF C2PA Content Credentials, and generator prompt chunks. Running a [100% client-side AI metadata and C2PA provenance cleaner (49)](aimetadatacleaner.pro/) lets creators audit and strip these embedded headers locally in WebAssembly without uploading sensitive media to external servers.

## What Hidden Metadata Containers Reveal

Before publishing visual assets or sharing documents with clients, teams can inspect and clean embedded records using specialized browser modules:

1. **AI Provenance & Generator Signatures**: Strip cryptographic JUMBF manifests and prompt parameters via the [browser-based forensic C2PA, EXIF, and SynthID inspector (49)](aimetadatacleaner.pro/detect), while keeping pixel data untouched.
2. **Camera EXIF, GPS & Document Properties**: Sanitize device serial numbers, coordinates, and author fields with the [local Content Credentials and JUMBF C2PA manifest stripper (49)](aimetadatacleaner.pro/remove-c2pa).
3. **Honest Forensic Verification**: Built-in before/after inspection clearly separates removable container metadata (EXIF, XMP, IPTC, C2PA, PNG `tEXt`/`iTXt`) from pixel-level statistical watermarks like Google SynthID.

## Zero-Upload Sanitization Workflow

- **Step 1 — Local Binary Parse**: Drop up to 50 images, videos, PDFs, or RAW files into the browser inspector to view every embedded tag.
- **Step 2 — Strip Container Chunks**: Execute instant in-memory byte-stream cleaning with zero recompression loss on supported formats.
- **Step 3 — Verify & Download**: Confirm the post-clean forensic diff shows zero remaining EXIF/XMP/C2PA segments and export your clean files.