Z.ai GLM-5.3-Flash

GLM-5.3-Flash — chat with a 320B multimodal model, and a table it does not lead

Hand it a screenshot, a CAD blueprint, a spreadsheet or a long coding task. Start the conversation above, then use the guide below to keep three sets of numbers apart: what the provider ran before release, what its own sixteen-row table actually says, and what this chat box switches on.

Explore the model guide
GLM-5.3-Flash

What is GLM-5.3-Flash?

GLM-5.3-Flash is Z.ai’s 320B-parameter multimodal model, released on 26 August 2026 and the first model in the GLM-5 line to accept video, images, text and files instead of text alone. Its API model code is glm-5.3-flash, and the same official page also covers a glm-5.3-flashx variant that this site does not carry; the documented context window is 1M tokens and the documented maximum output is 128K tokens, with text as the only output modality. Eighteen billion parameters are active. The launch post says the model was tested anonymously as ox-alpha on OpenCode and OpenRouter before release and became the most popular model of the week on those two services, with all of that traffic served on Chinese AI chips. Three architectural claims travel with it: a hybrid of sparse and linear attention, which the provider describes as a first for an open-source frontier model; IndexPool, which compresses four indexer key vectors into one through weighted pooling; and Manifold-Constrained Hyper-Connections, credited in the post with better scaling efficiency. Against GLM-5.3 the provider reports 3.0× less attention compute and a 4.4× smaller KV cache, and its own comparison puts this model’s KV cache slightly above Kimi-K3 and DeepSeek-V4-Flash. Two size comparisons sit beside that one: this generation is 320B against the GLM-4.5 line’s 355B, while activated parameters fall from 32B to 18B and layers from 92 to 45. Thinking cannot be turned off. The migration guide states that `thinking.type` accepts only `enabled` and that `reasoning_effort` chooses between low, high and max, defaulting to max; it also warns callers who currently send `disabled` to change that value before switching the model id, or the request fails. The same release-notes feed dates GLM-5.3 to 18 August 2026 and GLM-5.2 to 16 June 2026, which is what makes this model the newest of the three rather than the middle one.

What GLM-5.3-Flash is worth using for

Read the release as a market test, not only a launch

One paragraph in the launch post describes something providers usually keep quiet, and it is the most useful thing on the page for judging the model. Before release, Z.ai says, GLM-5.3-Flash was served anonymously as ox-alpha on OpenCode and OpenRouter so that user feedback could be collected without the model’s name attached. The post states that it quickly became the most popular model of the week on those two services, and adds a second, less expected detail: all of that traffic was served on Chinese AI chips. That combination matters for how the rest of the page is read. The popularity claim is a provider’s own summary of its own anonymous window, not an independent measurement, and the same post gives no traffic figures, no date range and no comparison set behind it, so this page repeats it with its source and does not turn it into a ranking. What the paragraph does establish is that the serving stack described further down had been exercised under real, if unnamed, load before the weights were published. Third parties later wrote up the reveal under the handle, and several of the comparison articles ranking for this model’s name still use ox-alpha in their titles — which is why the alias is worth knowing even though it appears nowhere in the model code. If you are reading reviews of this model, a review that talks about ox-alpha and one that talks about GLM-5.3-Flash are discussing the same weights.

Suggested prompt
A model provider says it released a model anonymously under a codename before launch to collect feedback, and that it became the most popular model on two platforms. List the specific pieces of evidence that would let me treat that as verified rather than as marketing, and tell me which of them the provider would have to publish.

Count the places its own sixteen-row table does not lead

The table in the launch post prints six model columns and sixteen scored rows, and it is the single official page that carries both this model and GLM-5.2, which is why the reproduction further down is drawn entirely from it. Read only the first two columns and the story is a clean generational win: all eight rows where GLM-5.2 has a value move in this model’s favour, the largest gaps being 48.8 against 26.2 on AutomationBench v1.0.6 and 63.4 against 46.2 on DeepSWE v1.1. Read all six columns and a second reading appears. Across the sixteen rows this model finishes first on six, second on five, third on three and fourth on two, and never fifth — so the column has no floor but also no clean sweep. The rows where other models lead are worth naming, because a headline cannot be written from either end of that distribution. On Terminal Bench 2.1 it scores 84.3, behind GPT-5.6 Terra at 87.4, Gemini 3.7 Flash at 85.8 and Claude Opus 4.8 at 85.0. On Agents’ Last Exam it scores 26.3 against 28.0, 27.3 and 27.0. On BabyVision it scores 53.4 where Gemini 3.7 Flash scores 70.9 and GPT-5.6 Terra scores 61.6. On CharXiv Reasoning with tools it scores 89.4 against Claude Opus 4.8’s 89.9, on MVbench 77.8 against 82.2, and on MMVU 80.5 against 82.3. The eight Vision rows carry one more thing worth noticing: GLM-5.2’s cell is a dash in every one of them, because that model takes text only, so those rows compare this model with rivals rather than with its predecessor.

