Remove supported AI metadata without uploading the file.
No Trace Share looks for explicit AI-related records stored inside supported file metadata and provenance structures. It can show you what was found, where it was found, clean supported records, and verify the generated copy afterward.
Opens the private browser-based cleaner so you can inspect AI Traces before choosing what to remove.
What counts as an AI Trace?
In No Trace Share, AI Traces means embedded records that explicitly point to an AI-generation or AI-editing workflow. These are not guesses based on how an image looks.
Generation parameters
Supported text fields such as prompts, negative prompts, workflow data, generation settings and tool-specific metadata can be identified when they are stored in the file.
Generator / software markers
Software names and creator-tool fields can be flagged when the value matches a recognized AI-generation tool or an AI-related provenance action.
AI source-type records
Supported metadata and C2PA actions can explicitly describe trained-algorithmic or synthetic media. Those records are reported as AI-related rather than generic metadata.
Content Credentials / C2PA
No Trace Share inspects supported embedded Content Credentials and can distinguish explicit AI-related records from generic provenance records.
Where No Trace Share can find these records
The exact storage depends on the format and the application that created the file. Current checks include supported XMP fields, PNG/JPEG text-style metadata, ordinary software/generator fields, and supported C2PA / Content Credentials structures in compatible image formats.
What happens during cleaning?
- Inspect: the file is parsed locally and supported findings are categorized.
- Report: explicit AI-related findings appear under AI Traces & Content Credentials, with the source and value where available.
- Clean: supported metadata blocks or selected fields are removed according to the format and your choices.
- Verify: the generated copy is inspected again. If the explicit AI-related records detected before cleaning are gone, the file card can report that the supported AI Traces were cleared.
Every run creates a separate output. The original selected file is never overwritten.
Important limits
Not an AI image classifier
No Trace Share does not inspect the pixels and announce that an image “looks AI-generated.” The current feature is evidence from embedded records.
Not a watermark remover
Invisible pixel-level watermarks and other media-embedded signals are outside the current metadata-cleaning scope.
C2PA is broader than AI
A Content Credential may describe ordinary capture or editing history. Generic C2PA is therefore shown separately unless the credential contains an explicit AI-related signal.
Format safety comes first
HEIF/HEIC and complex documents use more conservative rules. No Trace Share can retain or refuse structures it cannot safely rewrite rather than damaging the file.
AI metadata removal FAQ
What does No Trace Share mean by AI Traces?
Explicit AI-related records found in supported metadata or provenance structures: generation parameters, prompts, workflow fields, generator/software markers, or C2PA actions that identify algorithmically generated or edited media.
Does it detect AI by looking at the pixels?
No. The current web app reports embedded metadata and file-structure records. It does not classify the visible image and does not scan for invisible pixel-level watermarks.
Can Content Credentials exist without proving AI generation?
Yes. C2PA Content Credentials can describe origin and editing history for many kinds of media. No Trace Share separates generic Content Credentials from records carrying an explicit AI-related signal.
Check your own file, not just the explanation.
Open the No Trace Share workspace to inspect supported metadata, review the exact findings, and create a verified cleaned copy.
Clean a file nowYour selected files stay in your browser and are not uploaded to No Trace Share.