EU AI Act Article 50: what film and advertising producers have to mark
Enforcement begins in August 2026. Article 50 attaches to the content rather than to the employment relationship, which is why it catches productions that have already cleared every performer correctly.
At a glance
- Authority
- Regulation (EU) 2024/1689 — the EU AI Act
- Jurisdiction
- European Union
- Effective
- August 2026
Who this applies to
- Productions and campaigns distributed into the European Union
- Content containing AI-generated or AI-manipulated image, audio or video
- Post and finishing vendors responsible for export and delivery masters
Dates
| Date | Event |
|---|---|
| August 2026 | Article 50 transparency enforcement begins |
What Article 50 asks for
Article 50 of the EU AI Act sets transparency obligations for certain AI systems and their outputs. Two of them touch audiovisual work, and — this is the part most summaries get wrong — they fall on different parties.
Article 50(2) requires that AI-generated or AI-manipulated output be marked in a machine-readable format and be detectable as artificially generated. That duty sits on the provider of the generative AI system, not on the production. In the Act's vocabulary a production is a deployer; the tool vendor is the provider. Article 50(4) is the one that attaches to you: as deployer, you disclose that the content has been artificially generated or manipulated.
The practical consequence is that the marking task is a procurement question rather than a finishing question. Confirm with each AI vendor that their system marks its outputs, and keep the confirmation. Productions routinely over-comply here, spending finishing time on watermarking that Article 50(2) does not ask of them, while under-documenting the vendor confirmations that actually matter.
C2PA Content Credentials remain worth applying at export — not because Article 50(2) obliges you to, but because they give you a positive, contemporaneous record of what was generated and when. Treat credentials as evidence you choose to create, not as discharge of a duty you owe.
Why productions that did everything else right still get caught
The Article 50 trigger is the content and its distribution, not the contract under which it was made. A production can hold perfect SAG-AFTRA riders, a complete consent file and a clean chain of title, and still have nothing that satisfies a machine-readable marking obligation, because none of those artifacts live in the file.
This is also why it arrives late and badly. The obligation attaches when the title reaches the EU, and EU distribution is frequently a decision made after post has wrapped — a festival pickup, a territory sale, a platform adding a market. The finishing suite that could have applied credentials at export has moved on to another job, and the person now asking for provenance is a delivery coordinator with a spreadsheet.
The mitigation is to decide the export spec before finishing, on the assumption that EU distribution is possible rather than confirmed. Applying Content Credentials to material that never ships to the EU costs almost nothing. Not having applied them to material that does is a re-export.
Marking and disclosure are two different tasks
Machine-readable marking is invisible to the audience; it is for systems and downstream reviewers. Deep fake disclosure is visible; it is for viewers. Doing one does not do the other, and productions routinely conflate them because both get filed under “AI transparency”.
For narrative work the disclosure obligation is materially lighter than most coverage suggests. Where the content forms part of an evidently artistic, creative, satirical, fictional or analogous work, Article 50(4) is relaxed to disclosing the existence of generated or manipulated content, in a manner that does not hamper the display or enjoyment of the work. In practice that supports an end-credit or metadata disclosure rather than a persistent on-screen legend. Note the relaxation applies to 50(4) only — it has no bearing on 50(2), which was never your obligation in the first place.
Advertising sits outside the obvious centre of that carve-out, and the answer there is more legible anyway: ad formats already carry disclosure conventions, and the audience-facing rules from Google, Meta and New York all point the same way. Where you do rely on the lighter route, write down the basis on which the work was treated as evidently creative before you rely on it.
Keep the two in separate columns on your delivery checklist, and note that they have different owners in the legal sense as well as the practical one. Marking under 50(2) is the AI provider's duty; your task is procurement — getting and keeping the vendor's confirmation, with credentialed export as a voluntary belt-and-braces record produced by finishing. Disclosure under 50(4) is genuinely yours, owned by the producer or brand, triggered by the nature of the content, and output as something the viewer sees.
What to keep on your own side
Credentials can be stripped or lost when an asset is re-encoded, re-wrapped or re-uploaded downstream, and you do not control every hop. That is a reason to keep your own provenance record rather than to skip the credentials.
A provenance and export manifest — which shots contain AI-generated or AI-manipulated material, which tool or vendor produced them, which export carried credentials, and the hash of the delivered master — is the artifact that survives when the file’s own metadata does not. It is also what lets you answer a question about a specific shot two years later without re-opening the project.
What you must actually do
Assume EU distribution is possible and spec for it
Decide the export spec before finishing wraps. Retrofitting provenance after the suite has moved on is materially harder and less meaningful.
Get the provider/deployer allocation right first
Article 50(2) machine-readable marking is the AI vendor's duty, not yours. Confirm in writing that each system you use marks its outputs, and keep the confirmation. Article 50(4) disclosure is the obligation that attaches to the production.
Apply Content Credentials at export anyway
Not required of you, but it is the cheapest contemporaneous record of what was generated and when. Make it a post deliverable with the AI assertion populated where applicable.
Keep a shot-level AI provenance manifest
Which shots, which tools, which vendors, which exports carried credentials, and the hash of the master. This is your record when downstream metadata is lost.
Handle viewer-facing disclosure separately
Machine-readable marking is not audience disclosure. Track them as two deliverables with different owners.
Put the obligation in vendor deliverable specs
If the post house does not know credentials are required at export, they will not be there, and nobody will discover it until delivery.
Where the law is still open
These are the live edges — the points where the text stops and drafting practice takes over. Here is what to watch on each, and how careful practitioners are handling it now.
- The boundary of “evidently artistic, creative, satirical or fictional” is untested — branded content and docudrama are the hard cases, and the lighter existence-disclosure route depends on landing inside it. Record your classification at the point you make it; retrofitting the reasoning is what looks weak.
- How an existence disclosure should be presented in narrative work — placement, prominence, duration — is not prescribed for audiovisual formats. An end-credit card plus a metadata entry is the posture that satisfies the text without hampering the work.
- Content Credentials survive downstream re-encoding unevenly, and nobody has settled who owns the problem when marking is stripped after delivery. That is precisely why your own provenance manifest is the durable record, not the file.
- The line between AI-assisted post work that has been ordinary practice for years and “AI-manipulated” content within the meaning of the transparency obligation is not sharply drawn. Log the borderline shots either way — the manifest costs nothing and settles the question if it is asked.
- Enforcement posture toward non-EU producers whose work reaches the EU through a distributor rather than directly is still forming. Assume the distributor will push the obligation back to you contractually, because that is where delivery schedules are heading.
Questions this entry answers
The same material, in the form it usually arrives — as something that happened on a job, before anyone knew which agreement or statute it belonged to.
- Do we have to watermark AI content for the EU AI Act?
- Almost certainly not — that duty is the AI vendor’s, not yours. Article 50(2) requires machine-readable marking of AI-generated output and it falls on the provider of the generative system; in the Act’s vocabulary a production is a deployer, and the obligation that attaches to you is Article 50(4) disclosure. Productions routinely spend finishing time on watermarking they do not owe while under-documenting the vendor confirmations that actually matter. The task is procurement: confirm in writing that each system you use marks its outputs, and keep the confirmation.
- Our film uses AI in a few shots and might sell into Europe. What do we have to tell the audience?
- For evidently artistic or fictional work, materially less than most coverage suggests. Article 50(4) is relaxed where the content forms part of an evidently artistic, creative, satirical or fictional work — to disclosing the existence of generated or manipulated content, in a manner that does not hamper display or enjoyment. In practice that supports an end-credit card plus a metadata entry rather than a persistent on-screen legend. Write down the basis on which the work was treated as evidently creative at the time you rely on it; retrofitting that reasoning is what looks weak.
- EU distribution wasn’t decided until after we finished. Are we exposed?
- This is the ordinary case, not the unusual one — the obligation attaches when the title reaches the EU, and that is frequently a festival pickup or a territory sale made after post has wrapped. The mitigation is to spec the export before finishing on the assumption that EU distribution is possible rather than confirmed. Applying Content Credentials to material that never ships to the EU costs almost nothing; not having applied them to material that does is a re-export, after the finishing suite has moved to another job.
Does this apply to your production?
Answer a five-minute intake — contract type, AI usage, airing states, platforms, EU distribution — and ClearFrame returns the requirements that apply to your specific production, with citations and effective dates. Free, one project, no card.
Sources cited by the ClearFrame corpus
- Content Authenticity Initiative — The state of content authenticity in 2026
- C2PA Content Credentials — cryptographic provenance adoption
The sources the rules corpus records for this entry. Follow them through to the primary text.