EU AI Act Article 50 timeline: code of 10 June, duties from 2 August

Article 50 transparency duties apply from 2 August 2026. The final labelling code was published 10 June 2026, with about 190 signatories by end of July.

4 min readSume
All posts

The Commission's page says the Article 50 transparency obligations apply from 2 August 2026. The final Code of Practice on marking and labelling AI-generated content was published on 10 June 2026, after drafts on 17 December 2025 and 3 March 2026, and about 190 organisations had signed by the end of July 2026. For anyone publishing AI video in the EU, the start date is already behind us.

The dates in order

The page is the Commission's own summary. Other dates on related pages are not part of this table.

Code of Practice and Article 50 dates (read 2026-10-03)
DateEvent
17 December 2025First draft code published
3 March 2026Second draft published
10 June 2026Final code published
2 August 2026Article 50 transparency obligations apply
End of July 2026About 190 organisations signed

Reading the timeline as a producer

Three things follow for a team that makes generated video. First, the code is final, so you can read it rather than waiting for it. Second, the legal duties are live, so an assessment of your own role is overdue. Third, a large signatory list means many platforms and tools are working to the same code.

Your role depends on what you do. Running a generator is different from publishing its output, and the code treats those differently. The video docs describe generating a clip through the API; what you do with the file afterwards is the publishing side.

A short checklist

This is a summary of a Commission page, not legal advice. For an actual decision, read the code and the regulation text, or ask counsel.

  • Write down which of your outputs are realistic synthetic video, audio or images.
  • Mark who in your team publishes them and where.
  • Read the final code's sections for providers and for deployers.
  • Keep a dated record of each clip: job, prompt, date, label applied.

Using the dates

The sequence shows how the work moved: two drafts, a final code, then the application date. Teams that started reading the drafts in December had months to adjust; teams starting now are late but not blocked.

Start with an inventory. List the AI-generated content you publish, the channel, the audience country and who approves it. Then map each row to a duty. Most video teams will find a short list of rows with real obligations.

Review the inventory on a schedule, such as quarterly, and whenever you add a new content type. A generated voice or a new avatar format changes your rows.

Sources

Related posts

More in Use cases

All Use cases posts

Written by Sume