nomic-ai · embedding

nomic-embed-text-v1

nomic-ai/nomic-embed-text-v1

nomic-embed-text-v1 at Q4_K_M is exactly 84,106,624 bytes (0.08 GiB / 0.08 GB) — an effective 4.921 bits per weight, not the nominal 4.

From the file· summed from 1 file(s)From the file· KV per layer
Parameters
137M
Architecture
nomic-bert
12 layers
Context
8,192
native (config.json)
License
apache-2.0

Shipped quantizations

exact bytes, summed from published files
QuantSizeExact bytesEffective bpwTensorsPublisher
Q2_K0.05 GiB49,361,0882.888nomic-ai
Q3_K_S0.06 GiB59,649,1523.490nomic-ai
Q3_K_M0.06 GiB67,169,4083.930nomic-ai
Q3_K_L0.07 GiB71,593,0884.189nomic-ai
Q4_00.07 GiB77,802,8804.552nomic-ai
Q4_K_S0.07 GiB78,097,7924.569nomic-ai
Q4_K_M0.08 GiB84,106,6244.921nomic-ai
Q5_00.09 GiB94,888,7685.552nomic-ai
Q5_K_S0.09 GiB94,888,7685.552nomic-ai
Q5_K_M0.09 GiB99,588,9285.827nomic-ai
Q6_K0.11 GiB113,042,5286.614nomic-ai
Q8_00.14 GiB146,146,4328.551nomic-ai
F160.26 GiB274,290,56016.048nomic-ai
F320.51 GiB547,664,76832.043nomic-ai

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_K_M at roughly 0.07 GiB. The real file is 0.08 GiB, because a quantization is a mixture and some tensors are always kept at higher precision.

Architecture

from config.json
Layers
12
Attention heads
12
KV heads
12
Head dim
64
Hidden size
768
Vocab
30,528
Sliding window
none
SWA period
MLA
no
Experts
Experts per token
use_sliding_window

Questions people ask

How much VRAM does nomic-embed-text-v1 need?
Q4_K_M is exactly 84,106,624 bytes (0.08 GiB) in weights. Add the KV cache, which depends on your context length, plus roughly half a gigabyte of runtime overhead.
Which quantization of nomic-embed-text-v1 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.