Machine-Readable Marking Just Became Law: Rebuilding Your Export Step

The date that mattered for this passed a few weeks ago, and most export pipelines didn't notice, because the obligation it created doesn't point at them. Article 50 of the EU AI Act became applicable on 2 August 2026, and Article 50(2) requires the providers building AI systems to implement marking of AI-generated or manipulated content in a machine-readable format, plus related detection mechanisms. Read that sentence carefully: it binds the companies that build the models, not the pipeline you run after their output leaves the model. That gap is where an honest audit of a real export step needs to start.

What actually changed on 2 August

The obligation is real and it's binding, not a guideline — but it's also narrower than the headlines about it suggest. It requires the AI provider (the company operating the system that generated the content) to mark that content in a way a machine can detect, and to build detection mechanisms alongside it. It does not, on its own text, tell you what that mark has to look like. The Commission's own materials describe the scope in general terms — marking, provenance, watermarking and/or detection — without prescribing a specific technical standard. There's no line in this obligation that names C2PA, SynthID, or any other specific scheme as the mandated implementation. Providers get to choose their own mechanism, which is exactly why the landscape right now is several different watermarking and metadata schemes competing rather than one required format everyone implements identically.

The voluntary path most providers are actually using

Because the law states an outcome without mandating a mechanism, the Commission built a voluntary Code of Practice that providers can sign to demonstrate a path to compliance — practical measures assessed by the Commission and the AI Board, rather than a single certified checklist. The signing numbers give a sense of how seriously the industry is treating it: by the end of July 2026, about 190 organisations had signed, split into 82 provider signatories (the companies whose systems generate the content) and 152 deployer signatories (the companies putting that content in front of the public). That deployer number matters as much as the provider one — a lot of the practical burden of getting this right sits downstream of the model, with whoever ships the content, which is closer to where most creative pipelines actually live.

Auditing a real export step

Here's a completely ordinary pipeline, and where a mark would need to survive each hop to still be there at the end:

1. Generate. Whatever mark the provider implements under Article 50(2) — if it implements one as an embedded, machine-readable signal rather than only a visible badge — is at its strongest right here, on the file as it leaves the model. This is the one hop the law is actually pointed at.

2. Download. A straight download usually preserves file-level metadata. This is the last point in most pipelines where an embedded mark is guaranteed intact by default, because nothing has touched the pixels or the container yet.

3. Edit. The moment a file goes through any compositing, cropping, colour-grading or multi-clip assembly step, an invisible watermark keyed to the original pixel pattern is no longer looking at the original pixel pattern. Whether it survives depends entirely on how durable that specific watermark's implementation is — some are designed to survive transformation, most consumer-facing ones are not tested against it.

4. Re-encode. Final export is the hop most likely to break a mark outright, because re-encoding rewrites the container and frequently strips metadata that isn't explicitly preserved by the encoder. Versely's own final-export path — edit_video, the agent-driven render that stitches, trims, captions and mixes a multi-clip assembly into one output — is a real re-encode step of exactly this kind: it produces a new file, at a new bitrate, in a new container, and metadata that isn't part of what it's designed to carry doesn't ride along for free.

5. Upload. Most social platforms re-encode again on ingest, for their own delivery pipeline. Whatever survived hop four gets a second chance to be stripped here, by a system you don't control and can't inspect.

Five hops, and the honest finding is that a mark applied only at generation has multiple independent chances to not make it to the platform where a viewer actually sees the content — none of which is Article 50(2)'s problem to solve, because that obligation ends at the provider's own output.

What this means for a Versely pipeline specifically

Versely doesn't apply a watermark on any plan — that's a stated, deliberate product choice, not an oversight: no watermarks on any plan, including the free tier, which is a fair trade for most creative work but means the export step described above starts from a file with nothing embedded to lose in the first place. That's worth being explicit about rather than assuming. If the underlying model you generated with does apply its own machine-readable mark upstream of Versely — several providers on the catalog do, independently of anything Versely adds — the survival question above still applies to everything that happens after generation, inside or outside Versely's pipeline.

Rebuilding the export step, practically

The realistic fix isn't a setting to toggle; it's recognising that a mark applied once, at the start, is not the same commitment as a disclosure that travels with the finished file. Two different things need separate handling here, and conflating them is the actual mistake:

Machine-readable marking (what Article 50(2) is about) is a provider-side, technical signal — something a detector reads, not something a viewer sees. You generally can't add this yourself after the fact if the provider didn't embed it, and you can't guarantee it survives your own edit and re-encode steps even if it was there.

Disclosure (what a platform's AI content label or a synthetic media disclosure obligation actually asks for) is something you control directly, at publish time, regardless of what happened upstream — a toggle, a caption, a stated line in the post. This is the layer worth treating as your responsibility every time, precisely because the machine-readable layer might not have survived the pipeline by the time you're ready to publish.

A Versely walkthrough: closing the disclosure gap at export

Since the technical mark isn't something the export step can guarantee, the practical move is making the human-facing disclosure part of the export itself rather than a separate step someone forgets:

"Using edit_video, assemble the final cut from these clips with the standard transitions and music mix, and add a small on-screen text overlay in the last two seconds reading 'Made with AI' — burn it into the export rather than leaving it as a caption I have to remember to add on each platform separately."

That's texts passed alongside clips, transition and music in one edit_video call — a disclosure that ships baked into the file itself, so it survives the upload re-encode step that would otherwise be the last chance to lose a caption typed separately into each platform's post composer. It doesn't solve Article 50(2)'s machine-readable requirement — that's not a job a burned-in caption does — but it does close the part of the gap that's actually yours to close.

FAQ

Does Article 50 require every AI tool to embed a watermark? It requires AI providers to mark content in a machine-readable format and build detection mechanisms — but leaves the specific mechanism unspecified. Not every provider has implemented an embedded, transformation-resistant mark yet, and the law doesn't currently name one required standard.

Does the AI Act mandate C2PA specifically? No. The Commission's materials describe the required scope as marking, provenance, watermarking and/or detection, without naming C2PA or any single standard as mandatory. Providers choose their own implementation path.

If my export pipeline strips a watermark, am I breaking the law? Article 50(2)'s marking obligation is on the AI provider, not on downstream editors or re-encoders. What might apply to you instead — separately, and depending on what you're publishing and where — is a disclosure obligation for realistic synthetic content, which is a different requirement with a different trigger.

What's the difference between a machine-readable mark and a disclosure label? A machine-readable mark is meant for a detector, not a viewer, and is usually embedded at generation time by the provider. A disclosure label — a platform's AI-content toggle, or a caption — is meant for a human viewer and is something you control at publish time regardless of what the file carries underneath.

The law landed on the provider side of the line. The export step is still entirely yours to get right — which means treating disclosure as something you build into the final render, not something you hope survived from further upstream.