← All modelsMODEL CHECK

Can I run Qwen3-VL 8B?

Qwen3-VL 8B by Alibaba needs around 8 GB of RAM at the recommended 4-bit quantization (4.9 GB download). Your hardware is checked below β€” instantly, nothing leaves your browser. Expect roughly ~63 tok/s on a NVIDIA RTX 3060 12GB.

Reading your hardware signals…

Real-world notes

Qwen3-VL 8B is Alibaba's vision-capable model in the 8B class, which makes it the one to reach for when you want a local assistant that can actually look at images and screenshots, not just read text. At a 4-bit quant it lands around 4.9 GB, so it fits on a 12 GB card like an RTX 3060 with room to spare and sits comfortably in unified memory on any Apple Silicon Mac. The minimum sensible footprint is about 8 GB of RAM, and if you are tight you can drop to a 2-bit build at roughly 3.4 GB, though the heavier q8 weighs in near 8.5 GB.

In daily use it feels quick for an 8B model. On an RTX 3060 you can expect around 63 tokens per second at 4-bit, and an M-series Max pushes that to roughly 72, both fast enough that replies stream faster than you read; a 4090 runs away at about 177. The headline number is the 256K context window, but treat it as a ceiling, not a default. At 128K context the model plus KV cache already needs around 21.7 GB total, well past what a single mid-range card holds, so keep working context modest unless you have a big GPU.

Against Llama 3.1 8B, which is the obvious same-size point of comparison, Qwen3-VL's standout is the thing Llama simply cannot do: it reads images. For plain text chat the two are close enough that the choice comes down to whether you need vision. If you only ever feed it text, Llama still has the deeper tooling ecosystem; if you want to describe screenshots or pull text out of a photo locally, this is the better tool. It ships under Apache 2.0, so you can use it commercially and in production without license worries.

Specifications

Parameters8B
Context window256K tokens
ProviderAlibaba
LicenseApache 2.0
Released2025-10
Best forVision, Chat

Size by quantization

QuantizationBits/weightDownloadMin RAMQuality
Q2_K3.353.4 GB6 GBNoticeable loss
Q4_K_MRecommended4.854.9 GB8 GBRecommended
Q5_K_M5.655.7 GB12 GBHigh
Q8_08.58.5 GB16 GBNear-original
F161616.0 GB24 GBOriginal

Sizes are estimates from parameter count Γ— bits per weight; real GGUF builds vary slightly. Β· Data updated: 2026-06-11 Β· How we calculate these numbers β†’

Memory needed by context length

ContextKV cache (est.)Total memory (Q4)
4K tokens~0.5 GB~5.4 GB
8K tokens~1.0 GB~5.9 GB
32K tokens~4.2 GB~9.1 GB
128K tokens~16.8 GB~21.7 GB

The KV cache grows with context length β€” a model that fits at 4K can run out of memory at 32K. Estimates assume an FP16 cache with grouped-query attention; actual usage varies by runtime.

Estimated speed by hardware

HardwareBandwidth~Speed
NVIDIA RTX 3060 12GB360 GB/s~63 tok/s
NVIDIA RTX 4090 24GB1008 GB/s~177 tok/s
Apple M-series (base)100 GB/s~18 tok/s
Apple M-series Pro270 GB/s~47 tok/s
Apple M-series Max410 GB/s~72 tok/s
CPU only (dual-channel DDR5)60 GB/s~11 tok/s

Token generation is memory-bandwidth bound: tok/s β‰ˆ bandwidth Γ— 0.85 Γ· model size at Q4. Real-world numbers vary by runtime and context length.

Run it locally

The easiest path is Ollama β€” one command and you're chatting:

ollama run qwen3-vl:8b

Frequently asked questions

Qwen3-VL 8B System Requirements β€” Can I Run It Locally?