EU AI Act and AI Watermarking: Article 50 Explained

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 required technology. 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 obligation also carries a specific exemption list. 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. For the full breakdown and why the rule stays technology-neutral, see the machine-readable AI marking page.

Providers mark. Deployers disclose. They can be two entirely different companies, and one piece of content can trigger duties owed by both at once.

Deployers have to disclose deepfakes, and disclose AI-generated or manipulated text published to inform the public on matters of public interest. There are exceptions for human review and editorial responsibility.

Law firm Greenberg Traurig's reading of the Commission's own guidance adds texture the statute alone doesn't give you:

• The deepfake duty applies regardless of whether anyone intended to deceive
• It covers realistic depictions of fictional people, not only real ones
• 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

That is one firm's reading, not a Commission ruling. For the full four-duty breakdown, see the AI-generated content disclosure page.

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.

Law firm Cooley's reading names three genuinely undefined terms:

• 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.

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.

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.

The mechanism is boring and powerful. Maintaining one behavior for EU users and another for everyone else is expensive and easy to get wrong, so companies pick one behavior.

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.

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.