Google Flow's output specs, read the way the sheet reads
The pages behind Google Flow state 720p, 1080p or 4k generated directly, 24fps output, landscape 16:9 by default with portrait 9:16 available, and generations of 8 seconds with 4 and 6 also offered. Every video carries a verifiable SynthID watermark, and the HDR line is left without a figure. From 4 source pages, read 2026-09-25; no maker pays to be listed.
1What the sheet already carries
Six readings of the pages behind the app — the HDR line among them is the one read and not printed — then four references the sheet measures a delivery against.
- Veo 3.1720p, 1080p or 4k generated directly; 4k is not available for Veo 3.1 Litecontrol the resolution
- Model parameters24fps outputframe rate
- Veo page read in full; no HDR or bit-depth statementNo figure on the vendor's spec pages (checked 2026-09-25)
- Veo 3.1Landscape 16:9 by default, or portrait 9:16control the aspect ratio
- Model parameters8 seconds per generation, with 4 and 6 also offered; 8 is required at 1080p and 4kdurationSeconds
- LimitationsEvery video carries a SynthID watermark that can be verifiedwatermarking
- Recommendation pageITU-R BT.709 sets parameter values for HDTV; version 6 (06/2015) is in force
- Video resolution and aspect ratio16:9 is the standard aspect ratio on a computer; the player adapts to other shapes
- Frame rateUpload in the frame rate recorded; 24, 25, 30, 48, 50 and 60 are named as common
- Upload requirementsHDR uploads in 720p, 1080p, 1440p or 2160p, with UHD widths preferred to DCIresolution
2What the pages behind the app print
Google Flow is the interface; the figures come from the model pages behind it, and they are printed per model rather than per product. Veo 3.1 generates 720p, 1080p or 4k directly, with 4k unavailable on the Lite model, and the output frame rate is stated once as 24fps.
The shape and the length are written the same way. Landscape 16:9 is the default and portrait 9:16 is the alternative; a generation runs 8 seconds, with 4 and 6 offered as well, and 8 is required once the resolution is 1080p or 4k. The marks line is a single sentence: every video carries a SynthID watermark, and the page says it can be verified.
3The one line read and not printed
HDR and bit depth is the line this vendor leaves empty. The page was read in full and carries no HDR or bit-depth statement, so the figure is filed as no figure — the middle of the sheet's three states, between a printed value and a page that would not load.
On a delivery sheet HDR is the line fewest vendors fill, which is why the empty cells are worth as much attention as the filled ones. A broadcaster asking for an HDR master cannot read this line as a refusal: it is a statement about the pages read, not about the model, and the sheet's method page says as much. What the vendor does print is a bit-depth-free watermark sentence, and nothing more.
4Reading a generated 4K against the upload references
The references give the resolution line two ends to meet. BT.709 sets the parameter values for HDTV and covers the 720p and 1080p cells; the upload guidance the sheet keeps asks for 2160p among its HDR resolutions and prefers UHD widths to DCI ones, which is the shape a 4k generation has to arrive in to count as a delivery.
The same guidance asks for material to be uploaded at the rate it was recorded at, naming 24, 25, 30, 48, 50 and 60 as the ordinary rates, and treats 16:9 as the standard shape a player assumes. A model that prints one frame rate, one default shape and one generation length sits inside those references rather than beside them — and a 4K generated directly is a different line on this sheet from the same figure reached by upscaling elsewhere.
5What the counted material keeps
The family behind the app has a full set of counts in the collection: Veo at 4,456 posts and 705 comment mentions, 211 positive against 78 negative. The two quotations kept beside it are the community's own question about the model — whether anyone is still using it, and whether a cheaper tier with trials would win users back.
Neither quotation is about resolution, and the sheet does not dress them up as one. SceneMixer's row below is a reading of the same shape as the vendor rows above: its frame shape is chosen for the project and its resolution follows the tier, both printed and both dated. Tables here carry the vendors' words, and the words are the only thing being compared — not the pictures made with them.
6What each vendor prints on its own pages
| Vendor | What it is built around | Characters it lists | Access it prints | Pages 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 | Features vary by subscription tier, platform and region; 18+ | 2026-10-13 |
| SceneMixer | “Video is 16:9 landscape by default, with 9:16 vertical available; you set it once per project. Segments are typically 4 to 15 seconds, and some model tiers go to 30.” | Not carried on the pages read | Not carried on the pages read | 2026-10-13 |
Inclusion rule. Rows are the vendors this page is about, each read on its own public pages, plus the production app whose spec lines this sheet keeps. A field a vendor'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 vendor name.
| Asked of each reading | Google Veo | Runway | SceneMixer |
|---|---|---|---|
| Highest resolution | 720p, 1080p or 4k generated directly | 4K by upscaling on paid plans | Set by the tier; the tier table lists 480P as the default, then 720P and 1080P |
| Frame rate | 24fps output | 24, 25, 30, 48, 50, 60 or 120 fps, converted after generation | No figure on the readings printed |
| Frame shape | Landscape 16:9 by default, or portrait 9:16 | No figure on the readings printed | 16:9 landscape by default, or 9:16 portrait, chosen once per project |
| Longest single output | 8 seconds per generation, with 4 and 6 also offered | No figure on the readings printed | Segments of 15 or 30 seconds, chosen per episode |
Inclusion rule. Answers read from each vendor's own pages as this sheet recorded them — the vendor pages on 2026-10-13, the sheet's readings on 2026-09-25. A line the pages do not print is written here as no figure, which describes the reading rather than the product. Order. As the lines are listed above.
7What the collection counted up
The counts below are the collection's record for the model family this page reads. They describe talk about the model, not figures on a page.
| Family | Posts | Comment mentions | Positive | Negative |
|---|---|---|---|---|
| Veo | 4456 | 705 | 211 | 78 |
Inclusion rule. Families the collection counted that bear 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 another vendor's pages answer better
- The delivery will be watched online — A default 16:9 with a portrait alternative matches the shape the upload guidance assumes and the shape a player adapts to.
- 4K has to come from the model — 720p, 1080p and 4k are generated directly on the models that offer them, so the resolution line is not a finishing step bolted on afterwards.
- The mark has to be checkable — A SynthID watermark that the page says can be verified is printed as the marks line, which suits a platform that reads provenance after upload.
The words behind this page are "veo 3 flow"; the counts below belong to the model family the page reads, not to the app it is reached through. Beside it: a 15-second ceiling and three empty lines and a 4K reached in post.