Gemma 3 1B IT VRAM & Memory Requirements
Specific checkpoints with sourced architecture and weight files. GGUF Q4_0 (Google QAT): 1.10 GiB–1.50 GiB at 8,192 tokens, 1 sequence, FP16 KV, llama.cpp.
This result is an estimate, not a measured trace.Not verifiedFile-backed weights
Publisher and provenance
- PublisherGoogle
- Hugging Face
google/gemma-3-1b-it - Revision
dcc83ea841ab6100d6b47a070329e1ba4cf78752 - Total parameters999,885,952
- Layers26
- Query heads4
- KV heads1 (sliding-window)
- Head dimension256
- Recorded context capability32,768
- Completenesscomplete · full
Memory layers in this estimate
Artifact bytes, raw KV, engine extras, and total demand are separate. This is not a runtime trace.
- Weight artifact
- 0.93 GiB (1,003,541,152 bytes)
- Raw KV cache
- 0.04 GiB (45,088,768 bytes)
- Engine extras / workspace
- 0.13 GiB–0.52 GiB
- Total estimated demand
- 1.10 GiB–1.50 GiB
Published artifacts
| Quantization | Selected files | Bytes | Engine | Evidence |
|---|---|---|---|---|
| Official BF16 safetensors (text only) bf16 | model.safetensors | 1,999,811,208 (1.86 GiB / 2.00 GB) | vllm, sglang, unspecified | file-metadata |
| GGUF Q4_0 (Google QAT) gguf-q4_0 | gemma-3-1b-it-q4_0.gguf | 1,003,541,152 (0.93 GiB / 1.00 GB) | llama.cpp, ollama, unspecified | file-metadata |
| INT4 theoretical | No published file | 499,942,976 (theoretical) | — | theoretical |
Memory by quantization and context
Concurrent sequences = 1. KV defaults to FP16. The range includes documented runtime extras for the listed engine. These figures use the same core as the interactive calculator.
| Quantization | 2,048 tokens | 8,192 tokens | 32,768 tokens |
|---|---|---|---|
| Official BF16 safetensors (text only) | 2.51 GiB–4.38 GiB | 2.53 GiB–4.41 GiB | 2.62 GiB–4.50 GiB |
| GGUF Q4_0 (Google QAT) | 1.08 GiB–1.47 GiB | 1.10 GiB–1.50 GiB | 1.20 GiB–1.60 GiB |
| INT4 theoretical Theoretical rows are not downloadable artifacts. | 0.61 GiB–1.20 GiB | 0.63 GiB–1.23 GiB | 0.73 GiB–1.34 GiB |
Raw KV contribution
Related pages
Sources
- Gemma 3 model card (Google AI for Developers) — Input context 128K tokens for 4B, 12B, 27B and 32K for 1B; images encoded to 256 tokens each. License: Gemma Terms of Use.
- Google gemma_pytorch config.py (architecture) — get_config_for_1b: num_hidden_layers=26, num_attention_heads=4, num_key_value_heads=1, hidden_size=1152, head_dim=256, sliding_window_size=512, attn_types = 5 LOCAL_SLIDING then 1 GLOBAL, cycled by layer index (gemma/model.py: attn_types[i % len(attn_types)]), so 4 global and 22 sliding layers. The Hugging Face config.json is gated (HTTP 401), so it was not read.
- Cross-check only: llama.cpp org GGUF header converted from Google's config (not an official Google source) — Header read with an HTTP range request on 2026-10-18: block_count 26, head_count 4, head_count_kv 1, embedding_length 1152, key_length 256, sliding_window 512, context_length 32768. All agree with gemma_pytorch config.py.
- Gemma releases — March 10, 2025: release of Gemma 3 in 1B, 4B, 12B and 27B sizes.
- Hugging Face API (BF16) — sha dcc83ea841ab6100d6b47a070329e1ba4cf78752; gated manual; safetensors.total=999885952; 1 safetensors siblings.
- Hugging Face API (QAT Q4_0 GGUF) — sha d1be121d36172a4b0b964657e2ee859d61138593; gemma-3-1b-it-q4_0.gguf = 1,003,541,152 bytes.
Assumptions that affect this result
- Requested context is within the recorded native window of 32768 tokens.
- Full-resident weight estimates use total parameters, including inactive MoE experts.
- Weight bytes come from the selected weight files only, not from every file in the repository.
- Download file size is not peak GPU memory. Runtime layout, allocator padding, and KV are extra.
- Counted files: gemma-3-1b-it-q4_0.gguf.
- Context budget is the number of cached tokens per sequence (prompt plus reserved generation).
- Concurrent sequences share one model replica; weights are not multiplied by sequence count.
- KV dtype is independent of weight quantization unless you change it.
Calculator
Loading catalog snapshot…
Search or pick a catalog checkpoint to see memory demand.
Search or pick a catalog checkpoint to see memory demand.