ThinkFacility

Open models on your own hardware

Can I run it locally? How much VRAM open models need

Pick your graphics card, Mac or DGX Spark to see which open models fit, or open a family for every size and quant. File sizes come from Hugging Face, the rest is arithmetic on each model's config, and it's redone every day.

What can my machine run?

Each model at its common 4-bit file. Family pages have every quant.

Model families

66 models across 10 families. Dots are each model at 4-bit with a 32K context, on a scale from 1 GB to 2 TB; the marks are 8, 24, 128 and 512 GB.

What we found

The weights are only half the question. The other half is the context cache, the keys and values a model keeps for every token it has read, and it varies wildly. Llama 3.3 70B at its full 128K context carries 42.9 GB of cache, roughly the size of its 4-bit weights. Qwen3.6 35B A3B, a year and a half newer, needs 5.4 GB for twice the context.

Two unit traps catch people out. A "24 GB" graphics card holds 24 GiB, which is about 25.8 GB in the decimal units Hugging Face uses for file sizes, so a 25 GB total does fit. Macs go the other way: macOS lets the GPU use only two thirds of unified memory up to 32 GB and three quarters above, so a 64 GB Mac starts out with 48 GB for the model.

The download counts were a surprise too. The most downloaded GGUF in Unsloth's catalog is Qwen3 Coder 30B A3B, from July 2025, at 11.6 million in the last 30 days. It fits a 24 GB card at 4-bit. Whether any of this saves money is another question, and we priced a home rig against a subscription to find out.

How the numbers are worked out

Total memory is three parts added together. Weights are the exact size of the GGUF file on Hugging Face, all parts summed when a quant is split. The context cache (the KV cache) comes from each model's own config.json:

cache = layers × kv_heads × head_dim × 2 (K and V) × 2 bytes × tokens

Sliding-window layers stop at their window plus llama.cpp's 512-token batch. Linear-attention and Mamba layers keep a fixed state instead, which we add once. Latent-attention models (DeepSeek, Kimi, GLM-5) cache kv_lora_rank + rope dimensions per layer, the way llama.cpp does. Overhead is our allowance: 0.5 GB for the GPU context plus the output buffer, 512 × vocabulary × 4 bytes.

A "24 GB" card holds 24 GiB, which is 25.8 GB in the decimal units file sizes use, and we count it that way. Macs get the share Metal allows by default, two thirds of unified memory up to 32 GB and three quarters above (llama.cpp discussion 2182); CPU-only machines and the DGX Spark keep 4 GB back for the operating system. All of it assumes llama.cpp's defaults: an f16 cache and one conversation at a time. Quantizing the cache to q8_0 halves it.

Files are Unsloth's GGUF uploads, the most downloaded quantizations on Hugging Face, and the list refreshes daily from Hugging Face's API. A model joins when its repo passes 20,000 downloads in 30 days. Last checked September 25, 2026.