What GPU do I need to run unsloth/Qwen3.8-27B-NVFP4?
19.9B parameters, published in F8_E4M3. View on Hugging Face
Set up Qwen3.8-27B-NVFP4Qwen3.8-27B-NVFP4 is published by unsloth on Hugging Face, with 2,588,917 downloads and 404 likes to date. It's a Qwen3_5ForConditionalGeneration model built for text-generation, published natively in F8_E4M3.
VRAM required & cheapest live GPU fit
Required VRAM = weight size at each precision times a flat 1.2 overhead for activations and fragmentation. The KV-cache grows with context and is not in that factor; it is listed per model below where the architecture is published. Full formula and assumptions: methodology.
| Precision | Weight size | Required VRAM | Cheapest live fit | GPUs needed | Est. $/hr (full fit) |
|---|---|---|---|---|---|
| FP8 (native) | 18.5 GB | 22.2 GB | RTX 4090 | 1 | $0.374/hr |
| INT4 (quantized) | 9.3 GB | 11.1 GB | RTX A4000 | 1 | $0.167/hr |
A GPU is only matched to a row if its hardware supports that precision, and the primary recommendation is always a single-GPU fit when one exists.
INT4 requires a quantized checkpoint actually published for this model, check its Hugging Face page before relying on this row.
Cheapest way to run Qwen3.8-27B-NVFP4 at its published (F8_E4M3) precision: 1× RTX 4090, at $0.374/hr per GPU ($0.374/hr total). Quantizing to FP8 or INT4 (rows above) can cost less, but requires a compatible quantized checkpoint to exist for this model.
Qwen3.8-27B-NVFP4: KV cache by context length
The KV cache is the memory the attention layers hold for every token of context, on top of the weights. It is not part of the flat 1.2x overhead in the table above, grows with context length and with every concurrent request, and is why a long-context deployment needs more VRAM than the table shows.
Hybrid: only the full-attention layers cache per token; the other layers keep a fixed-size state. Cached per token: 65,536 bytes at 16-bit.
| Context | KV cache, one sequence |
|---|---|
| 4K | 0.25 GB |
| 32K | 2.0 GB |
| 128K | 8.0 GB |
| 256K (model maximum) | 16.0 GB |
Computed from the layer, head and window counts in the model's own configuration (unsloth/Qwen3.8-27B-NVFP4), at 16 bits per cached value. Each concurrent sequence needs its own cache, on top of the weights.
Qwen3.8-27B-NVFP4: common questions
Does Qwen3.8-27B-NVFP4 fit on a 24 GB GPU?
Yes. At FP8 (native) it needs 22.2 GB of VRAM, so a 24 GB card holds it with 1.8 GB to spare. A 16 GB card is not enough for it at FP8 (native).
Is Qwen3.8-27B-NVFP4 already quantized?
Yes. It is published in FP8, one byte per parameter, so the 22.2 GB figure is already a quantized footprint rather than a full-precision one. Only INT4 goes below it, at 11.1 GB. A GPU without FP8 tensor cores cannot run it as published, which is why cards here are matched on precision support and not on VRAM alone.
What is the least VRAM Qwen3.8-27B-NVFP4 can run in?
11.1 GB, at INT4 (quantized), which fits a 12 GB card, against 22.2 GB at FP8 (native). That row assumes an INT4 checkpoint has actually been published for this model, so check its Hugging Face page before planning around it.
Does quantizing Qwen3.8-27B-NVFP4 lower the GPU bill?
Yes. At FP8 (native) the cheapest live fit is one RTX 4090 at $0.374/hr. At INT4 (quantized) it drops to one RTX A4000 at $0.167/hr, provided a quantized checkpoint exists for it.
Weight-to-VRAM math, the fit rules, and how live prices are normalized: full methodology.
More Qwen3.8 models
- Qwen3.8-27B-ABLITERATED-UNCENSORED-PHILADELPHIA-CLASS (27.4B, BF16)
- Ektome-Qwen3.8-27B-PristinelyUncensored (27.4B, BF16)
- clef (27.4B, BF16)
- AREX-2 (27.4B, BF16)
- Holo4-27B (27.4B, BF16)
Lineage
Based on Qwen3.8-27B.
More on Qwen3.8-27B-NVFP4
Fits on a 24 GB GPU at FP8: every model that fits in 24 GB.
Fits on a 12 GB GPU at INT4: every model that fits in 12 GB.
Related reading: RTX 4090 pricing and specs, How much VRAM you need for LLMs, and What AI inference is.
