What EU AI Act Article 50(2) Requires

Most teams heard "EU AI Act watermarking" and translated it into "slap a watermark on generated images." That's too simplistic, and honestly, a little dangerous.

If you build image or video features, Article 50(2) is not really about adding a logo in the corner. It's about whether your output is marked and still detectable as AI-generated when it leaves your system. That distinction matters a lot. [1]

Key Takeaways

• Article 50(2) applies from 2 August 2026 to providers of systems that generate synthetic audio, image, video, or text. [1]
• The law does not specifically require a visible watermark. It requires machine-readable marking and detectability, as far as technically feasible. [1]
• Recital 133 mentions watermarks, metadata labels, and cryptographic methods as examples, not as a single mandated technique. [1]
• "Technically feasible" is not a free pass. Providers still need an approach that is effective, interoperable, robust, and reliable. [1]
• In practice, image and video watermarking is still fragile under compression, cropping, edits, and forgery attacks, which makes implementation harder than the headlines suggest. [1][2]

---

What does Article 50(2) actually require?

Article 50(2) requires providers of AI systems that generate synthetic image, video, audio, or text content to ensure outputs are marked in a machine-readable format and detectable as artificially generated or manipulated, as far as this is technically feasible. The law also says the solution should be effective, interoperable, robust, and reliable, while taking cost, content type, and the state of the art into account. [1]

That wording matters because it kills a few lazy assumptions.

First, the text is technology-neutral. The law does not say "use visible watermarks." It does not say "C2PA only." It does not say "metadata alone is enough." Instead, Recital 133 points to a toolbox: watermarks, metadata labels, and cryptographic methods. [1]

Second, the obligation is on providers of the generating system. If you ship a model or product that creates synthetic image or video outputs, you own the design problem. You do not get to outsource the issue to end users.

Third, "as far as technically feasible" is real, but limited. It recognizes that current marking methods are imperfect. It does not mean you can do nothing and call it a day. The standard still expects a reasonable technical solution grounded in the current state of the art. [1]

---

Does Article 50(2) mean visible watermarks on images and video?

No. Article 50(2) does not specifically mandate visible watermarks on every image or video; it mandates outputs that are machine-readable and detectable as AI-generated or manipulated. Visible watermarks may help in some cases, but they are only one possible implementation path and may not satisfy the full legal standard on their own. [1]

This is where a lot of commentary goes off the rails.

A visible badge can help with human disclosure. But the article's core language focuses on machine-readable marking and detectability. If your mark disappears after export, remixing, or transcoding, you may have a weak compliance story even if users briefly saw a label in your app.

For image and video teams, the practical implication is simple: think in layers, not stickers. A stronger design usually combines at least two things: user-facing disclosure and embedded provenance or detection signals.

Here's the cleanest mental model I found:

Requirement	What it means in practice	What often fails
Human understanding	Users can tell AI was involved	Tiny UI disclaimers nobody sees
Machine readability	Systems can inspect the output	Purely visual labels
Detectability	AI origin can be verified later	Metadata stripped on upload
Robustness	Signal survives common transforms	Cropping, compression, re-encoding
Interoperability	Others can read the signal	Proprietary closed detectors

That's why teams should stop asking, "Do we need a watermark?" and start asking, "Can another system still tell this is AI output after it moves through the internet?"

---

Why is compliance so hard for image and video output?

Compliance is hard because current watermarking and provenance methods are fragile under normal media workflows, and the legal standard asks for something stronger than a best-effort UI badge. Research published in 2026 argues that today's methods often struggle to meet the law's expectations for robustness, interoperability, and reliability. [1][2]

This is the catch.

The most relevant legal-technical paper I found argues that Article 50(2) creates a structural problem: the regulation expects reliable, interoperable marking, but does not define operational benchmarks, and the standards landscape is still unfinished. [1]

The technical side is rough too. Recent image watermarking research shows progress, but also a steady stream of removal and forgery attacks. In one 2026 paper on diffusion-model watermarking, the authors explicitly frame current schemes as vulnerable to removal and spoofing, even while proposing a stronger method. Their own conclusion is basically: better, yes; solved, no. [2]

So if you generate images or video, your risk is not just legal ambiguity. It is that normal platform behavior can destroy your signal:

• JPEG compression
• cropping
• resizing
• format conversion
• video transcoding
• post-editing and remixing

That is why Article 50(2) should be treated as a product architecture problem, not a launch checklist item. [1]

---

How should product teams prepare before August 2026?

Product teams should prepare by mapping every image and video output path, choosing a layered marking strategy, documenting tradeoffs, and testing whether AI-origin signals survive common transformations. The best approach is not perfection; it is a defensible, evidence-backed implementation tied to the current state of the art. [1][2]

If I were advising a product team shipping generative media in Europe, I would push a four-step workflow.

1. Audit where AI media is created, edited, exported, and shared. Include API responses, downloads, screenshots, embeds, and third-party publishing flows.

2. Separate on-screen disclosure from output-level marking. You likely need both. A visible "AI-generated" label inside your app is helpful, but it is not the whole story.

3. Test resilience. Run your marking approach through compression, cropping, resizing, transcoding, and light edits. If it fails instantly, you have learned something important before a regulator does.

4. Document why your approach is technically feasible today. That means recording known limits, cost tradeoffs, and why you chose one method over another.

A simple before-and-after compliance prompt can help internal teams get specific:

Before

Add watermarking for EU compliance.

After

Design an Article 50(2) compliance plan for our AI image and video outputs.

Include:
- user-facing disclosure in product UI
- machine-readable output marking
- post-export detectability strategy
- robustness tests for compression, cropping, resizing, and transcoding
- known limitations and "technically feasible" rationale
- rollout plan before August 2, 2026

This is exactly the kind of vague-to-useful transformation I like to automate with tools like Rephrase, especially when legal, product, and engineering teams all need a shared brief fast.

---

What should prompt and workflow designers do with this change?

Prompt and workflow designers should assume provenance is now part of the product surface, not just the model layer. If your team uses AI to generate images, storyboards, or video assets, your prompts, export flows, and editing steps should preserve disclosure and provenance rather than accidentally stripping them away. [1]

This is where prompt engineering quietly meets compliance.

If you use AI inside creative pipelines, your prompts should ask for outputs that fit your provenance workflow. For example, if you know downstream editors will heavily crop or recompress assets, your compliance design needs to account for that. And if your team writes internal specs through chat tools all day, Rephrase can help turn fuzzy requests into tighter implementation prompts before they hit your model or your ticketing system.

You can also find more articles on AI workflow design on the Rephrase blog.

---

August 2026 is close enough that "we'll handle watermarking later" is now a risky strategy. My take is simple: Article 50(2) is less about a visible badge and more about whether your generated media carries durable, inspectable evidence of AI origin.

If you ship image or video features, start designing for that now.

---

References

Documentation & Research

1. Transparency as Architecture: Structural Compliance Gaps in EU AI Act Article 50 II - arXiv cs.AI (link)
2. Towards Robust Content Watermarking Against Removal and Forgery Attacks - arXiv cs.LG (link)

Community Examples 3. [D] Impact of EU AI Act on your work? - r/MachineLearning (link)