Qwen3.7 Max: 1M Context, API & Pricing

Last verified: August 3, 2026. This independent guide is not operated by or affiliated with Alibaba Cloud, QwenCloud, or the Qwen team. Model specifications, availability, retirement notices, and prices should be checked against the linked provider documentation before production use.

Qwen3.7 Max remains an active hosted model with the exact mainline ID qwen3.7-max. It provides a documented context window of up to one million tokens, hybrid thinking, Function Calling, and built-in tools. It was introduced as the flagship of the Qwen3.7 Max series, but it is no longer Qwen’s newest or highest-positioned model: QwenCloud launched qwen3.8-max as its current flagship on August 3, 2026.

The new flagship does not make Qwen3.7 Max retired. The current model directory continues to list qwen3.7-max and its documented snapshots, and the deprecation table checked on August 3 does not assign them a retirement date. In fact, that table still names qwen3.7-max as the formal replacement for several older Qwen3 Max IDs scheduled to retire on October 10, 2026. This is a point-in-time lifecycle check, not a guarantee of permanent availability.

Qwen3.7 Max at a glance

Specification	Verified information
Rolling model ID	`qwen3.7-max`
Fixed snapshots	`qwen3.7-max-2026-05-20` and `qwen3.7-max-2026-06-08`
US-scope model ID	`qwen3.7-max-us`
Portfolio position	Active predecessor to `qwen3.8-max`; no longer the current flagship
Lifecycle	Still listed; no retirement date published for the mainline ID or its two documented snapshots in the policy checked August 3, 2026
Legacy-replacement role	Formal replacement for the affected `qwen3-max` branch scheduled to retire October 10, 2026
Context window	Up to 1,000,000 tokens
Thinking	Hybrid thinking; enabled by default and configurable per request
Rolling alias modalities	Text input and text output
Function Calling	Supported
Built-in tools	Supported where available for the selected API and deployment scope
Structured output	Alibaba Cloud Model Studio documents JSON mode for the Qwen3.7-Max series; QwenCloud’s current overview matrix omits a support mark for `qwen3.7-max`. Verify the exact product and API.
Deployment	Hosted through Alibaba Cloud Model Studio and listed by QwenCloud

What is Qwen3.7 Max designed for?

Qwen3.7 Max remains a high-capability hosted option for multi-step problem solving, software architecture analysis, complex code review, research synthesis, agent planning, and other reasoning-heavy workloads. The August 3 launch of Qwen3.8 Max supersedes its flagship positioning, not its availability. Existing applications may reasonably keep Qwen3.7 Max when regional availability, a validated snapshot, cost, latency, or regression history matters, while evaluating Qwen3.8 Max separately before any migration.

This does not mean that Max is automatically the best economic choice for every request. Routine extraction, classification, short-form writing, and high-volume support workflows may be served more efficiently by Qwen3.7 Plus or Qwen3.6 Flash. Model selection should consider output quality, token volume, latency requirements, modality, and cost together.

Rolling alias and fixed snapshots

The rolling alias qwen3.7-max was mapped to qwen3.7-max-2026-05-20 on the verification date. A rolling alias is convenient because Alibaba can maintain the model behind one identifier. A dated snapshot is more appropriate when an application requires reproducible behavior across evaluations, releases, or compliance reviews.

Use qwen3.7-max when you want the provider-managed rolling version.
Use qwen3.7-max-2026-05-20 when you need the documented text snapshot associated with the alias on the verification date.
Use qwen3.7-max-2026-06-08 only when its documented features, including multimodal API support, match your selected endpoint and deployment scope.
Use qwen3.7-max-us only with the corresponding US deployment scope and endpoint.

The 1M-token context window

Qwen3.7 Max has a published context window of up to one million tokens. A large context can help with long repositories, collections of reports, lengthy conversations, or document sets that cannot be represented well by a short prompt.

The one-million-token figure describes the context budget, not a promise that every request should contain one million input tokens and then produce an equally large answer. Input messages, retained conversation content, tool results, reasoning tokens, and generated output must remain within the applicable service limits.

Large requests also increase processing cost and may benefit from retrieval, chunking, summarization, or context caching. Applications should send relevant evidence rather than filling the available context without a clear purpose.

Thinking and non-thinking modes

Qwen3.7 Max is a hybrid-thinking model. Thinking is enabled by default, but applications can disable it for direct tasks or control reasoning depth through the supported API parameters.

Thinking mode: suited to planning, debugging, multi-stage comparisons, and problems where additional reasoning may improve the answer.
Non-thinking mode: suited to simpler prompts, lower-latency interactions, and structured transformations that do not require extended reasoning.
Chat Completions: uses enable_thinking. Reasoning and final-answer content are returned in separate fields.
Responses API: uses reasoning.effort to control reasoning depth.

Reasoning tokens are billable output tokens. Enabling thinking can therefore increase both response time and cost. Applications should evaluate thinking and non-thinking configurations on representative tasks.

Text and multimodal support

Do not assume that the rolling qwen3.7-max alias accepts images or video. Alibaba documents the rolling alias and May 20 snapshot as text models, while multimodal API support is documented for qwen3.7-max-2026-06-08.

If an application requires image or video understanding, verify that the June 8 snapshot, selected API, region, and message format support the intended input. For a provider-recommended multimodal model with clearly published image and video limits, consider Qwen3.7 Plus.

Built-in image search or image-generation tools are separate platform tools. Their presence does not prove that the rolling Max alias accepts native visual input.

Function Calling and built-in tools

Qwen3.7 Max supports Function Calling. The model can return a structured request for a function, but it does not execute a database query, payment operation, private API, or other custom function by itself.

