LLMSwaps

Which model each app runs today, and when it last changed

A current generation, and the earlier ones unaddressed

This page names a current generation and a separate real-time line, which is a product distinction rather than a lifecycle one. Whether the two earlier generations are still offered is not addressed. Neither of the named lines is presented as the route off the other. As of 2026-09-22.

What the page settles about the generations it no longer names. Recorded 2026-09-22.
What the page is askedWhat Vidu publishesWhat that leaves open
Is a successor namedNothing names oneTwo lines are named, neither as a destination
Are earlier generations addressedNot addressed on the page readNumbered versions imply that they existed
What separates the two named linesOne is presented as a real-time modelA capability split, not a version sequence
What a reader can rely onOnly that both named lines exist todayWith no statement about either continuing

Inclusion rule. Read from the public home page. A version still reachable in the product but not named on a public page does not fill a cell. Order. The absence first, then what the two named lines are.

1Two lines that are not two generations

Naming a current model and a real-time model looks at a glance like an older and a newer version sitting together. It is not: the split is about how fast a result arrives, so neither line is a fallback for the other.

That distinction decides whether this entry has a cushion. A capability split gives a production two tools; a version split gives it somewhere to stand when one moves. This page publishes the first.

A capability split is not a version cushionNaming a current model and a real-time model looks like an older and a newer version sitting together. The split is about how fast a result arrives, so neither line is a fallback for the other when one of them moves.A version splitA capability splitWhat differsHow new the weights areHow fast a result arrivesIf one movesStay on the otherLose that capabilityGives youSomewhere to standTwo toolsPublished hereNothing about earlier generationsA current line and a real-time lineWhy two named lines are not two generations
Fig. 1 The difference decides whether this entry has somewhere to stand, and on this page it does not.

2Numbering invites a question the page leaves open

A generation labelled with a number tells every reader that lower numbers existed. Nothing here says whether they are still purchasable, which is the one thing a production already working on one of them needs.

The register records the silence rather than resolving it. Assuming the older lines are gone would be as unfounded as assuming they remain, and both guesses lead to a different plan.

3Where this leaves a series already in flight

A production mid-season on an unnamed earlier generation cannot tell from any public page whether it will be able to finish. The absence of a date is not reassurance, and the presence of a newer line is not a deadline.

The defensible response is the one this register keeps recommending in place of prediction: record which model made which delivered file, and archive the files themselves. Both are cheap now and impossible to reconstruct later.

  • Whether Q1 and Q2 are still offered
    No date announced (as of 2026-09-12)not statedVidu, home page / recorded 2026-09-22
  • Models carried
    Vidu Q3, with Vidu S presented as a real-time modelcurrent generation onlyVidu, home page / recorded 2026-09-22

4Sources

Read from the home page on vidu.com, 2026-09-22. The whole entry is on Vidu, and the column it sits in is on Named replacement. Same column, other entries: Hailuo AI, invideo AI.