LLMSwaps

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

Wan: one family at four different version levels

Four entries carry this family and no two carry the same version: a third-generation line split across three resolutions, a 2.5 line priced per output, an unversioned mention among six makers, and the publisher's own repository listing of downloadable weights. As of 2026-09-22.

What has been announced, entry by entryFilled where the vendor has announced something in that column, hollow where it has not.What has been announced, entry by entryHow it appears thereHow it appearsthereAnnounced end for this lineAnnounced end forthis linefalfal — How it appears there: A 2.5 line priced individually per output unitfal — Announced end for this line: No date announcedinvideo AIinvideo AI — How it appears there: Named as a maker, with no version giveninvideo AI — Announced end for this line: No date announcedSceneMixerSceneMixer — How it appears there: A third-generation line at three resolutions, one of them the defaultSceneMixer — Announced end for this line: No date announcedWan-AIWan-AI — How it appears there: The publisher's own listing of downloadable weightsWan-AI — Announced end for this line: No date announced
Fig. 1 Filled where the vendor has announced something in that column, hollow where it has not.
Every entry here that carries this family, and which version it names. Recorded 2026-09-22.
EntryHow it appears thereAnnounced end for this line
falA 2.5 line priced individually per output unitNo date announced
invideo AINamed as a maker, with no version givenNo date announced
SceneMixerA third-generation line at three resolutions, one of them the defaultNo date announced
Wan-AIThe publisher's own listing of downloadable weightsNo date announced

Inclusion rule. An entry appears when it names this family on a page a reader can reach without an account. The version recorded is the one the entry itself states. Order. Alphabetical by entry name.

1Four carriers, four versions, one name

Every other family in this register appears at roughly the same version level across its carriers. This one does not, which means the family name tells a reader almost nothing about what produced their work.

A production that recorded only the family would be unable to reproduce anything. The spread here is the strongest argument in the register for recording the version alongside every delivered file.

One family name covering four different versionsEvery other family in this register appears at roughly the same version level across its carriers. Here a third-generation line, a 2.5 line, an unversioned mention and a set of downloadable second-generation weights all carry the same family name.Four carriers, four version levelsThird generation, threeresolutionsOne of them is the tier a new project starts on, so mostdelivered work runs here.A 2.5 line, priced peroutputA different version, on a different meter, from a differentseller.Named as a maker onlyNo version given, so nothing can be matched to a delivered file.Downloadable weightsSecond generation, under a permissive licence. Outside theretirement question.The strongest case here for recording a version per file
Fig. 2 A production that recorded only the family name would be unable to reproduce anything.

2One carrier publishes the weights rather than access

The publisher's own listing is not a menu; it is a set of repositories with download commands and a permissive licence. That puts one row of this table outside the retirement question entirely, because a copy already taken cannot be withdrawn.

So the same family is simultaneously the most exposed and the least exposed line here, depending on which row a production is on. The succession reading sets out what the download route trades away in exchange.

3A default tier on one of the four

One entry makes a resolution of this family the tier a new project starts on, so more delivered work in this register runs on this family than on any other. That is a fact about one product's default rather than about the family.

It still concentrates the exposure. The default reading for that entry explains why an unselected tier reaches more finished material than any selected one.

  • Models carried
    Wan 3.0 at 480P, 720P and 1080P, plus MiniMax H3 and H3 Fastnamed per tierSceneMixer, price list / recorded 2026-09-12
  • Default tier
    Wan 3.0 at 480Pwhat a new project getsSceneMixer, price list / recorded 2026-09-12
  • Models carried
    Wan 2.5, Kling 2.5 Turbo Pro, Veo 3 and Ovi, each priced individuallypriced per model rather than per planfal, pricing page / recorded 2026-09-22
  • Models carried
    Google Veo 3.1, Sora 2, Kling AI, Wan AI, Pixverse AI and Hailuo AIaggregatedinvideo AI, model list / recorded 2026-09-12
  • Models published
    Wan2.2-T2V-A14B, Wan2.2-I2V-A14B, Wan2.2-TI2V-5B, Wan2.2-S2V-14B and the Animate variantsweights rather than an endpointWan-AI, repository listing / recorded 2026-09-22
  • Licence stated on the weights
    Apache 2.0Wan-AI, Wan2.2-T2V-A14B model card / recorded 2026-09-22

4Sources

Each row is read from the page that entry publishes itself, 2026-09-22, and any date comes from whoever makes the model. Every announced date is on the calendar. Other models read this way: Sora 2, Single-carrier lines.