google · text

embeddinggemma-300m

google/embeddinggemma-300m

embeddinggemma-300m at Q4_0 is exactly 277,852,192 bytes (0.26 GiB / 0.28 GB) — an effective 7.339 bits per weight, not the nominal 4.

From the file· summed from 1 file(s)From the file· KV from mirror (mirror:unsloth/embeddinggemma-300m)
Parameters
303M
Architecture
gemma-embedding
24 layers
Context
2,048
native (config.json)
License

Shipped quantizations

exact bytes, summed from published files
QuantSizeExact bytesEffective bpwTensorsPublisher
Q4_00.26 GiB277,852,1927.339314unsloth
IQ4_XS0.28 GiB303,472,1928.016316cstr
Q4_K0.28 GiB305,978,9448.082cstr
Q5_K0.30 GiB318,660,1608.417cstr
Q8_00.31 GiB328,577,0568.679314unsloth
Q8_00.31 GiB333,590,9448.812316ggml-org
Q8_00.33 GiB356,703,8089.422cstr
BF160.57 GiB612,429,79216.177unsloth
F321.13 GiB1,217,982,43232.172unsloth

No KV cache

architectural, not a gap in our data

This architecture allocates no KV cache. Encoder and embedding models process their input in one pass rather than generating token by token, so there is nothing to carry forward between steps and memory does not grow with context. Its footprint is the weights plus a working buffer, and that is the whole story.

Compare with

same modality, comparable size

Will it run on your card?

full quant x context sweep

Why other calculators give a different number

A parameters × bits ÷ 8 estimate puts Q4_0 at roughly 0.16 GiB. The real file is 0.26 GiB, because a quantization is a mixture and some tensors are always kept at higher precision.

Architecture

from mirror:unsloth/embeddinggemma-300m
Layers
24
Attention heads
3
KV heads
1
Head dim
256
Hidden size
768
Vocab
262,144
Sliding window
512
SWA period
6
MLA
no
Experts
Experts per token
use_sliding_window

Questions people ask

How much VRAM does embeddinggemma-300m need?
Q4_0 is exactly 277,852,192 bytes (0.26 GiB) in weights. Add the KV cache, which depends on your context length, plus roughly half a gigabyte of runtime overhead.
Which quantization of embeddinggemma-300m should I use?
Q4_K_M is the usual default. Pick the largest quantization that fits your card at the context you actually need — the table above gives exact sizes for every one published.