BestLLMfor Your hardware. Your LLM. Your call.
APIOpen data Find my LLM
Guide · 2026-08-01

State of Local LLMs — August 2026 Monthly Report

Last updated 2026-08-01

Our monthly read on which open-weight models, quants, runtimes and hardware are worth your money right now — with numbers, not vibes.

By Mohamed Meguedmi · 8 min read

Key Takeaways

  • The 24GB tier now runs frontier-class reasoning. Qwen3.5-32B and GLM-5-32B at Q4_K_M land within single-digit points of last year's closed flagships on MMLU-Pro, and both fit a single RTX 4090 or 5080.
  • MoE is the story of 2026. Sparse mixture-of-experts models (Qwen3-235B-A22B, Llama 4 Scout) give you 200B+ knowledge at ~22B active-parameter speed — if you have the RAM to hold them.
  • Gemma 4 27B is the new default 12–16GB pick for general assistant work; its Q4_K_M weights fit 16GB with room for a 16K context.
  • Runtime consolidation is real. llama.cpp powers Ollama and LM Studio under the hood; vLLM owns multi-GPU serving. Pick by workload, not brand.
  • Price/performance keeps falling. Used RTX 3090 24GB cards remain the best dollar-per-usable-VRAM buy, but the 5060 Ti 16GB reshaped the entry tier.

What actually changed in August 2026

Three things moved the needle this month. First, the Qwen3.5 refresh shipped improved instruction-following and a longer default context (128K) across the 8B/14B/32B dense line, with day-one GGUF quants on Hugging Face. Second, Gemma 4 quantization-aware training (QAT) weights matured to the point where the Q4_0 build loses almost nothing versus FP16 on everyday tasks — a meaningful win for 16GB owners. Third, Ollama pushed structured-output and tool-calling improvements to stable, closing much of the gap that previously sent power users to vLLM.

None of this is revolutionary on its own, but the cumulative effect is that the "good enough to replace a cloud call" bar is now clearly met on hardware most developers already own. If you benchmarked local models a year ago and walked away unimpressed, August 2026 is a fair time to re-test. Our full model matrix lives in the catalog, and every score below is reproducible from our methodology.

Best open-weight models by VRAM tier

The table below is our current recommendation per tier for a general-purpose local assistant, using the quant we'd actually run. Scores are MMLU-Pro (5-shot) and HumanEval pass@1 from our August test pass; treat them as directional, not absolute.

VRAMRecommended model + quantParams (active)MMLU-ProHumanEvalBest for
8 GBQwen3.5-8B Q4_K_M8B58.171.3Chat, RAG, light coding
12 GBGemma 4 12B Q4_K_M12B62.468.9Balanced assistant
16 GBGemma 4 27B Q4_0 (QAT)27B67.074.5General default pick
24 GBQwen3.5-32B Q4_K_M32B71.882.1Coding + reasoning
24 GBGLM-5-32B Q4_K_M32B71.280.4Agentic / tool use
48 GB+Qwen3-235B-A22B Q4_K_M235B (22B)78.986.7Frontier local reasoning

Two verdicts. For most people the winner is unglamorous: Gemma 4 27B at Q4_0 on a 16GB card is the best effort-to-reward ratio in the ecosystem right now. If you have 24GB, Qwen3.5-32B Q4_K_M is the coding and reasoning champion and the model we'd default to for daily developer work. See the model card on Hugging Face for the full quant list and license terms.

The MoE inflection point

Mixture-of-experts is why a 235B-parameter model is suddenly plausible on a well-specced desktop. Qwen3-235B-A22B activates only ~22B parameters per token, so throughput feels like a 22B dense model even though quality tracks something far larger. The catch is memory footprint: the Q4_K_M weights are ~130GB, so you either need multi-GPU (2× 48GB) or you offload experts to system RAM and accept slower prompt processing.

Our take: MoE is worth chasing only if you have 128GB+ of fast system RAM or dual pro GPUs. For everyone else, a dense 32B remains the pragmatic ceiling. Llama 4 Scout occupies a similar niche — strong, but demanding — and the details are documented in Meta's official model announcements.

Runtimes: which one, and when

The runtime landscape has consolidated into clear lanes. Don't overthink the choice — match it to your workload.

  • Ollama — best default for single-user desktop use. One-line pulls, sane defaults, now with solid tool-calling and structured output. Backed by ollama.com/library.
  • llama.cpp — the engine underneath most GUIs. Use it directly when you want maximum quant control, CPU/GPU split tuning, or the newest GGUF features first.
  • vLLM — the answer for concurrent serving and multi-GPU throughput. If you're serving a team or an app, this is the production pick.
  • LM Studio — the friendliest GUI for non-terminal users; great for evaluating models before scripting anything.

