Felldude · text

gemma-4-E4B-uncensored

Felldude/gemma-4-E4B-uncensored

gemma-4-E4B-uncensored at Q4_K_M is exactly 5,302,273,632 bytes (4.94 GiB / 5.30 GB) — an effective 5.342 bits per weight, not the nominal 4. Its KV cache at 32K is 0.51 GiB, not the 2.63 GiB a flat formula predicts.

From the file· summed from 1 file(s)From the file· KV per layer
Parameters
7.9B
Architecture
gemma4
42 layers
Context
131,072
native (config.json)
License
apache-2.0

Shipped quantizations

exact bytes, summed from published files
QuantSizeExact bytesEffective bpwTensorsPublisher
I1-IQ1_S3.06 GiB3,289,757,5363.314mradermacher
I1-IQ1_M3.14 GiB3,372,271,4563.397mradermacher
I1-IQ2_XXS3.27 GiB3,509,794,6563.536mradermacher
I1-IQ2_XS3.38 GiB3,627,841,3763.655mradermacher
I1-IQ2_S3.42 GiB3,677,280,0963.705mradermacher
I1-IQ2_M3.53 GiB3,787,298,6563.815mradermacher
I1-IQ3_XXS3.71 GiB3,982,841,6964.012mradermacher
I1-Q2_K_S3.98 GiB4,269,590,3684.301mradermacher
Q2_K4.08 GiB4,376,782,4324.409mradermacher
I1-Q2_K4.08 GiB4,376,782,6884.409mradermacher
I1-IQ3_XS4.23 GiB4,545,886,0484.580mradermacher
Q3_K_S4.31 GiB4,630,959,7124.665mradermacher
I1-Q3_K_S4.31 GiB4,630,959,9684.665mradermacher
I1-IQ3_S4.32 GiB4,635,834,2084.670mradermacher
I1-IQ3_M4.37 GiB4,687,361,8884.722mradermacher
Q3_K_M4.49 GiB4,823,062,1124.859mradermacher
I1-Q3_K_M4.49 GiB4,823,062,3684.859mradermacher
Q3_K_L4.65 GiB4,990,506,5925.027mradermacher
I1-Q3_K_L4.65 GiB4,990,506,8485.027mradermacher
I1-IQ4_XS4.69 GiB5,037,385,5685.075mradermacher
IQ4_XS4.71 GiB5,057,865,3125.095mradermacher
I1-IQ4_NL4.81 GiB5,159,528,2885.198mradermacher
I1-Q4_04.81 GiB5,163,132,7685.201mradermacher
Q4_K_S4.82 GiB5,171,979,8725.210mradermacher
I1-Q4_K_S4.82 GiB5,171,980,1285.210mradermacher
Q4_K_M4.94 GiB5,302,273,6325.342mradermacher
I1-Q4_K_M4.94 GiB5,302,273,8885.342mradermacher
I1-Q4_15.03 GiB5,401,519,9685.442mradermacher
Q5_K_S5.26 GiB5,648,098,9125.690mradermacher
I1-Q5_K_S5.26 GiB5,648,099,1685.690mradermacher
Q5_K_M5.33 GiB5,723,997,7925.766mradermacher
I1-Q5_K_M5.33 GiB5,723,998,0485.766mradermacher
Q6_K5.75 GiB6,172,079,7126.218mradermacher
I1-Q6_K5.75 GiB6,172,079,9686.218mradermacher
Q8_07.43 GiB7,972,726,3688.032mradermacher
F1613.92 GiB14,942,971,48815.054mradermacher

KV cache by context

computed per layer — this model uses sliding-window attention
ContextKV cache (f16)Flat formulaOverstated byFull / windowed / recurrent
4,0960.12 GiB0.33 GiB2.67×7 / 35 / 0
8,1920.18 GiB0.66 GiB3.69×7 / 35 / 0
16,3840.29 GiB1.31 GiB4.57×7 / 35 / 0
32,7680.51 GiB2.63 GiB5.19×7 / 35 / 0
65,5360.94 GiB5.25 GiB5.57×7 / 35 / 0
131,0721.82 GiB10.50 GiB5.77×7 / 35 / 0

35 of 42 layers cache only a 512-token window rather than the full context, on a period of . Figures assume the default configuration; --swa-full disables the saving entirely.

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 4.16 GiB. The real file is 4.94 GiB, because a quantization is a mixture and some tensors are always kept at higher precision. The larger discrepancy is the cache: a flat formula gives 2.63 GiB at 32K context where the real figure is 0.51 GiB, because most of this model's layers cache a fixed window rather than the whole context.

Architecture

from config.json
Layers
42
Attention heads
8
KV heads
2
Head dim
256
Hidden size
2560
Vocab
262,144
Sliding window
512
SWA period
MLA
no
Experts
Experts per token
use_sliding_window

Questions people ask

How much VRAM does gemma-4-E4B-uncensored need?
Q4_K_M is exactly 5,302,273,632 bytes (4.94 GiB) in weights. Add the KV cache, which depends on your context length, plus roughly half a gigabyte of runtime overhead.
How large is gemma-4-E4B-uncensored's KV cache?
0.51 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 gemma-4-E4B-uncensored 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.