gemmaExtract needs about 7.2 GB of memory at Q4_K_M (a 5.3 GB file) with an 8K context window, so it fits on a 8 GB GPU. This repository has 12 quants, from 4.4 GB (Q2_K) to 15.1 GB (F16). Longer context needs more: at 32K tokens the KV cache alone adds about 5.6 GB.
GemmaExtract: extract typed fields from documents in one pass
GemmaExtract is a 7.52B parameter Gemma4 model fine‑tuned for field extraction. It returns field values, positions, presence probability, confidence, and a best guess without generating text. The model reads the document once, keeping latency low regardless of field count.
Good at
- Fast single‑pass extraction
- No text generation, no hallucination
- Provides position and confidence for each field
Limits
- No vision support
- License is cc‑by‑nc‑4.0
- Context length 131072 tokens
Best for
- Extracting structured data from PDFs
- Automating form processing
- Building data pipelines for documents
Who it’s for. Developers needing reliable field extraction from multilingual documents. Researchers building extraction pipelines without generative components. Enterprises requiring non‑hallucinatory data extraction under a non‑commercial license.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| Q2_K | 4.4 GB | 6.3 GB | Fits | Get file → | |
| Q3_K_S | 4.7 GB | 6.6 GB | Fits | Get file → | |
| Q3_K_M | 4.9 GB | 6.8 GB | Fits | Get file → | |
| Q3_K_L | 5.0 GB | 6.9 GB | Fits | Get file → | |
| IQ4_XS | 5.1 GB | 7.0 GB | Fits | Get file → | |
| Q4_K_S | 5.2 GB | 7.1 GB | Fits | Get file → | |
| Q4_K_M | 5.3 GB | 7.2 GB | Tight | Get file → | |
| Q5_K_S | 5.7 GB | 7.6 GB | Tight | Get file → | |
| Q5_K_M | 5.8 GB | 7.7 GB | Tight | Get file → | |
| Q6_K | 6.2 GB | 8.1 GB | Too big | Get file → | |
| Q8_0 | 8.0 GB | 9.9 GB | Too big | Get file → | |
| F16 | 15.1 GB | 17.0 GB | Too big | Get file → |
For 8 GB VRAM, use Q4_K_M (file size 5.34 GB, estimated 7.2 GB memory). For 12 GB VRAM, Q5_K_M (5.76 GB, 7.7 GB memory) or Q6_K (6.22 GB, 8.1 GB memory). Higher precision quants like F16 need 17 GB memory and 15.05 GB file size.
What GPU do you need for gemmaExtract?
These figures add the file size, an fp16 KV cache at an 8K context window (worked out from this model’s own header) and about 0.5 GB for the runtime. They are estimates, so leave a little headroom, and expect to use less context or a smaller quant if you are right at the limit.
- 4 GB VRAM: no quant fits at an 8K context.
- 6 GB VRAM: no quant fits at an 8K context.
- 8 GB VRAM: the best quant that fits is Q5_K_M (5.8 GB file, about 7.7 GB in use).
- 12 GB VRAM: the best quant that fits is Q8_0 (8.0 GB file, about 9.9 GB in use).
- 16 GB VRAM: the best quant that fits is Q8_0 (8.0 GB file, about 9.9 GB in use).
- 24 GB VRAM: the best quant that fits is F16 (15.1 GB file, about 17.0 GB in use).
Which gemmaExtract quant should you choose?
Q4_K_M is the usual starting point for gemmaExtract: it balances file size and quality well. Here it is a 5.3 GB file.
The Q8_0 file is 8.0 GB, about 1.5 times the size of Q4_K_M. It keeps the weights closer to the original, which only matters if you have the memory to spare.
If memory is tight, the smallest file is Q2_K at 4.4 GB, with the quality trade-offs that come with fewer bits. Use it only when memory is very tight. Expect a clear drop in quality, which is usually worse on small models and easier to live with on large ones.
New to quant names? Read GGUF quantization explained.
Specifications
Architecture from the GGUF header
Source
Frequently asked questions about gemmaExtract
How much VRAM does gemmaExtract need?
About 7.2 GB at Q4_K_M with an 8K context window. That is the 5.3 GB file, plus the KV cache and roughly 0.5 GB of runtime overhead. Smaller quants need less and longer context needs more.
Can I run gemmaExtract on an 8 GB GPU?
Yes, with Q5_K_M: the 5.8 GB file needs about 7.7 GB at 8K context. Larger quants in this repository do not fit in 8 GB.
What is the file size of gemmaExtract GGUF?
It depends on the quant: Q2_K is 4.4 GB, Q3_K_S is 4.7 GB, Q3_K_M is 4.9 GB, Q3_K_L is 5.0 GB, IQ4_XS is 5.1 GB, Q4_K_S is 5.2 GB and 6 more.
What context length does gemmaExtract support?
The GGUF header lists a trained context length of 131,072 tokens (128K). The KV cache grows with the context you use: about 1.4 GB at 8K and 5.6 GB at 32K.
Where can I download gemmaExtract GGUF?
The files are on Hugging Face in the mradermacher/gemmaExtract-GGUF repository. The download buttons on this page open the file on Hugging Face. ggufmodels.com does not host any model files.
What license does gemmaExtract use?
Hugging Face lists the license as cc-by-nc-4.0. Licenses can differ between the quantized files and the original model, so check the repository and the base model before commercial use.
Can I run GemmaExtract on 8 GB VRAM?
Yes, the Q4_K_M quant uses about 7.2 GB memory at 8 k context, fitting within 8 GB VRAM.
Does GemmaExtract support vision?
No, the model has no vision capability.