Your application must validate the proposed tool name and arguments, execute an authorized operation, and return the tool result to the model. Sensitive actions should require explicit application-side permission checks.

Model Studio also documents built-in tools. Availability can differ by API, account plan, model version, and deployment scope. A built-in web-search tool should not be presented as proof that every Qwen3.7 Max request has unrestricted web access.

Structured JSON output

Alibaba Cloud Model Studio’s structured-output guide explicitly documents JSON mode for the Qwen3.7-Max series. However, QwenCloud’s current text-generation overview omits the structured-output checkmark for qwen3.7-max. Because these first-party product documents are not aligned, do not promise universal support across Model Studio, QwenCloud, regions, and API interfaces.

Where the selected service documents JSON mode, set response_format to {"type":"json_object"}, explicitly request JSON, parse the result, and validate it against an application-owned schema. Thinking-mode output may still require validation or repair. Confirm the exact endpoint’s current documentation before enabling this behavior in production.

Qwen3.7 Max pricing

The following table contains Singapore International list prices verified on July 21, 2026. It excludes temporary promotions, taxes, and separate tool charges.

Input tokens per request	Input price	Output price
More than 0 and up to 1M	US$2.50 per 1M tokens	US$7.50 per 1M tokens

Singapore International list prices. Reasoning tokens and final-answer tokens are billed as output.

An eligible International deployment activation may receive a one-million-token free quota valid for 90 days after Model Studio activation. This is a conditional introductory quota, not permanent free access and not a universal allowance across deployment scopes.

See the independent Qwen API pricing guide for model comparisons, but use the provider’s billing page and console for purchasing decisions.

Node.js API example

This example uses the OpenAI-compatible Chat Completions interface. Set DASHSCOPE_BASE_URL to the OpenAI-compatible URL for your Model Studio workspace and region. The API key and endpoint must belong to matching deployment scopes.

import OpenAI from "openai";

const client = new OpenAI({
  apiKey: process.env.DASHSCOPE_API_KEY,
  baseURL: process.env.DASHSCOPE_BASE_URL,
});

const stream = await client.chat.completions.create({
  model: "qwen3.7-max",
  messages: [
    {
      role: "system",
      content:
        "Analyze carefully. State assumptions and give a concise final recommendation.",
    },
    {
      role: "user",
      content:
        "Compare blue-green and rolling database migrations for a critical service.",
    },
  ],
  enable_thinking: true,
  max_completion_tokens: 12000,
  stream: true,
  stream_options: {
    include_usage: true,
  },
});

for await (const chunk of stream) {
  const answer = chunk.choices[0]?.delta?.content;
  if (answer) process.stdout.write(answer);
}

For production evaluations, replace the rolling alias with a dated snapshot. Do not expose private reasoning content to end users, logs, or analytics unless the application has a justified and reviewed requirement to process it.

Limitations and claims to avoid

Do not describe Qwen3.7 Max as Qwen’s newest, current flagship, or strongest model after the August 3, 2026 launch of qwen3.8-max.
Do not describe Qwen3.7 Max as retired or deprecated. No retirement date for this ID was present in the policy checked on August 3, 2026.
Do not describe Qwen3.7 Max as open-source, open-weight, downloadable, or self-hostable.
Do not copy parameter counts, architecture details, hardware requirements, or licenses from unrelated Qwen3 open models.
Do not describe the 1M context window as a one-million-token output limit.
Do not claim that the rolling alias accepts images or video without verifying the selected snapshot and API.
Do not publish temporary discounts as permanent prices.
Do not promise one universal rate limit across every region and snapshot.
Do not imply that Function Calling executes external actions without application-side code.
Do not guarantee perfectly valid JSON in thinking mode.

Qwen3.7 Max FAQ

Is Qwen3.7 Max an open-source model?

No. The reviewed Model Studio materials present this model ID as a hosted commercial service and do not publish model weights or self-hosting instructions for it.

Does Qwen3.7 Max have a 1M context window?

Yes. Alibaba documents a context window of up to one million tokens. The context window covers the request’s total working budget and should not be interpreted as an output allowance.

Does qwen3.7-max accept images and video?

The rolling alias is documented for text input and text output. Alibaba separately documents multimodal API support for qwen3.7-max-2026-06-08. Verify the snapshot, endpoint, and API before sending visual inputs.

Should I use Max or Plus?

Evaluate qwen3.8-max when the current flagship tier is required and the exact ID is available through your product and region. Keep or evaluate qwen3.7-max when you need its documented snapshots, an already-validated integration, or its formal role as the migration target for retiring Qwen3 Max IDs. Choose Qwen3.7 Plus for a lower-priced balance of performance, tools, long context, and clearly documented multimodal support.

Is Qwen3.7 Max still the latest Qwen flagship?

No. QwenCloud launched qwen3.8-max as its current flagship on August 3, 2026. Qwen3.7 Max remains a separately listed model and should retain its own page, evaluations, and lifecycle notes.

Is Qwen3.7 Max retired?

No retirement date was published for qwen3.7-max, qwen3.7-max-2026-05-20, or qwen3.7-max-2026-06-08 in the policy checked on August 3, 2026. The policy still names qwen3.7-max as the replacement for affected older Qwen3 Max IDs. Recheck the policy before deployment because lifecycle notices can change.

Should production applications pin a snapshot?

Pinning a dated snapshot is preferable when repeatable evaluations and controlled releases matter. The rolling alias is more convenient when provider-managed model updates are acceptable.

Official references

Compare the current Qwen3.8 Max guide, review the Qwen Max identity and lifecycle guide, check current costs in the Qwen pricing guide, or use the Qwen API guide for implementation details.

Qwen3.7 Max: 1M-Context Reasoning Model Guide