GateTrue

What each generator documents about marking its output

Veo marks every video and publishes no way off

Veo's documentation says videos it creates are watermarked using SynthID, and publishes no plan, parameter or setting that alters that. The mark is presented as a property of the output. As of 2026-09-22.

Two developer documents, two grammars for one markOne reference lists a watermark field with a published default, treating the mark as an input the caller decides. The other names the mark under Limitations, treating it as a property of the output. The same genre of document, and opposite values in this column.Listed as an inputListed as a limitationWhere it appearsAmong the request parametersUnder a heading called LimitationsWhat the caller doesSets a boolean, default falseWorks around itThis column recordsA parameter instead of a tierNo route publishedWhat is namedThe text and the corner of the stampThe scheme and its verifierBoth rows are read from documentation written for callers
Fig. 1 The grammar of the document predicts the cell better than the technology does.
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 valueSame mark, no removal documented
The vendor's own wordsVideos created by Veo are watermarked using SynthID, with nothing published about changing that.
How the reading was takenRead from developer documentation whose statement appears under Limitations rather than among features.

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.

No tier attached to the mark: the generators whose paid tier answer takes the same form. Recorded 2026-09-22.
GeneratorPaid tier
Amazon Nova ReelSame mark, no removal documented
SoraNot documented
VeoSame mark, no removal documented

Inclusion rule. Generators whose pages describe a mark on output and attach no plan, tier or subscription to it anywhere, so there is no crossing point to record. Order. Alphabetical by generator name.

1Under Limitations, which is where things you cannot change go

The placement is the finding. A heading called Limitations collects the properties a developer has to work around: rate limits, supported lengths, and here a watermark. Putting the mark there is a statement that it is not a feature, not a tier and not negotiable through the interface.

Compare the vendor next door in this register, whose reference lists a watermark field with a published default of false. Both are developer documents; one treats the mark as an input and the other as a constraint. The difference lands in this column as a parameter on one row and nothing at all on the other.

2An invisible mark is not the same kind of thing to remove

The mark here is a signal rather than an overlay, which changes what removal would even mean. A visible badge is a thing a plan can decline to apply; a provenance signal is the point of the exercise, and a vendor offering to switch it off would be offering to make its own detection route useless.

So the blank in this column should not be read as the mark is permanent. That would be a claim about the product. The register's claim is narrower: no plan and no request parameter is published, which is what a reader integrating this model needs to know before promising anything to a client.

3What is published instead of a price

Two sentences, and both hand a reader something to do. The scheme is named, so its scope, timing and robustness can be looked up on the pages of the organisation that builds it. The verification platform is named, so a file can be checked. Neither of those is available on any priced row in this register.

Read across the row, the shape is consistent: a filled file-contents cell, a named public reader, an empty visible-mark cell and an empty crossing point. Three generators here have that shape and all three are read from a document written for developers or reviewers.

4Sources

  • Control
    Not documented on the vendor's public pages (as of 2026-09-22)no plan and no request parameter publishedGemini API, Veo documentation / recorded 2026-09-22
  • 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

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 paid tier column page. Neighbouring readings: Wan, API parameter, Amazon Nova Reel, paid tier.