Veo and Flow on joining finished segments
Veo and Flow rate three for assembly, a value shared with one other tool in the emptiest part of this column. Three sits above the six tools publishing nothing about joining and below the tools that document it as a step of its own. As of 2026-09-12.
| Point | As the rubric has it, or as the table records it |
|---|---|
| The question this column asks | Does the tool join finished segments into one deliverable? |
| What this tool rates | 3 of 5 |
| Tools holding the same value | Two of the sixteen rated here |
| What a five looks like | Joining is a documented step with its own published price |
| What sits at the bottom of the scale | Nothing published about joining segments |
| Tools left unrated on this column | None of the sixteen |
Inclusion rule. The rubric's own wording for this criterion, with this tool's value beside it. Nothing here is taken from a demo, a benchmark or a review. Order. The question first, then the value, then the rule it was given under.
1The whole column, with this row marked
| Tool | Assembly |
|---|---|
| CapCut | 5 of 5 |
| Dreamina | 2 of 5 |
| Hailuo (MiniMax) | 1 of 5 |
| invideo AI | 5 of 5 |
| Kling AI | 1 of 5 |
| LTX Studio | 4 of 5 |
| Luma Dream Machine | 1 of 5 |
| Morph Studio | 3 of 5 |
| Pika | 1 of 5 |
| PixVerse | 2 of 5 |
| Runway | 2 of 5 |
| SceneMixer | 5 of 5 |
| Sora (OpenAI) | 2 of 5 |
| Veo / Flow (Google) | 3 of 5 |
| Vidu | 1 of 5 |
| Wan (Tongyi Wanxiang) | 1 of 5 |
Inclusion rule. Tools rated on this rubric: a public English product page addressing at least four of the seven criteria. An unrated cell means nothing usable is published on that point. Order. Alphabetical by tool name.
2Three means output handling without a documented join
The value covers tools that clearly return usable material in a workable shape without describing the join as a step. That is more than a bare generator offers and less than a production needs to schedule against, and it is the narrowest band in a bimodal column.
The practical consequence is that the join stays a person's job with an unknown boundary. Whether a fifteen-minute deliverable is assembled here or in an editor is not settled by anything published.
3The contrast with the two fives on the same row
Picture and sound both reach five on this row while script handling sits at the floor and assembly at three. The strength is concentrated in the generation step and thins out in both directions from there.
For serial work that means the surrounding pipeline has to be supplied from elsewhere, and the cost of supplying it does not appear on any rate card. It is the most consistent hidden cost in this whole table.
4A three here is not a step towards a five
Because the column is bimodal, the three is not a product on its way to documenting assembly. It is a product that has decided the timeline is somebody else's concern and publishes enough to make handing over practical.
Reading it as an unfinished five would be the wrong inference. The tools at five in this column are built around holding an episode; this one is built around generating a shot, and the value records that rather than a gap.
Ratings describe what each vendor publishes on its own pages, read 2026-09-12, and are given under the rule on how scoring works. This column across every tool is on assembly; this tool across all seven is on Veo / Flow (Google). Nearby cells: Morph Studio, assembly, SceneMixer, cost transparency. All of them: single ratings.