GateTrue

What each generator documents about marking its output

Veo names a scheme and a platform that reads it

Veo's documentation says videos it creates are watermarked using SynthID and that they can be verified using the SynthID verification platform. A scheme and a reader, in two sentences. As of 2026-09-22.

What a complete pairing in this column looks likeA cell is useful here when it names a scheme a reader can look up and a route a reader can use. This row names both. The scheme's own pages then supply scope, timing and robustness, which no generator documentation in this register supplies on its own.The generatorsaysEvery video itcreates iswatermarkedusing a namedscheme.A name to lookupThe scheme'spages sayWhere it isembedded, whenit is written,what it shouldsurvive.A route to checkThe platformNamed in thedocumentationas the way toverify a file.An answer aboutone fileWhat apublisher hasA signal, aspecificationand a readerthey can usethemselves.
Fig. 1 The scheme and the generator are kept as separate entries because a scheme can be documented fully while the products using it stay silent.
One cell of the register, and what it rests on. Read from the vendor's Veo API documentation on 2026-09-22.
The readingWhat it holds
The recorded valueSynthID, with a verification platform named
The vendor's own wordsVideos are watermarked using SynthID, and can be verified using the SynthID verification platform.
How the reading was takenRead from developer documentation, which names both the scheme and the route for checking a file.

Inclusion rule. One row for the value, one for the sentence or absence behind it, one for the method. Nothing here is drawn from output, support replies or coverage by anyone else. Order. Fixed order: the value, then its evidence, then the method.

A standard named, with a public reader: the generators whose machine-readable marking answer takes the same form. Recorded 2026-09-22.
GeneratorMachine-readable marking
Amazon Nova ReelInvisible watermark plus C2PA Content Credentials
VeoSynthID, with a verification platform named

Inclusion rule. Generators that name a provenance scheme and also name a route by which somebody outside the vendor can read it in a file. Order. Alphabetical by generator name.

1Two sentences that between them do the whole job

A filled cell here has to hand a reader something to do next. This one hands over two things: the name of a scheme, which can be looked up, and the name of a platform, which can be used. Nothing else in the generator table pairs those, and the pairing is what makes the cell useful rather than merely filled.

The scheme's own pages carry what the documentation does not: where the signal is embedded, that it is written the moment content is created, which transformations it is designed to stand up to, and two published routes for checking a file. This row is the generator-side end of that, which is why the scheme is kept as a separate entry.

2An in-picture signal fails differently from a manifest

This mark lives in the picture rather than in the container around it. That is the opposite arrangement from a credential manifest, and it fails in the opposite direction: a re-encode that strips a manifest does not obviously remove a signal carried by the pixels, and a filter or a crop that leaves a manifest untouched is exactly what threatens one.

The register does not test either claim, and it can put them side by side. Two generators here name a credential manifest and one names an in-picture signal, so a reader comparing rows is comparing mechanisms with different failure modes rather than different amounts of diligence.

3What the row leaves empty, and why that is consistent

The visible-mark cell on this generator records not documented, because nothing in the documentation describes anything on the frame. The control cell records no route. So the row is filled in one column and empty in three, which is the shape produced by a document written for developers rather than buyers.

Three generators have that shape, and all three were read from a reference or a card. The nine read from a pricing grid have the mirror shape: a crossing point and a price, and nothing at all about the file. The split follows the genre of the document almost exactly.

4Sources

  • Machine-readable marking
    Videos created by Veo are watermarked using SynthID, described as the vendor's tool for watermarking and identifying AI-generated contentstated under LimitationsGemini API, Veo documentation / recorded 2026-09-22
  • Detection
    Videos can be verified using the SynthID verification platforma named platformGemini API, Veo documentation / recorded 2026-09-22

The value above is read from ai.google.dev, the vendor's Veo API documentation, on 2026-09-22. The whole row for this generator is on its own page, and the rule for what this column may hold is on the machine-readable marking column page. Neighbouring readings: Amazon Nova Reel, file contents, SceneMixer, file contents.