Suggested prompt
Here is an official benchmark table with several model columns and some empty cells. Tell me, for the column I name, which rows it leads, which rows it loses and to whom, whether the empty cells are missing results or a genuine capability difference, and what single sentence a fair summary could use.

Treat vision as a step in the coding loop, not an attachment

The claim the official pages make most often about this model is not that it accepts images, but that seeing is part of how it works. The model page says visual capabilities are built into the coding loop so that the model observes interfaces, rendered results and interaction feedback and then improves its own work, coordinating across code, browsers and graphical interfaces. The launch post gives that a mechanism: a data-synthesis pipeline focused on self-visual judgement and test-time improvement, producing trajectories in which the model interacts with an environment, inspects what it produced and revises it, plus reinforcement learning with environment feedback for frontend work and agent-based verification grounded in real user flows for interface judgement. The concrete examples the provider lists are unusually specific and are the reason this page does not describe the feature in the abstract. One is an autonomous run of about sixteen hours that built a roughly 400-square-metre professional chef’s residence and test kitchen in Blender, starting with no external assets — a task where geometry, materials, lighting and spatial relations all have to stay consistent from several viewing angles. Another is a workflow in which the model converts screenshots, multiple page images, a website URL or a screen recording into a runnable Next.js project and then re-screenshots each page to compare against the reference. Two more extend the same loop past code: Office deliverables where the model renders its own PPTX, PDF, DOCX or XLSX output and looks for overflow, misalignment and overlapping elements, and a CAD workflow that reads a part blueprint into parametric build123d code and renders it from several angles for comparison. The provider also frames the gap that this closes — that for frontend, game and 3D work the real output is not the code but the interface, interaction or world a person ends up using, and many failures only surface when the result is rendered, touched or played. Each of those examples is a provider description of a capability, not a measurement of this chat box, and the prompts the provider publishes for them are reproduced in the sources below.

Suggested prompt
I want to check whether a model can genuinely improve its own output using what it sees, rather than just describing an image. Give me a small task I can run in an afternoon, describe what I should change to make it impossible to pass without looking at the rendered result, and tell me what a fake pass would look like.

Keep the efficiency numbers attached to what they measure

This model’s headline is cost rather than raw capability, and the provider attaches precise definitions to the claims, which is what makes them usable. The architecture is a hybrid of linear attention, which captures local dependencies through state modelling, and sparse attention, which retrieves global context through a lightweight indexer. The number that makes the 1M-token window affordable is IndexPool: at a million tokens the indexer’s own latency and memory become the bottleneck, and IndexPool compresses four indexer key vectors into one by weighted pooling. The comparison the provider publishes alongside it is deliberately normalised — attention compute per head per layer and average KV cache size per layer in BF16 — because the models being compared are different sizes. Against GLM-5.3 that yields 3.0× less attention compute and a 4.4× smaller KV cache, and the post states the one place it does not win: its KV cache is still slightly larger than Kimi-K3’s and DeepSeek-V4-Flash’s, which it calls a target for later work. The base-model table carries the same discipline in the other direction. It compares this model’s base against GLM-4.5-Base, GLM-5-Base and DeepSeek-V4-Flash-Base across five rows, and the honest reading is mixed: it beats GLM-4.5-Base on every row and wins one row against GLM-5-Base (LiveCodeBench-Base, 37.6 against 34.4) while losing the other four, and the footnote says the DeepSeek column was re-run in the provider’s own framework to control for implementation differences — which is a fair thing to do and also a reason not to compare that column with other published DeepSeek numbers. The same section gives the size story in one line: 320B total parameters against the GLM-4.5 line’s 355B, 18B activated against 32B, and 45 layers against 92.

