Receipt To Json Models needs about 1.4 GB of memory at Q4_K_M (a 0.5 GB file) with an 8K context window, so it fits on a 4 GB GPU. This repository has 12 quants, from 0.4 GB (Q2_K) to 1.5 GB (F16). Longer context needs more: at 32K tokens the KV cache alone adds about 1.7 GB.
Receipt‑to‑JSON model for on‑device vision
This model converts a photo of a shopping receipt into structured JSON. It is a small vision‑language model based on Qwen3.5‑0.8B. The model is quantized for efficient on‑device inference.
Good at
- Vision‑to‑JSON conversion
- Structured receipt parsing
- Offline inference
Limits
- No vision support beyond receipts
- Limited to 262144 context tokens
- Apache‑2.0 license
Best for
- Mobile receipt scanning apps
- Offline data extraction
- Embedded POS systems
Who it’s for. Developers building mobile or embedded applications that need to parse receipts without cloud connectivity. The model is lightweight and runs on CPUs with modest VRAM.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| Q2_K | 0.4 GB | 1.3 GB | Fits | Get file → | |
| Q3_K_S | 0.4 GB | 1.4 GB | Fits | Get file → | |
| Q3_K_M | 0.5 GB | 1.4 GB | Fits | Get file → | |
| Q3_K_L | 0.5 GB | 1.4 GB | Fits | Get file → | |
| Q4_K_S | 0.5 GB | 1.4 GB | Fits | Get file → | |
| IQ4_XS | 0.5 GB | 1.4 GB | Fits | Get file → | |
| Q4_K_M | 0.5 GB | 1.4 GB | Fits | Get file → | |
| Q5_K_S | 0.6 GB | 1.5 GB | Fits | Get file → | |
| Q5_K_M | 0.6 GB | 1.5 GB | Fits | Get file → | |
| Q6_K | 0.6 GB | 1.5 GB | Fits | Get file → | |
| Q8_0 | 0.8 GB | 1.7 GB | Fits | Get file → | |
| F16 | 1.5 GB | 2.4 GB | Fits | Get file → |
For 8 GB VRAM, use Q4_K_M (0.53 GB file, ~1.4 GB memory). For 4 GB VRAM, Q3_K_M (0.47 GB file, ~1.4 GB memory) is suitable. For 2 GB VRAM, Q2_K (0.42 GB file, ~1.3 GB memory) is the lightest option.
What GPU do you need for Receipt To Json Models?
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 (1.5 GB file, about 2.4 GB in use).
Which Receipt To Json Models quant should you choose?
Q4_K_M is the usual starting point for Receipt To Json Models: it balances file size and quality well. Here it is a 0.5 GB file.
The Q8_0 file is 0.8 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 0.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 Receipt To Json Models
How much VRAM does Receipt To Json Models need?
About 1.4 GB at Q4_K_M with an 8K context window. That is the 0.5 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 Receipt To Json Models on an 8 GB GPU?
Yes, with F16: the 1.5 GB file needs about 2.4 GB at 8K context. Larger quants in this repository do not fit in 8 GB.
What is the file size of Receipt To Json Models GGUF?
It depends on the quant: Q2_K is 0.4 GB, Q3_K_S is 0.4 GB, Q3_K_M is 0.5 GB, Q3_K_L is 0.5 GB, Q4_K_S is 0.5 GB, IQ4_XS is 0.5 GB and 6 more.
What context length does Receipt To Json Models support?
The GGUF header lists a trained context length of 262,144 tokens (256K). The KV cache grows with the context you use: about 0.4 GB at 8K and 1.7 GB at 32K.
Where can I download Receipt To Json Models GGUF?
The files are on Hugging Face in the mradermacher/receipt-to-json-models-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 Receipt To Json Models 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 4 GB VRAM?
Yes, the Q3_K_M quant uses about 1.4 GB of VRAM at 8k context, which fits within a 4 GB budget.
Does the model support other languages?
The model is trained on receipts and does not include language support beyond the receipt text.
What license applies to this model?
The model is released under the Apache‑2.0 license.