The ChatGPT text watermark EU rollout applies to eligible ChatGPT and Codex text output in the European Union only at launch, with API opt-in available globally for select models from October 5, 2026. OpenAI announced the change on October 5, and The Verge reported the same day that the textGrain watermark would not be a global default at launch. Search Engine Journal reported on October 6 that OpenAI is also opening opt-in watermarking for API users worldwide.
OpenAI says the move responds to EU AI Act requirements that generative AI providers make generated text identifiable in a machine-readable way. Search Engine Journal ties the timing to Article 50 transparency rules, which began applying on August 2, 2026, and says AI systems placed on the market before that date have until December 2 to meet the marking and detection obligation. OpenAI's announcement says textGrain will be made available in open source and that its technical report will get more detail in the coming weeks.
What the ChatGPT text watermark EU rollout covers
OpenAI is applying text watermarking to eligible ChatGPT and Codex users across all plans in the European Union, while API customers outside the EU must turn it on. OpenAI Help Center says API customers can activate text watermarks from Organization settings, Data controls, Text provenance or from Project Settings, Text provenance, then choose which models receive the watermark. OpenAI's announcement also says cloud partners will get watermarking for OpenAI model outputs through their services in the coming weeks.
The rollout does not cover every output. OpenAI Help Center says the EU AI Act Code of Practice does not require watermarks for outputs shorter than 200 tokens, about 150 English words, or for code snippets. Search Engine Journal says OpenAI's October 5 update did not specify which API models are part of the opt-in program and did not say whether EU ChatGPT users can disable the watermark.
How textGrain changes generated text
TextGrain works by changing the randomness used when a model chooses words, so some valid word choices become statistically more likely than others. OpenAI Help Center says it does not add hidden characters, invisible spaces, unusual punctuation, extra tokens, or visible changes. The detector then checks whether the expected statistical pattern appears in a passage.
Search Engine Journal says OpenAI reported about 80 percent detection for 200-token passages and about 95 percent detection for 400-token passages, at a target false positive rate of 1 percent, for content such as psychology. The same report says results were lower for content such as math, where word choice has less flexibility. In a separate 400-token English test using ELI5 prompts, replacing 10 percent of words with synonyms reduced detection from about 92 percent to 66 percent, and replacing 25 percent reduced it to 17 percent.
Who can verify a watermark
OpenAI is not making text watermark detection public at launch. OpenAI's Content Provenance API documentation says text verification requires an application and is currently available only to approved organizations, including AI research and academic institutions. The Verge reported that the tool will report whether it detects an OpenAI watermark without identifying the user or revealing prompts or conversations.
An OpenAI text watermark is evidence that a detector found OpenAI's statistical signal in eligible text, not evidence of who wrote the document. OpenAI API documentation says a not_detected result also does not rule out OpenAI generation, because metadata can be stripped, a watermark can degrade, older models may lack signals, or the content may predate provenance signals.
What search teams should change
Search and content teams should treat textGrain as a provenance control, not as a ranking or authorship signal. No source in the record says textGrain affects search ranking, AI answer citations, paid media bidding, or analytics attribution. The supported inference is narrower: teams that publish ChatGPT or Codex output from EU users need records that explain how the content was created, because the detector is limited and editing can weaken the signal.
| Workflow | Specific check | Operational reason |
|---|---|---|
| OpenAI API | Review Organization settings, Data controls, Text provenance and Project Settings, Text provenance. | API watermarking is opt-in globally, so teams need to know which projects and models are marked. |
| EU ChatGPT and Codex use | Record which teams, offices, or contractors generate copy in the European Union. | Eligible EU output may be watermarked while similar non-EU output is not watermarked at launch. |
| CMS and editorial policy | Add a content note for AI assistance, model family, region, and human review status. | OpenAI says a watermark does not measure human contribution or prove human authorship. |
| Vendor contracts | Avoid clauses that treat a detector result as sole proof of authorship or breach. | OpenAI cites missed watermarks and false positives as reasons for limiting detector access. |
Where the evidence is still thin
The open questions are practical rather than theoretical. OpenAI has not named the select API models in the October 5 materials cited here, has not said whether EU ChatGPT users can opt out, and has not published public access to the text detector. OpenAI Help Center gives EU AI Act guidance as general information only and says customers, developers, and users remain responsible for assessing their own obligations.
The comparison with Anthropic is also unsettled. Search Engine Journal reported that Anthropic marks supported Claude models worldwide and says it does not yet have a durable way to scope watermarking by region, while OpenAI is starting with an EU-only rollout. In r/ClaudeAI on October 7, practitioners reacted to that difference with mixed signals: one commenter said they would cancel a subscription over watermarking, another said disclosure matters, and another said they moved translation work from Claude to local Qwen3.8. That subreddit discussion shows user concerns, not verified adoption data.
The next triggers are OpenAI's promised technical report update, the open-source release of textGrain, cloud partner availability in the coming weeks, and the December 2, 2026 compliance date for AI systems placed on the EU market before August 2.