Suggested prompt
A vendor publishes a comparison of attention compute and KV cache size between models of different sizes, normalised per head per layer. Explain what that normalisation does and does not let me conclude, and tell me what I would need to see before I could estimate what an hour of long-context traffic would cost me.

Official GLM-5.3-Flash specifications

Developer
Z.ai (Zhipu AI)
Model ID
glm-5.3-flash
Official context window
1M tokens
Official maximum output
128K tokens
Official inputs
Video, images, text and files
Output
Text
Z.AI Developer Documentation · GLM-5.3-Flash ↗

GLM-5.3-Flash and GLM-5.2 side by side

Every value below comes from a single table, the six-column comparison in the Z.ai launch post, checked on 27 September 2026, so one official page carries both columns. The left column is this page’s model and the right column is GLM-5.2, the generation it succeeds. Rows are matched by benchmark name, never by position. Eight of the table’s sixteen scored rows are reproduced here, and those eight are exactly the ones where GLM-5.2 has a value: the remaining eight are Vision rows where that model’s cell is a dash, because it accepts text only, and those rows compare this model with Gemini 3.7 Flash, GPT-5.6 Terra, Claude Opus 4.8 and DeepSeek-V4-Vision-Exp instead. All eight rows move in this model’s favour, so the table supports a claim about this pair and nothing wider. Three things have to travel with the numbers. The table prints six columns in total, and across all sixteen rows this model finishes first six times, second five times, third three times and fourth twice, with no fifth place, so a leaderboard claim cannot be written from it either. The post prints bare numbers with no unit column, and the labels above keep that shape rather than adding a unit the provider did not publish. Two gaps are the largest on the page and both are agentic: 48.8 against 26.2 on AutomationBench v1.0.6 and 63.4 against 46.2 on DeepSWE v1.1. The launch post’s own summary of this table names those two, and also states the comparison it does not win — that on its in-house Z.ai Code Bench v1.0 the model approaches but does not match Claude Opus 4.8 at maximum effort, 29.0 against 29.5. The post also prints a row of Artificial Analysis figures in the same table, and those are reported in the pricing section by source rather than mixed into a benchmark table.

Provider benchmarkGLM-5.3-FlashGLM-5.2
Coding · Terminal Bench 2.184.381.0
Coding · DeepSWE v1.163.446.2
Coding · NL2Repo56.348.9
Agentic · Toolathlon Verified78.459.9
Agentic · AutomationBench v1.0.648.826.2
Agentic · Agents’ Last Exam26.320.4
Agentic · HLE w/ Tools55.354.7
Agentic · GDPval-AA v217731504
Z.ai Blog · GLM-5.3-Flash: Frontier Intelligence, Flash Cost ↗

How to use GLM-5.3-Flash online

  1. Choose the model

    This page opens with GLM-5.3-Flash selected. The model navigation on the left and the selector inside the chat box stay in sync, and switching models keeps the current conversation. Start a new chat when you want a clean context.

  2. Send the artefact, not a description of it

    The attach button here accepts images, so a screenshot, a diagram or a page of a scanned document can go in directly alongside the prompt. Files are capped at 24 MB each and PDFs are converted to text before sending. State what you want checked as well as what you want produced; a prompt that names the specific defect you are looking for works better here than one that asks for a general review. Any prompt in this guide can be sent as it stands or edited first.

  3. Sign in, send and check the cost

    Sending a message needs an account with available points. The composer reads a reference price from the live model catalog and a finished request reports what it actually cost. Follow up with corrections rather than starting over, and remember that this box has no control for the provider’s reasoning-effort levels.

What GLM-5.3-Flash costs

