Open weights for Wan 3.0: which version actually has them

The register records no published weights for Wan 3.0. Wan 2.1 and 2.2 are published by the vendor's own organisations under Apache 2.0, and 3.0 is the version the hosted service here sells, described on its price list as a model served through an API. Files for a version and seconds of that version are two different products. As of 2026-10-13.

1What this register already holds

Everything this register holds for the family: the two published versions and their licence, the model the repository states a consumer card can run, the figure other commands ask for, and the two hosted services' own lines.

• Version 3.0
  No weights published (as of 2026-09-12)the one the hosted service here sellsWan-AI on Hugging Face / recorded 2026-09-12
• Published versions
  The vendor's own organisations publish weights for 2.1 and 2.2no 3.0 listedWan-AI on Hugging Face / recorded 2026-09-12
• Licence
  Apache 2.0stated in the repositoryWan-Video, Wan2.2 repository / recorded 2026-09-12
• Smallest published model
  A 5B text-to-video and image-to-video model at 720P and 24fpsTI2V-5BWan-Video, Wan2.2 repository / recorded 2026-09-12
• Hardware
  The repository states TI2V-5B runs on consumer-grade graphics cards such as a 4090, generating a 5-second 720P video in under 9 minutes on a single consumer GPUvendor's own figureWan-Video, Wan2.2 repository / recorded 2026-09-12
• Hardware
  Other commands in the same repository state a requirement of at least 80GB of VRAMthe larger modelsWan-Video, Wan2.2 repository / recorded 2026-09-12
• What the hosted service sells
  Wan 3.0 seconds at published per-second rates, from about $0.06 at 480PSceneMixer, price list / recorded 2026-09-12
• What the hosted service sells
  LTX-2.5 API seconds at $0.09 to $0.39LTX Studio, API / recorded 2026-09-12

2The version the search names is not the version with files

The register's entry for Wan 3.0 is short: no weights published. The line beside it records what the vendor's own organisations do publish — 2.1 and 2.2 — which is the whole of the open side of this family. A reader searching for open weights under the 3.0 number is looking at a generation whose files do not exist in the register, and the honest answer is that the number and the release have come apart.

That is not a scandal; it is the ordinary shape of a family in which a later generation is sold as a service first. The same pattern sits in the neighbouring family: LTX-Video is published under Apache 2.0 while the version LTX Studio bills is LTX-2.5, a different release. Two families, the same trap, one row apart in the register's own table.

3What the published versions do carry

Wan 2.1 and 2.2 are Apache 2.0. The repository's smallest published model is a 5B text-to-video and image-to-video model at 720P and 24fps, and it is the one the same repository states runs on consumer-grade cards such as a 4090, generating a 5-second 720P clip in under nine minutes on a single card. Other commands in that repository state a requirement of at least 80GB of VRAM.

Two figures, one repository, and the difference between them is the configuration rather than the family. This register keeps both and attaches each to the model it was written for; collapsing them into one 'Wan needs 80GB' is the kind of summary that sends a reader shopping for the wrong card.

4What the service selling 3.0 actually states

The version does have a public description, just not a file. The pipeline this register follows sells Wan 3.0 seconds at published per-second rates from about $0.06 at 480P, and names the family on the same price list. Its own documentation describes Wan 3.0 as a model reached through an asynchronous submit-then-poll API — a service shape, not a download.

So the two halves of this page answer two different searches. A reader who wants to run the model and own the output has the 2.x files; a reader who wants the newest generation has a rate per second and a queue. The register refuses to present either as the other, because the price of a second says nothing about the cost of a card.

5Where a platform's own page fits

The services in this column are read the same way as the repositories: what does the page state, and what does it leave open. Krea lists a commercial licence on its plans and trains LoRAs from 50 images, which answers the commercial-use question for its own units and says nothing about any model's weights. Those are two separate statements about two separate things, and a reader needs both.

The table below sets the published version against the sold one, question by question. It is the shortest summary of this family the register can honestly produce, and its empty cells are as much a part of it as the filled ones.

6What each one's own pages state

Inclusion rule. Rows are the services this page reads plus one pipeline this register follows. A cell carries the service's own wording for the question on this page; a page that does not address the question is written that way rather than read as a denial. Order. Alphabetical by service name.

Inclusion rule. Cells are the statements the register holds for each version, each attached to the page it was read from. A question a version does not answer is written as unanswered rather than inferred from the other version. Order. As the questions are listed above.

7What the material counted

Two lines from the material collected for this column: the counts for the family whose release this page is about, and the pairing the threads keep coming back to.

Inclusion rule. Names the collection counted and that this page is about. The two tallies come from the same posts, and a post arguing with itself can land in both. Order. Descending by posts.

Inclusion rule. Pairs carried in the collection that name a family on this page. Order. Descending by the count.

8When the other answer is the better one

• The newest generation is the requirement — The service sells the 3.0 seconds it names on its price list, which is the only route to that version in this register.
• A file under a standard licence is the requirement — Wan 2.1 and 2.2 are Apache 2.0 as the repository writes it, and the vendor's own organisations are where the files sit.
• Nothing has to be bought before it works — A rate per second is payable as it is spent; a file is a card, a driver setup and a night of benchmarking before the first clip exists.

Searched as "wan 3.0 open weights". Beside it: Higgsfield alternatives with weights and Wan 3.0 run locally.