Anthropic Now Watermarks All Claude Output: Text Watermarks and C2PA for Files

Anthropic now marks every piece of text and every file its Claude models generate. The company updated its support documentation on August 11 to confirm it is rolling out machine-readable watermarking under its commitments to the EU AI Act's Code of Practice on Transparency of AI-Generated Content, and the change applies everywhere Claude is offered, including the API, Claude Code, Cowork, and Tag.

The headline number: all Claude models launched on or after August 2, 2026 support marking at launch, and Anthropic says it is working to add marking to models released before that date under the law's transition period.

Two marking mechanisms, applied at the model level#

Anthropic uses two complementary techniques:

• Embedded watermarks in text. When a supported model generates text, it weaves an imperceptible watermark into the text itself. Anthropic states the mark does not change the meaning, quality, or readability of the response, and because the watermark is part of the text it travels with copy and paste and may persist through some editing. Crucially, the mark is applied at the model level, so it is present no matter which product or surface generated the text.
• Signed provenance metadata on files. For supported file types such as .svg, .png, and .jpg, Claude attaches signed provenance metadata following the C2PA open standard, which lets a verifier detect whether a file was processed by Claude and whether it has been tampered with.

The coverage is broad. Marking applies to output from supported models across the Claude Platform (API), Claude, Claude Code, Claude Cowork, and Claude Tag, and it also applies when supported models are accessed through AWS, Google Cloud, or Microsoft Foundry, though Anthropic notes signed provenance metadata may not be supported on every partner platform. The marks ship worldwide, not just in the EU.

Detection is promised but not shipped yet#

The missing half of the loop is detection. Anthropic says it is working to enable users and third parties to detect both the embedded watermarks and the provenance metadata, and that a detected mark "indicates that the content may have been processed by Claude." Details of the detection mechanism are deferred to forthcoming technical documentation.

The support page is explicit about what marks are not. A detected mark does not confirm full provenance: Claude is often used to proofread, translate, summarize, or convert files, so output can carry a mark even when the underlying ideas came from elsewhere. And the absence of a mark proves nothing, because the text may have been heavily edited, paraphrased, translated, or mixed with other writing, may be too short for a reliable signal, or may have had its metadata stripped by format conversion, re-saving, or screenshots.

What this means for developers#

This is the most concrete, dated, default-on text watermarking commitment any large model provider has put on the table, and it lands directly in the developer workflow, not just in a consumer chat app.

Code is watermarked too. Claude Code output is covered, which means generated code, commit messages, and plan text carry the mark at the model level. If Anthropic ships the promised third-party detection, "no AI-generated code" policies become technically enforceable for the first time, and code-review tooling can flag Claude-authored patches. The flip side is the false-positive problem: the support page itself concedes marks are a signal, not conclusive proof, so a detection-based policy will inevitably mislabel human code that merely passed through a Claude edit or review. Teams will need to decide whether that trade is acceptable before wiring detection into CI.

API consumers inherit the mark. The watermark is embedded in raw text responses, and Anthropic claims it survives copy and paste and some editing. Post-processing chains that translate, reformat, or summarize responses can still strip it, per the limitations section, so the watermark's durability in real pipelines is exactly what the forthcoming detection docs will have to answer.

EU-facing products built on Claude have their own obligations. Anthropic explicitly tells builders: "you should independently assess what Article 50 requires of your products and services." The company says it will publish technical guidance on its marking and detection approach, but as of today a developer shipping a Claude-backed product in the EU has a stated compliance gap to plan around, with the marker's detection story still unannounced.

C2PA is the piece to integrate early. Signed provenance metadata on generated images and SVG files is standard-compliant and verifiable, so any pipeline that stores or distributes Claude-generated assets can start validating signatures now, before the text-watermark detection API exists.

Our take#

The model-level, default-on design is the right architecture, and it is more honest than the file-level metadata approach alone, which dies on the first screenshot. The two open questions are durability and detection. We will not know how much editing a watermark survives, and we will not know how reliable third-party detection is, until the technical docs land. Until then, treat the announcement as a compliance commitment with an unfinished verification story, and treat any tool that claims to detect Claude text today as unverified.

The move also widens the gap between providers. Google and OpenAI have published provenance commitments of their own, but Anthropic is the one that has now named a concrete, dated mechanism for text. That is the pattern to watch: watermarking stops being a research demo and becomes a default property of an API contract, which changes how attribution, review tooling, and compliance checkboxes work for everyone building on top.

Continue Reading#

• VS Code Copilot Co-Author Attribution - why attribution of AI-generated code is really a consent and audit problem
• Ghost Font: Text That Humans Can Read But AI Cannot - the other side of the coin, hiding text from models instead of marking it
• Apertus: Europe's Answer to AI Sovereignty - how EU compliance shapes open model development
• Agent Identity as a Security Layer - provenance and identity for agent output in production workflows
• Claude Code Permissions Settings Guide - how Claude Code handles boundaries before it touches your repo

Sources#

• Anthropic support article, "How Claude marks AI-generated content" (updated August 11, 2026): support.claude.com/en/articles/16266773
• European Commission, "Drawing-up a General-Purpose AI Code of Practice": digital-strategy.ec.europa.eu/en/policies/ai-code-practice
• C2PA specification: c2pa.org