DISCLOSETAGBETALocal-only mode

EU AI Act Article 50 for advertisers, from 2 August 2026

Article 50 of the EU AI Act — the transparency chapter — applies from 2 August 2026. The Commission's guidance on transparency of AI-generated content does not describe a transition or grace period beyond that date. If you run ads into the EU with AI-generated creative, this is the second disclosure regime landing on you inside two months, after New York's on 9 June.

Two rules an advertising image may have to satisfyIn effectAmazon disclosure rule2 Aug 2026EU AI Act Article 50From this date, one image can fall under both
Dates reflect when each obligation applies to advertisers, not when the text was adopted.

What Article 50 actually says

The obligations split by role:

Compliance can be shown through the Code of Practice on Transparency of AI-generated content, or through alternative means of equivalent adequacy.

An honest caveat. The Commission's transparency guidance does not set out specific requirements for AI-generated people in commercial advertising the way New York's statute does. Anyone telling you Article 50 is a drop-in equivalent of the synthetic performer law is overstating it. What is concrete is the date, the machine-readable marking duty, and the deepfake disclosure duty on deployers.

How it differs from New York's synthetic performer law

New York GBL § 396-bEU AI Act Article 50
In force9 June 20262 August 2026
Who it bindsAdvertisers running commercial adsProviders and deployers of AI systems
TriggerA synthetic performer — a figure that reads as human but is not any identifiable real personAI interaction, AI-generated or manipulated content, deepfakes
Disclosure formConspicuous disclosure in the adMachine-readable marking, plus informing people for deepfakes
Penalty$1,000 first violation, $5,000 afterSet by the AI Act's penalty regime

The two regimes point in the same direction but do not overlap neatly. New York cares whether the figure on screen looks like a person who does not exist. Article 50 cares whether audiences can tell — by machine or by notice — that content was AI-generated or manipulated at all.

The platforms have already moved

You can see this converging in the ad platforms without waiting for enforcement. Since July 2026 Google has permitted labels drawn directly into image and video creatives, and for campaigns targeting the EU, India and New York it renders a visible overlay on assets designated as AI created or edited. In other words, Google is already treating these three jurisdictions as one operational bucket. Google also says explicitly that using its label setting “doesn't guarantee compliance with specific regulations”.

The practical read: the platform toggle is a tool, not a safe harbour. If a creative needs disclosure, put the disclosure where a person can see it, and keep a record of what you did.

Are advertisers providers or deployers?

Article 50 splits its duties between the two, and most advertisers are neither in the obvious sense — which is exactly why the answer matters.

The practical read for an ad team: you are most likely a deployer, your generator's vendor is the provider, and you cannot assume the vendor's marking survives your production pipeline — which is the same problem as metadata being stripped between tagging and upload.

Does using Google's AI label discharge the obligation?

No, and Google says so itself: using the AI label setting “doesn't guarantee compliance with specific regulations”. The platform toggle does what the platform needs; the legal duty sits with the advertiser regardless.

In practice the two work together rather than one replacing the other. Set the platform's flag so its own rendering is correct, keep the machine-readable marking in the file so the Article 50 direction is covered, and where the audience needs to see something, put a visible label on the creative. Then record what you did — both regimes turn partly on what you knew and when.

What is coming after 2 August

The Commission points to the Code of Practice on Transparency of AI-generated content as a route to demonstrating compliance, or alternative means of equivalent adequacy. That phrasing leaves room for methods that are not yet settled — provenance standards such as C2PA are the obvious candidate for the machine-readable half, and are already what Amazon's XMP requirement resembles in miniature.

For an ad team the near-term move is unglamorous: know which creatives contain synthetic humans, keep a marking in the file, keep a visible disclosure where it is needed, and keep records. None of that depends on how the standards question resolves.

A practical checklist for ad creative

  1. Inventory which creatives contain AI-generated humans, separating generic synthetic people from real people who were merely retouched. The distinction decides which regime applies.
  2. Keep the machine-readable mark. Metadata — XMP dc:subject, C2PA and similar — is the machine-readable half. Amazon reads it today, and Article 50 pushes the same direction. Verify it survived after every export.
  3. Add a visible label where the platform will not add one for you. Burn it into the creative, keeping it away from edges that get cropped.
  4. Turn off crop-happy enhancements — Google names Asset Enhancements and Adaptive Layouts as features that can trim rendered content.
  5. Record the provenance: which tool generated the asset, who reviewed it, which markets it ran in, and what disclosure was applied. Both regimes turn partly on what you knew.
Generate a disclosure label →

Sources: the European Commission's guidelines on transparency of AI-generated content, and Google's advertising policy and Display & Video 360 documentation on AI content labels. This page summarises public documents and is not legal advice.