Skip to main content
AI Watermark Removal

Regulation

EU AI Act and AI Watermarking: Article 50 Explained

Article 50 of the EU AI Act names no watermarking technology. Not C2PA, not SynthID, nothing at all. It just requires outputs to be marked in a machine-readable format and detectable as artificially generated, as far as technically feasible, and leaves the how to providers. That rule took effect on 2 August 2026, carries fines of up to 15 million euros or 3 percent of global turnover, and has already changed how Claude behaves everywhere, not only inside the EU, while OpenAI chose to mark consumer text in the EU only.

By ignacio-sjPublished Revised Sources verified Official announcement

Correction,

The machine-readable AI marking page, merged into this page on October 6, 2026, listed five exemptions, including source code, short sequences of characters and machine-to-machine output, as defined by Article 50(2). Article 50(2) itself exempts three things: AI systems performing an assistive function for standard editing, outputs that do not substantially alter the input data or its meaning, and uses authorised by law to detect, prevent, investigate or prosecute criminal offences. This page now lists the Article's three exemptions separately from the Commission FAQ's list and the Code of Practice's carve-outs. A quotation attributed to IPTC calling C2PA the only technology meeting the Code's metadata-signing specification, and details of CEN-CENELEC's Joint Technical Committee 21, have also been removed, because no source for either could be linked.

All corrections

Correction,

The machine-readable AI marking page, since merged into this page, said there was no confirmed official EU icon and that Commission texts contain no icon specifications of any kind. Both were wrong. The Commission publishes three official icons in four variations, free to use, with placement rules in Section 2 of the Code of Practice. The icons serve the Article 50(4) deployer disclosure duty rather than the Article 50(2) machine-readable marking duty, and their use remains optional. The separate rumour about a mandated 24x24px size, PMS 286C blue and a required C2PA pathway is still unsupported and stays flagged.

All corrections

Key takeaways

  • Article 50's transparency rules took effect 2 August 2026. A separate transitional deadline, 2 December 2026, covers certain Article 50(2) marking duties for systems already on the market before that date, and that grace period comes from the EU's later Digital Omnibus reform, not the Act's original text.
  • Getting it wrong is expensive: fines up to 15 million euros or 3 percent of global annual turnover for companies, up to 750,000 euros for EU institutions.
  • The Commission's Guidelines, adopted 20 July 2026 as C(2026) 5054 final, close the gap the article leaves: marking on its own is not compliance. They state that fulfilling only one element, "for machine-readable marking of outputs without the means for their detection being available," "will not suffice to comply with that provision," and that a provider must ensure the means of detection are available to "the persons potentially exposed to the content."
  • The same Guidelines define machine-readable, which the article never does: marks structured so software can "easily identify, recognise and extract them without human intervention." Watermarking is one option among watermarks, metadata identifications, cryptographic provenance methods, logging methods, and fingerprints, and providers may combine them.
  • The Code of Practice permits the one restriction that matters most for text, and only for a while. Detection of free-form-text watermarks "may be restricted to verified expert users," limited in time, while detection must be free of charge and unrestricted for regulators, law enforcement, media, fact-checkers, trusted flaggers, independent researchers, educational and research institutions, and civil society organisations.
  • About 190 organizations, including Anthropic, Google, Meta, Microsoft, and OpenAI, signed the EU's Code of Practice on AI-generated content by the end of July 2026. It names no vendor product (not C2PA, not SynthID), but it is more prescriptive than "technology-neutral" suggests: it commits signatories to an imperceptible watermark, exempts text under 200 tokens, and expects two marking layers for media but only one for free-form text, because free-form text cannot carry metadata.
  • The Commission publishes three optional icons for labelling AI-generated content, and they serve the Article 50(4) deployer disclosure duty, not the Article 50(2) marking duty. Claims that the EU mandated C2PA, a 24x24px icon or PMS 286C blue have no Commission source.
  • Signing is not a safe harbour. The Commission concluded on 8 July 2026 that the Code adequately covers the Article 50(2), (4) and (5) obligations, the AI Board adopted its Adequacy Assessment the next day, and the Commission states in the same breath that "Adherence to the code does not constitute conclusive evidence of compliance with these obligations."
  • Providers mark outputs. Deployers separately disclose deepfakes and certain public-interest AI text, and lawyers still disagree on what counts as genuine human editorial review.
  • Anthropic's Claude marking rollout says its watermark applies "wherever Claude is offered, worldwide." A regional compliance deadline is already the reason Claude's output looks the way it does no matter where you live.
  • OpenAI's first text watermark, textGrain, was announced on 2026-10-05, about two months after the rules took effect. For consumers it covers the EU only, ChatGPT and Codex text across all plans, rolling out over the coming weeks; API customers worldwide can opt in. OpenAI's post says the AI Act "requires generative AI providers to make generated text identifiable in a machine-readable way" but names no article. Its detector is limited at launch to approved researchers and expert organizations.
