Qwen3.5 9B Instruct
Best for: Quality, Coding, Reasoning·Pop: 86/100
Perf: est. 53 tok/s, typical error 5% · first token ~0.6s
Fits in 12 GB VRAM with room to spare. Best for quality, coding, reasoning on RTX 3060.
The RTX 3060 is the cheapest way into 12GB of VRAM for local AI, handling 7B-8B parameter models at est. 50 tok/s, typical error 5%. It is no longer the bargain it was: the 2026 memory shortage pushed it far above its launch MSRP, close to cards with more VRAM, so check the current price against a newer 16GB card before buying.
The best local LLM for the RTX 3060 is Qwen3.5 9B Instruct (est. 53 tok/s, typical error 5%) on its 12GB VRAM. It uses ~7GB of VRAM; the RTX 3060 handles up to 9B parameter models at Q4. A 14B model at Q4 runs at est. 30 tok/s, typical error 15%. (ModelFit, 2026)
Sizing rule: a Q4 model needs about 0.6 GB of VRAM per billion parameters, and ModelFit budgets 90% of this card's 12GB for weights, context, and KV-cache. The per-size table below uses that same budget. Other strong fits: Ornith 1.0 9B (9B, ~5.6GB) and Gemma 4 12B (12B, ~8GB). On this card Qwen3.5 9B Instruct runs at est. 53 tok/s, typical error 5%. What it will not run: a 20B MoE (3.6B active) model does not fit in VRAM alone, so it spills to system RAM over PCIe and slows sharply.
Speeds are ModelFit estimates from memory bandwidth and model size, not measured benchmarks. Typical error: the median gap between the ModelFit speed model and measured runs on hardware the model was not fitted on, for this backend and model size.
Cite this page: ModelFit, RTX 3060 12GB Local LLM (2026): Best 7B-9B Picks, est. 50 tok/s, https://modelfit.io/gpu/rtx-3060/, updated October 2026, CC BY 4.0.
| Model size | Est. speed | Fit on 12GB |
|---|---|---|
| 7B | est. 57 tok/stypical error 5% | Fits in VRAM |
| 14B | est. 30 tok/stypical error 15% | Fits in VRAM |
| 20B MoE (3.6B active) | est. 50 tok/stypical error 15% | CPU offload (slow) |
| 32B | est. 1 tok/stypical error 5% | CPU offload (slow) |
| 35B MoE (3B active) | est. 28 tok/stypical error 15% | CPU offload (slow) |
| 70B | est. 1 tok/stypical error 10% | CPU offload (slow) |
| 120B MoE (5.1B active) | est. 17 tok/stypical error 15% | CPU offload (slow) |
Decode speed, generic Q4_K_M model of each size at 4K context, 360 GB/s, typical error 5-15%
ModelFit estimates, not measured benchmarks: decode speed of a generic Q4_K_M model of each size at 4K context on the RTX 3060's 360 GB/s bandwidth. MoE rows scale by active parameters (decode reads only the active experts), so a 35B MoE runs far faster than a dense 32B. "CPU offload" sizes exceed the 12GB VRAM; dense models slow to a crawl there, MoE models degrade less because hot experts stay GPU-resident. What typical error means.
Qwen3.5 9B Instruct loads ~7 GB of weights; at 16k context the KV cache adds ~0.5 GB (still fits the ~11 GB usable VRAM), and at 64k it adds ~2.0 GB (still fits).
The model leaves about 3.3 GB of the usable VRAM budget free after weights and 16k context.
KV-cache figures assume an fp16 cache, the llama.cpp/Ollama default. Standard GQA models use a size-class estimate (8 KV heads x 128 head dim class); hybrid linear-attention models (Qwen3.5/3.6, Qwen3-Next) use the exact per-token cost from their published config, since only their sparse full-attention layers cache KV. A q8_0 KV cache roughly halves either figure. Estimates, not measurements.
One email when a new open-weight model is a better fit for 12 GB of VRAM, plus the Thursday weekly.
You'll also get the weekly ModelFit email. By signing up you agree to our Privacy Policy. Unsubscribe from either email anytime, in one click.
ModelFit may earn a commission on purchases through these links, at no extra cost to you.
With 12GB GDDR6, the RTX 3060 loads any 7B-9B model in Q4 quantization with room left for a 4K-8K context window. Models like Qwen 2.5 7B and Llama 3.2 8B use about 5-6GB, leaving headroom for KV cache. Larger 14B models require Q3 quantization or partial CPU offloading, which cuts speed by 70-80%. Stick to 7B-9B Q4 for the best experience on this card.
| Hardware | Memory | Speed | Bandwidth |
|---|---|---|---|
| RTX 3070 | 8 GB | est. 61 tok/stypical error 5% | 448 GB/s |
| RTX 3060 | 12 GB | est. 50 tok/stypical error 5% | 360 GB/s |
| RTX 4070 | 12 GB | est. 73 tok/stypical error 5% | 504 GB/s |
| RTX 4060 Ti | 16 GB | est. 43 tok/stypical error 5% | 288 GB/s |
| RTX 5060 Ti | 16 GB | est. 68 tok/stypical error 5% | 448 GB/s |
Best for: Quality, Coding, Reasoning·Pop: 86/100
Perf: est. 53 tok/s, typical error 5% · first token ~0.6s
Fits in 12 GB VRAM with room to spare. Best for quality, coding, reasoning on RTX 3060.
Best for: Agentic coding on small machines·Pop: 76/100
Perf: est. 53 tok/s, typical error 5% · first token ~0.6s
Fits in 12 GB VRAM with room to spare. Best for agentic coding on small machines on RTX 3060.
Best for: Chat, Coding, Multimodal·Pop: 80/100
Perf: est. 35 tok/s, typical error 15% · first token ~0.9s
Fits in 12 GB VRAM with room to spare. Best for chat, coding, multimodal on RTX 3060.
Best for: On-device agents, tool calling, multilingual chat·Pop: 72/100
Perf: est. 139 tok/s, typical error 15% · first token ~0.2s
Fits in 12 GB VRAM with room to spare. Best for on-device agents, tool calling, multilingual chat on RTX 3060.
Best for: On-device, Mobile, Chat·Pop: 82/100
Perf: est. 53 tok/s, typical error 5% · first token ~3.5s
Fits in 12 GB VRAM with room to spare. Best for on-device, mobile, chat on RTX 3060.
Best for: Agentic coding, Small machines·Pop: 60/100
Perf: est. 51 tok/s, typical error 5% · first token ~0.6s
Fits in 12 GB VRAM with room to spare. Best for agentic coding, small machines on RTX 3060.
Best for: Chat, Coding, Vision·Pop: 74/100
Perf: est. 44 tok/s, typical error 5% · first token ~0.7s
Fits in 12 GB VRAM with room to spare. Best for chat, coding, vision on RTX 3060.
Best for: Coding, Agents, Multimodal·Pop: 88/100
Perf: est. 91 tok/s, typical error 5% · first token ~0.3s
Fits in 12 GB VRAM with room to spare. Best for coding, agents, multimodal on RTX 3060.
Best for: Chat, Reasoning, Vision·Pop: 74/100
Perf: est. 30 tok/s, typical error 15% · first token ~1.1s
Fits in 12 GB VRAM with room to spare. Best for chat, reasoning, vision on RTX 3060.
Best for: Quality, Coding, Reasoning·Pop: 86/100
Perf: est. 33 tok/s, typical error 5% · first token ~3.9s
Fits in 12 GB VRAM with room to spare. Best for quality, coding, reasoning on RTX 3060.
Per-model verdict pages for this exact card: weights, KV cache by context length, and estimated tok/s, each derived from the same engine the recommendations above use.
Speeds are estimates for Qwen3 8B Q4_K_M, typical error 5%.
The RTX 3060 has 12GB GDDR6 VRAM. After OS and driver overhead (~0.5GB), about 11.5GB is available for model loading. This comfortably fits 7B-9B parameter models at Q4 quantization with room left for the KV cache.
You can run up to 9B parameter models at Q4 quantization. Popular choices include Qwen 2.5 7B (~5.2GB), Llama 3.2 8B (~5.6GB), and Mistral 7B (~4.4GB). For 14B models, you would need Q3 quantization which reduces output quality.
Yes. The RTX 3060 remains the cheapest route to 12GB of VRAM in 2026, especially used. On 8B models it delivers est. 50 tok/s, typical error 5%, fast enough for interactive chat. Its 12GB VRAM handles most popular 7B models at full quality.
The RTX 4060 Ti 16GB has 4GB more VRAM, allowing 14B models. However, its bandwidth is lower (288 vs 360 GB/s), so it is actually slower for 7B-8B models. If you only run 7B models, the RTX 3060 is better value. For 14B models, the 4060 Ti wins.
Install Ollama from ollama.com: it auto-detects your RTX 3060 via CUDA. Then run "ollama run qwen2.5:7b" to start chatting. No extra configuration is needed. Make sure your NVIDIA drivers are up to date (545+ recommended).
The RTX 3060's 12GB of VRAM cannot fit a 32B model comfortably. The largest size class it fits is 14B, at est. 30 tok/s, typical error 15%. The largest individual model in the catalog that fits is Ministral 3 14B (14B).
Measure a fixed Ollama reference model on your machine. This separate, opt-in contribution does not change ModelFit's third-party SWE-Bench leaderboard; results appear on the measured-speed leaderboard after the next site update.
Use our interactive wizard to compare models across Apple Silicon and NVIDIA GPUs.