Best local LLM for 24GB
Short answer: Recursive Flint 40B-A2.5B at Q3_K_M for general use — 20.6 GB of 24GB, leaving 3.4 GB. Also: MiniCPM-V 4.7 35B-A3B (Images).
“Best” here means the largest model in its category that clears the card with headroom left, at the highest-quality quant that still fits. This index measures memory and published perplexity, not task quality — it cannot tell you which model answers better, and does not pretend to.
The picks
| For | Model | Quant | Est. VRAM | Headroom | Loss | Why |
|---|---|---|---|---|---|---|
| General · Coding | Recursive Flint 40B-A2.5B40B-A2.5B | Q3_K_M | 20.6 GB | 3.4 GB | — | The largest model of any kind that fits this budget. Its quantizer published no perplexity figure, so none is quoted. Past 16K context the KV cache pushes it over.Download: bartowski/RecursiveSI_flint-GGUF · RecursiveSI_flint-Q3_K_M.gguf · 19.53 GB · listing read 2026-10-23 |
| Images | MiniCPM-V 4.7 35B-A3B35B-A3B | Q4_K_S | 20.9 GB | 3.1 GB | — | The largest in its category that still leaves headroom. Its quantizer published no perplexity figure, so none is quoted. Only at 4K context — a longer window does not fit.Download: openbmb/MiniCPM-V-4.7-35B-A3B-gguf · MiniCPM-V-4_7-35B-A3B-Q4_K_S.gguf · 19.89 GB · + vision projector 1.12 GB, separate · listing read 2026-10-20 |
Sized at 4K context with a 10% activation buffer; 94 of 125 models in the index clear this budget comfortably. Loss is the quantizer’s published perplexity figure against FP16, or a dash where none was published.
Cards this applies to
What fits is decided by capacity alone, so every card here returns the same list. What differs is how fast it reads the weights — each card’s page states its bandwidth and what that costs you.
What does not fit
The nearest miss is K2 Horizon MoVA 36B-A4B. Its smallest build in this index, Q4_K_M, needs about 24.2 GB — 0.2 GB over 24GB, before any context beyond 4K. Offloading to system RAM will load it at a speed set by your RAM, which is a different machine rather than a smaller quant.
Pushing context
At 4K context 94 models clear this budget. At 16K it is 90, and at 32K it is 80. The weights do not change — the KV cache is what grows.
Check your exact context lengthCommon questions
What is the best local LLM for 24 GB of VRAM in 2026?
Recursive Flint 40B-A2.5B at Q3_K_M for general use — 20.6 GB of 24 GB, leaving 3.4 GB. MiniCPM-V 4.7 35B-A3B if you want images. "Best" here means the largest model in its category that clears the card with headroom — this index measures memory and published perplexity, not task quality, so it cannot rank models on how well they answer.
How many models fit 24 GB?
94 of the 125 models in this index clear it comfortably at 4K context — comfortably meaning the estimate uses at most 88% of the memory, so there is margin for the display and the runtime. At 16K that falls to 90, and at 32K to 80: the KV cache is what moves, not the weights.
What will not run on 24 GB?
The nearest miss is K2 Horizon MoVA 36B-A4B: its smallest build here, Q4_K_M, needs about 24.2 GB — 0.2 GB over, before any context beyond 4K. Offloading part of it to system RAM will load it, at a speed set by your RAM rather than your card; that is a different machine, not a smaller quant.
Do all 24 GB cards run the same models?
They hold the same models — what fits is decided by capacity alone, so all 4 cards at this tier return this same list. What differs is how fast they read the weights: token generation reads the whole weight set once per token, so memory bandwidth sets the ceiling, and two cards with identical memory can be more than 2.5× apart on it. Each card's own page states its bandwidth and what that implies.