Does my file stay on my device while using the tools?
Yes. The default path processes supported images locally in the browser. An API upload requires separate, explicit consent.
Free local tools for C2PA Content Credentials, metadata inspection, and privacy cleaning. Directly in your browser with zero file upload.
Five local inspection tools run directly in the tool hub. The standalone disclosure generator opens on the matching generator domain.
Add visible disclosures and official EU icons locally.
Inspect EXIF, IPTC and XMP metadata fields with zero file upload.
Verify C2PA Content Credentials, manifest chains, and signatures locally.
Strip sensitive GPS and camera metadata locally via clean re-encoding.
Record metadata and provenance state as a versioned JSON verification snapshot.
Inspect MP4 and WebM video containers, codecs, and tracks locally.
AI media transparency relies on two distinct layers: A visible overlay informs human viewers directly within the image. Machine-readable signals such as C2PA Content Credentials or XMP metadata store origin data securely in the file header. A robust workflow validates both layers post-export.
Technical background knowledge on Content Credentials, image metadata, and practical workflows.
Understand what Content Credentials can technically establish, how signatures are checked and where their meaning has limits.
Plan visible notices, technical provenance and a reviewable export check for AI-generated or materially edited video.
A practical technical guide to visible disclosures, accurate wording and a transparent publishing workflow for AI-generated images.
Why visible notices and machine-readable provenance solve different problems and become stronger when used together.
Answers about C2PA validation, metadata stripping, and client-side processing.
Yes. The default path processes supported images locally in the browser. An API upload requires separate, explicit consent.
No parseable C2PA manifest was found. This does not establish whether the file is authentic or modified, and it does not show whether AI was used.
The cleaner locally re-encodes the image and then checks whether supported EXIF, IPTC and XMP fields were removed. The original file remains unchanged.
Never automatically in the standalone build. An enabled server function must be shown clearly and requires explicit confirmation before each transfer.