Anthropic watermarks Claude-generated text worldwide

The watermark isn't hidden Unicode or a suffix appended to the output - Anthropic describes it as an imperceptible signal woven directly into the words Claude chooses as it generates ^[1]. That framing also explains why the mark travels with copy-paste and can persist through light edits - the underlying word and phrasing choices carry it - but degrades under heavy editing, paraphrasing, translation, or format conversion, where too little of the original wording survives ^[7]. The technique is statistical and token-choice-based rather than a set of visible characters, and does not alter the meaning or quality of the text ^[1][4]. Images and files get a different, simpler mechanism: signed C2PA provenance metadata, effectively a digital receipt attached to .svg, .png, and .jpg outputs ^[1]. Re-saving the file can strip that metadata ^[7].

The proximate trigger is narrow and dated: the EU AI Act's Article 50 transparency code took effect on August 2, 2026, requiring generative AI providers to make synthetic outputs machine-detectable or face fines up to EUR 15 million or 3% of global annual turnover ^[2]. Anthropic could have scoped the watermark to EU traffic only. Instead it applied the behavior at the model level everywhere Claude runs - the Claude app, the API, Claude Code, Claude Cowork, Claude Tag, and cloud-partner deployments - rather than maintain region-specific model behavior ^[1][2]. The comparison to OpenAI is telling: OpenAI also signed the same EU Code of Practice but has reportedly sat on a highly accurate text detector for roughly two years without releasing it, and has not shipped text watermarking for ChatGPT even though it does embed Google's SynthID for images ^[3]. Anthropic's global, no-opt-out rollout is as much a positioning choice as a compliance minimum.

The backlash clusters around two distinct risks. The first is technical: source code is a poor host for a statistical token watermark because of rigid syntax and identifier constraints, and common formatting tools like Prettier likely degrade or eliminate the marks in Claude Code output, undermining any reliability as a provenance signal ^[4][5]. The second is legal, and according to Stephen Smith, more consequential - the watermark itself carries no prompt, client, or case content, so it isn't the liability many assume. The real exposure he identifies is organizations failing to track jurisdiction-specific rules that require disclosing AI use in filings and professional work product; the mark is a red herring next to that compliance gap ^[6].

Anthropic's own documentation undercuts the strongest version of the claim being made about the feature: a detected mark shows only that text may have passed through Claude, not that Claude authored it, since proofreading, translating, or converting human-written text through Claude still produces marked output ^[1][4]. The reverse is also true - absence of a mark doesn't prove a text is human-written ^[1][4], and Anthropic itself warns detection is unreliable on short or heavily edited snippets ^[7]. Compounding the problem, the detection API that would let outsiders verify any of this independently isn't public yet, so for now only Anthropic can confirm whether a given passage is marked ^[4].