Context is the active conversation window
Context length is the number of tokens a runtime can keep available as input and recent conversation for a request. A token is a model-specific text unit, not exactly a word or character.
A model card may document a maximum context, but that maximum is not automatically a sensible setting for every computer. The runtime, backend, batch settings, and available memory all matter.
Why more context needs more memory
The runtime maintains attention-related state for the active context, commonly described as a key-value cache. As the context grows, that state can take more memory in addition to the model weights and runtime buffers.
This means a model can load at a short context but fail, slow down, or leave less headroom at a much larger context. The exact cost depends on architecture and runtime settings, so a simple public estimate should not pretend to calculate it exactly.
How to use the guidance
Start with a context length that matches the work you actually do and leave memory headroom. If a setup is close to the boundary, reducing context can be more useful than immediately choosing a much lower-quality quantization.
LLMGauge shows model context metadata and gives approximate compatibility guidance. It does not promise that the published maximum context will fit on your hardware or predict a tokens-per-second result.