Which models Vidu carries
Vidu (vidu.com) names a current generation, Q3, and a separate real-time model, and prices the first in credits per five seconds. Earlier Q generations are not mentioned on the page. As of 2026-09-12.
| Model | Whose model | Announced end |
|---|---|---|
| Vidu Q3 | In house, priced per five-second clip | No date announced |
| Vidu S | In house, presented as real-time | No date announced |
Inclusion rule. Models the app names on its own public pages. A model the app does not name is not listed, and an end date is recorded only when the vendor that makes the model has announced one. Order. As the app orders them on its own page.
1How many models each application names
| Entry | Rows it publishes |
|---|---|
| Adobe Firefly | 5 rows |
| Amazon Bedrock | 3 rows |
| fal | 4 rows |
| Gemini API | 5 rows |
| Hailuo AI | 1 row |
| invideo AI | 5 rows |
| Kling AI | 3 rows |
| LTX Studio | 4 rows |
| Luma | 6 rows |
| Microsoft Foundry | 2 rows |
| Pika | 1 row |
| PixVerse | 4 rows |
| Runway | 5 rows |
| SceneMixer | 5 rows |
| Vidu | 2 rows |
| Wan-AI | 5 rows |
Inclusion rule. Entries whose own pages name a model, a version identifier or a lifecycle state. House tier names with no model behind them are not counted. Order. Alphabetical by entry name.
| Entry | Rows with an announced end |
|---|---|
| Adobe Firefly | 1 announced |
| Amazon Bedrock | 3 announced |
| fal | 1 announced |
| Gemini API | 5 announced |
| Hailuo AI | 0 announced |
| invideo AI | 1 announced |
| Kling AI | 0 announced |
| LTX Studio | 0 announced |
| Luma | 1 announced |
| Microsoft Foundry | 2 announced |
| Pika | 0 announced |
| PixVerse | 0 announced |
| Runway | 0 announced |
| SceneMixer | 0 announced |
| Vidu | 0 announced |
| Wan-AI | 0 announced |
Inclusion rule. Counted only where the vendor that makes the model has announced a date in public. A date reported by press coverage alone is not counted. Order. Alphabetical by entry name.
2Two models doing different things is not two generations
It would be easy to read a two-row menu as a current model plus a fallback. It is not: one row is the general generation and the other is an interactive line built for latency rather than for fidelity. They are alternatives for different work, not a migration path, and a production that loses the first cannot continue on the second.
That distinction matters for how this register counts. Two named models here buy a reader less protection than two named generations elsewhere, and a count of models per entry is therefore a weak proxy for resilience. The register publishes the count because it is checkable, and says here why it should not be over-read.
3Pricing per clip length pins the model to the invoice
Quoting a credit price against a five-second clip has the same side effect as a per-second rate: it makes the model a billable unit rather than a background implementation detail. When a vendor charges by the model, a swap has to be reflected somewhere a customer can see, because the price list is the place the swap shows up first.
The opposite arrangement is visible at fal, which prices each model separately with no plan at all, and at the plan-based entries where one subscription covers everything and no line item moves when the menu does.
4Read column by column
This register reads Vidu along named replacement and default tier. One page each.
- Named replacement — a current generation and a real-time line on the page, with earlier generations unaddressed
- Default tier — a current generation and a real-time line, with neither marked as the starting one
5Sources
Menu taken from the home page on vidu.com, 2026-09-22. Any end date beside a model comes from whoever makes it, and is listed on the calendar.
- Whether Q1 and Q2 are still offeredNo date announced (as of 2026-09-12)not stated