Console surface: a vendor's own front door
A console surface is a vendor's own web interface for trying a model. The register used the term for one entry's console until 2026-10-25, when the guide behind that entry was replaced; the word stays for the reading it names. As of 2026-10-25.
| The term | Console surface |
|---|---|
| What it names | A vendor's own web interface for generating output |
| What it is not | The models behind it, which may be reachable another way |
| Where the register uses it | One earlier reading, dated 2026-09-22; no current cell |
Inclusion rule. Words this site uses in a narrow sense, where the ordinary sense would lead a reader to misread a cell. No vendor statement appears on this page. Order. Fixed order: what the word names, what it excludes, then where it is used here.
1A surface is not a plan and not a product
Console access is usually not a free tier; it is a place to try things. The free-tier column records what somebody gets without doing anything special, which is the question underneath the column's name, so a console default belongs there even though no plan is involved.
It is also not the model. The same models can be reached through a documented interface with different behaviour, which is why a value should name the surface rather than the product. Generalising it would produce a statement the vendor's own other page could contradict.
2Why a console may mark when an interface does not
A console is a shop window. It is used by people who have not paid, it produces output that circulates, and a stamp on it costs the vendor nothing. An interface is used by somebody who has integrated the product and has commercial reasons to control the output; handing that caller a switch is normal, which is what a documented default of false amounts to.
That is a pattern, not a rule. The register records what a vendor's pages say about each surface and does not predict one from the other.
3How the register used the term
On 2026-09-22 the register applied the word to one entry's console, whose guide said it always stamped videos and could not be told not to. That guide has since been replaced, and the reading of 2026-10-25 found no such statement on the page that took its place. The earlier reading is kept as a dated record on its own page, Wan's console stamp, as described in September 2026.
The term matters for planning rather than for forensics. Nothing in a delivered file records which door produced it, so a production can decide which door to use and a recipient cannot work out which door was used.
Nothing on this page is a vendor statement; the values it helps read are on the support table, with the page and the date each one was read from. See also the user toggle column, source documents. Nearby terms: API surface, request parameter, documented default.
4A generator's own account
Next to the marking question in “Console surface”, 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)