LFM2 1.2B Tool needs about 2.3 GB of memory at Q4_K_M (a 0.7 GB file) with an 8K context window, so it fits on a 4 GB GPU. This repository has 6 quants, from 0.7 GB (Q4_0) to 2.3 GB (F16). Longer context needs more: at 32K tokens the KV cache alone adds about 4.3 GB.
LFM2 1.2B Tool – concise, precise tool‑calling model
LFM2 1.2B Tool is a 1.17 billion‑parameter model designed for efficient tool use. It performs JSON function definition, Pythonic function calls, execution, and final answer generation. The model is optimized for low‑latency inference on edge devices.
Good at
- Tool calling with JSON definitions
- Low‑latency API integration
- Embedded system support
Limits
- No internal chain‑of‑thought
- Requires 8 k context for memory estimates
- No vision support
Best for
- Real‑time car assistants
- IoT device command execution
- Battery‑powered embedded tools
Who it’s for. Developers building edge‑AI assistants that need instant API calls or database queries without cloud dependency. Ideal for mobile, automotive, and IoT applications where response latency is critical.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| Q4_0 | 0.7 GB | 2.3 GB | Fits | Get file → | |
| Q4_K_M | 0.7 GB | 2.3 GB | Fits | Get file → | |
| Q5_K_M | 0.8 GB | 2.4 GB | Fits | Get file → | |
| Q6_K | 1.0 GB | 2.5 GB | Fits | Get file → | |
| Q8_0 | 1.2 GB | 2.8 GB | Fits | Get file → | |
| F16 | 2.3 GB | 3.9 GB | Fits | Get file → |
For 8 GB VRAM, Q4_0 or Q4_K_M (0.7 GB file, ~2.3 GB memory) is recommended. If 12 GB VRAM is available, Q5_K_M (0.84 GB) or Q6_K (0.96 GB) can be used for slightly higher precision. Larger Q8_0 or F16 require more memory and are not suitable for low‑resource devices.
What GPU do you need for LFM2 1.2B Tool?
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 (2.3 GB file, about 3.9 GB in use).
Which LFM2 1.2B Tool quant should you choose?
Q4_K_M is the usual starting point for LFM2 1.2B Tool: it balances file size and quality well. Here it is a 0.7 GB file.
The Q8_0 file is 1.2 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 Q4_0 at 0.7 GB, with the quality trade-offs that come with fewer bits. The usual sweet spot between file size and quality, and the quant most people start with.
New to quant names? Read GGUF quantization explained.
Specifications
Architecture from the GGUF header
Source
Frequently asked questions about LFM2 1.2B Tool
How much VRAM does LFM2 1.2B Tool need?
About 2.3 GB at Q4_K_M with an 8K context window. That is the 0.7 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 LFM2 1.2B Tool on an 8 GB GPU?
Yes, with F16: the 2.3 GB file needs about 3.9 GB at 8K context. Larger quants in this repository do not fit in 8 GB.
What is the file size of LFM2 1.2B Tool GGUF?
It depends on the quant: Q4_0 is 0.7 GB, Q4_K_M is 0.7 GB, Q5_K_M is 0.8 GB, Q6_K is 1.0 GB, Q8_0 is 1.2 GB, F16 is 2.3 GB.
What context length does LFM2 1.2B Tool support?
The GGUF header lists a trained context length of 128,000 tokens (125K). The KV cache grows with the context you use: about 1.1 GB at 8K and 4.3 GB at 32K.
Where can I download LFM2 1.2B Tool GGUF?
The files are on Hugging Face in the LiquidAI/LFM2-1.2B-Tool-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 LFM2 1.2B Tool use?
Hugging Face lists the license as other. 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 LFM2 1.2B Tool on 8 GB VRAM?
Yes, the Q4_0 or Q4_K_M quantizations fit within 8 GB VRAM with an estimated 2.3 GB memory usage at 8 k context.
Does the model support vision tasks?
No, LFM2 1.2B Tool does not support vision capabilities.
What decoding strategy is recommended?
Greedy decoding with temperature=0 is recommended for best tool‑calling performance.