NuExtract tiny Resume Data Extractor needs about 1.0 GB of memory at Q4_K_M (a 0.4 GB file) with an 8K context window, so it fits on a 4 GB GPU. Longer context needs more: at 32K tokens the KV cache alone adds about 0.4 GB.
NuExtract tiny Resume Data Extractor – fine‑tuned Qwen2 for resume extraction
NuExtract tiny Resume Data Extractor is a Qwen2‑based model fine‑tuned for structured extraction from resumes. It outputs a clean JSON object with name, contact details, skills, work experience, education, and other details. The model is trained on a private high‑quality dataset and supports long documents.
Good at
- Resume and CV structured extraction
- JSON output ready for ATS or LangChain
- Low‑parameter efficient
Limits
- No vision support
- Requires temperature near 0 for best results
- Only one quant available
Best for
- Automated hiring pipelines
- Resume parsing for ATS
- Data extraction in low‑resource environments
Who it’s for. Developers building hiring tools or data pipelines that need accurate resume extraction. The model is suitable for teams with limited GPU memory and who prefer a lightweight, open‑licensed solution.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| Q4_K_M | 0.4 GB | 1.0 GB | Fits | Get file → |
The Q4_K_M quant file is 0.4 GB and requires approximately 1 GB of VRAM at 8 k context. This is suitable for systems with 8 GB or more VRAM. For tighter budgets, no other quant is available.
What GPU do you need for NuExtract tiny Resume Data Extractor?
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: the best quant that fits is Q4_K_M (0.4 GB file, about 1.0 GB in use).
Which NuExtract tiny Resume Data Extractor quant should you choose?
Q4_K_M is the usual starting point for NuExtract tiny Resume Data Extractor: it balances file size and quality well. Here it is a 0.4 GB file.
New to quant names? Read GGUF quantization explained.
Specifications
Architecture from the GGUF header
Source
Frequently asked questions about NuExtract tiny Resume Data Extractor
How much VRAM does NuExtract tiny Resume Data Extractor need?
About 1.0 GB at Q4_K_M with an 8K context window. That is the 0.4 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 NuExtract tiny Resume Data Extractor on an 8 GB GPU?
Yes, with Q4_K_M: the 0.4 GB file needs about 1.0 GB at 8K context. Larger quants in this repository do not fit in 8 GB.
What is the file size of NuExtract tiny Resume Data Extractor GGUF?
It depends on the quant: Q4_K_M is 0.4 GB.
What context length does NuExtract tiny Resume Data Extractor support?
The GGUF header lists a trained context length of 32,768 tokens (32K). The KV cache grows with the context you use: about 0.1 GB at 8K and 0.4 GB at 32K.
Where can I download NuExtract tiny Resume Data Extractor GGUF?
The files are on Hugging Face in the nimendraai/NuExtract-tiny-Resume-Data-Extractor repository. The download buttons on this page open the file on Hugging Face. ggufmodels.com does not host any model files.
What license does NuExtract tiny Resume Data Extractor use?
Hugging Face lists the license as mit. 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 NuExtract tiny on 8 GB VRAM?
Yes, the Q4_K_M quant requires about 1 GB of VRAM at 8 k context, leaving ample headroom on an 8 GB GPU.
Does this model support vision tasks?
No, the model is purely text‑based and does not support vision.
What temperature should I use?
Use a temperature at or very close to 0 for best extraction performance.