How much VRAM does jina-reranker-v1-tiny-en need?

Q4_K_M is exactly 33,257,536 bytes (0.03 GiB) in weights. Add the KV cache, which depends on context length, plus roughly half a gigabyte of runtime overhead.

jinaai · embedding

jina-reranker-v1-tiny-en

jinaai/jina-reranker-v1-tiny-en

jina-reranker-v1-tiny-en at Q4_K_M is exactly 33,257,536 bytes (0.03 GiB / 0.03 GB) — an effective 8.051 bits per weight, not the nominal 4.

From the file· summed from 1 file(s)From the file· KV per layer

Parameters

33M

Architecture

jina-bert-v2

4 layers

Context

8,192

native (config.json)

License

apache-2.0

Shipped quantizations

● exact bytes, summed from published files

Quant	Size●	Exact bytes●	Effective bpw●	Tensors●	Publisher
Q3_K_S	0.03 GiB	31,644,736	7.661	—	mradermacher
Q2_K	0.03 GiB	31,644,736	7.661	—	mradermacher
IQ4_XS	0.03 GiB	31,884,352	7.719	—	mradermacher
Q3_K_M	0.03 GiB	32,123,968	7.777	—	mradermacher
Q3_K_L	0.03 GiB	32,474,176	7.862	—	mradermacher
Q4_K_S	0.03 GiB	32,879,680	7.960	—	mradermacher
Q4_K_M	0.03 GiB	33,257,536	8.051	—	mradermacher
Q5_K_S	0.03 GiB	33,580,096	8.129	—	mradermacher
Q5_K_M	0.03 GiB	33,828,928	8.190	—	mradermacher
Q6_K	0.03 GiB	36,105,280	8.741	—	mradermacher
Q8_0	0.03 GiB	36,676,672	8.879	—	mradermacher
F16	0.06 GiB	67,504,192	16.342	—	mradermacher

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

vs nomic-embed-text-v1.5 vs all-MiniLM-L6-v2 vs mxbai-embed-xsmall-v1 vs gte-small vs nomic-embed-text-v1 All alternatives →Will it fit on my card? →

Why other calculators give a different number

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

Architecture

from config.json

Layers

Attention heads

KV heads

Head dim

Hidden size

384

Vocab

61,056

Sliding window

none

SWA period

—

MLA

Experts

—

Experts per token

—

use_sliding_window

—

Questions people ask

How much VRAM does jina-reranker-v1-tiny-en need?: Q4_K_M is exactly 33,257,536 bytes (0.03 GiB) in weights. Add the KV cache, which depends on your context length, plus roughly half a gigabyte of runtime overhead.
Which quantization of jina-reranker-v1-tiny-en 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.