Two kinds of price are published for this model and they are not interchangeable, so each is reported with the page that carries it. The official pricing page, checked on 27 September 2026, lists this model first in its “Latest Models” table at $0.15 per million input tokens, $0.03 per million cached input tokens and $0.50 per million output tokens, with a cached-storage column reading “Limited-time Free” and no end date attached to it. The same table prices the glm-5.3-flashx variant at $0.37 and $1.25, and GLM-5.3 at $1.4 and $4.4 — which is the arithmetic behind the launch post’s description of this model as costing one tenth of its sibling. The second kind of price is the subscription offer, and that one is dated: the official campaign page states that the GLM Coding Plan usage campaign for GLM-5.3-Flash runs from 3 September 2026 to 7 October 2026, that the end date was moved out from 20 September, that the window is 23:00 to 09:00 the following day in Singapore time and applies on weekends and public holidays, that calls made through ZCode or AutoClaw consume no quota at all during it, and that calls through other supported agents get double the plan’s standard quota. That page also records two limits: the campaign covers GLM-5.3-Flash only, and usage that has already hit the plan’s five-hour weekly ceiling cannot take part until the ceiling resets. A third statement exists and is deliberately not turned into a figure here. The Chinese documentation page says this model is priced at one tenth of GLM-5.3 and at one twentieth during a limited-time discount, while the English pricing table carries only the one-tenth figures; the discount sentence arrives without a date or a matching row, so this page records the discrepancy instead of picking the lower number. The launch post adds one more dated figure that is not a list price: it reports an Artificial Analysis Intelligence Index v4.1.1 score of 57 at $0.045 per task, and marks that per-task number as discounted. The subscription quota rules the model page describes — three times the quota of GLM-5.3, with off-peak calls including all day at weekends consuming only 50% of the standard points — are the provider’s own subscription terms and carry no published end date, so they are reported as the provider states them. None of the dollar figures above is this site’s checkout price. This site bills in points, and the reference price in its catalog at the date below is 7.8378 points per million input tokens and 27.027 points per million output tokens. Third-party resellers quote figures that differ from the official page, and none of those is used here.

View points and plans ↗

GLM-5.3-Flash FAQ

Which rows of the official table does GLM-5.3-Flash not lead?

Ten of the sixteen scored rows, and every one of them is printed by the same official table. On Terminal Bench 2.1 it scores 84.3 against GPT-5.6 Terra at 87.4, Gemini 3.7 Flash at 85.8 and Claude Opus 4.8 at 85.0. On DeepSWE v1.1 it scores 63.4 against 69.6 and 65.3. On NL2Repo it scores 56.3 against DeepSeek-V4-Vision-Exp at 57.7 and Claude Opus 4.8 at 69.7. On Agents’ Last Exam it scores 26.3 against 28.0, 27.3 and 27.0. On BabyVision, 53.4 against 70.9 and 61.6. On CharXiv Reasoning with tools, 89.4 against 89.9; on MVbench, 77.8 against 82.2; on MMVU, 80.5 against 82.3; on AutomationBench v1.0.6, 48.8 against 52.3; and on HLE with tools, 55.3 against 57.9. Counted across all sixteen rows the model finishes first six times, second five times, third three times and fourth twice, and it never finishes fifth. That distribution is why the comparison above is written against GLM-5.2 rather than as a claim about the whole table.

What is ox-alpha, and what does the provider actually claim about it?

Ox-alpha is the alias under which the provider says it served this model before release. The launch post states that GLM-5.3-Flash was tested anonymously as ox-alpha on OpenCode and OpenRouter to gather user feedback, that it quickly became the most popular model of the week on those services, and that all of that traffic was served on Chinese AI chips. What the post does not give is any traffic figure, date range or comparison set, which is why this page reports the claim with its single source rather than as a measurement. The alias does not appear in the model code or in the API surface — the model code is glm-5.3-flash — and the practical use of knowing it is that third-party write-ups of this model often carry ox-alpha in the title, so articles under either name are discussing the same weights.

How does GLM-5.3-Flash differ from GLM-5.3?

They are different models in the same line, released five weeks apart, and the official pages separate them on modalities first. GLM-5.3-Flash is described as the first native multimodal model in the GLM-5 series, accepting video, images, text and files, while the Chinese documentation page for GLM-5.3 states that it currently handles text modality only. Their documented limits are otherwise the same, at a 1M-token context window and a 128K maximum output, and both are quoted at a 128K output ceiling. On price they are not: the pricing page lists GLM-5.3-Flash at $0.15 per million input tokens and $0.50 per million output tokens, and GLM-5.3 at $1.4 and $4.4. Each is documented with its own architecture story, so this page reports the Flash model’s and names the flagship’s only where the two official pages overlap.

Can GLM-5.3-Flash read images and video here?

Images and PDFs, yes; video, no. The catalog entry behind the page publishes image among its input modalities, so JPEG, PNG and WebP files are accepted alongside PDFs, each capped at 24 MB. A PDF is converted to text before the model sees it, so a scan the extractor cannot read returns an error rather than an empty answer. Video is a different matter. Both the official page and the catalog entry behind this page list video among this model’s four input modalities, but the attachment adapter accepts only image types and PDF, so a video cannot be attached here in any form. That is a gap between what the model accepts and what this composer offers rather than a property of the model.

