Running Wan 3.0 locally, from the figures vendors publish

Nothing published covers Wan 3.0, so a local install of that exact version has no weights to start from. For the versions that are published, the repository states what local means: the 5B model on a consumer card such as a 4090, a 5-second 720P clip in under nine minutes, and at least 80GB of VRAM for other commands. As of 2026-10-13.

1What this register already holds

The hardware figures this register holds, each as its own repository wrote it: two from the Wan family, and six from families in the same section whose notes show how far apart two figures for one model can sit.

• 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
• Published models
  A 13B model, with distilled and fp8 variants published for lower VRAM and faster inferenceseveral variantsLightricks, LTX-Video repository / recorded 2026-09-12
• Hardware
  From 4GB in FP16 for the 2B model, from 5GB in BF16 for the 5B, and from 10GB for CogVideoX1.5-5Bthe lowest figures the repository statesTHUDM, CogVideo repository / recorded 2026-09-12
• Hardware
  9.3G BF16 with cpu_offload, against 27.5G if CPU offload is not enabledsingle GPU memory usage on the same runrhymes-ai/Allegro on Hugging Face / recorded 2026-09-22
• Hardware
  Approximately 60GB VRAM on a single GPU, with at least one H100 recommendedthe vendor's own figureGenmo, Mochi repository / recorded 2026-09-12
• Hardware
  Peak GPU memory of 60GB at 720px1280px and 129 frames, and 45GB at 544px960pxthe vendor's own figuresTencent-Hunyuan, HunyuanVideo repository / recorded 2026-09-12
• Hardware
  78.55 GB peak GPU memory at 768px768px204f, 77.64 GB at 544px992px204f and 72.48 GB at 544px992px136fstated per configuration at batch size onestepfun-ai, Step-Video-T2V repository / recorded 2026-09-22

2Local starts with a file, and 3.0 does not have one

The word local assumes something to install. In this register the Wan family answers that assumption twice: 2.1 and 2.2 are published by the vendor's own organisations under Apache 2.0, and 3.0 is recorded as having no published weights at all. A reader who plans a local setup around the 3.0 number is planning around a version that exists here only as a service on someone else's hardware.

The register does not speculate about why, and neither does this page. What it does is keep the version beside the file, so the question 'can I run it' is answered by a row rather than by a reputation.

3What a local run asks of the machine

For the versions that are published, the repository writes two figures that belong to two configurations. The smallest model — a 5B text-to-video and image-to-video release at 720P and 24fps — is stated to run on consumer-grade cards such as a 4090, producing a 5-second 720P clip in under nine minutes on one card. Other commands in the same repository state a requirement of at least 80GB of VRAM.

That spread is the reason this register quotes memory figures with the configuration they were stated for, and refuses to derive one. A buyer who reads only the second number shops for a datacentre card; one who reads only the first is surprised by the larger models. Both numbers are true of the same repository on the same day.

4How far a card can be stretched, in six other repositories

The rest of this section shows what the hardware column looks like when vendors write it well. CogVideoX publishes a ladder from 4GB in FP16 for its 2B model to 10GB for the 1.5-5B release. Allegro states 9.3G with CPU offload against 27.5G without it — one model, one run, two figures and the setting that separates them. HunyuanVideo states 60GB of peak memory at its larger setting and 45GB at a smaller one, measured on a single 80G card.

Mochi states approximately 60GB and recommends at least one H100; Step-Video gives three peak figures between 72GB and 79GB for three configurations. None of those numbers can be guessed from a parameter count, which is why the register treats a stated figure and a derived one as different kinds of entry.

5Where a local run stops and a service begins

There is a point on every one of those ladders where a card is no longer the cheap answer. The hosted services this register follows sell seconds on hardware the buyer never sees — the pipeline sells Wan 3.0 at published per-second rates, and LTX Studio sells LTX-2.5 seconds — and both name the version they serve, which lets a reader place them on the same axis as the files.

This page takes no side. It records that a local run trades a rate for a machine, that the machine is sized by a figure the vendor published, and that the version matters as much as the model: a local setup of a published generation is not a local setup of the generation being sold.

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 each repository carries, quoted with the configuration they were written for. Where a figure is stated for one setting only, that setting travels with it here. Order. As the questions are listed above.

7What the material counted

One pairing and one quoted line from the material behind this column. The pairing is the argument this page sits inside: a model whose files are out against one served only as a product.

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

Seedance 2.5 vs Wan 3.0 vs MiniMax H3 — which one handles emotion and acting best?

r/seedance2pro, collected 2026-10-14

8When the other answer is the better one

• The card on the desk has to be enough — A 5B release stated to run on consumer cards, with a nine-minute figure for one clip, is the cheapest published entry point in this section.
• The output size is the fixed requirement — CogVideoX publishes memory from 4GB for its smallest model, and every figure is attached to the model it was measured on rather than to the family.
• Nothing should be installed at all — Where the version wanted has no file, a service that names the version and sells seconds is the only route the register can point to.

Searched as "wan 3.0 local". Beside it: Wan 3.0 and its weights and Higgsfield alternatives with weights.