Alibaba opens preview of Qwen4-Max with one-million-token context

- Reading
- 3 min
- Tables
- 1
Qwen4-Max, the flagship of the new generation of the Qwen family, entered preview this Wednesday with support for image, video, and a context window of up to one million tokens.
What Alibaba launched
Alibaba opened the preview of Qwen4-Max this Wednesday (the 11th), the flagship model of the new generation of the Qwen family. According to TechNode, the model accepts image and video inputs, in addition to processing up to one million tokens of context in a single window.
Access to the preview happens through Alibaba's Token Plan subscription. The model is also already in early use within the Qwen app, Qoder, QwenWork, and QwenStudio, according to the report. There are, so far, no public details about pricing outside China or about when the model will move from preview to general availability.
Why one million tokens matters for developers
Context is the amount of space the model can see at once, before it needs to summarize, cut, or fetch pieces of text externally using techniques like RAG. The larger this window, the less extra engineering a developer needs to do for the model to understand an entire project instead of a single isolated file.
In practice, a context of one million tokens opens space for:
- Pasting an entire repository (or a good part of it) into a single query, without splitting it into pieces and losing cross-references between files.
- Analyzing extensive production logs, complete stack traces, or long commit histories in a single pass.
- Processing voluminous technical documentation (specs, RFCs, API manuals) without manual preprocessing.
- Reviewing large pull requests with the entire diff and surrounding code in the same window, instead of analyzing the diff in isolation.
In short: tasks that today require a context retrieval pipeline (indexing the code, searching for the relevant snippet, assembling the prompt) can now, in theory, fit into a single call to the model.
Qwen4-Max in the landscape of long-context models
A context of one million tokens is not exclusive to Qwen4-Max: other models on the market already offer windows of this size. What changes now is that this feature has arrived in Alibaba's flagship model, with built-in multimodal support (image and video).
| Feature | Qwen4-Max (preview) |
|---|---|
| Maximum context | 1 million tokens |
| Accepted inputs | Text, image, and video |
| Access | Token Plan (subscription) |
| Also available in | Qwen app, Qoder, QwenWork, QwenStudio |
For developers in Brazil who already use or are considering alternatives to the OpenAI ecosystem, this is another point of competitive pressure: teams that today build RAG pipelines just to work around short context windows now have more model options capable of natively handling enormous inputs.
What remains open
The announcement, for now, describes features and access channels, not performance figures. The source does not include benchmarks on response quality as the context approaches the one-million-token limit, nor information about latency or cost per token in this extended configuration.
It's also unclear whether Qwen4-Max will have, in the future, any open-weight variant, or whether it will remain available only via closed API. While the preview runs only through the Token Plan and within Alibaba's own apps, anyone wanting to test the model in Brazil depends on international access to these platforms, something that has not yet been detailed for outside China.
For those following the race for ever-larger context windows, Qwen4-Max confirms a trend: long context has stopped being a rare differentiator and is becoming the expected baseline for top-tier models, including outside the Google-OpenAI-Anthropic axis.
Translated from the Brazilian Portuguese original · Read the original
Angular gets a Rust compiler that promises cold builds up to 3x faster
The Angular team rewrote part of the compilation pipeline in Rust to survive TypeScript 7's rewrite in Go. Independent betas already show builds 2x to 3x faster and lower memory use, but the feature only reaches production with Angular 22.





