Grok 4.3 vs GLM 5V Turbo
At a Glance
| Compare | Grok 4.3xAI | GLM 5V TurboZ.ai |
|---|---|---|
| Intelligence, Cost, and Efficiency | ||
| IntelligenceHigher is better · MM Intelligence v2.5 | #40 of 4616.6 score · 2/3 sources · provisional · missing ARC-AGI-2 · full-core range 11.1–44.4 | UnrankedNot in the 46-model eligible cohort |
| CostLower is better · Published-token output estimate | #7 of 44$0.028 per LiveBench case | UnrankedNot in the 44-model eligible cohort |
| EfficiencyHigher is better · MM Efficiency v1.5 | #33 of 3846.0 score · 2/3 sources · provisional · missing ARC-AGI-2 · full-core range 43.3–59.9 | UnrankedNot in the 38-model eligible cohort |
| Pricing and Limits | ||
| Input priceFrom · USD / 1M tokens | $1.25Xai ↗ · Sep 3, 2026 | Not reported |
| Output priceFrom · USD / 1M tokens | $2.50Xai ↗ · Sep 3, 2026 | Not reported |
| Context windowMaximum documented tokens | 1,000K | 200K |
| Model facts checked | Sep 3, 2026View model evidence → | Aug 29, 2026View model evidence → |
Token prices are the lowest available sourced USD rates; input and output may use different providers. Cost ranking estimates output spend on LiveBench, not a full request bill. Ranking methodology →
Available Benchmarks
Side-by-Side Facts
| Field | Grok 4.3 | GLM-5V-Turbo |
|---|---|---|
| Developer | xAI | Z.ai |
| Family | Grok 4 | Glm 5v |
| Model | Grok 4.3 | GLM-5V-Turbo |
| Version | Grok 4.3 | GLM-5V-Turbo |
| Lifecycle | active | active |
| Released | 2026-06-17 | Unknown |
| Knowledge cutoff | Unknown | Unknown |
| Input modalities | Text, Image | Text, Image, Video, Document |
| Output modalities | Text | Text |
| Context window | 1,000K | 200K |
| Total parameters | Unknown | Unknown |
| Active parameters | Unknown | Unknown |
| License | Unknown | Unknown |
| Open weights | No | No |
| API available | Yes | Yes |
| Self-hostable | No | No |
| Provider access | Xai (Standard) | Z.ai (Standard) |
| Capabilities | chat, generation, reasoning, structured_outputs, tools | agents, chat, computer-use, reasoning, tools, vision |
Grok 4.3 Capabilities
GLM 5V Turbo Capabilities
Primary Evidence
Sources and Freshness
Questions
Grok 4.3 vs GLM 5V Turbo FAQs
Is Grok 4.3 or GLM 5V Turbo better for coding?+
This comparison does not currently contain a protocol-matched coding benchmark for both Grok 4.3 and GLM 5V Turbo, so Model Markets cannot name a coding leader from pricing, context size, or capability labels alone.
Which is cheaper, Grok 4.3 or GLM 5V Turbo?+
Only Grok 4.3 has a directly sourced input price: $1.25 per million tokens. Only Grok 4.3 has a directly sourced output price: $2.50 per million tokens.
Which has a larger context window, Grok 4.3 or GLM 5V Turbo?+
Grok 4.3 has the larger sourced context window. Grok 4.3 supports 1,000K and GLM 5V Turbo supports 200K.
Which performs better in benchmarks, Grok 4.3 or GLM 5V Turbo?+
There is no overall benchmark winner: At least two independently verified, protocol-matched benchmarks are required for an overall winner.
Can Grok 4.3 or GLM 5V Turbo be self-hosted?+
Both models have the same recorded self-hosting status: unsupported. Grok 4.3 is not marked open weight; GLM 5V Turbo is not marked open weight.
Can Grok 4.3 and GLM 5V Turbo understand images?+
Grok 4.3 is documented with image input; GLM 5V Turbo is documented with image input. This reflects supported input modalities, not vision quality.
Which can generate longer answers, Grok 4.3 or GLM 5V Turbo?+
Neither has a larger sourced maximum output. Grok 4.3 is — and GLM 5V Turbo is 131K.
Do Grok 4.3 and GLM 5V Turbo support reasoning and tool use?+
Grok 4.3: reasoning, tool calling, and image input. GLM 5V Turbo: reasoning, tool calling, and image input. Feature support does not establish relative quality.
Which is available from more inference providers, Grok 4.3 or GLM 5V Turbo?+
Grok 4.3 has 1 sourced provider route; GLM 5V Turbo has 1, a tie.
Which offers better value, Grok 4.3 or GLM 5V Turbo?+
There is no universal value winner. Compare the input and output prices above with the matched benchmark result for your workload: cheaper tokens can be offset by different quality, token usage, latency, or provider availability.