Anthropic will watermark all Claude-generated text under EU AI Act rules

Anthropic has published how it intends to mark content generated by Claude, having signed the EU’s Code of Practice on Transparency of AI-generated Content. Two mechanisms are described: an imperceptible watermark woven into generated text, and C2PA signed provenance metadata attached to generated files. The legal trigger is Article 50 of the EU AI Act, which applies from 2 August 2026.

The scope is the part worth registering. This is an EU obligation, but Anthropic states that marking “will apply to output from supported models wherever Claude is offered, worldwide”, across Claude Platform (API), Claude, Claude Code, Claude Cowork and Claude Tag, and through AWS, Google Cloud and Microsoft Foundry.

Read the tense carefully before acting on any of it. The documentation is written almost entirely in the future and in-progress voice, and the detection tooling that would let anyone actually check a piece of text is described as forthcoming. This is a dated commitment, not a capability available today.

What Article 50 requires

Article 50(2) puts the obligation on providers of generative systems: outputs must be “marked in a machine-readable format and detectable as artificially generated or manipulated”, using solutions that are “effective, interoperable, robust and reliable as far as this is technically feasible”. Article 50 sits in Chapter IV of the AI Act, which applies from 2 August 2026.

The Code of Practice is the voluntary route to demonstrating compliance. The Commission published the final version on 10 June 2026, the Commission and the AI Board confirmed its adequacy in July, and roughly 190 companies had signed by the end of that month. Signing is not itself the legal requirement. The Article 50 obligation applies to providers in scope either way; the Code offers signatories a more predictable enforcement path.

One distinction is easy to lose: the Code requires machine-readable marking and detectability, not watermarking specifically. Watermarks plus C2PA are Anthropic’s chosen implementation, not a mandated design.

What Anthropic has committed to

Text. A supported model “weaves an imperceptible watermark directly into the text itself”. Anthropic says it does not change meaning, quality or readability, travels with the text through copying and pasting, and “may persist through some editing”. Two details matter more than the mechanism. It is applied at model level rather than per product, so no surface avoids it, and Anthropic states that embedded watermarks “will apply to all generated text”.

Files. Generated .svg, .png and .jpg files carry signed provenance metadata following the C2PA standard, which also allows tamper detection.

Timing. Models launched on or after 2 August 2026 support marking at launch. Earlier models fall under a transition period, and Anthropic says it is working to add support to them.

The limitations, which the documentation states plainly

Anthropic is unusually direct about what the marks do not establish, and the caveats run in both directions.

A detected mark indicates content “may have been processed by Claude”, not that Claude wrote it. The reason given is that people use Claude to “proofread, translate, summarize, or convert files”, so a mark can sit on text whose substance came from a person. That maps onto an exception written into Article 50(2) itself, which carves out systems performing an assistive editing function or not substantially altering the input.

Absence of a mark proves nothing either. Anthropic lists the gaps: output from models released before marking support, text that has been heavily edited, paraphrased, translated or mixed into other writing, passages too short to carry a reliable signal, file metadata stripped by format conversion or screenshots, and platforms or file types where a marking type is unsupported.

Does this touch search?

Not on any confirmed mechanism, and nobody has claimed otherwise. No platform has stated that provenance marks are used as ranking signals, which is the same position we recorded when Google brought SynthID and C2PA verification to Search and Chrome in May 2026.

What has changed is the reliability class of the question. Until now, working out whether text was machine-written meant running a third-party detector, and detectors are the weakest instrument in this field, prone to flagging human writing as machine-written. A provider marking its own output is a different kind of evidence: not a statistical guess about style, but a signal the generating system deliberately inserted. That distinction will matter as soon as the detection tooling ships, and it is a reason to treat detector-based statistics about the share of AI content on the web with continued caution rather than new confidence.

What this means

1. Know what your content pipeline emits. If you generate copy through the Anthropic API or Claude Code and publish it, the output is intended to carry a model-level mark regardless of region. That is a fact about your published assets, not a penalty, and there is no indication any search engine reads it.
2. Check whether Article 50 lands on you as a deployer, not only as a user. The Act places separate obligations on deployers, including disclosure where AI-generated text is published to inform the public on matters of public interest, with a carve-out where the content has undergone human editorial review. Anthropic’s own guidance is that anyone building with Claude “should independently assess what Article 50 requires”. Whether it applies to a given publisher is a question for their own legal assessment, not something this article can answer.
3. Do not treat this as detection yet. No public tool exists to check a Claude mark. Anyone selling one before Anthropic publishes its technical documentation is guessing.

The editorial-review carve-out is the detail most likely to age well. It puts a legal frame around a distinction this site has argued on quality grounds for a long time: content a person genuinely reviewed and stands behind sits in a different category from output published straight from a pipeline.

Sources

• How Claude marks AI-generated content — Anthropic
• Article 50: Transparency Obligations for Providers and Deployers of Certain AI Systems — EU Artificial Intelligence Act
• Code of Practice on Transparency of AI-generated Content — European Commission