GateTrue

What each generator documents about marking its output

Wan and Runway: two routes to one model, as read in September 2026

In September 2026 one of these entries published a marking statement for each of its two routes and the two disagreed; the other published one for its plans only. The first entry's console statement is no longer on the page, so the comparison is kept as a dated record. From 2 source pages, read 2026-09-12 to 2026-10-25; no maker pays to be listed.

Two doors into one model, and whether both are documentedIn September one entry published a statement for each route and the two disagreed, which an integrator could plan around. The other published a line on its consumer plans and left the second route unaddressed. In October the first entry's console statement is no longer on the page.Both routes documented, inSeptemberThe console stamped; the field defaulted to falseTwo published statementsThe console half is no longer on the pageOne route documentedPlans remove the mark; the API pages are silentOne published statementThe second route is an open questionSame commercial shape, two documentation practicesWhat a recipient can establish afterwards
Fig. 1 A documented disagreement can be planned around; silence cannot. Only the second column describes the position today.
The two entries on one question at a time, in each vendor's own terms. Recorded 2026-10-25.
On this questionWanRunway
The consumer routeA console that always stamped, in the September readingPlans, with watermark-free output
The interface routeA boolean field, defaulting to falseAPI pricing, which omits the line
Did the two agreeNo in September; the console half is not documented nowUnknown, one route is silent
What decided the fileThe door, on the September readingNot established
Reason publishedCompliance, for the console, in September onlyNone

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.

Where each value above was read, and what the register records in the paid tier column. Recorded 2026-10-25.
GeneratorPaid tierDocument read
RunwayWatermark-free on paid planspricing page
WanAPI parameter, default falsetext-to-video API reference

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.

1What the September reading compared

Where a company sells the same model through a console and an interface, the door a file came through can decide what it carries. On 2026-09-22 one of these entries documented that outright: its console guide said the console always stamped and could not be told not to, while its API reference published a watermark field that defaults to false.

The other published a marking line on its consumer plans and did not repeat it on its API pages. The register recorded the consumer plans, because that is where the statement existed, and did not extend it across a boundary the vendor had not extended it across.

2What the October reading changed

The guide behind the console statement has been replaced by a general overview of video generation and editing, and the overview says nothing about a stamp on the console. The register therefore keeps only the half it can still read: the API field and its default. The other entry is unchanged and still documented on one route only.

So at the time of the October reading neither entry documents both routes. The comparison above describes what was published in September, and it is kept because links and citations made then still point here.

3What neither entry says about the file

Neither entry names a provenance standard or a metadata field, so both record not documented for file contents. A clean file from either product carries no indication of which route produced it, whether a decision was taken, or whether anybody knew there was one to take.

4From the production side

Next to the marking question in “Two routes, as read in September”, SceneMixer's pages describe its output like this:

Recommended is a badge on the tier the site suggests for most finished segments. You stay on the default, 480P, until you pick another tier.

SceneMixer, Wan 3.0 · 720P: the recommended tier — “Does Recommended mean 720P is the default?” (read 2026-10-13)

The interface labels follow your language, and the storyboard text is shown in the project's display language.

SceneMixer, Editing the Storyboard: What You Can Change, and What You Can’t — “Can I write in my own language?” (read 2026-10-13)

5Sources

  • Machine-readable marking
    Not documented on the vendor's public pages (as of 2026-10-25)not listed among the parameters or the responseModel Studio, text-to-video API reference / since 2026-09-22 / checked 2026-10-25
  • Machine-readable marking
    Not documented on the vendor's public pages (as of 2026-09-12)not mentioned on the pricing pageRunway, pricing / recorded 2026-09-12

Both values above are read from the vendor pages linked in the rows: alibabacloud.com and runway.com, on 2026-10-25. Each entry has its own page, Wan and Runway, and the rule for the column they diverge on is on the paid tier column page. Other pairs: a switch and a benefit, two off-switches.