GitMylo · text

nsfwvision-qwen3-vl-8b-v3-safetensors

GitMylo/nsfwvision-qwen3-vl-8b-v3-safetensors

nsfwvision-qwen3-vl-8b-v3-safetensors at Q8_0 is exactly 8,709,519,616 bytes (8.11 GiB / 8.71 GB) — an effective 7.947 bits per weight, not the nominal 8. Its KV cache at 32K is 4.50 GiB.

From the file· summed from 1 file(s)From the file· KV per layer
Parameters
8.8B
Architecture
qwen3vl
36 layers
Context
262,144
native (config.json)
License
apache-2.0

Shipped quantizations

exact bytes, summed from published files
QuantSizeExact bytesEffective bpwTensorsPublisher
Q8_08.11 GiB8,709,519,6167.947dummy9996

KV cache by context

computed per layer
ContextKV cache (f16)Flat formulaOverstated byFull / windowed / recurrent
4,0960.56 GiB0.56 GiB36 / 0 / 0
8,1921.13 GiB1.13 GiB36 / 0 / 0
16,3842.25 GiB2.25 GiB36 / 0 / 0
32,7684.50 GiB4.50 GiB36 / 0 / 0
65,5369.00 GiB9.00 GiB36 / 0 / 0
131,07218.00 GiB18.00 GiB36 / 0 / 0

Compare with

same modality, comparable size

Will it run on your card?

full quant x context sweep

Why other calculators give a different number

A parameters × bits ÷ 8 estimate puts Q8_0 at roughly 4.59 GiB. The real file is 8.11 GiB, because a quantization is a mixture and some tensors are always kept at higher precision.

Architecture

from config.json
Layers
36
Attention heads
32
KV heads
8
Head dim
128
Hidden size
4096
Vocab
151,936
Sliding window
none
SWA period
MLA
no
Experts
Experts per token
use_sliding_window

Questions people ask

How much VRAM does nsfwvision-qwen3-vl-8b-v3-safetensors need?
Q8_0 is exactly 8,709,519,616 bytes (8.11 GiB) in weights. Add the KV cache, which depends on your context length, plus roughly half a gigabyte of runtime overhead.
How large is nsfwvision-qwen3-vl-8b-v3-safetensors's KV cache?
4.50 GiB at 32K context with an f16 cache, computed per layer. Quantizing the cache to q8_0 roughly halves it, which is often the difference between a context length fitting and not.
Which quantization of nsfwvision-qwen3-vl-8b-v3-safetensors should I use?
Q4_K_M is the usual default. Pick the largest quantization that fits your card at the context you actually need — the table above gives exact sizes for every one published.