Markdown edition

# Create and check a complete scene in Google Flow

> A documented route from permitted Google Flow clips through version choice and Scenebuilder assembly to a downloaded scene checked from beginning to end.

By BIG CHANGE Editorial

Published: 2026-10-19T16:35:34.847Z
Updated: 2026-10-19T16:35:34.847Z
Canonical: https://bigchange.ai/blog/google-flow-create-check-complete-scene

![Conceptual charcoal illustration of an unbranded monitor showing three separate video clip stills beneath one larger playback frame, with the middle clip outlined in orange.](https://bigchange.ai/api/media/file/google-flow-scene-playback-hero-v1.png)
AI-generated conceptual illustration by BIG CHANGE; no Google Flow interface, actual generated video or BIG CHANGE test result is depicted.

Google Flow can generate video clips, keep earlier versions when you edit them, and arrange selected clips in Scenebuilder. This guide takes a creator with a short scene brief from separate clips to one downloaded sequence. It follows Google's current help pages, checked on 19 October 2026. BIG CHANGE did not generate, edit or download a Flow video, so the file checks below are instructions for your own result, not a reported test.

## The big change

- **What changed:** Flow's documented workflow reaches beyond generating a clip: it keeps edit versions, arranges clips in Scenebuilder and downloads the [complete sequence as one file](https://support.google.com/flow/answer/16935308?hl=en). Google does not date the introduction of these controls, so this is a description of the current capability.
- **Why it matters:** A creator can choose a version for each shot, adjust the order and trims, then compare the downloaded scene with the intended sequence. That final file check catches problems an attractive individual clip cannot reveal, including a missing shot or awkward join. Google's [editing guide](https://support.google.com/flow/answer/16935718?hl=en) documents those assembly controls.
- **What to watch:** The practical decision turns on the account's available model and regional controls, the current credit quote, and whether the downloaded file passes a full image and required-audio check. Those checks determine whether to keep the scene or repair a specific clip or cut.

## Before you start

You need an age-verified account for someone 18 or older, a [supported region](https://support.google.com/flow/answer/16353544?hl=en), and eligible Google AI access or a qualifying Workspace plan. Google's [access guide](https://support.google.com/flow/answer/16353333?hl=en) recommends Flow on a desktop computer in a Chromium-based browser for the best experience. Check the controls actually available to your account; some features vary by region and model.

Write a short brief listing each intended shot in order, what must be visible, whether sound is required, and how the scene should end. Keep only references you have permission to use. In the same document, leave room to record the accepted clip version and any cut or audio problem. This is your acceptance list, not a promise that Flow will follow every instruction.

Credits vary by model and feature. Before each generation, inspect the active model, resolution and current credit quote in the prompt settings, as Google's [model guide](https://support.google.com/flow/answer/16352836?hl=en) advises. Decide how many attempts you are willing to spend on each shot rather than assuming a fixed cost for the scene.

## Build, refine and export the scene

1. **Create one project and make the first clip.** Open [Google Flow](https://labs.google/fx/tools/flow), choose **+ New project**, and use the standard prompt box. Describe the subject, action, setting, light and visual style from the first shot in your brief. Click the model name, select **Video**, then check aspect ratio, number of outputs, model and generation length before **Generate**. Google's [creation guide](https://support.google.com/flow/answer/16353334?hl=en) documents this route. Watch the returned clip rather than assuming its prompt was obeyed.
2. **Make the remaining clips to the same brief.** Repeat for each shot, noting which returned version you accept. If your permitted images would help, **Video > Frames** can set a start or end image, and **Video > Ingredients** can supply visual references. Describe how each reference should be used and check that the chosen model supports the feature. These are optional creation routes, not a guarantee that details will remain identical across clips. Review each clip's visible action, start and end before moving on.
3. **Refine a clip only where the control is available and the change matters.** Google documents video editing with **Omni Flash**: open generation settings, select **Video** and the Omni Flash model, then select or upload the clip. For an upload, the listed formats are `.mov`, `.mp4`, `.avi` and `.wmv`, with a limit of 60 seconds and 1 GB. An upload longer than 30 seconds must be trimmed to 30 seconds in Flow. Choose a segment of up to 10 seconds, state the specific change in a prompt, and generate. You can make up to three conversational refinement turns while retaining the earlier edit context. Review the new result against the original before accepting it. These limits and steps come from Google's [editing guide](https://support.google.com/flow/answer/16935718?hl=en).

   Uploaded-video editing is unavailable in the European Economic Area, Switzerland and the UK. Google also prohibits editing uploaded videos of identifiable minors. If that route is unavailable or unsuitable, work with permitted generated clips and available creation controls; do not treat a region restriction as an error to bypass. The [region guide](https://support.google.com/flow/answer/16353544?hl=en) lists these limits. Flow's separate **Extend** control applies to eligible Veo-generated clips: Google's current [model table](https://support.google.com/flow/answer/16352836?hl=en) says an eight-second Veo 3.1 clip is extended with Veo 3.1 Lite. It is not the Omni editing route, and Google's editing guide says other edit modes cannot be applied to an extended clip.

4. **Keep the chosen version.** Flow retains the original and earlier prompts in the clip's **History** panel. If you want an earlier edited version in the scene, open the video, hover over the desired version in History and click **Save to Project**. Record which version you chose for each shot. This avoids losing a good take when a later refinement fails to improve it.
5. **Assemble the complete scene.** In the project, hover over each accepted clip and choose **More > Add to Scene**. In Scenebuilder, drag clips into the brief's order and use the handles to trim the beginning or end of each one. Preview the *whole* sequence. Check every join, the opening, the ending and the intended duration; listen for required audio. Fix an affected clip or cut, then preview the whole scene again. Google's [Scenebuilder instructions](https://support.google.com/flow/answer/16935718?hl=en) document ordering, handle trims and whole-sequence preview.
6. **Download the scene and inspect the file.** Use Scenebuilder's scene download control for the complete sequence. A project, collection or individual asset has a separate download path; those controls do not establish that you have exported the assembled scene. Google's [asset guide](https://support.google.com/flow/answer/16935308?hl=en) explicitly describes the full Scenebuilder sequence as one downloaded file. Open that file in a player on your device. Play it from start to finish and compare the actual shot order, cuts, duration, image, required audio and ending with your brief and accepted clip versions. If the file is incomplete or a join is wrong, correct the affected scene edit, download again and inspect the new file. Keep the version that passes your list.

If generation fails, read Flow's response and check your [AI credit activity](https://support.google.com/googleone/answer/16287445?hl=en) before trying again. Google says credit use varies and credits for a failed activity may take time to reappear. Allow for that delay when deciding whether to retry. Your final check belongs to the complete downloaded file, played from beginning to end.

## Sources & further reading

- [Create videos in Google Flow](https://support.google.com/flow/answer/16353334?hl=en) explains the standard Video prompt, settings, frames and ingredients.
- [Edit videos & build scenes in Google Flow](https://support.google.com/flow/answer/16935718?hl=en) gives edit limits, version recovery and Scenebuilder's assembly controls.
- [Manage your Google Flow projects, assets & collections](https://support.google.com/flow/answer/16935308?hl=en) distinguishes project and asset downloads and confirms the complete Scenebuilder sequence can be one file.
- [Get started](https://support.google.com/flow/answer/16353333?hl=en), [models and supported features](https://support.google.com/flow/answer/16352836?hl=en), and [regional availability](https://support.google.com/flow/answer/16353544?hl=en) establish account, device, model and location limits.
- [Manage AI credits with Google One](https://support.google.com/googleone/answer/16287445?hl=en) explains variable credit use, activity history and delayed return after a failed tool activity.

## Sources

- [Create videos in Google Flow](https://support.google.com/flow/answer/16353334?hl=en) — Creation steps and optional frames and ingredients.
- [Edit videos & build scenes in Google Flow](https://support.google.com/flow/answer/16935718?hl=en) — Clip editing and limits, History, Scenebuilder controls and scene download.
- [Manage your Google Flow projects, assets & collections](https://support.google.com/flow/answer/16935308?hl=en) — Separate asset/project download paths and full Scenebuilder sequence as one file.
- [Get started with Google Flow](https://support.google.com/flow/answer/16353333?hl=en) — Eligibility and desktop browser recommendation.
- [Learn about Google Flow models & supported features](https://support.google.com/flow/answer/16352836?hl=en) — Model support, Veo extension eligibility and credit quote check.
- [Where you can use Google Flow](https://support.google.com/flow/answer/16353544?hl=en) — Supported regions and uploaded-video edit restrictions.
- [Manage your AI credits with Google One](https://support.google.com/googleone/answer/16287445?hl=en) — Variable credits, activity history and failed-activity delay.