Verdict: solo developer on one machine → Ollama or llama.cpp. Serving many users → vLLM. There's no prize for suffering through vLLM's config to chat with a single 8B model.

Hardware: price/performance in August 2026

VRAM is still the binding constraint, and the used market still wins on dollars-per-gigabyte. Approximate US street prices this month:

GPUVRAMApprox. price (USD)$/GB VRAMTier it unlocks
RTX 5060 Ti16 GB$429$26.8Gemma 4 27B Q4_0
RTX 3090 (used)24 GB$650$27.1Qwen3.5-32B Q4_K_M
RTX 508016 GB$999$62.4Fast 27B, tight context
RTX 4090 (used)24 GB$1,500$62.532B + long context
RTX 509032 GB$1,999$62.532B headroom / small MoE
Apple M4 Max (128GB)~110 GB usable$3,700$33.6MoE via unified memory

The standout remains the used RTX 3090: at roughly $650 it delivers a full 24GB and comfortably runs our top 32B pick. For a clean-slate 16GB build, the RTX 5060 Ti reset expectations at the entry level. And for MoE-curious buyers, an Apple M4 Max with 128GB of unified memory is the cheapest way into 200B-class models, at the cost of prompt-processing speed. Model these scenarios against your electricity rate in our cost calculator.

Benchmarks that matter now

Raw MMLU is played out. In August 2026 we weight four things: MMLU-Pro (harder reasoning), HumanEval / LiveCodeBench (real coding), tool-calling accuracy (agentic reliability), and long-context recall (does 128K actually work, or just load?). The gap between advertised and usable context is where many models still disappoint — several 128K-tagged releases degrade sharply past 32K in needle-in-haystack tests. We publish the full battery on the benchmarks page, and every number is queryable through the BestLLMfor public API (CC BY 4.0) or the open-source MCP server, so you can pull live scores straight into your own tooling.

Cost of ownership: local vs cloud

The economic case for local has quietly gotten stronger. A used RTX 3090 running Qwen3.5-32B produces roughly 35–45 tokens/sec on a single stream. At typical US residential power (~$0.17/kWh) and a ~350W draw, marginal cost is a fraction of a cent per thousand tokens — effectively free at the margin once the card is paid off. The breakeven versus a metered API is now measured in weeks of heavy use, not years, for anyone generating serious volume. Privacy, offline capability, and no rate limits are the bonus.

Verdict

Your situationBuyRunRuntime
Entry / first local modelRTX 5060 Ti 16GBGemma 4 27B Q4_0Ollama
Best value all-rounderUsed RTX 3090 24GBQwen3.5-32B Q4_K_MOllama / llama.cpp
Coding-first developerUsed RTX 4090 24GBQwen3.5-32B Q4_K_Mllama.cpp
Agentic / tool useRTX 5090 32GBGLM-5-32B Q4_K_MvLLM
Frontier local reasoningApple M4 Max 128GBQwen3-235B-A22B Q4_K_Mllama.cpp

Bottom line for August 2026: if you want one recommendation, it's a used 24GB card running Qwen3.5-32B on Ollama. It's the sweet spot of price, quality and simplicity, and nothing this month unseats it. Browse the alternatives in the best-of rankings if your use case is narrower.

Frequently asked questions

What is the single best local LLM to run in August 2026?

For a 24GB GPU, Qwen3.5-32B at Q4_K_M is our overall pick — it leads on coding and reasoning while staying fast. On 16GB, Gemma 4 27B (Q4_0 QAT) is the best default.

Do I need a new GPU, or is a used one fine?

A used RTX 3090 24GB (~$650) is the best dollar-per-usable-VRAM buy this month and runs our top 32B recommendation comfortably. New cards buy you speed and warranty, not necessarily more capability at this tier.

Is Ollama or vLLM better?

Ollama for single-user desktop use and quick setup; vLLM for multi-GPU or multi-user serving where throughput matters. Both sit on top of proven engines — pick by workload, not brand.

Can I really run a 235B model locally?

Yes, if it's a sparse MoE like Qwen3-235B-A22B and you have 128GB+ of fast RAM or dual 48GB GPUs. It activates only ~22B parameters per token, so speed is reasonable, but the memory footprint is large.

How do I access these benchmark numbers programmatically?

Every score is available via the BestLLMfor public API (licensed CC BY 4.0) and through our open-source MCP server, so you can pull live model and benchmark data into your own scripts and agents.

Recommended hardware

For running local LLMs comfortably, an RTX 5070 Ti (16 GB VRAM) is the best value for money.

Amazon Check RTX 5070 Ti price →

As an Amazon Associate, BestLLMfor earns from qualifying purchases, at no extra cost to you. It does not influence our independent rankings.