An AI drama in Google Flow, read one layer at a time
Google Flow's own pages list Veo 3.1 for video with native audio, plus Nano Banana, Gemini Omni, an agent and Scenebuilder, and they name characters, avatars and ingredients-to-video from references. Its help pages, filed in this register, say an edited clip keeps its original and the History panel holds every earlier version. From 6 source pages, read 2026-09-25; no maker pays to be listed.
1What the register already keeps
Every row this register keeps for Google Flow, read from its help pages, then three rows from two other editors on what a drama leans on hardest: the unit and the join.
- ScenebuilderClips are arranged in sequence, reordered and trimmed into a scene in Scenebuilder
- FramesTransitions are made with start and end frames
- Edit your video clipsA single clip is edited or extended on its own, and the original is not lost
- Edit your video clipsEditing keeps the original; the History panel holds every previous version and its prompt
- Agent promptsThe Agent can make several variations of a video at once
- Save past videosA previous version of an edited clip can be saved to the project and added back into Scenebuilder
- FAQFailed generations are not chargedcharged for a failed generation
- First/last frame and universal referenceShots are guided by first-frame and last-frame references
- CompositingThe composite joins the active version of every segment, without re-encoding where it can; no transition is named
- Quick answerAn episode holds segments, and a segment holds every take generated of it
2What Google Flow's own pages state
Google Flow's pages describe a creative studio built on Google's own models: Veo 3.1, which the pages say generates video with native audio, with Nano Banana and Gemini Omni beside it. An agent works alongside the person making the film, and Scenebuilder is where the clips are put in order. For people on screen the pages list characters and avatars, and ingredients-to-video, which builds a clip out of reference images.
The access line deserves a reading before a series is planned around it. Features, the pages say, vary by subscription tier, by platform and by region, and users must be eighteen or over. A drama written on one account in one country may meet a different set of tools on another, so everything quoted here describes the pages on the day they were read rather than a promise made to every account.
3Where a drama sits among Flow's tools
A drama asks three things of a tool: a cast that stays the same across many scenes, scenes that join, and a cut that survives being changed. Flow's pages answer the first with characters, avatars and references — a person is defined once and brought into clips instead of being described again in every prompt. Its help pages, as this register filed them, answer the second with Scenebuilder, where clips are arranged in sequence, reordered and trimmed into a scene, and with transitions made from a start frame and an end frame.
The third need is where the help pages say the most. Editing a clip keeps the original. The History panel lists every earlier version with the prompt that made it, and an earlier version can be saved to the project and put back into Scenebuilder. The Agent can also make several variations of a video at once, which turns a choice between two takes into a pick from a set. A generation that fails is not charged.
4Scene, episode, series: what the pages name and what they leave
Scenebuilder works at the size of a scene. The pages read for this column name nothing above it: no unit that gathers scenes into an instalment, and nothing about carrying a cast from one instalment to the next beyond the characters feature itself. A drama made in Flow is therefore assembled one level up by whoever is making it, either as scenes exported and ordered somewhere else or as one long Scenebuilder sequence treated as an episode.
That is a reading of what the pages say, not of what people manage to do with the tool, and the register keeps the two apart. OiiOii, filed beside it, stitches shots into narrative videos longer than a minute and guides each shot with first-frame and last-frame references. SceneMixer's row makes the episode itself the container: segments inside it, every take of a segment kept, and the composite joining the active version of each one.
5What the collection counted for Veo
Veo comes to 4,456 posts and 705 comment mentions in the material gathered for this column. Of the two lines kept with those numbers, one wonders if anybody still uses the current release; the other asks whether a lower price and some free attempts would bring former users back. Both are about staying with a model family, which is the question a series puts to any tool long before its last episode is finished.
Counts like these measure talk in one subreddit and say nothing about the help pages read above. A failed generation going uncharged and every version staying in History are facts about the product; a thread asking whether anyone still uses the model is a fact about the mood around it. The tables below keep the two kinds apart and put a date on both.
6What each maker's own pages state
| Maker | What its own pages state | Characters it states | Access it states | Pages read |
|---|---|---|---|---|
| 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 | Features vary by subscription tier, platform and region; 18+ | 2026-10-13 |
| SceneMixer | “An AI short drama is a serialized show of 60–120 second vertical episodes whose cast, sets and footage are generated by AI. Making one takes six steps: analyze the script into episodes, lock a consistent cast with reference art, localize for your market, write and edit storyboards, generate each 4–15 second shot, then composite and publish.” | Not carried on the pages read | Not carried on the pages read | 2026-10-13 |
Inclusion rule. Rows are the makers this page is about, each read on its own public pages, plus the segment-based editor whose six readings this register keeps. A line a maker's page does not carry is written here as not carried on the pages read, which describes the reading rather than the product. Order. Alphabetical by maker name.
| Asked of each reading | Google Flow | OiiOii | SceneMixer |
|---|---|---|---|
| The unit a scene is made of | Clips arranged, reordered and trimmed into a scene in Scenebuilder | Shots stitched into narrative videos longer than sixty seconds | An episode of segments, each holding every take generated of it |
| Joining two shots | Transitions made with start and end frames | Shots guided by first-frame and last-frame references | The composite joins the active version of every segment; no transition is named |
| Redoing one of them | A single clip edited or extended on its own, the original not lost | Any single shot regenerated on the canvas while the story around it stays | One segment edited and regenerated without redoing the episode |
| Changing a finished cut | An earlier version saved to the project and added back into Scenebuilder | Linked editing updates related scenes when one element changes | The episode composited again; the earlier file stays until the new one replaces it |
Inclusion rule. Answers read from each page as this register recorded it — the vendor pages on 2026-10-13, the register rows on 2026-09-25. A line a page does not carry is written here as not carried on the pages read, which describes the pages rather than the product. Order. As the lines are listed above.
7What the collection counted
One model family below, the one Flow's pages name for video, with the counts the collection keeps and the two questions stored beside them. Both ask whether people are staying with it.
| Family | Posts | Comment mentions | Positive | Negative |
|---|---|---|---|---|
| Veo | 4456 | 705 | 211 | 78 |
Inclusion rule. Families the collection counted on this page's subject, from one subreddit. A thread can be counted on both sides. Order. Descending by posts.
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 maker's way suits better
- The models should be Google's own — The studio is built around Google's own image and video models, with sound generated natively by Veo 3.1, so a project that wants those models first starts in the right place.
- The cast is designed from pictures — Characters, avatars and ingredients-to-video from references are listed on the pages, which suits a cast drawn from images rather than written out in words.
- Every earlier version should stay in reach — The help pages say editing keeps the original and History holds every previous version with its prompt, which suits a drama revised many times before anyone watches it.
The words behind this page are "how to make ai drama in google flow"; the counts below belong to the model family Flow generates its video with. Beside it: a redo scoped inside a shot and the edit step read across ten rows.