Run GLM-5.3 locally

GLM-5.3 is 753B parameters (40B active per token — a mixture-of-experts, so it still needs room for all 753B in memory). Here's the VRAM it needs at each quantization, the smallest GPU that fits, and how a self-hosted box compares with the cheapest verified API.

VRAM by quantization

QuantizationVRAM neededFits onNotes
int4 (Q4)451.8 GB8× H100 (640 GB) ($13.84/hr)smallest footprint, minor quality loss
int8 (Q8)903.6 GBmulti-node (>640 GB)near-lossless
fp16 (full)1807.2 GBmulti-node (>640 GB)reference quality

VRAM ≈ params × bytes/param × 1.2 (overhead). See the fullmethod and break-even calculator.

Self-host vs API

Cheapest API for GLM-5.3 is $4.64 / 1M tokens(blended) via GMICloud. Running it yourself in int4 fits a8× H100 (640 GB) at $13.84/hr — about $10,103.2/month at 24/7. Those two lines cross at roughly 2.2B tokens/month: below that the API wins on cost, above it the dedicated GPU does (assuming you keep it busy). Tune your own volume in the break-even calculator.

Run it at home

In int4, GLM-5.3 needs 451.8 GB — more than any consumer desktop or Apple machine we track holds, so at home it means a multi-GPU server. Renting cloud GPUs by the hour, or the API, is the practical route. See the machines table for the ceiling.

Get the weights

Quantized builds on the model hubs — links search live, so they track new builds as they appear:

License: open weights under GLM-5.3 License · terms. Compare all providers on the glm-5.3 API page.