How much VRAM does markdownizer need?

I1-IQ1_S is exactly 2,019,628,096 bytes (1.88 GiB) in weights. Add the KV cache, which depends on context length, plus roughly half a gigabyte of runtime overhead.

How large is markdownizer's KV cache?

4.00 GiB at 32K context with an f16 cache, computed per layer from the model's architecture. Quantizing the cache to q8_0 roughly halves it.

LLMDH · text

markdownizer

LLMDH/markdownizer

markdownizer at I1-IQ1_S is exactly 2,019,628,096 bytes (1.88 GiB / 2.02 GB) — an effective 2.012 bits per weight, not the nominal 1. Its KV cache at 32K is 4.00 GiB.

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

Parameters

8.0B

Architecture

llama

32 layers

Context

131,072

native (config.json)

License

—

Shipped quantizations

● exact bytes, summed from published files

Quant	Size●	Exact bytes●	Effective bpw●	Tensors●	Publisher
I1-IQ1_S	1.88 GiB	2,019,628,096	2.012	—	mradermacher
I1-IQ1_M	2.01 GiB	2,161,972,288	2.154	—	mradermacher
I1-IQ2_XXS	2.23 GiB	2,399,212,608	2.390	—	mradermacher
I1-IQ2_XS	2.43 GiB	2,605,782,080	2.596	—	mradermacher
I1-IQ2_S	2.57 GiB	2,758,489,152	2.748	—	mradermacher
I1-IQ2_M	2.75 GiB	2,948,281,408	2.937	—	mradermacher
I1-Q2_K_S	2.78 GiB	2,988,815,424	2.978	—	mradermacher
I1-Q2_K	2.96 GiB	3,179,131,968	3.167	—	mradermacher
I1-IQ3_XXS	3.05 GiB	3,274,912,832	3.263	—	mradermacher
I1-IQ3_XS	3.28 GiB	3,518,747,712	3.506	—	mradermacher
I1-Q3_K_S	3.41 GiB	3,664,499,776	3.651	—	mradermacher
I1-IQ3_S	3.43 GiB	3,682,325,568	3.668	—	mradermacher
I1-IQ3_M	3.52 GiB	3,784,823,872	3.771	—	mradermacher
I1-Q3_K_M	3.74 GiB	4,018,918,464	4.004	—	mradermacher
I1-Q3_K_L	4.03 GiB	4,321,956,928	4.306	—	mradermacher
I1-IQ4_XS	4.14 GiB	4,447,663,168	4.431	—	mradermacher
I1-Q4_0	4.35 GiB	4,675,892,288	4.658	—	mradermacher
I1-IQ4_NL	4.36 GiB	4,677,989,440	4.660	—	mradermacher
I1-Q4_K_S	4.37 GiB	4,692,669,504	4.675	—	mradermacher
I1-Q4_K_M	4.58 GiB	4,920,734,784	4.902	—	mradermacher
I1-Q4_1	4.78 GiB	5,130,253,376	5.111	—	mradermacher
I1-Q5_K_S	5.21 GiB	5,599,294,528	5.578	—	mradermacher
I1-Q5_K_M	5.34 GiB	5,732,987,968	5.711	—	mradermacher
I1-Q6_K	6.14 GiB	6,596,006,976	6.571	—	mradermacher

KV cache by context

computed per layer

Context	KV cache (f16)●	Flat formula	Overstated by	Full / windowed / recurrent
4,096	0.50 GiB	0.50 GiB	—	32 / 0 / 0
8,192	1.00 GiB	1.00 GiB	—	32 / 0 / 0
16,384	2.00 GiB	2.00 GiB	—	32 / 0 / 0
32,768	4.00 GiB	4.00 GiB	—	32 / 0 / 0
65,536	8.00 GiB	8.00 GiB	—	32 / 0 / 0
131,072	16.00 GiB	16.00 GiB	—	32 / 0 / 0

Compare with

same modality, comparable size

vs gemma-4-E4B-it vs Qwen3-4B vs Qwen3-8B vs HyperCLOVAX-SEED-Text-Instruct-1.5B vs Llama-3.2-1B-Instruct vs Qwen3-VL-8B-Instruct-abliterated-v1 All alternatives →Will it fit on my card? →

Why other calculators give a different number

A parameters × bits ÷ 8 estimate puts I1-IQ1_S at roughly 4.21 GiB. The real file is 1.88 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

128

Hidden size

4096

Vocab

128,256

Sliding window

none

SWA period

—

MLA

Experts

—

Experts per token

—

use_sliding_window

—

Questions people ask

How much VRAM does markdownizer need?: I1-IQ1_S is exactly 2,019,628,096 bytes (1.88 GiB) in weights. Add the KV cache, which depends on your context length, plus roughly half a gigabyte of runtime overhead.
How large is markdownizer's KV cache?: 4.00 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 markdownizer 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.