LiquidAI · vision language

LFM2.5-VL-450M

LiquidAI/LFM2.5-VL-450M

LFM2.5-VL-450M at Q4_K_M is exactly 229,313,568 bytes (0.21 GiB / 0.23 GB) — an effective 4.088 bits per weight, not the nominal 4. Its KV cache at 32K is 0.38 GiB.

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

Shipped quantizations

exact bytes, summed from published files
QuantSizeExact bytesEffective bpwTensorsPublisher
Q4_00.20 GiB219,311,2643.910LiquidAI
Q4_K_M0.21 GiB229,313,5684.088LiquidAI
Q5_K_M0.24 GiB260,377,6324.642LiquidAI
Q6_K0.27 GiB293,383,2005.231LiquidAI
Q8_00.35 GiB379,219,1046.761LiquidAI
F160.66 GiB711,486,01612.685erikku-sama
BF160.66 GiB711,486,49612.685LiquidAI
F160.66 GiB711,486,62412.685LiquidAI
F321.32 GiB1,420,324,00025.322LiquidAI

KV cache by context

computed per layer
ContextKV cache (f16)Flat formulaOverstated byFull / windowed / recurrent
4,0960.05 GiB0.13 GiB2.67×6 / 0 / 10
8,1920.09 GiB0.25 GiB2.67×6 / 0 / 10
16,3840.19 GiB0.50 GiB2.67×6 / 0 / 10
32,7680.38 GiB1.00 GiB2.67×6 / 0 / 10
65,5360.75 GiB2.00 GiB2.67×6 / 0 / 10
131,0721.50 GiB4.00 GiB2.67×6 / 0 / 10

10 of 16 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 2.7× 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 0.24 GiB. The real file is 0.21 GiB, because a quantization is a mixture and some tensors are always kept at higher precision.

Architecture

from config.json
Layers
16
Attention heads
16
KV heads
8
Head dim
64
Hidden size
1024
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.5-VL-450M need?
Q4_K_M is exactly 229,313,568 bytes (0.21 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.5-VL-450M's KV cache?
0.38 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.5-VL-450M 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.