Free template · Art. 50(2)

Free AI-Generated Content Label Template — Article 50(2)

Free, general examples of machine-readable labels for AI-generated audio, images, video and text — the marking Article 50(2) of the EU AI Act asks for — plus a visible label to pair with them.

Scan for free

The templates

Image / video file · IPTC digital source type (XMP)

<!-- Fully AI-generated -->
<Iptc4xmpExt:DigitalSourceType>
  http://cv.iptc.org/newscodes/digitalsourcetype/trainedAlgorithmicMedia
</Iptc4xmpExt:DigitalSourceType>

<!-- Real photo edited with generative AI (inpainting, outpainting) -->
<Iptc4xmpExt:DigitalSourceType>
  http://cv.iptc.org/newscodes/digitalsourcetype/compositeWithTrainedAlgorithmicMedia
</Iptc4xmpExt:DigitalSourceType>

Page markup · flag AI-generated elements

<img src="/images/[file].webp" alt="[Description]" data-ai-generated="true">

<section data-ai-generated="true">
  <!-- AI-generated text block -->
</section>

Visible label to pair with the markup

<span class="ai-label">AI-generated</span>

What Article 50(2) asks for

Providers of AI systems that generate synthetic audio, image, video or text must ensure the outputs are marked in a machine-readable format and detectable as artificially generated or manipulated, using solutions that are effective, interoperable, robust and reliable as far as technically feasible.

Timing: Article 50 has applied since August 2, 2026. Under Article 111(4), as amended by the Digital Omnibus on AI, generative systems already on the market before that date have until December 2, 2026 to comply with Article 50(2).

The IPTC digital source type in the first template is written into the file itself, so it travels with the image or video. Page markup only exists on your site — useful for your own pages (it's one of the markers Article50.io's scanner looks for), but not a substitute for marking in the file.

By media type

✔Images — IPTC digital source type or C2PA Content Credentials in the file; keep them through your CMS and CDN
✔Video — the same metadata in the file, plus an on-screen label where viewers can see it
✔Audio — use output your tool watermarks, and don't re-encode in a way that strips it
✔Text — mark AI-generated blocks in markup and pair them with a visible label

Background: labeling AI-generated content under Article 50(2).

Frequently Asked Questions

Who has to apply machine-readable labels under Article 50(2)?

The provider of the AI system that generates the content — the tool maker, or you if your product generates content for users. If you only publish output from someone else's tool, your job is mainly not to strip the marking it adds.

Is a data-ai-generated attribute enough to satisfy Article 50(2)?

On its own, probably not. Page markup disappears as soon as the image or text is copied elsewhere. Article 50(2) is aimed at marking that travels with the output — embedded metadata, watermarks and similar techniques. Markup is a useful extra layer on your own pages.

When does Article 50(2) apply?

Article 50 has applied since August 2, 2026. Under Article 111(4), as amended by the Digital Omnibus on AI, providers of generative systems already on the market before that date have until December 2, 2026 to comply with Article 50(2).

Want wording matched to your site?

This is a general template. Get language matched exactly to your site's specific findings — run a free scan.

Article50.io is an automated Article 50 transparency assessment platform that scans websites for potential EU AI Act transparency obligations and provides remediation guidance, implementation instructions, and compliance-ready disclosure language.

The free scan shows your single most severe finding in about 30 seconds — no signup, public pages only.