Commission Guidelines on the AI Act Transparency Obligations (Article 50)

On 20 July 2026 the Commission published C(2026) 5054 final — guidelines on how the Article 50 transparency obligations are to be applied. They arrived thirteen days before the obligation itself. What they are, what legal weight they carry, and what changes for providers and deployers.

What this page is. A reader's guide to the Commission's Article 50 guidelines — what document it is, what weight it carries, and what a compliance team should actually do with it. For the obligations themselves, see the Article 50 transparency pillar.

On 20 July 2026 the European Commission published guidelines on the transparency obligations of Article 50 of Regulation (EU) 2024/1689. The document is referenced C(2026) 5054 final; its annex carries the longer title Guidelines on the implementation of the transparency obligations for certain AI systems under Article 50 of Regulation (EU) 2024/1689 (the 'AI Act').

They landed thirteen days before Article 50 entered into application on 2 August 2026.

What the guidelines are — and are not

The distinction matters more here than it usually does. Article 50 is enforced by 27 national market surveillance authorities, each applying the same sentence independently, and the Commission has no direct enforcement power over anyone but general-purpose AI model providers. Guidelines are the mechanism by which the Commission tries to keep 27 readings from diverging. Non-binding does not mean inconsequential: an authority opening an inquiry will start from them, and a company whose design departs from them will be asked why.

Why they arrived when they did

The sequence is worth stating plainly, because it explains why so many programmes were built without them:

Anyone who scoped their Article 50 work in the first half of 2026 did so without the Commission's stated position on the exemptions. That is not a reason to redo the work; it is a reason to re-read it against the guidelines before an authority does.

What the guidelines address

The guidelines follow the structure of the article itself, covering each of the four substantive obligations and the conditions attaching to them:

• Art. 50(1) — systems interacting with natural persons. The scope of the provider's design duty, and the boundaries of the "obvious to a reasonably well-informed, observant and circumspect person" exemption.
• Art. 50(2) — machine-readable marking of synthetic content. What "effective, reliable, robust and interoperable" means in practice for providers of generative systems, including general-purpose AI systems, and where the assistive-editing exemption stops.
• Art. 50(3) — emotion recognition and biometric categorisation. The deployer's duty to inform exposed persons, and its interaction with the GDPR, which Article 50(3) expressly incorporates.
• Art. 50(4) — deepfakes and public-interest text. The deployer's disclosure duty, the editorial-responsibility exemption for text, and the proportionate-disclosure regime for artistic, creative, satirical and fictional works.
• Art. 50(5) — how disclosure is presented. Clear and distinguishable, at the latest at the time of first interaction or exposure, and consistent with accessibility requirements.

That last point is the one most likely to produce enforcement in the first cycle, because it is the only one that can be assessed from the outside without any access to a company's systems. A regulator can open your product and see whether the notice is there.

What to do with them

1. Re-read your disclosure design against Art. 50(5), first. Presentation is externally auditable in a way that internal marking pipelines are not. A notice buried behind a menu, in a footer, or in terms of service does not meet "clear and distinguishable at the latest at the time of first interaction".
2. Re-test your obviousness argument. If you concluded that no disclosure was needed because the AI nature was obvious, that judgement was made before the Commission stated where the bar sits. Document the reasoning again, against the guidelines.
3. Separate provider duties from deployer duties in writing. Paragraphs 1–2 and 3–4 land on different legal entities, frequently inside the same group. See providers vs deployers.
4. Date every generative system against 2 August 2026. The 2 December 2026 grace period is available only for systems already on the EU market before that date, and only for the Art. 50(2) marking duty.
5. Decide on the Code of Practice. Sign it, or record why your own method meets the same standard. A documented decision either way is worth more than an undocumented one.
6. Identify your market surveillance authority in each Member State where you operate — the national implementation tracker records the designations.

What the guidelines do not do

They do not defer anything. The Digital Omnibus deferred the high-risk regime — Annex III to 2 December 2027, Annex I to 2 August 2028, national sandboxes to 2 August 2027 — and left Article 50 exactly where it was. Reading the omnibus as a general reprieve is the most expensive misreading available right now, because the Regulation's broadest obligation is live, carries a €15 million or 3% ceiling under Article 99(4), and applies whatever risk tier your system occupies.

For what the omnibus did and did not move, see the Digital Omnibus analysis and the changes to Regulation (EU) 2024/1689.

Official sources

• European Commission — Guidelines on transparency obligations for providers and deployers of certain AI systems, 20 July 2026 (C(2026) 5054 final)
• European Commission — Transparency obligations under Article 50 of the AI Act (FAQ)
• European Commission — Code of Practice on Transparency of AI-generated Content
• European Commission — Commission starts enforcing AI Act rules and new transparency requirements on 2 August
• Regulation (EU) 2024/1689 — Article 50, Article 99

Editorial, not legal advice. This page describes the status and structure of the Commission's guidelines; for their operative text, read the official document linked above.