What GPU do I need to run orcarouter/Qwen3.8-Flash-Next-Uncensored-FP8?
180.0B parameters, published in F8_E4M3. View on Hugging FaceGated
Qwen3.8-Flash-Next-Uncensored-FP8 is published by orcarouter on Hugging Face, with 1,874 downloads and 16 likes to date. It's a Qwen4ExpForConditionalGeneration model built for image-text-to-text, published natively in F8_E4M3, and gated: you'll need to accept the model's terms on Hugging Face before downloading weights.
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) | 167.6 GB | 201.2 GB | RTX 5000 Ada | 7 | $3.77/hr |
| INT4 (quantized) | 83.8 GB | 100.6 GB | AMD MI300X | 1 | $2.63/hr |
| cheaper alt. | RTX A5000 | 5 | $0.880/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-Flash-Next-Uncensored-FP8 at its published (F8_E4M3) precision: 7× RTX 5000 Ada, at $0.539/hr per GPU ($3.77/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-Flash-Next-Uncensored-FP8: 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.
KV-cache size for Qwen3.8-Flash-Next-Uncensored-FP8 is not published for this architecture, so no figure is shown.
Qwen3.8-Flash-Next-Uncensored-FP8: common questions
Can Qwen3.8-Flash-Next-Uncensored-FP8 run on a single GPU?
No. At FP8 (native) it needs 201.2 GB of VRAM, more than a single 32 GB desktop card holds. The cheapest capable card in the live feed is a 32.0 GB RTX 5000 Ada, and it takes 7 of them.
Do I need approval to download Qwen3.8-Flash-Next-Uncensored-FP8?
Yes. orcarouter gates this repository on Hugging Face, so you have to accept its terms with a signed-in account before the weights will download. It does not change the 201.2 GB the model needs once you have them.
Is Qwen3.8-Flash-Next-Uncensored-FP8 already quantized?
Yes. It is published in FP8, one byte per parameter, so the 201.2 GB figure is already a quantized footprint rather than a full-precision one. Only INT4 goes below it, at 100.6 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.
How many GPUs do I need to run Qwen3.8-Flash-Next-Uncensored-FP8?
7 at FP8 (native). It needs 201.2 GB of VRAM and the cheapest capable live offer is a 32.0 GB RTX 5000 Ada, so 7 of them come to $3.77/hr in total.
Weight-to-VRAM math, the fit rules, and how live prices are normalized: full methodology.
More Qwen3.8 models
- Qwen3.8-Flash-Next (180.0B, BF16)
- Qwen3.8-Flash-Next-FP8 (180.0B, F8_E4M3)
- Qwen3.8-Flash-Next-FP8 (180.0B, F8_E4M3)
- CYBER-FROST-3.8-BF16 (180.0B, BF16)
- Qwen3.8-Flash-Next-Uncensored (180.0B, BF16)
Lineage
Based on Qwen3.8-Flash-Next.
Alternatives at this size
Other models for image-text-to-text within about a third of Qwen3.8-Flash-Next-Uncensored-FP8's 180.0B parameters, from other model lines.
- Inkling-Small (266.0B, BF16)
- Intern-S1 (240.7B, BF16)
- Darwin-180B-RSI (180.0B, BF16)
More on Qwen3.8-Flash-Next-Uncensored-FP8
Fits on a 288 GB GPU at FP8: every model that fits in 288 GB.
Fits on a 141 GB GPU at INT4: every model that fits in 141 GB.
Related reading: H100 pricing and specs, How much VRAM you need for LLMs, Serving LLMs with vLLM, vLLM vs TensorRT-LLM vs SGLang, and Best GPU for LLM inference.
Your own GPU cloud accounts
One console for the GPU clouds you already rent from. Your keys stay on your machine.
$20 a month, flat