AI Act Article 50(2): 2 December 2026 grace period, in plain terms
Commission FAQ: providers of systems on the market before 2 August get until 2 December 2026 to mark outputs. Older content needs no retroactive label.

Article 50(2) is the provider duty to mark AI outputs in a machine-readable way. The Commission's FAQ says a limited grace period is envisaged only for AI systems placed on the market before 2 August 2026, and only for that marking and detection duty; those providers must comply from 2 December 2026. It also says content generated before 2 August 2026 does not need to be labelled retroactively. This is not legal advice.
Dates are from two Commission FAQ pages; what Sume records is from its docs and OpenAPI. All read 2026-09-30.
What are the dates?
| Date | What the FAQ says |
|---|---|
| 2 August 2026 | Providers and deployers within Article 50(2) and (4) must comply with the transparency obligations |
| Before 2 August 2026 | Content generated then does not need to be labelled retroactively; the Commission encourages deployers to label where possible |
| 2 December 2026 | Marking and detection duty starts for systems placed on the market before 2 August |
Who does the 2 December date apply to?
Providers of those systems, for marking and detection under Article 50(2). The FAQ does not extend it to a deployer's disclosure of a deepfake, which it says must happen at first exposure at the latest. If you publish AI video, treat 2 August as your date and ask a lawyer whether the later one touches you at all.
How do I show when a file was made?
Sume's docs do not describe a mark inside outputs, so use the records it does keep. The usage ledger rows in the OpenAPI document are scoped to the authenticated workspace and carry job_id and created_at. A job also has events: GET /v1/jobs/:id/events is described as a public timeline for debugging and recovery, starting with job.created.
Store the job id and the Sume URL next to each delivered file, as in what to log per generated file. See Jobs and results for the event list.
Does a pre-August file need a label?
Per the FAQ, not retroactively, though the Commission encourages it. A file you edit or republish after 2 August is a separate question, so keep the original job record and the date you changed it. See also the Article 50 labeling guide for creators.
Sources
Related posts
More in Use cases
- ASA on AI deepfake ads: you answer for the output you run
CAP says a realistic AI celebrity endorsement can breach the Code and the advertiser stays responsible. Which Sume avatar inputs involve a real person's photo.
- Black Friday countdown video ad: burn the days-left text
Meta says countdown overlays create Black Friday urgency. A countdown is authored text, so burn a new days-left cue onto one clip each day with Sume.
- Bluesky video captions: WebVTT sidecar vs burned-in
Bluesky video embeds take WebVTT caption files next to the video. Sume burns captions into pixels, so build the VTT yourself from sentence segments.
- Break down a UGC ad by scene: $0.30 analysis or free stills?
To study a UGC-style ad, video inspect gives free stills and a $0.01 per minute transcript; the legacy analysis adds typed scenes for $0.30. What each returns.
Written by Sume