EU AI Act: Article 50 Marking Transition Closes for Generative Systems Already on the Market
The four-month transitional period for Article 50(2) content marking closes. The Digital Omnibus on AI, Regulation (EU) 2026/1744, gave providers whose generative AI systems were already placed on the market before August 2, 2026 an extra four months to mark synthetic audio, image, video and text in a machine-readable format detectable as artificially generated. From December 2, 2026 those systems carry the same marking duty as anything launched on or after August 2, 2026. This transition sits outside the Digital Omnibus deferral of the Chapter III high-risk obligations, which moved separately to December 2, 2027 and August 2, 2028.
Key Analytics
Impact Analysis
This is the near-term EU AI Act date most teams have wrong, because the headline story of 2026 was a deferral and this is not part of it. The obligation is technical rather than documentary: marking has to be embedded in the output in a machine-readable way, not stated in a policy or a footer, and it applies to systems that shipped before the Act's general application date and are still generating content. Retrofitting an already-deployed generation pipeline is the harder case, which is precisely why the transition existed. Providers who read the Digital Omnibus as a general reprieve and paused work have a narrow window left, and the Article 50 duties sit in the Act's enforcement regime alongside the disclosure requirement that people be told when they are interacting with an AI system.
Recommended Actions
- Inventory every generative AI system you placed on the EU market before August 2, 2026 that is still in service, since those are the systems the transition covered.
- Confirm that synthetic output from each of them carries machine-readable marking as required by Article 50(2), rather than a human-readable disclosure alone.
- Verify that marking survives the delivery path a real user takes, including re-encoding, resizing, and any downstream processing your product performs.
- Separate this deadline from the deferred Chapter III high-risk obligations in your roadmap, because the Digital Omnibus deferral does not reach Article 50.
- Record which systems were assessed and when, so the basis for any out-of-scope determination is producible if a national authority asks.
Always verify requirements with official regulatory sources.
Estimated Remediation Effort
Indicative effort to address this development, broken down by your organization's current compliance posture. Select the posture that best matches where you are today.
A partial program exists: some policies and controls are in place, but coverage, evidence, and ownership have gaps.
- ›Gap assessment against current controls
- ›Readiness assessment
- ›Remediation sprint to date
- ›Attestation or filing preparation
The Cost of Waiting
Readiness work is dramatically cheaper before a deadline than after one. The ranges below come from the same estimate: the difference is only how prepared you are when the work starts.
Roughly 50 to 145 hours avoided by preparing early
Effort ranges are indicative planning estimates, not quotes. Actual effort depends on organizational scope, environment complexity, and evidence maturity. Talk to us for a scoped assessment.