GLM-5.2 is rumored to be on par with Fable 5. But it required at least 223GB to run locally

The assessment that "the open-weight GLM-5.2 is almost on par with Fable 5 in Design Arena" has become a hot topic on Reddit. If an MIT-class open model has closed in on the top commercial models, you might think, "Wouldn't it be great if this could run locally?"

However, when I checked the specs actually required to run it, the story changed. In this article, I will explain what GLM-5.2 is, whether it really runs locally, calculate the required memory by quantization level, and organize the realistic options.

What you will learn in this article:

• Why GLM-5.2 is a hot topic

• The results of calculating the memory required for local execution by quantization level

• Whether it really runs on a Mac and where the realistic line is

• How to look at the phrase "runs locally" so you don't get deceived

Chapter 1: Why GLM-5.2 is a hot topic

GLM-5.2 is a 744B parameter (with 40B active) MoE (Mixture of Experts) model. The context window is massive at approximately 1 million tokens (1,048,576).

There are two sources for the buzz.

One is that the official Unsloth "local execution guide" garnered 427 points on HackerNews. The other is that a user who actually used it for a project on Reddit (r/LocalLLaMA) reported that "it was nearly on par with Fable in almost every category in Design Arena."

The benchmark numbers are also flashy, with 62.1% on SWE-Bench Pro, 99.2% on AIME 2026, and 91.2% on GPQA-Diamond being published. Looking at this alone, it's understandable why people are excited that "open weights have finally caught up to the top commercial models."

However, where many people get tripped up here is the expectation that "since it's 40B active, it should run lightly locally, right?" Because MoE only uses some experts during inference, the computational load is equivalent to 40B. But you have to load all 744B into memory. This was the pitfall.

Chapter 2: Calculating the required memory by quantization level

The Unsloth documentation lists the required memory (total of RAM + VRAM) for each type of quantization. These are quite significant numbers.