What GPU do I need to run google/embeddinggemma-2?

744M parameters, published in BF16. View on Hugging Face

744M
Parameters
BF16
Native precision
EmbeddingGemma2Model
Architecture
feature-extraction
Pipeline

embeddinggemma-2 is published by google on Hugging Face, with 475,436 downloads and 3,215 likes to date. It's a EmbeddingGemma2Model model built for feature-extraction, published natively in BF16.

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)
BF161.4 GB1.7 GBRTX 30701$0.088/hr
FP8 (quantized)0.7 GB0.8 GBRTX 5060 Ti1$0.180/hr
INT4 (quantized)0.3 GB0.4 GBRTX 30701$0.088/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 embeddinggemma-2 at its published (BF16) precision: 1× RTX 3070, at $0.088/hr per GPU ($0.088/hr total). Quantizing to FP8 or INT4 (rows above) can cost less, but requires a compatible quantized checkpoint to exist for this model.

embeddinggemma-2: 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.

Sliding-window attention: windowed layers stop growing at the window, the full-attention layers keep growing. Cached per token: 49,152 bytes at 16-bit while the context is inside the window.

ContextKV cache, one sequence
4K0.05 GB
32K0.27 GB
128K1.0 GB
256K (model maximum)2.0 GB

Computed from the layer, head and window counts in the model's own configuration (google/embeddinggemma-2), at 16 bits per cached value. Each concurrent sequence needs its own cache, on top of the weights.

embeddinggemma-2: common questions

How much VRAM does embeddinggemma-2 need?

1.7 GB at BF16, 0.8 GB at FP8 (quantized), 0.4 GB at INT4 (quantized). All of those sit under 6 GB, the smallest capacity this page reasons about, so VRAM is not what limits where this model runs. The 1.4 GB of weights plus inference overhead is the whole requirement.

How many copies of embeddinggemma-2 fit on one RTX 3070?

4, by VRAM alone. That card carries 8.0 GB and one copy needs 1.7 GB at BF16, on a live rate of $0.088/hr for the whole card. Throughput is not modelled here, so 4 copies is not 4 times the requests served.

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

More google models

All 3 google models: VRAM and GPU requirements

Alternatives at this size

Other models for feature-extraction within about a third of embeddinggemma-2's 744M parameters, from other model lines.

More on embeddinggemma-2

Related reading: RTX 3070 pricing and specs, How much VRAM you need for LLMs, and What AI inference is.

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

Connect your accounts

One console for the GPU clouds you already use.

Connect your accounts for $20 a month, flat. Your provider bills the GPU.

© 2026 Aquanode. All rights reserved.

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