Under nine months: two text watermarks, detectors almost nobody can use, and a rollout that finally has a date

Provider moves and regulatory dates on one line. Entries through 2026-08-11 were verified against a primary source on 2026-08-12, the 2026-09-01 entry on 2026-09-03, the 2026-09-04 entry on 2026-09-05, the 2026-09-14 and 2026-09-25 entries on 2026-09-25, the 2026-10-05 entry on 2026-10-06, and the 2026-09-30 entry on 2026-10-07. Entries marked Not yet are scheduled or open items that have not been verified as happened.

  1. Provider

    OpenAI adds SynthID to images

    Images from ChatGPT, the API and Codex get an invisible watermark alongside C2PA Content Credentials. Text is not covered at this point; OpenAI announces its text watermark on 2026-10-05.

  2. Regulation

    EU Code of Practice published

    Commits signatories to an imperceptible watermark, exempts text under 200 tokens, and accepts one marking layer for free-form text against two for everything else.

  3. Provider

    Meta ships Content Seal

    Images only, for Muse Image. The framework Meta open-sourced does cover text, but that component is a preprint with no deployment claim.

  4. Regulation

    Regulation (EU) 2026/1744 adopted

    The Digital Omnibus on AI inserts Article 111(4), creating a four-month transitional period for systems already on the market.

  5. Provider

    Claude Opus 5 ships

    Nine days before Anthropic's own marking threshold, so it launched unmarked, as every generally available Claude model before it did. Anthropic's 2026-09-04 email to Claude for Work administrators then scheduled Opus 5 output to carry the watermark from 2026-09-09. Its 2026-09-25 email to Claude Platform customers says the mark began on 2026-09-14, and its help page, re-read that day, lists Opus 5 as marked.

  6. Provider

    OpenAI adds audio; ~190 sign the Code

    Audio provenance lands two days before the law applies. The transparency Code reaches roughly 190 signatories including Anthropic, Google, Meta, Microsoft, Mistral and OpenAI.

  7. Regulation

    Article 50 applies, and so does Anthropic's threshold

    EU transparency duties become applicable. The same date is Anthropic's cutoff: models launched on or after it carry marking at launch. On this date no shipped model did, which stayed true for thirty days.

  8. Coverage

    The news cycle

    Two posts pull about 1.3M and 1.2M views and coverage follows, eight days after the feature it describes. Most of it reports the watermark as live.

  9. Provider

    Claude ships marked models, and a gated detector

    Anthropic releases Fable 5.1 and Mythos 5.1, the first Claude models launched after its own 2026-08-02 threshold, and its help centre names them as supported. The promised text detection API enters private preview the same day, restricted to regulators, law enforcement, media, fact-checkers, researchers, educational bodies, EU civil society, and enterprises with their own verification duty; the 2026-09-04 administrator notice summarises that limit as "eligible EU organizations". The first detector for a production text watermark, and not one the public can use. Files are the separate case: Anthropic's help page points readers to a free, ungated checker at claude.com/check-files that reads C2PA Content Credentials and states outright that it does not check text.

  10. Provider

    Opus 5 gets a model name and a date, in an admin notice

    An email to Claude for Work administrators, headed "Text watermark extends to Claude Opus 5", says Opus 5 responses carry the watermark from 2026-09-09 and that other current Claude models "will follow over the coming weeks". It also says the mark is applied at the model layer, which is why it reaches every surface, and that there is no admin or user setting to turn it off. When read on 2026-09-05, the help page it directs readers to still named only Fable 5.1 and Mythos 5.1, and the 2026-08-14 news post said "coming months" rather than coming weeks. Anthropic's later documents give 2026-09-14.

  11. Provider

    Claude Opus 5 output carries the watermark

    The first model launched before Anthropic's own threshold to be marked. The 2026-09-04 administrator notice had said 2026-09-09; Anthropic's 2026-09-25 email says 2026-09-14, and the help page's per-model table lists Opus 5 as marked, with cloud partners phased in over the following week.

  12. Provider

    Three more models get a date, and the retrofit gets a deadline

    An email to Claude Platform customers, headed "Watermarking begins September 30, 2026", schedules the text watermark for Claude Fable 5, Claude Sonnet 5 and Claude Opus 4.8. The help page, re-read the same day, replaces its two-model sentence with a per-model table that also marks Opus 5.5, and says every model released before 2026-08-02 will be covered by 2026-12-02.

  13. Provider

    Fable 5, Sonnet 5 and Opus 4.8 carry the watermark

    The date in Anthropic's 2026-09-25 email. The help page did not tick these three models on 2026-09-25; re-read on 2026-10-07, its table ticks their text watermark on first-party surfaces and on cloud partners, so the mark is confirmed. The table gives no start date, so September 30 rests on the email. A footnote on the cloud-partner ticks says "Rollout on Amazon Bedrock will complete by October 12." The same re-read found that the help page no longer says every model released before 2026-08-02 will be covered by 2026-12-02.

  14. Provider

    OpenAI announces textGrain, its first text watermark

    OpenAI says it will add an invisible watermark to eligible ChatGPT and Codex text in the EU over the coming weeks, and lets API customers in every region opt in for select models, off by default. Consumers outside the EU are not marked at launch. The detector is limited to approved researchers and expert organizations, by application.

  15. RegulationNot yet

    Transitional deadline for Article 50(2)

    Providers of generative systems placed on the market before 2026-08-02 must satisfy the machine-readable marking duty. Article 50(1) disclosure had no grace period.

  16. RegulationNot yet

    Detector interoperability commitment

    Code signatories committed to implementing an interoperability solution for their detection mechanisms: a public API, an embedded signpost, a shared consortium tool, or equivalent. Voluntary, and the first real date on the detector question.

