Local LLM Finder

Model → hardware

Qwen3 8B

Plan for 8 GB of dedicated GPU memory at Q4_K_M and a 4,000-token context. 12 GB gives more headroom under the same settings.

General chat and mixed tasks. Memory fit is an estimate, not a speed or quality guarantee.

Hardware starting points

Planning estimates

Q4_K_M · 32 GB system RAM · one active request · full GPU residency

Dedicated GPU memoryAt 4,000 tokensAt 16,000 tokensExample from these guides
8 GBSmallest listed tier that fits6.2 GB + 0.24 GB reserveFits the estimate6.8 GB + reserveRTX 4060 8 GB
12 GBMore headroom6.2 GB + 0.36 GB reserveFits the estimate6.8 GB + reserveRTX 3060 12 GB
16 GBMore headroom6.2 GB + 0.48 GB reserveFits the estimate6.8 GB + reserveRTX 4060 Ti 16 GB

The smallest tier fits the calculation; it is not a verified minimum. Cache precision and runtime buffers can change the fit. “More headroom” means at least 2 GB remains after the estimate and reserve.

Use the publisher’s Instruct / chat template in a current GGUF-capable runtime. The 8 GB tier can become tight when display use, buffers or context grow. CPU offloading needs adequate system RAM and changes performance; it is not included in these full-GPU estimates.

Compare quantisation and context
File profileWeight input¹GPU estimate at 4KGPU estimate at 16K
Q4_K_M5.03 GB6.2 GB6.8 GB
Q5_K_M5.85 GB7.0 GB7.6 GB

¹ Catalogue planning weights. These can differ from an exact downloaded file; runtime memory also includes cache and buffers.

Keep the exact file, runtime version, cache type and context limit consistent when comparing. Q5 uses more memory; compare its answers on your own tasks before accepting the trade-off.

Setup and common questions

Which checkpoint should I download?

Use Qwen/Qwen3-8B and the publisher’s GGUF files. This checkpoint supports thinking and non-thinking modes. Keep that mode fixed when comparing results; thinking output uses tokens and time before the final answer.

Can I use its full context window?

Qwen lists 32,768 native tokens and up to 131,072 with YaRN. Extended context needs explicit runtime support and more memory. The Finder’s 64K planning limit does not verify YaRN support. See context length.

What if it loads but runs out of memory?

Close other GPU workloads and reduce context. If needed, use a smaller file or partial CPU offload. For Macs or CPU-only setups, select the appropriate mode in the Finder; installed RAM is not dedicated VRAM.

How are these recommendations chosen?

We compare dedicated GPU memory tiers using the main Finder’s memory calculation at the stated quantisation and context. These tiers describe memory fit, not speed or output quality.

GPU memory includes weights, context cache and a 0.9 GB runtime allowance, plus a 3% reserve (0.15–1.5 GB). Cache format and runtime buffers can change the fit. See the calculation assumptions.

Sources and related guides

These comparisons are planning estimates. No reviewed or independently reproduced measurements are available yet. About test evidence.