Local sandbox
Inspection and sanitization run in the browser’s Canvas and ArrayBuffer heap. There is no upload endpoint, no worker backend, and no log of filenames.
100% Client-Side • Zero Cloud Upload • Zero Server Logs
Strip C2PA, EXIF & GPS
Metadata in Your Browser
Erase AI Content Credentials, EXIF, GPS, and hidden tracking footprints from videos and images — 100% client-side.
Private tools · running locally
One toolbox. Five jobs. Your files stay here.
Clean metadata, compress video, read scans, organize PDFs, or prepare a platform appeal without turning private files into a cloud workflow.
Privacy · Live
Metadata Cleaner
Strip C2PA, EXIF, GPS and XMP from a sharing copy.
Open flagship tool ↘
Media · Live
Video Compressor
Hardware-first WebCodecs compression with large-file aware output.
Compress locally ↗
Documents · New
Local OCR
Extract English, 中文 and 日本語 text and build searchable PDFs.
Read scans locally ↗
PDF Toolkit
LiveMerge, split, reorder, rotate and convert PDFs without uploading them.
Telegram Ban Appeal
LivePrepare a concise account-recovery request with a dedicated workflow.
Drag & drop up to 50 files here or browse
JPG, PNG, WEBP, MP4, MOV — files or folders. Nothing leaves this tab.
Drop more files onto this strip
Or browse to append to the current batch
Total files
0 Items
Awaiting scan
| File | Risk assessment | Status | Action |
|---|
How client-side sandboxing works
CreatorPrivacyKit never opens a network request for your media. Every byte is parsed, redrawn, or rewritten inside this tab’s memory, then released.
Deep metadata stripping
Images are re-encoded through Canvas, which drops C2PA manifests, EXIF, GPS, and XMP. Videos are walked as ISO-BMFF boxes so udta, meta, and C2PA UUID atoms can be removed without touching A/V samples.
Instant export
Clean blobs download as a ZIP or as individual files. Rename the batch by date or random digits first if you do not want the original filenames traveling with the export.
C2PA vs EXIF vs XMP: what can travel with your files
These are file-level signals you can inspect before upload. A platform may read some of them, ignore them, or use other signals; the file alone cannot tell you how ranking or moderation works.
| Signal | What it stores | Where it lives | Why creators strip it |
|---|---|---|---|
| C2PA / Content Credentials | Signed AI-generation claims, edit history, tool identity, and sometimes a public credential URL. | JUMBF/APP11 in JPEG, caBX in PNG, UUID boxes in MP4. |
Removes the file-level provenance claim from the copy you share. A platform may still apply labels from other signals. |
| EXIF / GPS | Camera make/model, serial, lens, timestamp, and decimal GPS from phones and drones. | JPEG APP1 TIFF, PNG eXIf, WebP EXIF chunk, QuickTime udta. |
Keeps home addresses, studio locations, and device fingerprints off public posts and leaked raws. |
| XMP | Adobe/Lightroom history, creator contact fields, rights strings, and nested C2PA pointers. | APP1 XMP packets, PNG iTXt, ISO meta XML. |
Removes client names, job codes, and software fingerprints buried in “innocent” sidecars. |
Why creators need this
Provenance & AI labels
Some platforms publicly use provenance signals such as C2PA for transparency labels. Cleaning a file controls the metadata you send; it does not guarantee reach, ranking, or label outcomes.
Raw footage privacy
Phone video and stills embed GPS, serials, and software tags. Sending “raws” to an editor or a Discord drop can leak a home set, a school, or a brand’s unreleased location.
Client-contract residue
Lightroom and camera XMP often keep job titles, emails, and copyright strings. Sterilizing the export is a last-mile NDA habit, not a gimmick.
FAQ
No. CreatorPrivacyKit is a static page. Inspection uses FileReader on a 64KB slice; sanitization uses Canvas and in-memory ArrayBuffers. JSZip also runs locally. There is no API call with your media.
Images: JPG, PNG, WEBP. Video: MP4 and MOV (ISO-BMFF / QuickTime). Up to 50 files per batch. Classic non-ISO QuickTime files may be rejected if they lack a parseable box structure.
The hard cap is your browser tab’s memory, not a server quota. We process one file at a time (FIFO) and drop large buffers after each export so a 50-file batch of 4K stills or short MP4s stays stable. Very large 4K masters can still exhaust RAM — close other tabs if a file is several gigabytes.
PNG is re-exported losslessly. JPEG and WEBP are re-encoded via Canvas (high quality, ~0.95). That is the tradeoff that guarantees EXIF/C2PA cannot survive. Pixel dimensions are unchanged. Video sample data in
mdat is copied, not transcoded.Yes, for credentials stored as standard C2PA/JUMBF packets, UUID boxes, or XMP. The inspector surfaces generator identity when the file still carries it: OpenAI (DALL·E / ChatGPT / Sora), xAI Grok Imagine, Midjourney (prompt + Job ID in Description, even when the word “Midjourney” is missing), Firefly, Stable Diffusion / ComfyUI PNG parameters, Ideogram, Leonardo, Runway, FLUX, and others. Author & Identity and Custom properties are listed separately. Invisible pixel watermarks such as SynthID are not metadata and cannot be read or removed by a header stripper. Always review the expanded inspector row before you publish. Full walkthrough: How to remove Instagram’s AI Info label.
Guides
Platform walkthroughs for C2PA labels, EXIF GPS leaks, and client-side sanitization.