Read down the column and the pattern holds with two exceptions: every shipped provenance feature in this window is media, except Claude's text watermark and OpenAI's textGrain, and both text detectors went to vetted organizations or approved researchers rather than the public. The date that could change that for an ordinary reader, the voluntary 2027-02-02 interoperability commitment, is still ahead.

Figure 2

Five tiers of EU AI marking obligation, from binding law to invented spec

Most confusion about Article 50 comes from collapsing these five into one. A legal duty, a voluntary code, an optional icon, an industry standard, and a marketing rumour are not the same kind of thing.

TierStatusWho it bindsExampleWhat it does not do
Required by Article 50Binding lawProviders and deployersMark synthetic output machine-readably, 50(2). Disclose deepfakes, 50(4).Name any technology
Voluntary Code of PracticeOpt inSignatories onlyRoughly 190 signatories, incl. Anthropic, Google, Meta, Microsoft, OpenAIReplace the legal duty
Optional EU iconOptionalNobody, by itselfThree official icons, four variations, free SVG and PNGEstablish compliance on its own
Industry standardNot mandatedWhoever adopts itC2PA, SynthIDAppear in any EU legal text
Rumour or unsupportedUnsupportedNobody24x24px minimum, PMS 286C blue, 5mm print size, mandated C2PAExist in any Commission source

Method Tiers assigned from the AI Act text, the Code of Practice on Transparency of AI-Generated Content, and the Commission's published icon page. Rumour tier lists claims with no Commission source.

Checked 2026-08-13

What does EU AI Act Article 50 require of providers?

Official announcement

Article 50's provider duty quoted exactly, the three exemptions in Article 50(2) itself, and the five output categories the Commission's FAQ puts outside marking altogether.

Article 50 tells providers, general-purpose AI providers included, that synthetic audio, image, video, and text output has to be marked in a machine-readable format and detectable as artificially generated or manipulated. The qualifier is "as far as technically feasible."

It deliberately names no vendor product. Signed C2PA-style metadata, a statistical watermark like SynthID, or something nobody has built yet could all satisfy it, so long as the result is genuinely effective and interoperable.

The Code of Practice and the Commission's Guidelines do not name a technology either. Both set the bar at marking that is "effective, interoperable, robust and reliable," as far as technically feasible.

Law firm Jones Day reads that silence as intentional, writing that "no single labelling or marking technique is sufficient in all cases." It recommends a multilayered approach that mixes visible labels with invisible, machine-readable signals.

