What GPU do I need to run meta-llama/Llama-3.2-90B-Vision-Instruct?

88.6B parameters, published in BF16. View on Hugging FaceGated

88.6B
Parameters
BF16
Native precision
MllamaForConditionalGeneration
Architecture
image-text-to-text
Pipeline

Llama-3.2-90B-Vision-Instruct is published by meta-llama on Hugging Face, with 103,812 downloads and 358 likes to date. It's a MllamaForConditionalGeneration model built for image-text-to-text, published natively in BF16, 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.

PrecisionWeight sizeRequired VRAMCheapest live fitGPUs neededEst. $/hr (full fit)
BF16165.0 GB198.0 GBRTX A60005$1.81/hr
FP8 (quantized)82.5 GB99.0 GBAMD MI300X1$2.63/hr
cheaper alt.RTX 4000 SFF Ada5$0.990/hr
INT4 (quantized)41.3 GB49.5 GBA1001$1.21/hr
cheaper alt.RTX A50003$0.528/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 Llama-3.2-90B-Vision-Instruct at its published (BF16) precision: 5× RTX A6000, at $0.363/hr per GPU ($1.81/hr total). Quantizing to FP8 or INT4 (rows above) can cost less, but requires a compatible quantized checkpoint to exist for this model.

Llama-3.2-90B-Vision-Instruct: 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.

Grouped-query attention: every layer caches keys and values for a few shared KV heads. Cached per token: 409,600 bytes at 16-bit.

ContextKV cache, one sequence
4K1.6 GB
32K12.5 GB
128K50.0 GB

Computed from the layer, head and window counts in the model's own configuration (unsloth/Llama-3.2-90B-Vision-Instruct), at 16 bits per cached value. Each concurrent sequence needs its own cache, on top of the weights.

Llama-3.2-90B-Vision-Instruct: common questions

Can Llama-3.2-90B-Vision-Instruct run on a single GPU?

No. At BF16 it needs 198.0 GB of VRAM, more than a single 32 GB desktop card holds. The cheapest capable card in the live feed is a 48.0 GB RTX A6000, and it takes 5 of them.

Do I need approval to download Llama-3.2-90B-Vision-Instruct?

Yes. meta-llama 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 198.0 GB the model needs once you have them.

How many GPUs do I need to run Llama-3.2-90B-Vision-Instruct?

5 at BF16. It needs 198.0 GB of VRAM and the cheapest capable live offer is a 48.0 GB RTX A6000, so 5 of them come to $1.81/hr in total.

Does quantizing Llama-3.2-90B-Vision-Instruct lower the GPU bill?

Yes. At BF16 the cheapest live fit is 5 RTX A6000 cards at $1.81/hr. At INT4 (quantized) it drops to one A100 at $1.21/hr, provided a quantized checkpoint exists for it.

Weight-to-VRAM math, the fit rules, and how live prices are normalized: full methodology.

More Llama 3.2 models

All 15 Llama 3.2 models: VRAM and GPU requirements

Alternatives at this size

Other models for image-text-to-text within about a third of Llama-3.2-90B-Vision-Instruct's 88.6B parameters, from other model lines.

More on Llama-3.2-90B-Vision-Instruct

Related reading: RTX A6000 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.

Submit the job. Everything after that is ours.

Sign up in 60 seconds. Pay for the GPU minutes you actually use.

© 2026 Aquanode. All rights reserved.

All trademarks, logos and brand names are the property of their respective owners.