Qwen3-VL-8B-Instruct on RTX 5090: Runs comfortably (Sep 2026)

Conditional memory judgement for one configuration. Change context, quant, or engine and the conclusion can change. Configuration used on this page: BF16 safetensors, 8,192 cached tokens, 1 sequence, engine vllm. Status: Likely fits. Software: Not verified..

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

Verdict on GeForce RTX 5090 32GB (desktop)

Yes, run Q8_0. The calculator puts it at 9.4 GiB–10.0 GiB at 8,192 tokens, inside 30.0 GiB of usable VRAM (after the driver reserve).

With Q8_0, the longest context that still counts as a fit is about 124,037 tokens of a 262,144-token native window, one sequence, fp16 KV cache.

Published GGUF quants for Qwen3-VL-8B-Instruct on GeForce RTX 5090 32GB (desktop) at 8,192 tokens
GGUF quantFile weightsKV cacheEstimated totalVerdict
Q8_0 (recommended)8.1 GiB1.1 GiB9.4 GiB–10.0 GiBComfortable
Q6_K6.3 GiB1.1 GiB7.5 GiB–8.1 GiBComfortable
Q5_K_M5.4 GiB1.1 GiB6.7 GiB–7.3 GiBComfortable
Q4_K_M4.7 GiB1.1 GiB5.9 GiB–6.5 GiBComfortable

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

Qwen3-VL-8B-Instruct BF16 safetensors on the catalog RTX 5090 32 GB SKU. The page uses that published artifact and the calculator; it is not a new measurement.

Technical identifiers and share data
  • Modelqwen3-vl-8b-instruct
  • Hardwarenvidia-geforce-rtx-5090-32gb-desktop
  • Quantizationbf16
  • Share fragment for this identityv2.eyJzY2hlbWFWZXJzaW9uIjoyLCJjYWxjdWxhdG9yVmVyc2lvbiI6IjAuMy4wIiwiZGF0YXNldFZlcnNpb24iOiIyMDI2LTEwLTAyLjEiLCJjb25maWciOnsibW9kZWxJZCI6InF3ZW4zLXZsLThiLWluc3RydWN0IiwiaGFyZHdhcmVJZCI6Im52aWRpYS1nZWZvcmNlLXJ0eC01MDkwLTMyZ2ItZGVza3RvcCIsImRldmljZUNvdW50IjoxLCJxdWFudGl6YXRpb25JZCI6ImJmMTYiLCJjb250ZXh0VG9rZW5zIjo4MTkyLCJjb25jdXJyZW50U2VxdWVuY2VzIjoxLCJlbmdpbmUiOiJ2bGxtIiwia3ZUeXBlIjoiZnAxNiJ9fQ

Memory breakdown

Weight artifact
16.33 GiB (17,534,247,392 bytes)
Raw KV cache
1.13 GiB (1,207,959,552 bytes)
Engine extras / workspace
0.63 GiB–2.53 GiB
Total estimated demand
18.08 GiB–19.99 GiB
Net calculator budget
30.00 GiB
OS / display reserve
2.00 GiB
Remaining vs net budget
10.01 GiB–11.92 GiB

19.99 GiB high estimate vs 30.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 safetensors This pagevllm18.08 GiB–19.99 GiBRuns comfortably
GGUF Q8_0 (Qwen)llama.cpp9.36 GiB–9.98 GiBRuns comfortably
GGUF Q6_K (Unsloth)llama.cpp7.51 GiB–8.09 GiBRuns comfortably
GGUF Q5_K_M (Unsloth)llama.cpp6.70 GiB–7.26 GiBRuns comfortably
GGUF Q4_K_M (Qwen)llama.cpp5.93 GiB–6.48 GiBRuns comfortably

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.