The European Commission's FAQ on Article 50 lists the outputs it treats as outside the marking duty. Marking is not required for:

  • Short sequences of numbers, symbols, or letters
  • Source code
  • Machine-to-machine output no human ever sees
  • Closed-loop industrial processes, short of their final output
  • Standard editing-assistive functions

That last category is the loosest of the five and the one most likely to be argued over.

Article 50(2) carries a shorter exemption list of its own. The paragraph itself does not apply to:

  • AI systems performing an assistive function for standard editing
  • Outputs that do not substantially alter the input data provided by the deployer, or its meaning
  • Uses authorised by law to detect, prevent, investigate or prosecute criminal offences

The Code of Practice adds carve-outs on top. As OpenAI's help page summarises it, the Code does not require marks on outputs under 200 tokens or on code snippets.

What do the Commission's Guidelines require?

Confirmed

Adopted 20 July 2026 as C(2026) 5054 final. They interpret Article 50 rather than change it, and they are far more specific than the article about detection.

The Guidelines require two things together, marking and available detection, and they define what machine-readable means, which Article 50 never does. The Commission adopted its Guidelines on the Article 50 transparency obligations on 20 July 2026, as document C(2026) 5054 final. They call themselves "a first interpretation with practical examples" rather than new law, and they answer several questions the article leaves open.

Start with what machine-readable actually means, because the article never defines it. The Guidelines do: marks must be "structured in a way that allows software applications to easily identify, recognise and extract them without human intervention," and perceptible labels are "not excluded as a complementary measure" on top of that.

Watermarking is one technique among several, not the mandated one. Providers "may rely on a single marking technique or a combination of techniques," and the Guidelines point at Recital 133's examples: watermarks, metadata identifications, cryptographic methods for proving provenance and authenticity, logging methods, and fingerprints.

The detection duty has a named audience. The Guidelines say the provider "is obliged to ensure that the means of detection are available to the persons potentially exposed to the content," and that detection should produce human-readable results indicating whether content was AI-generated or manipulated.

There is also a preference about whose detector it should be. Providers "must rely on publicly-available industry standard detection solutions" that any third party can implement, ideally executable locally on the device; a provider's own or a third party's detector is permitted where such standards do not yet exist, "in particular at the initial stage of the implementation of Article 50(2) AI Act for watermarking technologies."

That fallback is explicitly temporary. The Guidelines say the possibility "should be limited in time until harmonised standards and a standardised provider-agnostic interoperable detection solution emerge that is secure, privacy-preserving and locally executable."

Two timing points close the document, and both get misread. Systems that are partly interactive and partly generative get the 2 December 2026 transitional period "only with regard to the marking obligation under Article 50(2)," while the duty to disclose that a person is interacting with an AI applied from 2 August 2026 with no grace period at all.

And nothing has to be marked backwards. Content generated or manipulated before 2 August 2026 "do not need to be marked or labelled retroactively," though text generated before that date and published on or after it does need labelling.

Who is allowed to check whether text is AI-generated?

Confirmed

The Code of Practice permits a gated detector for free-form text, for a limited time, and names the groups that must get free and unthrottled access anyway.

Under the Code of Practice, free-form text detection may be restricted to verified expert end-users, while regulators, law enforcement, media, fact-checkers, trusted flaggers, independent researchers, educational and research institutions, and civil society organisations must get free and unrestricted access. The Code of Practice draws a distinction the Guidelines do not: text detection may be gated. In its own words, signatories "may restrict access to detection mechanisms associated to watermarking techniques for free-form text to the extent that they have a lower level of reliability and robustness and that they may produce misleading or low-confidence results."

The reasoning is that a weak result shown to the general public misleads more than it informs, while the same result is useful to someone trained to read it. So the Code routes it to "verified expert end-users with a legitimate need" under "appropriate access controls and safeguards."

That permission is time-limited on the Code's own terms. Any restriction "will be limited in time until more reliable and robust detection mechanisms have emerged and have been adopted as the state of the art for detection mechanisms for the watermarking of free-form text."

The Code also names who cannot be charged or throttled. Signatories "will make the detection solution available free of charge" and "will always provide free access to their detection solution, without any restriction on the volume of requests," to:

  • Competent market surveillance authorities and other regulators
  • Law enforcement authorities
  • Media and fact-checkers
  • Trusted flaggers
  • Independent researchers
  • Educational and research institutions
  • Civil society organisations

