GLM-5.3-Flash is the first natively multimodal model in Z.ai's GLM-5 series. With 320B total parameters and 18B active per token, it outperforms GLM-5.2 across benchmarks and real-world workloads at roughly one-tenth the price, approaching Claude Opus 4.8 on coding and agentic benchmarks.
It starts from a newly trained base model whose architecture and training recipe were redesigned around capability and efficiency. For the first time in the GLM series it uses a hybrid attention stack combining sparse and linear attention, sharply reducing long-context serving cost while preserving precise long-context behaviour, and adopts Manifold-Constrained Hyper-Connections (mHC) to improve scaling efficiency. It was pre-trained on a 30T-token multimodal corpus.
The model understands text and images, and supports reasoning, function/tool calling, and a multi-token-prediction (MTP) draft layer for speculative decoding.
This model is ready for commercial use.
This model is not owned or developed by NVIDIA. This model has been developed and built to a third-party's requirements for this application and use case; see link to Non-NVIDIA GLM-5.3-Flash Model Card
GOVERNING TERMS: Use of this trial service is governed by the NVIDIA API Trial Terms of Service. ADDITIONAL INFORMATION: Use of the model is governed by the MIT License.
Global
Use Case: Multimodal assistants and agents: visual question answering and multi-image reasoning, document and screenshot understanding, coding and tool-using agents, and long-context document intelligence. The low active-parameter count makes it suited to high-throughput, cost-sensitive serving.
Huggingface: 08/25/2026 via link
References:
Architecture Type: Transformer (sparse Mixture-of-Experts, hybrid sparse + linear attention)
Network Architecture: GLM-5.3-Flash (Glm5NextForConditionalGeneration) — 45 decoder layers
in a hybrid attention stack: 34 KDA linear-attention layers interleaved with 11 DeepSeek sparse
attention layers (every fourth layer), plus Manifold-Constrained Hyper-Connections (mHC), 288
routed experts per MoE layer with top-8 routing, a vision encoder for native image input, and 1 MTP
layer.
Number of Model Parameters: 320B total, 18B activated per token
Input Type(s): Text, Image
Input Format(s): String; Image (png, jpg, jpeg, webp)
Input Parameters: Text: One-Dimensional (1D); Image: Two-Dimensional (2D)
Other Properties Related to Input: Context length up to 1,048,576 tokens. Up to 8 images per
request on this endpoint. Thinking budget is controlled by reasoning_effort, which accepts low,
high, or max and defaults to max. In the chat template clear_thinking defaults to false;
chat scenarios should pass clear_thinking=true explicitly.
Output Type(s): Text
Output Format: String
Output Parameters: One-Dimensional (1D)
Other Properties Related to Output: Reasoning content is returned separately from the answer.
Tool calls are emitted in OpenAI-compatible form.
Runtime Engines:
Supported Hardware:
Preferred Operating Systems: Linux
The integration of foundation and fine-tuned models into AI systems requires additional testing using use-case-specific data to ensure safe and effective deployment. Following the V-model methodology, iterative testing and validation at both unit and system levels are essential to mitigate risks, meet technical and functional requirements, and ensure compliance with safety and ethical standards before deployment.
GLM-5.3-Flash
Acceleration Engine: vLLM on NVIDIA Dynamo
Test Hardware: NVIDIA Hopper (H100)
This endpoint serves the native FP8 checkpoint tensor-parallel across 8 H100 GPUs, with MTP speculative decoding enabled.
GLM-5.3-Flash may produce inaccurate, biased, or objectionable responses, and may err in multi-step reasoning, particularly in scenarios not well represented in its training data. Image understanding quality varies with resolution and image quality. Deployers should perform use-case-specific safety evaluation and add appropriate guardrails.
NVIDIA believes Trustworthy AI is a shared responsibility and we have established policies and practices to enable development for a wide array of AI applications. Developers should work with their internal model team to ensure this model meets requirements for the relevant industry and use case and addresses unforeseen product misuse.