A help centre and an API reference, both narrower than a product page

One statement comes from a help centre and describes reusing images from one clip to the next. The other comes from an interface reference and describes images per call with nothing stored. Both genres are written to be true rather than to be attractive. As of 2026-09-22.

Inclusion rule. Both cells are documented and neither is a product page. The contrast is the documentation genre, which predicts how large a claim the text is allowed to make. Order. The support article first, then the interface reference.

1Genre is evidence, and this file records it

A support article exists because a user got stuck, so it describes the next click and nothing further. An interface reference exists because code has to work, so it publishes limits nobody would put in a headline. Neither has any reason to overstate.

Marketing pages are not dishonest for being ambitious; they are simply a different kind of text. Grading them alike would let a sentence written to sell outrank a sentence written to be used.

2The price of modesty is that the season question goes unanswered

Neither of these pages says anything about an episode, let alone forty. A producer reading only these two would learn precisely what happens on one generation and would have to invent the rest of the strategy themselves.

That is often the correct purchase for a team with engineers. It is a poor purchase for a team that expected the product to hold the series together.

3What each genre still fails to cover

The support article does not say whether images can be stored under a name, or what happens when two characters are held at once. The reference does not say what a caller should do to keep forty episodes aligned.

Both gaps are outside the genre's job. Recording them keeps a reader from mistaking precision on one question for coverage of another.

4The wording both sides published

• Cross-episode cast
  The help centre states that the same images for a character and key objects can be used consistently from one clip to the next through ingredientsa named input in documentationGoogle Flow, help centre / recorded 2026-09-22
• Cross-episode cast
  One to seven reference images per call, used so the model generates a video with consistent subjectsper call rather than per characterVidu, reference-to-video API reference / recorded 2026-09-12

5The same column, read for a third tool

On the cross-episode cast, SceneMixer's published page puts it in one line: A full-body sheet per character, made while the script is analysed. Its reading here, A reference sheet made once and cropped into every segment, sets out what that line settles for a series and what it leaves to a production run.

6Sources

Read from the help centre article at support.google.com and the reference-to-video API reference at platform.vidu.com, checked 2026-09-22 and 2026-09-12 respectively. The full column is on cross-episode cast; the single readings behind this contrast are Google Flow and Vidu. Other contrasts filed here: DramaSo and Dramily, TrendShort and Showrunner Studio, Luma Agents and Crano AI.