The Code is voluntary, and the Commission has assessed it rather than enacted it. On 8 July 2026 the Commission concluded that it "adequately covers the obligations provided for in Articles 50(2), (4) and (5) AI Act and facilitates their effective implementation," and the AI Board adopted its Adequacy Assessment the following day, 9 July 2026.

Read the caveat the Commission attaches to its own opinion: "Adherence to the code does not constitute conclusive evidence of compliance with these obligations." Signing buys a presumption and a smoother enforcement posture, not immunity.

About 190 organisations had signed by the end of July 2026, and the Commission names Anthropic among its examples of Section 1 signatories, alongside Aleph Alpha, Black Forest Labs, Cohere, Google, Meta, Microsoft, Mistral, OpenAI, and Synthesia. Meta's signature is dated 28 July 2026.

What must deployers disclose under the EU AI Act?

Official announcement

Article 50 gives providers one duty and deployers the rest. The company that marks the output is usually not the company that owes the disclosure.

Deployers have to disclose deepfakes, and disclose AI-generated or manipulated text published to inform the public on matters of public interest. Providers mark; deployers disclose. They can be two entirely different companies, and one piece of content can trigger duties owed by both at once.

Article 50 splits its four duties between the provider, who builds a system, and the deployer, who puts it in front of end users:

  • Article 50(1): deployers of directly interactive AI systems, such as chatbots, must inform people they are interacting with an AI system, unless that is already obvious
  • Article 50(2): providers must mark synthetic output in a machine-readable format, detectable as artificially generated
  • Article 50(4): deployers must label deepfakes, meaning realistic AI-generated or manipulated image, audio, or video content resembling existing people, objects, places, or events
  • Article 50(5): deployers publishing AI-generated or manipulated text on matters of public interest must disclose that it was artificially generated

Only the second is the provider's. A provider making its output machine-detectable does not satisfy a deployer's separate duty to tell the person on the other end, even when both duties attach to the same content.

The text duty has an exception where a human exercised editorial responsibility and control over the publication. Law firm Greenberg Traurig's reading of the Commission's own guidance adds detail the statute does not give:

  • The deepfake duty applies regardless of whether anyone intended to deceive
  • It covers realistic depictions of fictional people, not only real ones, so a realistic video of a person who does not exist still needs a label
  • Whether content "appears deceptive" gets judged against potentially vulnerable audiences, a tougher bar than the EU's usual "average consumer" standard
  • Multiple Article 50 duties can stack on a single system

Jones Day notes that the Code of Practice allows lighter or adapted labelling for artistic, fictional, or satirical works. That changes how light the label can be, not whether one is owed, and how far the adaptation can go is untested.

These are law-firm readings, not Commission rulings.

What are the official EU AI content icons for?

Official announcement

Three official icons, optional to use, aimed at the deployer disclosure duty rather than the provider marking duty.

The Commission publishes an official icon set for labelling AI-generated content. It is easy to miss because it answers a different question than machine-readable marking does.

There are three icons:

  • A basic icon, for when AI was involved in creating deepfake content or published text
  • Fully AI-Generated, for content generated entirely by AI with no human-created elements beyond prompting
  • Partially AI-Modified, for pre-existing human-made content that AI turned into a deepfake

Each comes in four variations: black, white, and both at 50 percent transparency, downloadable as SVG and PNG.

The Commission is direct about their status: "The use of these EU icons is optional, but the labelling requirements under Article 50 AI Act are not." It adds that using them "does not establish legal compliance by itself."

The icons were user-tested. The Commission notes performance improved across all measures when the basic icon was paired with a text label such as "modified."

Placement rules live in Section 2 of the Code of Practice. The icon must be perceivable at first exposure, must sit where no overlay covers it, and must remain visible when the content is reshared or downloaded.

The icons are free for anyone to use without attribution to the Commission or the AI Office. A non-signatory using them should not be read as claiming adherence to the Code.

Did the EU mandate C2PA and a 24x24px icon?

Rumor/speculation

Pixel dimensions, a Pantone code, a February 2027 deadline, none of it sourced to the Commission, and the real EU icons carry none of it.