Why is each reply limited to 4,096 tokens when the model supports 128K?

Because the ceiling is set by this workspace rather than by the model. The official pages document a 128K maximum output for the API, and the model page and the migration guide state the same figure. This site requests at most 4,096 output tokens per reply, and that number is a composer setting. It is worth being precise about where each number comes from, because the provider’s two documentation pages differ on a related value: the migration guide tells callers to set `max_tokens` appropriately against the 128K ceiling, while the model page’s own recommended-settings block lists sampling parameters and a reasoning effort instead. Neither of those is this site’s limit. Because the catalog entry behind this page publishes no context length either, the interface shows no context figure at all, so the official 1M-token window describes the API rather than this page. Long deliverables are best asked for in parts, carrying the context forward between them.

What does GLM-5.3-Flash cost, and is there a dated offer?

The official pricing page carries three model figures per million tokens in US dollars — $0.15 for input, $0.03 for cached input and $0.50 for output — with a cached-storage column reading “Limited-time Free” for which no end date is published. The dated offer lives on a separate official page and is about the subscription rather than the API: the GLM-5.3-Flash usage campaign in the GLM Coding Plan runs from 3 September 2026 to 7 October 2026, with the end date moved out from 20 September, during the daily window of 23:00 to 09:00 Singapore time. Inside that window, calls through ZCode or AutoClaw consume no quota, calls through other supported agents get double the plan’s standard quota, and the campaign applies to GLM-5.3-Flash only — selecting GLM-5.3 still consumes quota normally. One official statement is left out on purpose: the Chinese documentation page says this model is priced at one twentieth of GLM-5.3 during a limited-time discount, while the English pricing table carries only the one-tenth figures and the discount sentence has no date or matching row, so this page records the discrepancy instead of the lower number. This site charges points, with a catalog reference price of 7.8378 points per million input tokens and 27.027 per million output tokens.

Can thinking be disabled, and which reasoning levels are documented?

Thinking cannot be disabled, and three reasoning levels are documented. The migration guide states that `thinking.type` accepts only `enabled`, that `reasoning_effort` chooses between low for lighter thinking, high for enhanced thinking and max for deep thinking, and that max is the default. The same guide treats this as a breaking change rather than a new option, and warns that applications currently sending `thinking.type: "disabled"` must switch that value before updating the model id or the request will fail. The model page repeats the constraint from the other direction, describing the capability as supporting multiple thinking modes while stating that thinking cannot be disabled. Sampling parameters are documented alongside it: temperature defaults to 1 and top_p to 0.95, and the guide advises adjusting only one of the two. None of this is controllable in this chat box — the catalog entry marks reasoning as required and publishes no level list, so the composer offers neither a level selector nor an off switch.

What changed under the hood in this generation?

The launch post gives three changes and attaches a number to each. The architecture is a hybrid of linear attention, which captures local dependencies through state modelling, and sparse attention, which retrieves relevant global context through a lightweight indexer; the provider describes it as the first open-source frontier model to combine the two. IndexPool compresses four indexer key vectors into one by weighted pooling, which the post introduces specifically to reduce the indexer’s latency and memory overhead at a 1M-token context, and the models the provider reports against are GLM-5.3, DeepSeek-V4-Flash and Kimi-K3 with attention compute and KV cache normalised per head per layer so that differently sized models can be compared: 3.0× less attention compute and a 4.4× smaller KV cache than GLM-5.3, and a KV cache still slightly larger than the two smaller rivals. Manifold-Constrained Hyper-Connections are credited with better scaling efficiency, and the post attributes part of the gain to a 30T-token multimodal pre-training corpus. Serving is the third part: the model runs on a large cluster of Chinese accelerators through an Encode–Prefill–Decode disaggregated architecture, with the provider reporting a 3× end-to-end improvement over its initial baseline on the same hardware.

Sources and model information

Information checked

Start a GLM-5.3-Flash conversation

The chat box above runs this model, and the guide on this page is written to be checked rather than trusted: the specifications come from the official model page, the comparison comes from the single official table that prints both columns, and the gaps between the two are named rather than smoothed over. Send a screenshot or a PDF if that is what you have, ask for the specific thing you want checked, and re-check any price or promotion against the pages linked below before relying on it, because the dated one ends on 7 October 2026.

Start a chat with GLM-5.3-Flash ↑