Art. 50: Transparency obligations for certain AI systems under the EU AI Act
Art. 50 requires providers to inform natural persons of AI interaction and to mark synthetic audio, image, video and text in a machine-readable format. Deployers disclose emotion recognition, biometric categorisation and deep fakes. In this mapping, 11 elements are testable, 12 are documentation and 8 are process. Regulation (EU) 2026/1744 did not move the application date In force. Art. 111(4) gives systems already on the market a grace period for the Art. 50(2) marking duty Deferred. The adequate Art. 50(2) marking technique is an unsettled point; the page shows both readings.
Where this applies
- In forceArticle 50 transparency obligations
- DeferredArticle 50(2) machine-readable marking for systems placed on the market before the Article 50 date
- In forceDigital Omnibus on AI, entry into force
What the text requires
Art. 50(2) holds most of the testable elements: mark presence per modality, detectability by a third party, survival under ordinary transformations, readability by an independent tool, and detection reliability against a justified target. Each exemption in Art. 50(1) to (4) is a documentation element, because the exemption rests on a recorded determination.
| Requires | Testable | Documentation | Process |
|---|---|---|---|
|
|
|
|
Metrics and where thresholds come from
Threshold sources, in order of precedence
- A harmonised standard cited in the Official Journal (none as of the anchor date)
- A JTC 21 draft standard (prEN), with its stage
- An ISO/IEC standard or technical report, with its stage
- A Commission guideline or code of practice, with its date from the standards data
- NIST AI RMF or a sector framework
- The state of the art, which the provider justifies and documents
Art. 50 sets no numeric threshold. Art. 50(2) sets four qualitative criteria, effective, interoperable, robust and reliable, bounded by technical feasibility, the specificities and limitations of each content type, the costs of implementation and the generally acknowledged state of the art. No harmonised standard is cited in the Official Journal for Art. 50 and no JTC 21 draft covers it, so the hierarchy level in use today is a Commission code of practice and guideline: the Code of Practice on Transparency of AI-Generated Content and the Commission guidelines on Article 50, with the C2PA specification as a technique reference. Where the Code states a quantity, the record cites the Code and the condition it attaches; no quantity is attributed to the Act. The provider sets and justifies its own targets for detection rate, false-positive tolerance and the transformation set against the context of use; the PR-50-MARK target-setting step records the justification.
| Source and stage | Title | What it provides here | Verified on |
|---|---|---|---|
Code of Practice on Transparency of AI-Generated ContentPublished | Code of Practice on Transparency of AI-Generated Content (marking and labelling under Art. 50(2) and 50(4)) | operational measures for the Art. 50(2) marking layers (digitally signed and time-stamped metadata, imperceptible watermark, with fingerprinting and logging as supplementary measures only), a multi-layer expectation where a single technique cannot meet the criteria on its own, detection solution availability and interoperability commitments, and the Art. 50(4) label placement rules and EU icons | Verified on European Commission, Code of Practice on Transparency of AI-Generated Content |
Commission guidelines on Article 50 transparency obligationsPublished | Guidelines on the implementation of the transparency obligations for certain AI systems under Article 50 of the AI Act | the scope of each Art. 50 duty: the reasonably well-informed person test for the Art. 50(1) exemption, the reading of deep fake, the assistive-editing and no-substantial-alteration exemption examples, the two cumulative conditions for the Art. 50(4) editorial-control exemption, and the timing and accessibility reading of Art. 50(5) | Verified on European Commission, Guidelines on transparency obligations for providers and deployers of AI systems |
C2PA Content Credentials specificationPublished | C2PA Technical Specification (Content Credentials) | the provenance manifest structure, signature validation rules and manifest-binding checks used to verify the metadata and provenance layer for presence, validity and survival through edits | Verified on C2PA Specifications 2.1 (version selector also lists 2.2, 2.3 and 2.4) |
Procedures
Each protocol is versioned; its page states the derivation from the standards above. PR-50-MARK v1.0 covers the marking, survival and detection tests under Art. 50(2). PR-CLS v1.0 covers the assignment of each function to the Art. 50 paragraphs and the check of each claimed exemption.
- PR-50-MARK v1.0Article 50 marking and detection protocolv1.0
- PR-CLS v1.0Classification and role determination protocolv1.0
What an assessor asks for
- Article 50 applicability and exemption determination record (PR-CLS output)
- Marking architecture description per output modality
- Technical solution justification against the Art. 50(2) criteria
- Marking presence and survivability test report (PR-50-MARK output)
- Third-party detectability verification report (PR-50-MARK output)
- Interaction disclosure and label audit record (PR-50-MARK output)
- Editorial responsibility and human review measures record (Art. 50(4))
- Code of Practice adherence or alternative-means record (Art. 50(7))
Common findings
- Metadata is the only marking layer, and a screenshot or a re-encode removes it.
- The watermark detector runs only inside the provider's own service, so no other party can detect the mark.
- The interaction disclosure sits in the terms of service or a help page rather than in the interface at the first interaction.
- The deep fake label is an overlay on the player, and a crop, a download or a re-share removes it.
- The assistive-editing exemption is claimed for a function that replaces most of the input content.
- The technical solution is chosen without a written justification against the four Art. 50(2) criteria.
Questions
What does Article 50 machine-readable marking require?
Art. 50(2) requires providers of systems that generate synthetic audio, image, video or text to mark the outputs in a machine-readable format. The outputs must also be detectable as artificially generated or manipulated. The technical solution must be effective, interoperable, robust and reliable as far as technically feasible. The Act names no technique and no number. The Code of Practice on Transparency of AI-Generated Content names signed metadata and imperceptible watermarks as marking layers and treats fingerprinting and logging as supplementary. Which techniques count as adequate is an unsettled point; the page shows both readings.
What does the Code of Practice on Transparency of AI-Generated Content add to Article 50?
The Code is a voluntary instrument under Art. 50(7). Its first section covers provider marking and detection under Art. 50(2). Its second section covers deployer labelling under Art. 50(4). It expects more than one marking layer where a single technique cannot meet the four criteria on its own. It commits signatories to make a detection solution available. It supplies EU icons for deep fake and AI-modified content labels. The Commission assesses whether adherence to the Code is adequate, taking utmost account of the opinion of the Board. A provider that does not adhere shows conformity with Art. 50(2) and (4) by other means.
What is the EU AI Act Article 50 deadline?
Art. 50 applies from the general application date set in Art. 113; the article-50-transparency entry carries the date. Regulation (EU) 2026/1744 did not move that date. It added Art. 111(4), a grace period for the Art. 50(2) marking duty for systems that generate synthetic content and were placed on the market before the application date; the article-50-2-legacy-marking entry carries that date. The grace period covers only Art. 50(2). Disclosure duties under Art. 50(1), (3) and (4) have no grace period.
What does the AI Act require of chatbots?
Art. 50(1) requires a provider to design a system that interacts directly with natural persons so that those persons are informed that they interact with an AI system. The information must be clear and distinguishable and given at the latest at the first interaction under Art. 50(5). The duty does not apply where the interaction is obvious to a reasonably well-informed, observant and circumspect person. The Commission guidelines on Article 50 read the test as an average-person test that the provider records. A chatbot that also generates text may carry the Art. 50(2) marking duty for that text.
What does AI Act Article 50(4) require?
Art. 50(4) is a deployer duty. A deployer that generates or manipulates a deep fake must disclose that the content is artificially generated or manipulated. For an evidently artistic, creative, satirical, fictional or analogous work, the duty is limited to a disclosure that does not hamper the work. A deployer that publishes AI-generated text to inform the public on matters of public interest must disclose that the text is artificially generated or manipulated. That text duty does not apply where the content has undergone human review or editorial control and a natural or legal person holds editorial responsibility. The Commission guidelines on Article 50 treat these as two cumulative conditions and do not count spell-checking as human review.
Did the Omnibus delay the EU AI Act transparency obligations?
No. Regulation (EU) 2026/1744 did not change the content of Art. 50(1) to (6) and did not move the Art. 50 application date. It amended Art. 50(7) so that the Commission leads the codes of practice and assesses their adequacy with the opinion of the Board. It inserted Art. 111(4), a grace period for the Art. 50(2) marking duty for systems that generate synthetic content and were already on the market. The article-50-transparency and article-50-2-legacy-marking entries carry the dates.
How we test this
We test against Art. 50(1) to (5): the interaction notice on the first contact, the machine-readable mark on a sample of outputs per modality, its survival under a defined transformation set, its detection by an independent reader, and the disclosure on each distribution surface. We prepare the evidence as the PR-50-MARK outputs and the determination records listed above, within the limits stated on what we cannot do.
- Classification and readiness assessmentPR-CLS
- Article 50 transparency and marking/watermark testingPR-50-MARK
What we cannot do
- We do not perform conformity assessments where a notified body is required.
- We do not issue CE marking or the EU Declaration of Conformity.
- We are not a notified body.
- We do not give legal opinions on classification or liability.
- We test against requirements, prepare evidence, and structure documentation; compliance decisions remain with the provider or deployer, their notified body, and their counsel.