Can I run this LLM? Real file sizes, live from Hugging Face.
All models › embeddinggemma-2

embeddinggemma-2 requirements — can you run it?

~0.3B parameters · 6 quantizations measured · updated 2026-10-07 · source: unsloth/embeddinggemma-2-GGUF

Run embeddinggemma-2 (UD-Q4_K_XL) — copy-paste:
# llama.cpp (auto-downloads the GGUF)
llama-cli -hf unsloth/embeddinggemma-2-GGUF:UD-Q4_K_XL

# Ollama (pulls straight from Hugging Face)
ollama run hf.co/unsloth/embeddinggemma-2-GGUF:UD-Q4_K_XL

# LM Studio: search "unsloth/embeddinggemma-2-GGUF" in the model browser

Commands load the exact quant measured on this page.

Every quantization: real file size vs what you actually need

QuantFile (measured)VRAM/RAM needed (8K ctx)Runs on (first fit)
UD-Q4_K_XL0.2 GB1.7 GBRTX 3060 12GB
UD-Q5_K_XL0.2 GB1.8 GBRTX 3060 12GB
UD-Q6_K_XL0.2 GB1.8 GBRTX 3060 12GB
Q8_00.3 GB1.9 GBRTX 3060 12GB
BF160.6 GB2.2 GBRTX 3060 12GB
F160.6 GB2.2 GBRTX 3060 12GB

KV cache uses a flat +20% context/overhead rule because this repo does not publish its config; exact numbers may differ for long contexts. MoE models keep all experts in memory — total size counts, not just active params. Longer context grows the KV cache — use the selector above.

Can I run embeddinggemma-2 on my GPU? (UD-Q4_K_XL recommended quant)

HardwareMemoryVerdictEst. speed
RTX 3060 12GB12 GBRUNS~1537 tok/s
RTX 4060 Ti 16GB16 GBRUNS~1230 tok/s
RTX 3090 24GB24 GBRUNS~3996 tok/s
RTX 4090 24GB24 GBRUNS~4303 tok/s
RTX 5090 32GB32 GBRUNS~7651 tok/s
RTX PRO 6000 96GB96 GBRUNS~7651 tok/s
Mac 16GB unified16 GBRUNS~427 tok/s
Mac 32GB unified32 GBRUNS~640 tok/s
Mac 64GB unified64 GBRUNS~1166 tok/s
Mac 128GB unified128 GBRUNS~1708 tok/s
Mac 256GB unified256 GBRUNS~2331 tok/s
Mac 512GB unified512 GBRUNS~3497 tok/s
32GB system RAM (CPU)32 GBRUNS~213 tok/s
64GB system RAM (CPU)64 GBRUNS~213 tok/s
128GB system RAM (CPU)128 GBRUNS~342 tok/s
256GB system RAM (CPU)256 GBRUNS~342 tok/s
1TB server RAM (CPU)1024 GBRUNS~854 tok/s
2TB server RAM (CPU)2048 GBRUNS~854 tok/s

Speed = decode tok/s estimated from memory bandwidth ÷ measured file size (× MoE active share). Real numbers vary ±30% by runtime and settings.

How much VRAM does embeddinggemma-2 need?

The honest answer: 1.7 GB at the UD-Q4_K_XL quant with 8K context — that is the measured file size (0.2 GB) plus KV cache and runtime overhead. The smallest published build needs 1.7 GB; the lossless one needs 2.2 GB.
Cheapest hardware that runs it: Used RTX 3070 8GB (~$220, used market) — see which GPU to buy.

Can I run it with CPU offload?

Yes, if combined RAM+VRAM ≥ file size — but generation speed is limited by memory bandwidth. Expect roughly: DDR5 dual channel ~10-30 tok/s for small MoE actives, single digits for big ones, 0.1-1 tok/s when experts page from disk. CPU-only is fine for batch jobs, painful for chat.

Why do other sites show different numbers?

Most pages compute weights from a formula (params × bits/8). We use the actual file sizes published in GGUF repos, which include the embedding table, unquantized tensors, and container overhead — that is why our numbers can differ from a naive calculation.

FAQ

How much VRAM does embeddinggemma-2 need?

The measured answer: 1.7 GB at the UD-Q4_K_XL quant with 8K context. The smallest published build needs 1.7 GB; the lossless (F16/BF16) build needs 2.2 GB. These are real GGUF file sizes from Hugging Face, not formula estimates.

Can I run embeddinggemma-2 on a 24GB GPU (RTX 3090/4090)?

Yes — at UD-Q4_K_XL (1.7 GB). Quants that fit 24GB: UD-Q4_K_XL, UD-Q5_K_XL, UD-Q6_K_XL, Q8_0, BF16, F16.

How fast will embeddinggemma-2 run?

Decode speed is memory-bandwidth-bound. At UD-Q4_K_XL: roughly 4303 tok/s on an RTX 4090, 3996 tok/s on an RTX 3090, 1708 tok/s on an M-series Mac with 128GB, and 213.5 tok/s on CPU with dual-channel DDR4 — estimates from measured file size, MoE active-parameter share and memory bandwidth.

Can I run embeddinggemma-2 on CPU with system RAM?

Yes, if your usable RAM is at least the file size. At UD-Q4_K_XL you need ~1.7 GB of RAM. CPU generation is memory-bandwidth-bound: expect single-digit tok/s for large MoE models, 10-30 tok/s for small active params, and below 1 tok/s when experts page from disk.

Why do VRAM numbers for embeddinggemma-2 differ between sites?

Most sites compute weights from a formula (params x bits/8). ModelFit uses the actual GGUF file sizes published on Hugging Face, which include the embedding table, unquantized tensors, and container overhead — so our numbers reflect what you really download and load.

More models

Qwen3.8-27Bmeasured requirementsTernary-Bonsai-2-27Bmeasured requirementsOrnith-1.5-35B-A3Bmeasured requirementsQwen3.8-Flash-Next-GSQ-RCOmeasured requirementsOrnith-1.0-9Bmeasured requirementsQwen3.8-27B-Uncensoredmeasured requirementsHuihui-Qwen3.8-27B-abliteratedmeasured requirementsQwen3.8-27B-TURBO-Fable-Cold-Fusion-735-882-Heretic-Uncensored-NEO-CODER-MAX-MTPmeasured requirements
Share this page: 𝕏 Post Reddit Hacker News Telegram WhatsApp More…