Indian Address Parser 1.5B needs about 1.7 GB of memory at Q4_K_M (a 1.0 GB file) with an 8K context window, so it fits on a 4 GB GPU. This repository has 12 quants, from 0.7 GB (Q2_K) to 3.1 GB (F16). Longer context needs more: at 32K tokens the KV cache alone adds about 0.9 GB.
Indian Address Parser 1.5B – structured JSON from messy Indian addresses
Indian Address Parser 1.5B is a Qwen2‑based model fine‑tuned to convert unstructured Indian addresses into structured JSON. It handles abbreviations, typos, landmarks, and real pincode‑district relationships. The model is released under Apache‑2.0 and supports tool usage.
Good at
- Parsing Indian addresses into JSON
- Handling real pincode‑district relationships
- Tool‑enabled interactions
Limits
- No vision support
- Requires 8k context for full performance
- Only tool usage detected
Best for
- Address standardization in e‑commerce
- Data cleaning for logistics
- API integration for form validation
Who it’s for. Developers building address validation or parsing services for Indian markets. The model is suitable for backend pipelines that need structured address data from free‑form text.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| Q2_K | 0.7 GB | 1.4 GB | Fits | Get file → | |
| Q3_K_S | 0.8 GB | 1.5 GB | Fits | Get file → | |
| Q3_K_M | 0.8 GB | 1.6 GB | Fits | Get file → | |
| Q3_K_L | 0.9 GB | 1.6 GB | Fits | Get file → | |
| IQ4_XS | 0.9 GB | 1.6 GB | Fits | Get file → | |
| Q4_K_S | 0.9 GB | 1.7 GB | Fits | Get file → | |
| Q4_K_M | 1.0 GB | 1.7 GB | Fits | Get file → | |
| Q5_K_S | 1.1 GB | 1.8 GB | Fits | Get file → | |
| Q5_K_M | 1.1 GB | 1.9 GB | Fits | Get file → | |
| Q6_K | 1.3 GB | 2.0 GB | Fits | Get file → | |
| Q8_0 | 1.6 GB | 2.4 GB | Fits | Get file → | |
| F16 | 3.1 GB | 3.8 GB | Fits | Get file → |
For 8 GB VRAM, Q4_K_M (0.99 GB, 1.7 GB memory) or Q5_K_M (1.13 GB, 1.9 GB memory) are suitable. If VRAM is limited to 4 GB, use Q3_K_M (0.82 GB, 1.6 GB memory). Larger models like Q8_0 or F16 provide higher fidelity but need more memory.
What GPU do you need for Indian Address Parser 1.5B?
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 F16 (3.1 GB file, about 3.8 GB in use).
Which Indian Address Parser 1.5B quant should you choose?
Q4_K_M is the usual starting point for Indian Address Parser 1.5B: it balances file size and quality well. Here it is a 1.0 GB file.
The Q8_0 file is 1.6 GB, about 1.7 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 0.7 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 Indian Address Parser 1.5B
How much VRAM does Indian Address Parser 1.5B need?
About 1.7 GB at Q4_K_M with an 8K context window. That is the 1.0 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 Indian Address Parser 1.5B on an 8 GB GPU?
Yes, with F16: the 3.1 GB file needs about 3.8 GB at 8K context. Larger quants in this repository do not fit in 8 GB.
What is the file size of Indian Address Parser 1.5B GGUF?
It depends on the quant: Q2_K is 0.7 GB, Q3_K_S is 0.8 GB, Q3_K_M is 0.8 GB, Q3_K_L is 0.9 GB, IQ4_XS is 0.9 GB, Q4_K_S is 0.9 GB and 6 more.
What context length does Indian Address Parser 1.5B 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.2 GB at 8K and 0.9 GB at 32K.
Where can I download Indian Address Parser 1.5B GGUF?
The files are on Hugging Face in the mradermacher/indian-address-parser-1.5B-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 Indian Address Parser 1.5B use?
Hugging Face lists the license as apache-2.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 this model on 8 GB VRAM?
Yes, Q4_K_M or Q5_K_M quantizations fit within 8 GB VRAM with estimated memory usage of 1.7–1.9 GB at 8k context.
Does the model support vision inputs?
No, the model has no vision support; it only processes text.
What license applies to this model?
The model is released under the Apache‑2.0 license.