GateTrue

What each generator documents about marking its output

Products documented on more than one surface

Three entries can be reached more than one way. One publishes a marking statement for each route and the two disagree; one publishes a statement for its plans and not its interface; one scopes its statement to a route without addressing the others. As of 2026-09-22.

Two doors into one model, and what is published about eachWhere both routes are documented, an integrator can plan around a difference in defaults. Where only one is, the second route is an open question that no published page closes. In neither case does the delivered file record which route produced it.Both documentedA console that stamps, a fieldthat defaults to falseTwo published statementsA split an integrator canplan aroundOne documentedPlans remove the mark; theinterface pages are silentOne published statementAn open question about theother routeScoped to a routeDownloads from the vendor's ownsurfacesA statement with an edgeOther routes neitherincluded nor excludedThree ways of documenting more than one doorNo file from any of the three records which door it came through
Fig. 1 The vendor that documents both routes shows that assuming the second matches the first can be exactly wrong.
The rows this finding rests on, with the value each one's own pages support. Recorded 2026-09-22.
GeneratorFree tierDocument read
RunwayNo watermark-free output listedpricing page
SoraVisible moving watermark on downloadsSora 2 system card
WanConsole always stamps AI generatedvideo generation guide

Inclusion rule. Entries whose pages show that the same models are reachable through more than one surface, whether or not a marking statement is published for each of them. Order. Alphabetical by generator name.

1The route can decide what the file carries

One entry states it outright: its console always stamps videos in the lower-right corner and says the stamp cannot be switched off there, while its interface publishes a watermark field defaulting to false. Same models, opposite defaults, and both statements are on the vendor's own pages.

The second publishes watermark-free output as a plan feature and does not repeat the line on its interface pricing pages. The third scopes its visible mark to downloads from the vendor's own website and app, which is a route rather than a product, and does not address any other.

2Why a documented disagreement beats silence

An integrator who knows the two routes differ can plan around it: label the pipeline, decide which door production uses, and expect stamped files from the other. An integrator on a product whose second route is undocumented has an open question and no way to close it from published pages.

The register records only what is published, so silence about a second route stays silence. It does not become the same statement as the first route by implication, however reasonable that inference would be, because the one vendor that documents both shows the inference can be exactly wrong.

3What a recipient can tell afterwards

Very little. On the entry with opposite defaults, a stamped file at least proves the console route, and a clean file proves nothing: it could have come from a caller who set the field, or from one who never knew the field existed. On the other two there is no observable difference between routes at all.

None of the three names a provenance standard or a metadata field, so no file from any of them carries a published record of the route. That is the practical ceiling on this whole finding: the door matters and the file does not remember it.

4Sources

  • Free tier
    Videos generated on the Online Experience page of the Model Studio console always carry a watermark: the text AI generated in the lower-right corner of the videothe console surfaceModel Studio, video generation guide / recorded 2026-09-22
  • Paid tier
    The API request has a boolean watermark parameter that defaults to false; set true it adds a watermark in the lower-right corner with the text AI Generatedthe API surface, default offModel Studio, text-to-video API reference / recorded 2026-09-22
  • Machine-readable marking
    Not documented on the vendor's public pages (as of 2026-09-22)not mentioned on the pricing pageRunway, pricing / recorded 2026-09-12

Every row above is read from the vendor page named beside it, on 2026-09-22. The same values in register form are on the support table, the rule for this column is on the free tier column page, and what may fill a cell at all is on the what earns a row page. Other findings: durability caveats, the spread of prices.