NVIDIA-Nemotron-3-Ultra-550B-A55B-BF16 UD-IQ4_XS

This file is exactly 286,118,723,296 bytes — 266.47 GiB / 286.12 GB at an effective 4.084 bits per weight. The nominal rate for UD-IQ4_XS is lower; mixed-precision tensors make the real figure higher, always.

From the file· 7 file(s), summed

Get it

266.47 GiB · 7 files
llama.cpp
llama-cli -hf unsloth/NVIDIA-Nemotron-3-Ultra-550B-A55B-GGUF:UD-IQ4_XS

Downloads and runs in one step, resolving the quantization by name.

Hugging Face CLI
hf download unsloth/NVIDIA-Nemotron-3-Ultra-550B-A55B-GGUF --include "UD-IQ4_XS/NVIDIA-Nemotron-3-Ultra-550B-A55B-UD-IQ4_XS-*-of-*.gguf"

This quantization is split across 7 files totalling 266.47 GiB. You need every part — the first is not a smaller version of the model.

Size
266.47 GiB
286.12 GB
Effective bpw
4.084
from real bytes ÷ params
Tensors
Header
GGUF metadata

Fit by accelerator

AcceleratorMemoryTotal @4KTotal @32KFitstok/s @4K
Arc A310 4GB4 GB267.30 GiB267.30 GiBno
Arc A350M 4GB4 GB267.30 GiB267.30 GiBno
Arc A370M 4GB4 GB267.30 GiB267.30 GiBno
Arc A530M 4GB4 GB267.30 GiB267.30 GiBno
Arc Pro A30M 4GB4 GB267.30 GiB267.30 GiBno
Radeon Pro W64004 GB267.40 GiB267.40 GiBno
Radeon RX 64004 GB267.40 GiB267.40 GiBno
Radeon RX 6500 XT4 GB267.40 GiB267.40 GiBno
RTX A4004 GB267.50 GiB267.50 GiBno
Arc A380 6GB6 GB267.30 GiB267.30 GiBno
Arc Pro A40 6GB6 GB267.30 GiB267.30 GiBno
Arc Pro A50 6GB6 GB267.30 GiB267.30 GiBno
GeForce RTX 20606 GB267.30 GiB267.30 GiBno
GeForce RTX 30506 GB267.30 GiB267.30 GiBno
GeForce RTX 3060 OEM6 GB267.30 GiB267.30 GiBno
RTX A20006 GB267.50 GiB267.50 GiBno
Apple M18 GB267.05 GiB267.05 GiBno
Apple M28 GB267.05 GiB267.05 GiBno
Apple M38 GB267.05 GiB267.05 GiBno
Apple M48 GB267.05 GiB267.05 GiBno
Arc A530M 8GB8 GB267.30 GiB267.30 GiBno
Arc A550M 8GB8 GB267.30 GiB267.30 GiBno
Arc A570M 8GB8 GB267.30 GiB267.30 GiBno
Arc A580 8GB8 GB267.30 GiB267.30 GiBno
Spec sheetPredictedwhat these mean

Memory at context

ContextWeightsKV (f16)KV (q8_0)Working bufferTotal (f16)
From the filePredictedwhat these mean

Quantizing the KV cache to q8_0 is a roughly 2× lever on the dominant term at long context, and it is the single most useful setting most local users never touch. Totals here exclude the allocator reserve your driver takes, which is hardware-specific — the per-accelerator table above includes it.