If you produce films, television or commercial video, it is no longer useful to speak about AI disclosure as something that might arrive one day. The European Commission confirms that Article 50 of the AI Act applies from 2 August 2026.
That does not create one simple label for every film containing digital effects. It creates specific responsibilities that depend on the system, the content and the way it reaches people. Your team needs a clear account of what was used and who approved the delivery.
Marking an output and informing an audience are different jobs.
Article 50 distinguishes the provider of an AI system from the organisation or person using it. Providers of systems generating synthetic media have marking and detectability obligations, subject to the rules’ qualifications. Deployers have separate duties to disclose certain content to people exposed to it.
For image, audio and video, the deployer rule addresses content that constitutes a deepfake. The law also provides an adapted disclosure requirement when such content forms part of an evidently artistic, creative, satirical or fictional work. This is a qualified obligation, not a blanket permission to leave every AI film unlabelled.
A fictional setting does not settle every question.
The Commission’s guidance considers what viewers would reasonably understand about the content. Its examples explain that standard film effects and background scenes are not automatically deceptive just because AI was involved. The assessment depends on the context and audience as well as the resulting image or sound.
Where a deepfake disclosure is required, the Commission says it must be clear and perceivable. Embedded technical metadata alone does not fulfil that audience disclosure duty. Its guidance also describes a limited later deadline for the marking obligations of certain systems already on the market. That qualification should not be treated as a general postponement of every disclosure rule.
Decide how you will document use before delivery.
On 10 June 2026, the Commission published a voluntary Code of Practice to help organisations meet the marking and labelling requirements. It provides a practical route for implementing obligations that remain distinct from the voluntary choice to sign the code.
For a production, start with a simple internal record: which supplier or team used which tool, what material or activity it affected, and which delivered version contains it. Keep the approval and disclosure decision with that version. When a trailer is recut or a sequence is replaced, revisit the record.
A legal or distribution review can then work from concrete facts instead of a vague assurance that the film is compliant. This article describes the EU transparency framework as checked on 30 September 2026. A release in several territories also needs advice on the laws, contracts and platform terms that apply to that distribution.
Keep the standard you promise distinct from the minimum disclosure.
A production can disclose AI use accurately while making no claim that all of its creative work met a human creation standard. If your brief promises human craft, that promise needs its own evidence and review process.
DigiBridge’s strict programme excludes prohibited AI assistance and software acting in place of the contributor. Its verification agent assesses authorised activity alongside device, system and tool checks. Findings retain their reasons and evidence, with an opportunity for the creator to explain or challenge them.
The first confirmed incident holds the affected recording or version. A third distinct confirmed incident makes the project ineligible for directory publication. A model suspicion alone is not a confirmed incident. This gives the programme a defined consequence and a review process, while keeping legal compliance and creative verification separate.
“A clear creative promise needs a record of what happened and a rule for what follows.
How DigiBridge helps
Make your human creation standard reviewable.
DigiBridge connects registered projects, permitted activity and contributor context under a strict programme. Its record supports creative review; it is not a legal clearance or a substitute for the disclosures required for your release.
In the strict human creation programme, permitted device, operating system and creative tool evidence feeds layered checks and an AI verification agent. These detect prohibited AI assistance and software control, warn creators with supporting evidence, and inform publishing decisions after confirmation and review. A warning or uncertain result alone does not count as an incident.
Read the human creation standardSources and further reading
Primary and authoritative sources reviewed for this article. Statistics remain attributed to the organization that published them.
- 01AI transparency guidanceEuropean CommissionUpdated 6 August 2026. Article 50 application date and the guidance framework.
- 02Article 50EU AI Act Service DeskProvider and deployer obligations, artistic works and disclosure timing. Checked 30 September 2026.
- 03Transparency questions and answersEuropean CommissionUpdated 24 July 2026. Context, audience disclosure and qualified transitional timing.
- 04Marking and labelling code announcementEuropean Commission10 June 2026. A voluntary code supporting the transparency requirements.
Continue reading
Browse all insights