The EU published Regulation (EU) 2026/1744, known as the Digital Omnibus on AI, in the Official Journal of the European Union on 24 July 2026. It amends the AI Act, Regulation (EU) 2024/1689, along with two other regulations. It entered into force on the third day after publication.[1] The European Commission proposed the amendments on 19 November 2025. Parliament approved the agreed text on 16 June 2026 by 423 votes to 57, with 174 abstentions. The Council adopted it on 29 June.[2, 3]
The regulation fixes when the AI Act's rules for high-risk systems in Chapter III, Sections 1 to 3, apply. For systems classified as high-risk under Annex III, the AI Act's list of high-risk uses, the rules apply from 2 December 2027. For AI systems in products covered by the EU safety legislation listed in Annex I, the rules apply from 2 August 2028.[1, 3] The regulation's recitals, the statement of reasons at its start, give two causes for the delay: the late availability of standards and the slow establishment of national competent authorities.[1] The Commission had proposed linking these dates to the availability of standards, but the final text sets fixed dates.[2]
For content marking, the regulation adds a transitional rule. It covers AI systems that generate synthetic audio, images, video or text and were placed on the market before 2 August 2026. Their providers have until 2 December 2026 to comply with Article 50(2) of the AI Act.[1] That article requires such outputs to be marked in a machine-readable format and detectable as artificially generated or manipulated.[4]
From 2 December 2026, the regulation also prohibits two kinds of AI systems. The first are systems intended to generate child sexual abuse material or non-consensual intimate material of identifiable people. The second are systems that foreseeably produce such material without reasonable and adequate safeguards.[1, 3]
Sources
Check or correct this page
Verification record
The digest below shows whether the text you are reading matches the published source. It does not show that the reporting is correct. The build computes it from this page's Markdown source and lists it in the site manifest.
0b108ccbd4f9044bd77daad4c91fb38c5c79a6f47a0ce6be1f71a0566eea7136
