Qwen3-14B on RTX 5080: Fits (Sep 2026)

Conditional memory judgement for one configuration. Change context, quant, or engine and the conclusion can change. Configuration used on this page: GGUF Q5_K_M (Qwen), 8,192 cached tokens, 1 sequence, engine llama.cpp. Status: Likely fits. Software: Not verified..

Likely fitsNot verifiedThis result is an estimate, not a measured trace.

Verdict on GeForce RTX 5080 16GB (desktop)

Yes, run Q5_K_M. The calculator puts it at 11.2 GiB–11.8 GiB at 8,192 tokens, inside 14.0 GiB of usable VRAM (after the driver reserve). Q8_0 is the next step up and does not clear the bar (16.0 GiB–16.8 GiB).

With Q5_K_M, the longest context that still counts as a fit is about 12,933 tokens of a 40,960-token native window, one sequence, fp16 KV cache.

Published GGUF quants for Qwen3-14B on GeForce RTX 5080 16GB (desktop) at 8,192 tokens
GGUF quantFile weightsKV cacheEstimated totalVerdict
Q8_014.6 GiB1.3 GiB16.0 GiB–16.8 GiBDoes not fit
Q6_K11.3 GiB1.3 GiB12.7 GiB–13.4 GiBTight
Q5_K_M (recommended)9.8 GiB1.3 GiB11.2 GiB–11.8 GiBFits
Q4_K_M8.4 GiB1.3 GiB9.8 GiB–10.4 GiBFits

Engine llama.cpp, one sequence, fp16 KV. File weights are the published GGUF sizes in the catalog. Totals come from the same calculator that powers the tool below; they are estimates, not a measurement of this setup.

Fixed page configuration

GGUF Q5_K_M needs 11.2 GiB-11.8 GiB at 8,192 tokens against 14.00 GiB net on GeForce RTX 5080 16GB (desktop). Q8_0, Q6_K are tight or over budget.

Technical identifiers and share data
  • Modelqwen3-14b
  • Hardwarenvidia-geforce-rtx-5080-16gb-desktop
  • Quantizationgguf-q5_k_m
  • Share fragment for this identityv2.eyJzY2hlbWFWZXJzaW9uIjoyLCJjYWxjdWxhdG9yVmVyc2lvbiI6IjAuMy4wIiwiZGF0YXNldFZlcnNpb24iOiIyMDI2LTEwLTAyLjEiLCJjb25maWciOnsibW9kZWxJZCI6InF3ZW4zLTE0YiIsImhhcmR3YXJlSWQiOiJudmlkaWEtZ2Vmb3JjZS1ydHgtNTA4MC0xNmdiLWRlc2t0b3AiLCJkZXZpY2VDb3VudCI6MSwicXVhbnRpemF0aW9uSWQiOiJnZ3VmLXE1X2tfbSIsImNvbnRleHRUb2tlbnMiOjgxOTIsImNvbmN1cnJlbnRTZXF1ZW5jZXMiOjEsImVuZ2luZSI6ImxsYW1hLmNwcCIsImt2VHlwZSI6ImZwMTYifX0

Memory breakdown

Weight artifact
9.79 GiB (10,514,569,568 bytes)
Raw KV cache
1.25 GiB (1,342,177,280 bytes)
Engine extras / workspace
0.13 GiB–0.78 GiB
Total estimated demand
11.17 GiB–11.83 GiB
Net calculator budget
14.00 GiB
OS / display reserve
2.00 GiB
Remaining vs net budget
2.17 GiB–2.83 GiB

11.83 GiB high estimate vs 14.00 GiB net

Enough memory does not mean this engine, quant, and OS will run. Support does not mean it will be fast.

Other published files on this device

Same model, device and context (8,192 tokens, 1 sequence, FP16 KV). Each row is one published weight-file set with its usual engine, sorted by memory.

QuantizationEngineEstimated memoryFit
BF16 safetensorsvllm29.38 GiB–31.30 GiBDoes not fit
GGUF Q8_0 (Qwen)llama.cpp16.00 GiB–16.75 GiBDoes not fit
GGUF Q6_K (Qwen)llama.cpp12.66 GiB–13.35 GiBTight fit
GGUF Q5_K_M (Qwen) This pagellama.cpp11.17 GiB–11.83 GiBFits
GGUF Q4_K_Mllama.cpp9.76 GiB–10.39 GiBFits

Assumptions that affect this result

Open this combo in the calculatorKV Cache

Related pages

Sources

Calculator

This combo page keeps the route model and device. Customize to change them on the main calculator; the share then keeps that identity.

Loading catalog snapshot…

Choose a model first, then check a device.

Quantization

Device type

Workload

Context length primarily affects KV cache memory.

Advanced settings
Runtime

Engine and KV cache type for this estimate.

Workload

Overhead scenario and the prefill workspace.

Topology

How the model is split across devices. Memory is not added together.

Replica count is an advanced deployment option. Quantity is nodes or GPUs, not replicas.

Budget

System reserve and safety margin. An empty number keeps the previous value.

GiB (2^30 bytes)

%

Custom model

Import a config or type the architecture. Nothing is scanned until you import.

Parsed in the browser. The file is not uploaded.

Only huggingface.co, config.json, no token. Private repos are rejected.

Search or pick a catalog checkpoint to see memory demand.

Search or pick a catalog checkpoint to see memory demand.