Digital Omnibus timeline: June 16 to July 27 in order
A dated list of the EU Digital Omnibus steps as reported in 2026, from Parliament on June 16 to entry into force on July 27, with the Art. 50(2) grace date.

As reported by secondary sources, the EU Digital Omnibus was voted by Parliament on June 16, 2026, by Council on June 29, signed on July 8 and entered into force on July 27. Confirm each date against the Official Journal on EUR-Lex before you rely on it.
The dates in order
We could not read the legal text for this post, so the table below is a reported timeline, not legal advice. It is the order a compliance owner needs to put in a calendar.
| Date (2026) | Step | Status in this post |
|---|---|---|
| June 16 | Parliament | Reported, verify |
| June 29 | Council | Reported, verify |
| July 8 | Signed | Reported, verify |
| July 27 | In force | Reported, verify |
| Aug 2 | Cut-off for systems placed on the market before this date | Reported, verify |
| Dec 2 | End of the reported Art. 50(2) grace period for those systems | Reported, verify |
What the grace date means
Secondary sources describe a grace period for Article 50(2) up to December 2, 2026 for systems placed on the market before August 2, 2026. Article 50(2) concerns marking synthetic outputs in a machine-readable way. Whether a given generator or workflow counts as placed on the market before that date is a legal question about your own product.
What this means for a Sume user
The Sume changelog is the reader-facing record of what shipped and when. If your compliance file needs to say which Sume capability was available on a given date, cite the dated changelog entry, not a blog post. This post makes no claim that any Sume feature satisfies Article 50.
- Keep a copy of the changelog entries for the features you use
- Record which surface you call: model endpoint, Format run or agent
- Ask your counsel which of the dates above applies to your system
Related reading
The posts linked at the end of this page cover Article 50(2) marking, the editing exemption and providers outside the EU, each with a narrower question than a timeline.
Sources
Related posts
More in Use cases
- One 9:16 master for Instagram ads: what two Meta pages say
Meta's Instagram Feed video ad page lists 9:16 at 1080x1920 and 4 GB. Its placement chart shows a narrower Feed range. How to pick a master and check it.
- Parent-teacher conference reminder in English and Spanish for $0.63
A conference reminder from one slide image in two languages: TTS, a Timeline render and captions per version. $0.6333 for both on Sume, from docs.
- Performance Max image assets: three ratios, 5120 KB cap, 20 each
Performance Max wants landscape 1.91:1, square and 4:5 portrait images up to 5120 KB, 1 to 20 each. How to batch a matrix of images on Sume. Read 2026-10-03.
- Performance Max logo assets: 1200x1200 square and 1200x300 landscape
Performance Max takes a 1:1 logo at 1200x1200 (minimum 128x128) and a 4:1 landscape logo at 1200x300. How to prepare both with Sume. Read 2026-10-03.
Written by Sume