Google Flow's documented steps, read against a camera question

Flow's help centre documents the shot in pieces: videos from text prompts, ingredients, frames or other videos; clips arranged, trimmed and previewed in Scenebuilder; a clip changed by describing the change or extended when it ends too soon. No page in this reading is about camera control by name, which the map records as the gap it is. From 6 source pages, read 2026-09-25; no maker pays to be listed.

Fig. 1 Each layer is written by a different team, and only the first is on the map.

1What the map already records

All seven of Flow's step rows, the one page in the whole map whose own line names camera angles and movement, and the guide row about changing a single shot.

Create videos in Google Flow
Videos from text prompts, ingredients, frames or other videos, with or without its agentGoogle Flow Help / recorded 2026-09-25
Create & use your avatar in Google Flow
An avatar of yourself, with your own visual and audio likenessGoogle Flow Help / recorded 2026-09-25
Edit videos & build scenes in Google Flow
Scenebuilder: clips arranged, trimmed and previewed as one sequenceGoogle Flow Help / recorded 2026-09-25
Create videos in Google Flow
A voice reference that keeps one character's voice the same across clipsGoogle Flow Help / recorded 2026-09-25
Edit videos & build scenes in Google Flow
Changing a clip by describing the change, and extending a clip that ends too soonGoogle Flow Help / recorded 2026-09-25
Manage your Google Flow projects
Downloading a video or GIF, inside the page on managing projects and assetsassets & collectionsGoogle Flow Help / recorded 2026-09-25
Manage your Google Flow projects
A copy link that lets anyone find and use a video, inside the same pageassets & collectionsGoogle Flow Help / recorded 2026-09-25
Generate videos using text prompts
Video clips from text descriptions, camera angles and movement includedAdobe Firefly Help / recorded 2026-09-25
Fixing One Shot Without Redoing Everything
Editing one segment's storyboard and regenerating that segment aloneSceneMixer guides / recorded 2026-09-25

2What Flow's help centre documents

Google Flow's help centre is read for every step on this map. Creating videos is one article covering prompts, ingredients, frames and other videos, with or without its agent. An avatar of yourself is its own page. Scenebuilder arranges clips into a sequence. A voice reference keeps one character's voice the same across clips. Changing a clip by describing the change, and extending one that ends too soon, has a page. Downloading a video or GIF, and the copy link that lets anyone use a creation, sit inside the page on managing projects and assets.

Three of those seven readings are classed as covered inside a wider page rather than having a page of their own. The distinction matters when a step is being read closely: a section of an article is a shorter account of the step than an article written for it.

3Where a camera question lands

No step on the map is camera movement, so a camera question never gets a row of its own. The pages that would carry it are the ones about what a shot is made of: the create-videos article, with its prompts, ingredients and frames, and Scenebuilder, where clips are arranged and trimmed. What a model does with the words is a matter for the model's own documentation rather than the product's step map.

One page in the entire register names the layer in its own line: Adobe Firefly's help describes video clips generated from text descriptions, camera angles and movement included. That is the closest any of the entries comes to filing camera language as a documented feature, and it is a line inside a generation article, not a step.

4What the collection counted for the model behind the tool

The model layer is the one the tool names on its own page: an audio-carrying Veo 3.1, with Nano Banana and Gemini Omni beside it, and an agent plus Scenebuilder wrapped around them. The material collected for this column counts Veo at 4,456 posts and 705 comment mentions, and puts its share of the subreddit's posts at 12.5%; the two quotations carried for it ask whether anyone is still using Veo 3.1, and whether a cheaper version with free tries would win people back.

That is the context a camera question lands in: the model is the most-documented part of the pipeline and the most argued about, while the control layer inside the tool has no help-centre page of its own to argue from.

5What the map does with a step nobody documents

Four classes carry that answer. A step can have a page of its own, be covered inside a wider page, be served only by a troubleshooting page, or have no page found in the documentation searched. Flow's seven readings use the first two. Fifteen of the tools on this map write an article for every step, and the register's own drama pipeline documents all seven in guides.

A camera question has none of those four classes to fall into, because the map files steps, not controls. The honest reading of that is narrow: the pages read here settle where a production's work is explained, and they do not settle what any model does with a camera instruction.

6What each entry's own pages state

What each entry's own public page states, read 2026-10-13.
Entry	What its own page states	Characters it states	Checked
Google Flow	Google's models: Veo 3.1 (native audio), Nano Banana, Gemini Omni; an agent and Scenebuilder	Characters and avatars, and ingredients-to-video from references	2026-10-13
SceneMixer	“A location can hold multiple sub-plates for different camera positions, generated together, so cutting around a space stays coherent.”	Not stated in this reading	2026-10-13

Inclusion rule. Rows are the entries this page is about, each read on its own public page, plus the drama pipeline whose guides this map reads step by step. A point a page does not carry is written here as not stated in this reading, rather than inferred from the product's menus. Order. Alphabetical by entry name.

Fig. 2 Solid card: a page was found. Empty card: nothing found in the pages searched.

Three documented pipelines, four steps, read from their own help pages.
Asked of all three	Google Flow	Adobe Firefly	SceneMixer
What is documented about the shot	Videos from text prompts, ingredients, frames or other videos, with or without its agent	Video clips from text descriptions, camera angles and movement included	How a project divides into episodes, segments and takes
Changing one shot	Changing a clip by describing the change, and extending one that ends too soon	Editing an uploaded or generated clip with a text prompt	Editing one segment's storyboard and regenerating that segment alone
Building a sequence	Scenebuilder: clips arranged, trimmed and previewed as one sequence	Not documented in the pages searched	Compositing segments into one episode file
Getting the file out	Downloading a video or GIF, inside the page on managing projects and assets	Rendering a finished edit from its video editor into one file	A link to the finished episode that opens without an account

Inclusion rule. Answers read from each tool's own help pages as this map recorded them on 2026-09-25. A step a tool does not document is written here as not documented in the pages searched, which describes the reading rather than the tool. Order. As the steps are listed above.

7What the collection's counts came to

Two lines below for the model this tool runs on: what the threads posted, and how much of the posts read named it. Both come from the collection behind this column.

Posts and comment mentions for the entries this page is about, collected 2026-10-14.
Entry	Posts	Comment mentions	Positive	Negative
Veo	4456	705	211	78

Inclusion rule. Entries the collection counted on this page's subject. A thread arguing with itself can land in both the positive and the negative column. Order. Descending by posts.

Share of the posts the collection read in one subreddit that name a model family.
Model family	Share of posts	Posts counted
Veo	12.5%	2256

Inclusion rule. Model families the collection put a share against, counted from the posts it read. Order. Descending by share.

Is anyone still using Veo 3.1?
r/VEO3, collected 2026-10-14

Would cheaper Veo 3.1 with free tries win you back?
r/VEO3, collected 2026-10-14

8When the other tool's docs serve better

The model list is the deciding factor — Flow's page names Veo 3.1 with native audio, Nano Banana and Gemini Omni, with an agent and Scenebuilder around them — a model menu rather than a single engine.
References are how a character is held — Characters and avatars are built from references, with ingredients-to-video named on the same page.
An avatar of yourself is the point — The help centre documents an avatar with your own visual and audio likeness, which is a different feature from a stock actor.

Searches like "veo 3 camera" land here, though what the map can show is where a camera question is documented rather than which movement to use. Beside it: what a studio page documents and a documentation set with five gaps.