Last updated: August 2, 2026 · By Vishal Swami, Founder & Lead AI Reviewer, AISagely
The EU AI Act's Article 50 becomes enforceable today, August 2, 2026, requiring AI providers to mark synthetic audio, images, video, and text as machine-generated, and requiring anyone who deploys a deepfake to disclose it. It's the first binding AI-content labeling law to take effect in a G7 jurisdiction, and it applies to any provider or deployer reaching users in the EU, regardless of where the company is based.
Short answer: As of August 2, 2026, EU AI Act Article 50 requires AI providers to mark generated audio, images, video, and text as artificially produced in a machine-readable format, and requires deployers to disclose deepfakes and AI-written text on public-interest topics. Fines reach €15 million or 3% of global turnover. Systems already on the market get until December 2, 2026 to add the technical markings.
I track AI regulation the same way I track product launches on this site — by reading the primary text, not the press release. Article 50 has been law since the EU AI Act entered into force in August 2024; what changes today is that it's now enforceable, with real penalties attached. Here's what it actually requires, who it applies to, and which AI tools already comply.
What Article 50 actually requires
Article 50 has two separate tracks, and mixing them up is the most common mistake I'm already seeing in early coverage:
- Providers (the companies that build and ship AI systems, like OpenAI, Google, or Midjourney) must mark any synthetic audio, image, video, or text their system generates in a "machine-readable format," so it's detectable as artificially generated or manipulated. Think embedded metadata or a cryptographic watermark, not necessarily a visible stamp.
- Deployers (anyone who uses an AI system to create or publish content, including businesses and individual creators) must clearly disclose when they've published a deepfake, or AI-generated text on a matter of public interest that wasn't reviewed by a human editor.
The European Commission’s own FAQ on Article 50 is blunt about the standard: labels have to be "effective, interoperable, robust and reliable as far as this is technically feasible." There's no single required watermark technology — the law leaves room for C2PA metadata, SynthID-style invisible watermarks, or visible on-content labels, as long as the result is genuinely detectable.
Who has to comply, and from when
| Requirement | Applies to | Effective date |
|---|---|---|
| Mark AI-generated audio/image/video/text (machine-readable) | Providers | August 2, 2026 (new systems); December 2, 2026 (systems already on the market) |
| Disclose AI chatbots/interactive systems, unless obvious | Providers | August 2, 2026 |
| Disclose deepfakes at first exposure | Deployers | August 2, 2026 |
| Label AI-written text on public-interest topics without human review | Deployers | August 2, 2026 |
| Content generated before August 2, 2026 | N/A | No retroactive labeling required |
That grace period matters: the AI Omnibus provisional agreement reached in May 2026 gave generative AI systems already on the market before today until December 2, 2026 to finish implementing the technical marking. So a tool can be non-compliant on the labeling mechanics for another four months and still be operating legally, provided it was already on the market before today.
The deepfake rule is stricter than the general labeling rule
A deepfake, under Article 50(4), is AI-generated or manipulated image, audio, or video that resembles a real person, place, or event closely enough that it "would falsely appear to be authentic or truthful." Deployers publishing one must disclose it clearly, even if the content is otherwise legal. The only carve-out is for content that's "evidently artistic, creative, satirical, fictional, or analogous" — a political meme or an obvious parody video gets a lighter, less intrusive disclosure than, say, a fabricated news clip.
This is the part I'd flag hardest for US-based creators and marketers: the rule follows the audience, not the company's home country. If your AI-generated video, ad, or image reaches people in the EU, the disclosure obligation applies to you, even if you've never set foot in Europe.
In my testing: which AI tools already label their output
Checking for a C2PA manifest or a visible AI label has become part of every image and video tool review I run on this site, and going into today's deadline, coverage is uneven. When I checked OpenAI's own documentation and independent audits from outlets like PetaPixel, ChatGPT and DALL·E images already carry a C2PA Content Credentials manifest — it names OpenAI as the producer, timestamps the generation, and is verifiable at contentcredentials.org. Nearly 200 companies, including OpenAI, Google, Meta, Microsoft, and Anthropic, signed the EU’s voluntary Code of Practice on AI-generated content ahead of today's deadline, which is the clearest signal yet that the big providers built the machinery before the law forced them to.
Where it still breaks down, based on what I've seen testing image tools this year, is downstream: a screenshot or a re-upload strips embedded metadata almost every time. I saw exactly this failure mode when Google’s Earth AI image generator got pulled — its SynthID watermark didn't survive a basic screenshot, dropping an AI-detection tool's confidence to 1% on a clearly generated image. Article 50 requires the label at the point of generation; it doesn't guarantee the label survives the way people actually share content.
Comparison: AI tool labeling status as of August 2, 2026
| Tool | Signed EU Code of Practice | Embeds C2PA metadata | Survives a screenshot/re-upload |
|---|---|---|---|
| ChatGPT / DALL·E (OpenAI) | Yes | Yes | No |
| Gemini / Nano Banana (Google) | Yes | Yes (SynthID) | No |
| Meta AI (Meta) | Yes | Partial | No |
| Claude (Anthropic) | Yes | N/A (text-only outputs) | N/A |
| Midjourney | Not publicly listed as of this writing | Limited | No |
Rows reflect public statements and third-party testing as of August 2, 2026; treat "survives a screenshot" as effectively "no" for every current watermarking approach — none of the major invisible-metadata schemes are built to survive re-encoding.
Common mistakes to avoid
The mistake I'd expect most US marketers to make first is assuming this doesn't apply to them because their company isn't based in the EU. It applies the moment your AI-generated content reaches an EU audience — a targeted ad, a social post, an email campaign, all of it.
Second is treating a provider's built-in watermark as your compliance. If you're a deployer publishing a deepfake or AI-written news content, the disclosure obligation is yours, separate from whatever metadata the underlying model already embeds.
Third is confusing the two deadlines. New systems need to comply with the marking requirement starting today, August 2, 2026. Systems already on the market get until December 2, 2026 for that specific technical requirement — but the deployer disclosure obligations (deepfakes, public-interest text) apply from today regardless.
Fourth is assuming a small disclaimer buried in a terms-of-service page counts as disclosure. The Commission's guidance calls for the label to be presented "clearly and distinguishably" at the point where a person encounters the content, not tucked away where nobody will read it.
What this means if you publish AI-generated content
If you're a business or creator using AI tools to make images, video, audio, or text for an EU audience, here's the practical checklist:
- Check whether your tool already embeds credentials. Most major providers — OpenAI, Google, Meta, Anthropic — signed the EU's Code of Practice and already mark output at the point of generation.
- Add your own disclosure for anything deepfake-like. A caption noting "This image was created with AI" is the safe default for any photorealistic image or video of a real person, place, or event that didn't happen.
- Don't rely on the platform to catch it for you. Metadata strips on screenshot or re-upload, so if you're repurposing AI content across formats, keep your own disclosure attached to the caption or on-screen text, not just the file's metadata.
- Watch the December 2, 2026 date too. If you build on a model or platform that launched before today, its provider still has until then to finish the technical marking — that's not an excuse to skip your own deployer-side disclosure in the meantime.
- Keep a record of what you generated and when. Content published before today doesn't need retroactive labeling, so timestamps matter if a compliance question ever comes up.
For a running list of how AI vendors' claims hold up against testing, my AI tool ratings hub and AI tool reviews page track stories like this alongside the tools themselves. If you're trying to spot AI-generated text specifically — including your own drafts before you publish them — my guide to spotting AI writing walks through the detection methods that still hold up. For image generation tools and how their output is tagged, see my ChatGPT image tool walkthrough and my Gemini AI guide. I log regulatory changes like this one, alongside product launches and rollbacks, on AISagely’s AI news hub.
My take
The honest read on today's deadline: the biggest AI providers were largely ready for it. Signing the voluntary Code of Practice months in advance, and shipping C2PA metadata before the legal deadline forced their hand, tells me OpenAI, Google, and Meta all decided compliance was cheaper than the alternative. The gap that actually matters now sits with deployers, not providers — the businesses and creators who have to add their own disclosure on top of whatever metadata a tool already embeds, and who are far less likely to have a legal team watching this deadline. My honest caveat: metadata-based labeling still doesn't survive a screenshot, which means the law's real-world effectiveness depends on people manually disclosing AI use, exactly the behavior it's trying to make unnecessary.
Frequently Asked Questions
Does the EU AI Act's labeling rule apply to US companies?
Yes, if your AI-generated content reaches people in the EU. The obligation follows the audience the content reaches, not where your company is headquartered.
What counts as a deepfake under Article 50?
AI-generated or manipulated image, audio, or video content that resembles a real person, place, or event closely enough that it "would falsely appear to be authentic or truthful," per the EU AI Act's definition. Obvious satire, art, or fiction gets a lighter disclosure requirement.
Do I need to label AI content I created before August 2, 2026?
No. The European Commission's guidance is explicit that content generated before the applicability date doesn't need retroactive labeling, though voluntary labeling is encouraged.
What happens if a company doesn't comply?
Fines can reach €15 million or 3% of global annual turnover, whichever is higher, with proportionality considerations for smaller companies.
Which AI tools already label their output correctly?
As of today, ChatGPT/DALL·E, Gemini, Meta AI, and Claude's providers have all signed the EU's Code of Practice on AI-generated content and embed some form of machine-readable credentials. None of the current watermarking methods reliably survive a screenshot or re-upload, so provider-side labeling shouldn't be your only disclosure method.