Wan 3.0 Release Status: Official Listing and EvoLink Access
wan3.0-video service.Wan 3.0 status at a glance
| Question | Verified status | Where to act |
|---|---|---|
| Can developers call Wan 3.0 now? | Yes, through EvoLink production routes since August 18, 2026 | Open the Wan 3.0 model page |
| Which workflows are available? | Text-to-video, image-to-video, and reference-video | Choose the matching route on the model page |
| What output range is exposed? | 480P, 720P, or 1080P; 2–30 seconds | Confirm the live constraints before shipping |
| Is there a direct upstream identity? | EvoLink's three public routes map to wan3.0-video | Keep the EvoLink route ID configurable |
| What is the upstream release state? | Alibaba Cloud listed wan3.0-video for invite testing on August 6; this article does not claim provider-wide GA | Track broader region and account availability separately |
| Are Wan 3.0 weights and a license public? | Not confirmed in the checked official Wan repositories | Do not plan self-hosting yet |
| Is there an independent benchmark? | No benchmark is used to support this release update | Run workload-specific acceptance tests |
What changed since the first report
When this page was first published on August 4, searches for “Wan 3.0” led mostly to rumor pages. The official Wan repositories did not expose a Wan 3.0 model card, weight repository, or callable route that we could verify. Several sites nevertheless published precise-looking claims about 4K output, parameter counts, architecture, and an open-source license.
wan3.0-video on August 6 as an all-in-one video model in invite testing, supporting text-to-video, first/last-frame image-to-video, and reference-video workflows. EvoLink then completed backend integration and made three production routes available on August 18. That is enough to move the model from “watch and wait” to “test through a verified channel.” It is not enough to retroactively validate every pre-release specification. The callable EvoLink contract currently confirms up to 1080P and up to 30 seconds—not the unsourced 4K claims that circulated earlier.What developers can use today
EvoLink separates the main jobs into three IDs while maintaining a shared gateway contract:
| Job | EvoLink route | First production test |
|---|---|---|
| Generate a scene from a prompt | wan3.0-text-to-video | Prompt adherence, motion stability, readable text, and latency |
| Animate a source image | wan3.0-image-to-video | Subject identity, composition drift, camera motion, and edge artifacts |
| Use mixed reference material | wan3.0-reference-video | Reference fidelity, continuity, audio behavior, and unsupported-input handling |
The reference workflow accepts a broader input surface than a conventional image-to-video route, including video, audio, document, and public webpage references where supported by the live contract. Treat that breadth as a testing obligation: validate your exact MIME types, file limits, public URL behavior, and fallback path before you expose the feature to users.
What remains unconfirmed upstream
Four questions are still open and should stay out of procurement or architecture assumptions:
- Provider-wide general availability. Alibaba Cloud's August 6 record says invite testing, and EvoLink's route is live; neither fact proves that every Alibaba region or account tier has the same access state.
- Open weights and license. No Wan 3.0 weight artifact or final open-source license was found in the checked Wan-Video GitHub and Wan-AI Hugging Face records.
- Architecture and parameter count. Numbers published by unofficial Wan 3.0 domains remain unsupported here.
- Independent quality leadership. A production route proves access, not superiority. Quality claims require reproducible comparisons against the workflows your team actually runs.
Production evaluation checklist
Do not judge a video model from a single showcase clip. Build a small acceptance set from your own production prompts and measure:
- completion rate and error taxonomy by route;
- prompt and reference adherence across short and 30-second jobs;
- identity, wardrobe, object, and background continuity;
- 480P, 720P, and 1080P latency under representative load;
- audio presence, sync, intelligibility, and fallback behavior;
- cost per accepted output—not only cost per submitted task;
- callback, polling, cancellation, retry, and result-link expiry behavior;
- graceful fallback to Wan 2.7 or another model in the Wan collection.
Start with a shadow test or limited traffic slice. Record the prompt, input asset hashes, route ID, parameters, task status, latency, and human acceptance decision. This gives you a reproducible comparison if the upstream service changes after launch.
Should teams migrate from Wan 2.7 now?
Test Wan 3.0 now; migrate selectively after it clears your acceptance gates. Existing Wan 2.7 users do not need a blind cutover. Keep the model ID in configuration, retain a fallback, and compare matched prompts on quality, latency, failure rate, and accepted-output cost.
The strongest early candidates are workloads that need longer generations, higher output resolution, or richer reference inputs. Stable Wan 2.7 workflows can remain in place until Wan 3.0 demonstrates a measurable advantage. EvoLink's unified API makes model choice reversible instead of turning a release date into an infrastructure migration.
FAQ
What is Wan 3.0?
wan3.0-video identity.Is Wan 3.0 released?
wan3.0-video for invite testing on August 6, 2026. Wan 3.0 is available through EvoLink's production API as of August 18. These are channel-specific states, not a claim that every upstream region and account tier has reached general availability.When was Wan 3.0 released on EvoLink?
The production routes were confirmed live on August 18, 2026. This article was fully re-verified on August 19.
How can I use Wan 3.0 now?
What are the Wan 3.0 model IDs?
wan3.0-text-to-video, wan3.0-image-to-video, and wan3.0-reference-video. They map to the shared upstream wan3.0-video service. The model page remains the canonical contract if an ID changes.What duration and resolution does Wan 3.0 support?
The current EvoLink contract supports 2–30 seconds at 480P, 720P, or 1080P. Check the model page for route-specific constraints before submitting a job.
Is Wan 3.0 open source?
Not on the evidence checked for this update. We found no official Wan 3.0 weight repository or final open-source license. API availability and open-weight availability are different release states.
Does Wan 3.0 support audio and reference inputs?
The live product contract includes audio and broader reference inputs, but behavior can vary by route and asset type. Verify the exact audio fields, input limits, and failure handling on the model page and in a real request.
Is Wan 3.0 better than Wan 2.7?
It offers a broader exposed range, including up to 30 seconds, but “better” depends on your prompts, reference fidelity needs, latency target, and accepted-output cost. Run a matched evaluation before switching traffic.
Where can I find Wan 3.0 pricing?
Sources and update log
- EvoLink Wan 3.0 model page — live route IDs, pricing, inputs, and parameters
- Alibaba Cloud Model Studio release log — official August 6
wan3.0-videoinvite-testing record - Wan-Video GitHub organization — official code and repository record
- Wan-AI on Hugging Face — official model and weight record
- QwenCloud wan3.0-video listing — upstream service identity reference
wan3.0-video for invite testing in its official model release log.
