Can I run Qwen3 14B on the GeForce RTX 5060 Ti 16GB?

Runs greatQ4_K_M fits in VRAM with 4.5 GB to spare: Runs great, est. 30.3 tok/s (26.7–34.0, calibrated estimate ±12%).

16 GB VRAM · 448.0 GB/s · FP16 23.7 TFLOPS. Assumes 32 GB of DDR5-5600 system RAM, Windows with this GPU driving the display, 8k context and an f16 KV cache.

Every quant of Qwen3 14B on the GeForce RTX 5060 Ti 16GB

4 tracked GGUF files, smallest first, at 8k context
QuantFile sizeVerdictSpeedMemoryRuns asNotes
Q2_K5.75 GBRuns great
est. 44.2 tok/s38.9–49.5calibrated estimate ±12%
8.3 / 16.0 GBFull GPU—
IQ4_XS8.14 GBRuns great
est. 33.1 tok/s29.1–37.0calibrated estimate ±12%
10.7 / 16.0 GBFull GPU—
Q4_K_Mbaseline9.00 GBRuns great
est. 30.3 tok/s26.7–34.0calibrated estimate ±12%
11.5 / 16.0 GBFull GPU—
Q8_015.70 GBRuns slowly
est. 10.0 tok/s8.0–12.0calibrated estimate ±20%
16.0 / 16.0 GB + 2.2 GB RAMPartial offloadLess than 90% on the GPU — a GPU/CPU split is capped at Runs slowly

Where the memory goes at Q4_K_M

Weights, KV cache and compute buffer are the model; the OS reservation is the display driver.
GPU memory
Weights
9.0 GB
KV cache
1.3 GB
Compute buffer
0.6 GB
OS reserve
0.6 GB
Free
4.5 GB

Context length vs. KV cache

KV cache

Memory needed and verdict at Q4_K_M for each context length and KV cache type, with estimated tokens per second.
ContextKV f16KV q8_0KV q4_0
4k
10.2 GBRuns great
est. 32.4 tok/s28.5–36.3calibrated estimate ±12%
9.9 GBRuns great
est. 33.5 tok/s29.5–37.5calibrated estimate ±12%
9.7 GBRuns great
est. 34.1 tok/s30.0–38.2calibrated estimate ±12%
8k
10.9 GBRuns great
est. 30.3 tok/s26.7–34.0calibrated estimate ±12%
10.3 GBRuns great
est. 32.3 tok/s28.4–36.1calibrated estimate ±12%
10.0 GBRuns great
est. 33.4 tok/s29.4–37.4calibrated estimate ±12%
16k
12.3 GBRuns great
est. 26.8 tok/s23.6–30.1calibrated estimate ±12%
11.1 GBRuns great
est. 30.0 tok/s26.4–33.7calibrated estimate ±12%
10.4 GBRuns great
est. 32.1 tok/s28.3–36.0calibrated estimate ±12%
32k
15.2 GBRuns great
est. 21.8 tok/s19.2–24.4calibrated estimate ±12%
12.7 GBRuns great
est. 26.4 tok/s23.2–29.6calibrated estimate ±12%
11.3 GBRuns great
est. 29.8 tok/s26.2–33.4calibrated estimate ±12%

S = Runs great · A = Runs well · B = Runs slowly · F = Won't run

At Q4_K_M the verdict stays Runs great up to 32k context with an f16 KV cache, and up to 32k with q8_0.

Estimated speed

Generation
est. 30.3 tok/s (26.7–34.0, calibrated estimate ±12%)
Prompt processing
about 3,318 tok/s (1,991–4,645, rough estimate ±40%)

Measured on this exact combination

No public measurement for this exact combination yet; the numbers above are estimates.

If this is not enough

How to run it

Commands for the Q4_K_M file. Both tools download from Hugging Face on first run.

File: Qwen3-14B-Q4_K_M.gguf (9.00 GB) from unsloth/Qwen3-14B-GGUF.

llama.cpp
llama-server -hf unsloth/Qwen3-14B-GGUF:Q4_K_M -c 8192 -ngl all -fa on
  • -ngl all loads every layer on the GPU.
  • -fa on enables flash attention (needed for KV cache quantization).
  • --cache-type-k q8_0 --cache-type-v q8_0 shrinks the KV cache to 0.72 GB at 8k context.
Ollama

PowerShell (quit the Ollama tray app first):

$env:OLLAMA_CONTEXT_LENGTH="8192"; ollama serve
ollama run hf.co/unsloth/Qwen3-14B-GGUF:Q4_K_M
  • Ollama defaults to 4k context on GPUs under 24 GB. Set OLLAMA_CONTEXT_LENGTH when starting the server, or /set parameter num_ctx inside the chat.
  • /set parameter num_ctx 8192

Related pages

Frequently asked questions

Can I run Qwen3 14B on the GeForce RTX 5060 Ti 16GB?

Q4_K_M fits in VRAM with 4.5 GB to spare: Runs great, est. 30.3 tok/s (26.7–34.0, calibrated estimate ±12%). Q4_K_M needs 10.9 GB at 8k context; this setup has 15.4 GB of usable memory and 28.0 GB of free system RAM.

How much context can Qwen3 14B use on the GeForce RTX 5060 Ti 16GB?

At Q4_K_M the verdict stays Runs great up to 32k context with an f16 KV cache (5.4 GB of KV) and up to 32k with a q8_0 KV cache (2.9 GB). The model supports up to 32k.

Which quant should I use, and how fast is it?

Q4_K_M (9.00 GB) is the recommended balance: Runs great, est. 30.3 tok/s (26.7–34.0, calibrated estimate ±12%). It is also the largest tracked file that gets this verdict.

Speeds are estimates from memory bandwidth, calibrated against public benchmarks, and each one comes with an error band and a confidence label. Real results vary with drivers, backend, context length and thermals.