No. No Commission source supports the C2PA mandate, the pixel dimensions or the Pantone colour. A cluster of marketing and SEO sites assert that the Commission or the AI Office effectively endorsed C2PA as the primary technical pathway for Article 50 compliance. The specifics they cite:

  • A required icon at a 24x24px minimum
  • PMS 286C blue as the mandated color
  • A 5mm minimum size in print
  • An "EU AI Office Q1 2026 guidance" mandating C2PA plus SynthID as the compliance default
  • A February 2027 interoperable-detection deadline

None of this appears in the Code of Practice, the Guidelines, or any Commission source. No Commission text mandates a pixel dimension, a Pantone colour, or a print size, and none names C2PA as a required pathway.

The rumour sits next to something real. The official EU icons described above do exist, with placement rules in Section 2 of the Code, but they are optional, they concern visible labelling rather than machine-readable marking, and they carry none of the invented specs.

Treat the pixel dimensions, the Pantone code, the print minimum, and the C2PA mandate as rumor until a primary source confirms them. If you want to know what the real standard specifies, read the C2PA Content Credentials page.

When did EU AI Act Article 50 take effect?

Confirmed

Two dates, a ceiling of 15 million euros or 3 percent of global turnover, zero enforcement actions nine days in, and uneven national readiness.

Article 50's transparency rules applied from 2 August 2026. A second date, 2 December 2026, is a transitional deadline for certain Article 50(2) marking obligations, and only for systems already placed on the market before 2 August.

Fines run up to 15 million euros or 3 percent of a company's global annual turnover. EU institutions face up to 750,000 euros.

Enforcement is spread across three kinds of body:

  • National market-surveillance authorities in each member state
  • The EU AI Office
  • The European Data Protection Supervisor, for EU institutions specifically

As of 11 August 2026, nine days after the rule took effect, no fine, corrective order, or enforcement action had been publicly reported anywhere.

Veeam field CTO Edwin Weijdema expects corrective and suspension orders to significantly outweigh headline-grabbing fines in year one. He also flags an unresolved scope question: whether AI-agent interactions, or ticketing and procurement portals, even count as "direct interaction" with a person.

Member states are at visibly different stages of readiness:

  • Germany's KI-Marktüberwachungsgesetz names the Bundesnetzagentur as default national market-surveillance authority and EU AI Office contact point, backed by an internal coordination unit
  • France, per a January 2026 report, had not formally designated its competent authorities, after a draft list of 17 candidates including CNIL, DGCCRF, and ARCOM was withdrawn from the relevant bill

France's status was last confirmed in January 2026, so recheck it rather than assume it still holds.

What do lawyers still disagree about in Article 50?

Community discussion

Three phrases in the Commission's own Guidelines still have no agreed meaning, months after the rule went live.

Three terms in Article 50 remain genuinely undefined, and law firm Cooley's reading names them:

  • The "already obvious" exception to interactive-AI disclosure
  • How far "public-interest matters" extends for the deployer text-disclosure duty
  • What counts as "substantive human editorial review" strong enough to trigger the editorial exemption

Greenberg Traurig adds a warning on that third one. Simply having a human check AI-generated content is not, on its own, sufficient to qualify.

Cooley flags one concrete upside too. Signing the Code of Practice earns "a degree of presumption of conformity" plus more favorable enforcement treatment, which is presumably part of why roughly 190 organizations signed on by the end of July 2026.

The first term has a practical edge for support chatbots. Veeam's Edwin Weijdema asks whether an AI agent inside a ticketing or procurement portal is "directly interactive" at all, and the Commission has not precisely defined "already obvious." Companies deploying customer-facing AI now are making judgment calls ahead of the case law.

None of this has been settled by a court. It is informed legal commentary reading Commission text that leaves room, which makes it the live edge of the rule rather than background trivia.

Why does an EU rule change Claude's output worldwide?

Community discussion

Why does a European deadline change what Claude does in Ohio? Because maintaining two behaviors costs more than maintaining one.

Anthropic's marking applies wherever Claude is offered, worldwide, and the explanation this site finds most likely is cost: maintaining one behavior for EU users and another for everyone else is expensive and easy to get wrong. Anthropic has not published a reason. On 2 August 2026, the day the transparency rules took effect, an r/ClaudeAI thread thanking the EU for making Claude watermark its output collected the whole argument in one place. The reaction split three ways:

  • One camp welcomed the EU for forcing useful disclosure
  • Another resented that a European compliance deadline was shaping a product used everywhere
  • A third argued about whether biasing token choice can be done without hurting quality, citing Google's SynthID as proof subtler text watermarking is possible

