Guide / Comparison / editorial
Wan 2.0 vs Wan 2.1: compare evidence before outputs.
Wan 2.0 vs Wan 2.1 begins with an evidence asymmetry: Wan 2.1 has an official repository, release history, code, checkpoints, and named task families, while the current catalog checked here does not provide the same first-party specification for a Wan 2.0 listing.
Compare the ambiguous Wan 2.0 label with the officially documented Wan 2.1 release using identity, task families, repository evidence, access path, and matched production tests.
Compare identity and evidence
For each side, record the provider, exact identifier, official page, repository, release date, license, interface, and region. Missing evidence is a decision risk, not a feature difference.
Use one matched creative brief
If both paths can be verified and accessed lawfully, run the same text-led and image-led jobs with the same inputs, frame, attempt budget, and acceptance rubric.
Separate capability from operating fit
Document output observations, infrastructure, access, integration effort, moderation, rights process, editorial repair, support, and delivery compatibility. Do not turn repository claims into measured production results.