Which models PixVerse carries
PixVerse (pixverse.ai) names its own V6 line and four licensed entries on the front page, each with a one-line description of what it is for, and no reference to the V5 generation that preceded it. As of 2026-09-12.
| Model | Whose model | Announced end |
|---|---|---|
| PixVerse V6 | In house | No date announced |
| MiniMax H3 | Another vendor | No date announced |
| Flux 3 | Another vendor | No date announced |
| Seedance 2.5, Seedance 2 | Another vendor | 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.
2A front page that sorts models by job rather than by maker
Each name here arrives with a purpose attached: one line for audio-bearing video, one for fidelity, one for speed, one for stills. That is a more useful presentation than a bare list, and it has a lifecycle consequence the page does not mention. When models are sold by job, a withdrawal can be absorbed by moving the job to another name, and the page still reads sensibly afterwards.
So the version number is the only durable thing on the row. A description of a slot survives a swap; a version string does not, which is why this register copies the strings and largely ignores the descriptions.
3The missing predecessor is the interesting cell
A house line numbered six implies five earlier ones, and none of them appear. Whether they are still selectable inside the product, frozen for existing work, or removed, is not published on any page this register reads. The register records that as unstated rather than as removed, because the two are different and only one of them is a finding.
The pattern repeats one entry over: Hailuo AI names a current generation and no predecessor either, and both companies' models are resold by the entries with longer plan tables. A production that wants an older line kept available has nothing published to point at in either case.
4Read column by column
This register reads PixVerse along named replacement and ending early. One page each.
- Named replacement — promotes one house version and says nothing at all about the versions before it
- Ending early — a promoted version with no predecessor named, so a line can vanish with nothing to compare
5Sources
Menu taken from the home page on pixverse.ai, 2026-09-22. Any end date beside a model comes from whoever makes it, and is listed on the calendar.
- Whether V5 and earlier remain selectableNo date announced (as of 2026-09-12)not stated