DigitalForensicsText2SQLite needs about 3.5 GB of memory at Q4_K_M (a 2.0 GB file) with an 8K context window, so it fits on a 4 GB GPU. This repository has 4 quants, from 2.0 GB (Q4_K_M) to 6.4 GB. Longer context needs more: at 32K tokens the KV cache alone adds about 3.8 GB.
Fine‑tuned Llama‑3.2‑3B for forensic SQL generation
DigitalForensicsText2SQLite is a 3.21‑billion‑parameter Llama model fine‑tuned to translate natural language forensic queries into SQLite statements. It supports 131072‑token context and is licensed under apache‑2.0.
Good at
- Generating forensic SQLite queries
- Handling diverse mobile forensic databases
- Running fully offline
Limits
- No vision support
- Requires 8k context for memory estimates
- No other language support listed
Best for
- Mobile forensic analysts
- Automated forensic report generation
- Integrating with FQLite
Who it’s for. The model is intended for forensic investigators and researchers who need to convert investigative questions into executable SQL queries against mobile forensic databases. It is suitable for use in open‑source forensic tools and research projects.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| Q4_K_M | 2.0 GB | 3.5 GB | Fits | Get file → | |
| Q5_K_M | 2.3 GB | 3.8 GB | Fits | Get file → | |
| Q8_0 | 3.4 GB | 4.9 GB | Fits | Get file → | |
| — | 6.4 GB | 7.9 GB | Tight | Get file → |
For 8 GB VRAM, Q4_K_M (file size 2.02 GB, estimated 3.5 GB at 8k context) is recommended. If 12 GB VRAM is available, Q5_K_M (2.32 GB, 3.8 GB) can be used. For larger memory budgets, Q8_0 (3.42 GB, 4.9 GB) or the unknown quant (6.43 GB, 7.9 GB) are options.
What GPU do you need for DigitalForensicsText2SQLite?
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 Q5_K_M (2.3 GB file, about 3.8 GB in use).
- 6 GB VRAM: the best quant that fits is Q8_0 (3.4 GB file, about 4.9 GB in use).
- 8 GB VRAM: the best quant that fits is the main file (6.4 GB file, about 7.9 GB in use).
Which DigitalForensicsText2SQLite quant should you choose?
Q4_K_M is the usual starting point for DigitalForensicsText2SQLite: it balances file size and quality well. Here it is a 2.0 GB file.
The Q8_0 file is 3.4 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.
New to quant names? Read GGUF quantization explained.
Specifications
Architecture from the GGUF header
Source
Frequently asked questions about DigitalForensicsText2SQLite
How much VRAM does DigitalForensicsText2SQLite need?
About 3.5 GB at Q4_K_M with an 8K context window. That is the 2.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 DigitalForensicsText2SQLite on an 8 GB GPU?
Yes, with the smaller files: the 6.4 GB file needs about 7.9 GB at 8K context. Larger quants in this repository do not fit in 8 GB.
What is the file size of DigitalForensicsText2SQLite GGUF?
It depends on the quant: Q4_K_M is 2.0 GB, Q5_K_M is 2.3 GB, Q8_0 is 3.4 GB, file is 6.4 GB.
What context length does DigitalForensicsText2SQLite support?
The GGUF header lists a trained context length of 131,072 tokens (128K). The KV cache grows with the context you use: about 0.9 GB at 8K and 3.8 GB at 32K.
Where can I download DigitalForensicsText2SQLite GGUF?
The files are on Hugging Face in the pawlaszc/DigitalForensicsText2SQLite repository. The download buttons on this page open the file on Hugging Face. ggufmodels.com does not host any model files.
What license does DigitalForensicsText2SQLite 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, the Q4_K_M quant requires about 3.5 GB of VRAM at 8k context, which fits within an 8 GB budget.
Does the model support vision or image inputs?
No, the model has no vision capability and only processes text.
What license does the model use?
The model is released under the apache‑2.0 license.