The two entries that describe their own mark
Almost nothing in this register describes the mark itself. Two entries do: one says its watermark moves, the other gives the words and the corner. Both scope the claim to one surface. As of 2026-09-22.
| On this question | Sora | Wan |
|---|---|---|
| What is published | Visible, and moving | The text, and the lower-right corner |
| Scope of the claim | Downloads from the vendor's own surfaces | The console's generation page |
| Other route to the models | Not addressed | The API, defaulting to no stamp |
| Reason published | None | Legal compliance requirements |
| Document read | A system card | A console guide and an API reference |
Inclusion rule. One row per question on which these two entries can be compared from their own published pages. Questions neither vendor addresses are left out rather than filled with a dash. Order. Fixed order: the mechanism first, then who holds it, then what it leaves behind.
| Generator | Free tier | Document read |
|---|---|---|
| Sora | Visible moving watermark on downloads | Sora 2 system card |
| Wan | Console always stamps AI generated | video generation guide |
Inclusion rule. The two entries on this page, with the value each one's own pages support in the column they diverge on. Order. Alphabetical by generator name.
1Two descriptions, in a register of names
Thirteen entries name their mark in a word or two and describe nothing about it. These two go further. One adjective on the first, moving, rules out a fixed corner badge and tells a reader what a crop would leave behind. The second gives the words of the stamp and the corner it occupies, which lets a file be checked against the page.
Neither reaches a specification. Size, opacity and behaviour at other aspect ratios are unpublished on both, and the descriptions were produced for different reasons: one belongs to a safety enumeration, the other to instructions for using a console. Detail arrives as a by-product of the document's purpose.
2Both scope the claim to a surface, not to the model
One statement covers videos downloaded from the vendor's own website and app; the other covers videos generated on the console's own generation page. In both cases the claim is about a door rather than about a model, and the register records the scope as written instead of generalising it.
On one of the two, the second door is documented and disagrees: the API publishes a watermark field defaulting to false, so the same models return unstamped files to a caller. On the other, other routes are simply not addressed, which is a weaker finding and the same practical uncertainty.
3A reason on one side, a manifest on the other
The console entry attributes its unremovable stamp to legal compliance requirements, one of two published rationales in this register. The system card entry offers no reason and instead names C2PA metadata on all assets and internal detection tools, filling a column the console entry leaves empty.
So the two entries that describe their frame diverge completely on the file. One enumerates a provenance standard it cannot switch off; the other enumerates every request field and names no metadata at all. Describing the mark turns out to predict nothing about describing the file.
4Sources
- Visible markListed for general availability among the provenance tooling for the vendor's own products: a visible moving watermark on videos downloaded from sora.com or the Sora applisted as provenance tooling
- Free tierVideos 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 surface
Both values above are read from the vendor pages linked in the rows: openai.com and alibabacloud.com, on 2026-09-22. Each entry has its own page, Sora and Wan, and the rule for the column they diverge on is on the free tier column page. Other pairs: no free plan, or one that runs out, outside a price list.