Alibaba Cloud ships Wan3.0: video generation stretches to 30 seconds, but the strategy closes up

Alibaba Cloud made the `wan3.0-video` model available on 24 August 2026, extending the maximum length of a clip generated in a single request to 30 seconds at 30 frames per second — twice the 15-second ceiling of its predecessor Wan2.7 — with 1080P as the default resolution. The architecture accepts up to 10 input images, a maximum of 5 video clips and 5 audio clips (no more than 15 seconds in total for each type), plus a single office document of up to 50 pages or one public web address. Audio is generated by default and can be switched off with a parameter. Processing times for the asynchronous API, served from endpoints in the Singapore and Beijing regions, are given as one to five minutes per clip.

The real break concerns how the model is distributed. Wan 2.2 was published under an Apache 2.0 licence in July 2025, but a survey of the official repositories (27 on Hugging Face, 6 on GitHub) carried out on 20 August 2026 by Atlas Cloud found no weights beyond version 2.2; as of 25 August 2026, WinBuzzer reports none either. The company keeps the open source licence for ancillary control models, but reserves its flagship for the paid hosted service: list prices range from $0.05 per second for 480P to $0.20 for 1080P, which puts a 30-second high-definition generation at $6.00.

Commercialising the model fits a very specific financial picture. The launch came a day after a $10.2 billion share placement closed at an 8.4% discount, an operation after which the stock fell 8.1% to HK$113. The money is meant to fund compute infrastructure in a quarter that saw net profit drop 75% to 10.44 billion yuan and capital expenditure rise 75%, to 67.68 billion yuan. On the technical side, with no independent benchmarks run against public parameters, the claims about visual quality and audio synchronisation remain the company's own; nor have we been able to verify what data-handling and data-residency guarantees apply to the corporate documents uploaded in the various regions.

When server spending grows as fast as profits shrink, even the flagship projects of the open source community fall into line with cash needs. It remains to be seen how many enterprise customers will agree to send their own documents to a remote API for as long as it is unclear what handling and residency guarantees hold region by region.

— Olya