The commenter who quoted Anthropic was right, and it's checkable. Anthropic's support article says the marking applies across Claude's products and surfaces "wherever Claude is offered, worldwide," not only in the EU.

California's own AI Transparency Act landed on the identical day, 2 August 2026, after a separate state law delayed it to that date. Nobody has confirmed the timing was coordinated rather than coincidental.

OpenAI made the opposite choice for text. Its textGrain watermark, announced on 2026-10-05, is rolling out to ChatGPT and Codex text in the EU only, and OpenAI says it is "not making text watermarking a global default at launch." So the cost of running two behaviors did not stop at least one large provider from doing it.

Treat the worldwide-scope fact as confirmed from Anthropic directly. Treat the opinions about whether that is good policy, and the California coincidence, as context rather than evidence either way.

FAQ

Does the EU AI Act mandate one specific watermark technology?

No. Article 50 requires machine-readable marking and detectability as far as technically feasible, but names no universal technology for any modality. Claims that the EU officially endorsed C2PA as the required pathway are not supported by the Code of Practice or the Guidelines themselves.

Does Article 50 prove a provider's text is watermarked today?

No. Article 50 creates regulatory obligations and pressure, nothing more. Deployment still needs provider-specific evidence, such as Anthropic's Claude marking article, Google's SynthID Text documentation, or OpenAI's 2026-10-05 post on EU text provenance.

Does an EU rule only affect EU users?

Not necessarily. Anthropic's own marking policy, introduced the same day Article 50 took effect, says it applies "wherever Claude is offered, worldwide." A regional transparency deadline can end up shaping a product for every user, not just the ones the regulation was written for. OpenAI went the other way: its textGrain text watermark, announced 2026-10-05, is rolling out to consumer ChatGPT and Codex text in the EU only, with a global opt-in for API customers.

Has anyone actually been fined under Article 50?

Not as of 11 August 2026, nine days after the rule took effect. No enforcement action, fine, or corrective order has been publicly reported. One industry prediction expects corrective and suspension orders to outnumber major fines in the rule's first year, but that is a forecast, not a reported outcome. National enforcement is also uneven: Germany has a named authority in place, while France's designation status was last reported as unresolved in January 2026.

Does machine-readable mean C2PA?

Not under the legal text. Neither the Code nor the Guidelines names C2PA or any other standard as required, and Jones Day advises providers to combine multiple signals rather than rely on one.

Is there an official EU icon for AI-generated content?

Yes, and it is optional. The Commission publishes three icons (a basic icon, Fully AI-Generated, and Partially AI-Modified) in four variations each, free to use without attribution. They support the Article 50(4) deployer disclosure duty, not the Article 50(2) marking duty, and using them does not establish compliance by itself. The circulating claims about a 24x24px minimum, PMS 286C blue, and a 5mm print size have no Commission source.

Is a single required technical marking standard coming?

Nothing is confirmed. No harmonized standard for Article 50 marking has been published. Until one exists, "effective, interoperable, robust and reliable" is the bar providers have to clear.

Is a machine-readable watermark enough disclosure on its own?

No. Machine-readable marking is a provider obligation under Article 50(2) and aims to make output software-detectable. Disclosure duties under 50(1), 50(4) and 50(5) fall on deployers and aim to inform the person on the other end, through a chatbot notice, a deepfake label, or a text disclosure. A marked system can still need separate human-facing disclosure.

Does the deepfake labelling duty require an intent to deceive?

No. Per legal commentary, the deepfake disclosure duty applies regardless of intent to deceive, and it covers realistic depictions of fictional people as well as real ones.

Do satirical or fictional AI-generated videos still need a deepfake label?

Yes, but the label can be lighter. The Code of Practice permits lighter or adapted labelling for artistic, fictional, or satirical works. How much lighter, and who decides a given work qualifies, has not been tested by any enforcement action.

Is having a human check the output enough to count as editorial review?

Not necessarily. One law firm's reading of the Commission's guidance states that simply having a human check AI-generated content is not automatically sufficient, and the bar for "substantive human editorial review" remains undefined. Multiple Article 50 duties can also stack on one system, so clearing one exemption does not clear another.

Next steps

Sources and citation status