When the estimate is wrong, and in which direction
- Flash attention and paged KV reduce real usage below the estimate, sometimes by a few gigabytes at long context.
- Batch size above one multiplies the KV cache. This tool assumes a single conversation.
- Vision and audio inputs add encoder memory the tool does not model.
- Sliding-window, hybrid and latent-attention models are counted the way they actually cache, which is why Gemma, gpt-oss, Qwen3.5 and later, Nemotron, Mistral Small 4 and GLM Flash show a much smaller KV bar than their size suggests. A runtime that does not implement the matching cache stores every layer at full length and will use more than the estimate, by gigabytes at long context.
- The custom model option assumes a standard transformer. For a hybrid model, enter only its full-attention layers in the layers field.
- The desktop on the same card takes 0.5 to 2 GB. The 95% "fits" threshold assumes the card is otherwise free; on a desktop with a display attached, treat a tight fit as a maybe.
For the full background, read the self-hosted LLM guide. For a table of popular models at common settings, see which models fit on 16 to 96 GB. If you have a specific card in mind, the can-I-run-it checker answers the pairing and says what to change when it does not fit.