LiquidAI · vision language

LFM2-VL-3B

LiquidAI/LFM2-VL-3B

LFM2-VL-3B at Q4_K_M is exactly 1,563,668,256 bytes (1.46 GiB / 1.56 GB) — an effective 4.171 bits per weight, not the nominal 4. Its KV cache at 32K is 0.50 GiB.

From the file· summed from 1 file(s)From the file· KV per layer
Parameters
3.0B
Architecture
lfm2
30 layers
Context
128,000
native (config.json)
License
other

Shipped quantizations

exact bytes, summed from published files
QuantSizeExact bytesEffective bpwTensorsPublisher
Q4_01.38 GiB1,483,107,9683.956LiquidAI
Q4_K_M1.46 GiB1,563,668,2564.171LiquidAI
Q5_K_M1.70 GiB1,828,957,9844.879LiquidAI
Q6_K1.97 GiB2,110,828,3205.631LiquidAI
Q8_02.55 GiB2,733,010,5607.290LiquidAI
F164.79 GiB5,141,458,56013.715LiquidAI
BF164.79 GiB5,141,458,72013.715LiquidAI

KV cache by context

computed per layer
ContextKV cache (f16)Flat formulaOverstated byFull / windowed / recurrent
4,0960.06 GiB0.23 GiB3.75×8 / 0 / 22
8,1920.13 GiB0.47 GiB3.75×8 / 0 / 22
16,3840.25 GiB0.94 GiB3.75×8 / 0 / 22
32,7680.50 GiB1.88 GiB3.75×8 / 0 / 22
65,5361.00 GiB3.75 GiB3.75×8 / 0 / 22
131,0722.00 GiB7.50 GiB3.75×8 / 0 / 22

22 of 30 layers use linear attention, which keeps a fixed-size recurrent state instead of a per-token cache. Those layers do not grow with context at all — treating them as ordinary attention, as a flat formula does, overstates this model's cache by roughly 3.8× at long context.

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

Architecture

from config.json
Layers
30
Attention heads
32
KV heads
8
Head dim
64
Hidden size
2048
Vocab
65,536
Sliding window
none
SWA period
MLA
no
Experts
Experts per token
use_sliding_window

Questions people ask

How much VRAM does LFM2-VL-3B need?
Q4_K_M is exactly 1,563,668,256 bytes (1.46 GiB) in weights. Add the KV cache, which depends on your context length, plus roughly half a gigabyte of runtime overhead.
How large is LFM2-VL-3B's KV cache?
0.50 GiB at 32K context with an f16 cache, computed per layer. Quantizing the cache to q8_0 roughly halves it, which is often the difference between a context length fitting and not.
Which quantization of LFM2-VL-3B 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.