What You Actually Pulled: Reading Quantisation, Parameter Count and Context Out of an Ollama GGUF File

You pulled a tag. The download is 18.99 GiB for a model the card calls 31B. The agent that needed long history behaves as if it had a fraction of the context the card advertises. The quality does not match the benchmark chart that made you choose the model in the first place. None of those three surprises is a property of the model. All three are properties of the artifact: which quantisation the tag actually resolved to, how many bits per weight that quantisation really costs, and which metadata value declares the context this particular build was made for. ...

November 6, 2026 · 14 min · baeseokjae

Reading an Ollama Model's Quantization and Size From Its Registry Manifest

You ran ollama pull qwen3:32b and got a model file of about 20.2 GB, or 18.8 GiB. A nominal 32-billion-parameter model needs 64 GB for bf16 weights alone. The downloaded model file is about 31.6% of that nominal baseline, not one-fifth. The tag says 32b, but it does not spell out the quantization recipe. You can check the registry’s declared quantization and file sizes before downloading model-weight blobs. An Ollama manifest lists layers and byte sizes; its small config blob supplies file_type. Turning those bytes into bits per weight takes another step: the parameter count must describe the tensors in the same file. ...

November 3, 2026 · 11 min · baeseokjae