Provider or deployer: who labels under Article 50
Providers mark output in machine-readable form; deployers label deepfakes visibly on first exposure. Here is which role you occupy on a hosted generator.
Article 50 of the EU AI Act does not impose one labelling duty. It imposes two, on two different parties, satisfied by two different artefacts, aimed at two different readers. One is a machine-readable marker inside the file, aimed at a detector. The other is a perceivable label outside the file, aimed at a person. Confusing them produces the two most common failure states: a producer building watermarking infrastructure they were never asked for, or a producer assuming a tool's embedded marking discharges a duty that was always theirs.
The sorting question is short. Did you place the generative system on the market, or did you use someone else's to make something you then published?
The two duties, side by side
| Provider duty (50(2)) | Deployer duty (50(4)) | |
|---|---|---|
| Who carries it | Whoever supplies the generative AI system | Whoever publishes the content |
| What it produces | Machine-readable marking of synthetic audio, image, video and text output | A disclosure a human can perceive |
| Who reads it | Detection tooling, platforms, downstream verifiers | The viewer |
| Where it lives | Inside the file — metadata, watermark, embedded signal | On or around the content, at first exposure |
| Satisfied by metadata alone? | That is the point of it | No |
| Timing | At generation | Before or as the viewer encounters the content |
The row that decides most arguments is the last-but-one. A deployer duty is not satisfied by embedded metadata, because metadata is not something a scrolling viewer perceives. Equally, a visible caption does not satisfy the provider duty, because a caption is not machine-readable in the sense the obligation means. The two are not alternatives and neither one absorbs the other.
Which role a hosted generator puts you in
If you sign in to a generation platform, prompt it, download the output and publish it, you are a deployer of that system. You did not place it on the market. You are not responsible for whether its exports carry an embedded marker, and you cannot fix it if they don't — that engineering sits upstream, with the company operating the model.
This is the accurate description for nearly everyone reading a post like this: agencies, brands, in-house marketing teams, solo creators, production studios. It is worth saying flatly because the alternative wastes real money. You do not need a watermarking pipeline. You do not need to build a detection API. You do not need to procure C2PA signing infrastructure to meet 50(2), because 50(2) is not addressed to you.
What you do carry is the 50(4) label, and it does not wait on anyone.
The edge that is worth checking
There is a version of "I only use hosted tools" that stops being a deployer story, and it is worth recognising before a client asks.
If you are embedding a generative system into your own product and presenting it to customers under your own name, you are no longer only using a system. You may be placing one on the market. That covers a white-labelled generator inside your SaaS, a branded creative tool for clients, or an API you resell as your own. Whether that flips you into the provider column for Article 50 purposes depends on the arrangement, and it is exactly the kind of question that belongs in front of counsel rather than in a blog post. The signal to watch for: whose name and trademark does the end user see on the generation surface?
The same caution applies if you materially alter a system's behaviour and distribute the result. Fine-tuning a model for your own internal output is one thing; publishing the tuned model or offering it as a service is a different posture.
The middle ground — you use hosted models, you are the only person prompting them, the output goes out as your creative work — is deployer territory, and stays there.
What "first exposure" actually asks for
The deployer obligation is about disclosure to the audience, and its practical failure modes are all about placement rather than wording.
- Behind a tap. A disclosure that requires expanding a caption is not delivered at first exposure. Whatever the platform's UI does to your description on a mobile feed is what the regulator sees.
- At the end. A credit that appears at 0:44 of a 0:45 clip is technically present and functionally absent, and the majority of a short-form audience never reaches it.
- A flash frame. Present for four frames satisfies a screenshot, not a viewer.
- In the file only. Provenance metadata is a provider-layer artefact. It is genuinely useful and it is not your label.
- Wrong asset. Disclose on the asset that reaches the audience. If a 9:16 cut-down goes out separately from the master, the cut-down needs its own label.
The workable pattern is a fixed, consistent, readable disclosure placed where the eye already is, repeated identically across a channel. Consistency is doing real work — a label that looks the same every time reads as part of your format rather than as a warning.
One narrowing worth knowing: content that is evidently artistic, creative, satirical or fictional gets a lighter version of this obligation, limited to disclosing existence in a way that does not hamper enjoyment of the work. That is a genuine carve-out with a hard edge, and realistic synthetic depictions of real people generally sit outside it.
Doing the deployer half in a real pipeline
The deployer label is a production step, not a settings toggle, which is why it belongs in the edit rather than in a compliance folder.
- Flag the assets that need it at brief stage. Realistic avatars, cloned voices and any generated footage that could pass as an ordinary recording of a real person, place or event, headed for an audience that includes EU viewers. Anything built with the AI avatar generator or a voice clone starts flagged by default.
- Burn the label into the cut, not the upload form. In Versely that is a text overlay on the timeline. A request like "add the text 'Made with AI' as a small overlay in the bottom-left corner for the full clip" runs the text overlay step with your wording and position, so the label travels with the file to every destination rather than living in one platform's metadata field.
- Check it against a preview before you spend on the export. The editor runs off a single re-renderable EDL, so a free 480p preview pass — subject to a short per-user cooldown — shows you exactly where the label lands at real playback size. The final export is charged once, whatever the clip count.
- Set the platform toggle as well. The AI content label on YouTube, Meta or TikTok is contractual policy, not statute, and it stacks on top of the legal duty rather than replacing it. One disclosure, five destinations is the per-platform version of this step.
- Do not wait for the provider's marking to appear. Whether a given tool's export carries an embedded marker tells you about that provider's engineering timeline, not about your duty. The December deadline nobody diarised covers why some tools are still switching marking on.
Where the file layer still matters to you
None of the above means embedded provenance is irrelevant to a deployer. It is not your legal obligation, but it is increasingly a commercial one — buyers ask, platforms read it, and some downstream regimes are being built on the assumption that it exists.
The uncomfortable engineering reality is that a manifest is a hard binding to a file, and any re-encode, screenshot, format conversion or non-aware editing step invalidates it. Social platforms re-encode on upload as a matter of course. Durable approaches layer an invisible watermark and a perceptual fingerprint alongside the manifest to survive that, and even those are defeated by heavy crop or adversarial removal. Treat provenance data as a compliance aid, not proof — sign, strip, survive walks the chain step by step, and invisible watermarks covers where the pixel-level layer stops working.
If the question you actually have is which section of the voluntary Code of Practice your organisation would sign, that maps onto the same provider/deployer split and is covered separately in where a creator actually sits in the transparency code.
FAQ
I use a hosted generator. Am I a provider of anything?
Almost certainly not, if you are prompting someone else's system and publishing the result as your own creative work. You are a deployer. The marking obligation belongs to whoever operates the system.
Does my tool's watermark cover my disclosure duty?
No. Machine-readable marking answers a detector. The deployer duty answers a viewer, at first exposure. A file can carry perfect provenance metadata and still leave the labelling duty unmet.
What if I white-label a generator inside my own product?
That is the case where the line genuinely blurs, because your customers see a generative system presented under your name. Get advice on the specific arrangement rather than assuming the deployer answer carries over.
Do I need to label everything I make with AI?
The deployer labelling duty in 50(4) is aimed at realistic synthetic content — the kind that could be taken for an authentic recording. Colour grading, background cleanup and obviously non-realistic work are treated differently, and separate platform rules may still ask for a toggle regardless.