GateTrue

What each generator documents about marking its output

Veo publishes no parameter and no plan

Veo's documentation names the watermark under Limitations and offers no request field, plan or setting that changes it. In a document built to list every input, there is no input for this. As of 2026-09-22.

Where a marking statement sits in a developer documentTwo references written for the same audience place the same kind of statement differently. One lists a watermark field among the request parameters with a published default. The other names the mark under the heading collecting properties a caller cannot change.Same genre, two placementsAmong the parametersOne reference here publishes a boolean watermark field with adefault of false.Under LimitationsThis one names the mark where properties a caller works aroundare collected.What followsA parameter on one row, no published route on the other, fromthe same genre of page.Offered insteadA named scheme and a named verification platform, both of whicha reader can use.Why this empty cell is a finding rather than a gap
Fig. 1 In a document whose purpose is to enumerate inputs, the absence of an input is itself informative.
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 valueNot documented
The vendor's own wordsThe watermark is named under Limitations, with no parameter or plan published beside it.
How the reading was takenRead from developer documentation, where the absence of a parameter is informative because the document lists them.

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 route published: the generators whose control answer takes the same form. Recorded 2026-09-22.
GeneratorUser toggle
Amazon Nova ReelNot documented
SoraNot documented
VeoNot documented

Inclusion rule. Generators whose pages describe a mark on output and publish no plan, parameter or setting that changes it, so no route off the mark is recorded. Order. Alphabetical by generator name.

1Silence in a document that enumerates its inputs

An empty cell usually means a page did not raise a subject. This one means more than that. Developer documentation exists to list what a caller may send, and this one lists a good deal; the marking behaviour is filed under the properties a caller works around instead. The absence of a field is a statement in that context.

One other generator here proves the point by contrast. Its reference publishes a boolean watermark field with a default, in exactly the place a reader would look. Both documents are written for the same audience, and one of them offers the control while the other places the mark outside the caller's reach.

2An invisible mark changes what removal would mean

The documented mark is a signal rather than an overlay, so switching it off would not clean up a frame; it would defeat the mechanism the vendor built for identifying its own output. A vendor offering that option would be offering to make its own verification platform useless.

Which is why this cell should be read narrowly. Three rows record no published route and two of them describe invisible marks, where removal is not a customer feature anybody would expect. The finding is about what a reader can rely on, not about a withheld capability.

3What is offered instead of control

Two things, and both are actionable. The scheme is named, so its scope, the moment the signal is written and the transformations it is designed to survive can be looked up on the pages of the organisation that builds it. The verification platform is named, so a file can be checked by whoever holds it.

That pairing is the arrangement that helps a receiving party: an unremovable mark with a public way to read it. One other row in this column has it; a third has an unremovable mark and detection described as internal, which is the same empty cell and a different situation.

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
  • Visible mark
    Not documented on the vendor's public pages (as of 2026-09-22)nothing published about a mark on the frameGemini 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 control column page. Neighbouring readings: Amazon Nova Reel, control, D-ID, control.