Processor and graphics card specifications are live

Glossary/System/Quantisation (LLM)

Quantisation (LLM)

Quantisation stores a language model's weights in fewer bits each, shrinking the memory the model needs at some possible cost in quality.

Also known as quantization, model quantisation, 4-bit quantisation

Checked by a SystemCheck tool

The local AI readiness check checks this in your browser, on your own device. The paragraphs below say what it reads and what a browser cannot see.

A model's weights take parameters times bytes per weight. Bytes per weight: 2 at 16-bit, 1 at 8-bit, 0.5 at 4-bit. So a 7 billion parameter model's weights are 14 GB at 16-bit, 7 GB at 8-bit, 3.5 GB at 4-bit. Quantisation, storing the weights at fewer bits, is usually what moves a model from not fitting in a laptop's graphics memory to fitting.

Halving the bits halves the weights' memory and the data read for every generated token, which is why quantised models also tend to generate faster on memory-bound hardware. It can cost some quality, and by how much depends on the model and the method, a question for the model's own documentation. It does not shrink the context: the memory a runtime keeps for the conversation grows with its length on top of the weights, and real quantised files are somewhat larger than the bare arithmetic because they store scales alongside the weights.

The local AI readiness check sets the weights of each common size, at each precision, against the graphics memory the browser let it allocate and verify, and reports the largest that fits. It does not predict tokens per second, because the runtime, the model's design and the context length all change that.

Covered in full

This page defines the term. The pages below explain it, diagnose it and measure it.

Related terms