AI-Generated Content Labeling in the EU: What Article 50 Requires
AI-generated content labeling under the EU AI Act sounds like a simple rule — say it's AI-made — until a team actually tries to implement it consistently across every image, article, and clip they publish. Article 50 covers two related but distinct duties here, owed by different parties: providers of generative systems marking synthetic content in a machine-readable way (Article 50(2)), and deployers visibly labeling deepfakes and AI-generated text published on matters of public interest (Article 50(4)). Most non-compliant content isn't the result of anyone deciding not to label something — it's what a missed caption looks like at scale.
Two separate requirements, often confused
Article 50(2) — machine-readable marking (provider)
Providers of systems that generate synthetic text, image, audio, or video have to make sure the output is marked so software, not just a human reading the page, can detect it was AI-generated. This is the provider's duty, not the duty of a site owner who publishes the output. A visible label is not this kind of marking.
Article 50(4) — visible labeling (deployer)
Deepfakes need a human-visible label. So does AI-generated text published to inform the public on matters of public interest, unless a person or company took substantive editorial responsibility for it. This one is about what a reader sees, not what a machine can detect, and it covers only those two cases. Labeling other AI content is voluntary.
Why a caption isn't a labeling system
Where you do show a visible label, whether because Article 50(4) requires it or because you choose to, images and text need different implementations, because they don't behave the same way once they leave your system:
- An image gets downloaded, reposted, and screenshotted constantly. A caption on the page around it doesn't survive any of that. The only label that travels with an image is one baked directly into the pixels, not an overlay a download leaves behind. That is still a visible label, not the machine-readable marking of Article 50(2).
- Text can't carry a label inside it without mangling the actual words, which defeats the point of publishing it. What works instead is a positioned badge generated alongside the content at creation time, so there's no separate manual step someone has to remember.
The exemption is narrower than it sounds
“Substantive editorial review” is doing a lot of work in Article 50(4)'s exemption for human-reviewed text. A quick skim or a spell-check pass is not what the exemption describes — it's meant for cases where a person genuinely took editorial responsibility for the content, and that responsibility should be something you can point to, not something assumed by default because a human technically opened the document once.
How Disclarion labels content by default
Disclarion's SDK returns a ready-made label the moment content is logged, rather than treating labeling as a separate step: a visible label pixel-baked into images, and a positioned HTML badge for text, both produced by the same call that records the interaction for audit purposes. Neither requires designing anything or remembering to add it at publish time — the label is a byproduct of generating the content, not an afterthought bolted on before it ships.
Frequently asked questions
Does every piece of AI-generated content need a label?
No. Article 50(4) requires a visible label for two things: deepfakes (AI-generated or manipulated image, audio, or video that resembles real people, places, or events and would falsely appear authentic), and AI-generated text published to inform the public on matters of public interest, unless it was human-reviewed and someone holds editorial responsibility for it. A spell-check or quick skim doesn't qualify for that exemption. Labeling other AI content is voluntary. Separately, providers of generative systems must mark all synthetic output in a machine-readable way under Article 50(2), but that duty is the provider's, not the publisher's.
Is a caption under an image enough?
For a deepfake that needs a visible label, a clear caption shown with the image is a visible label. Its practical weakness is that it only exists as long as the surrounding page does: once the image is downloaded, reposted, or screenshotted, the caption is gone. A label baked into the pixels travels with the file. Neither is the machine-readable marking of Article 50(2), which is the provider's job.
What does 'machine-readable' marking actually mean?
It means the AI origin is technically detectable by software, for example through embedded metadata, signed provenance (Content Credentials), or an invisible watermark. Article 50(2) puts this on the provider of the generating system, so it is built in where the content is created. A visible caption or badge is a label for people, not a machine-readable mark.
Do all content types get labeled the same way?
No. Where an image needs a visible label, a label baked into the pixels survives downloads and reposts better than one on the page. Text can't carry a label inside the words without altering them, so a positioned badge shown alongside the content works better.