LocalAI functioncall phi 4 v0.3 i1 needs about 11.1 GB of memory at Q4_K_M (a 8.9 GB file) with an 8K context window, so it fits on a 12 GB GPU. This repository has 24 quants, from 3.4 GB (IQ1_S) to 12.0 GB (Q6_K).
LocalAI functioncall phi 4 v0.3 i1 – conversational model with function call support
LocalAI functioncall phi 4 v0.3 i1 is a 14.7B parameter model based on Phi architecture. It is optimized for conversation and executing function calls via LocalAI. The model supports a 16384 token context window and is released under Apache‑2.0.
Good at
- Conversational dialogue
- Function call execution
- Large context handling
Limits
- No vision support
- Requires 8k context for memory estimates
- No explicit language support list
Best for
- Chatbots needing function calls
- LocalAI deployments
- Testing conversational LLMs
Who it’s for. Developers building local chat interfaces that need function call capability. Researchers testing Phi‑based models in a local environment. Teams requiring a conversational model with a large context window and open‑source license.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| IQ1_S | 3.4 GB | 5.6 GB | Fits | Get file → | |
| IQ1_M | 3.7 GB | 5.9 GB | Fits | Get file → | |
| IQ2_XXS | 4.2 GB | 6.3 GB | Fits | Get file → | |
| IQ2_XS | 4.6 GB | 6.7 GB | Fits | Get file → | |
| IQ2_S | 4.8 GB | 7.0 GB | Fits | Get file → | |
| IQ2_M | 5.2 GB | 7.4 GB | Tight | Get file → | |
| Q2_K_S | 5.2 GB | 7.4 GB | Tight | Get file → | |
| Q2_K | 5.6 GB | 7.8 GB | Tight | Get file → | |
| IQ3_XXS | 5.8 GB | 8.0 GB | Tight | Get file → | |
| IQ3_XS | 6.2 GB | 8.4 GB | Too big | Get file → | |
| Q3_K_S | 6.5 GB | 8.7 GB | Too big | Get file → | |
| IQ3_S | 6.5 GB | 8.7 GB | Too big | Get file → | |
| IQ3_M | 6.7 GB | 8.9 GB | Too big | Get file → | |
| Q3_K_M | 7.2 GB | 9.4 GB | Too big | Get file → | |
| Q3_K_L | 7.8 GB | 10.0 GB | Too big | Get file → | |
| IQ4_XS | 8.0 GB | 10.2 GB | Too big | Get file → | |
| Q4_0 | 8.4 GB | 10.6 GB | Too big | Get file → | |
| IQ4_NL | 8.4 GB | 10.6 GB | Too big | Get file → | |
| Q4_K_S | 8.4 GB | 10.6 GB | Too big | Get file → | |
| Q4_K_M | 8.9 GB | 11.1 GB | Too big | Get file → | |
| Q4_1 | 9.3 GB | 11.4 GB | Too big | Get file → | |
| Q5_K_S | 10.2 GB | 12.3 GB | Too big | Get file → | |
| Q5_K_M | 10.4 GB | 12.6 GB | Too big | Get file → | |
| Q6_K | 12.0 GB | 14.2 GB | Too big | Get file → |
For 8 GB VRAM, use IQ1_S (3.41 GB file, 5.6 GB memory at 8k context) or IQ1_M (3.69 GB file, 5.9 GB memory). For 16 GB VRAM, Q4_K_M (8.89 GB file, 11.1 GB memory) or Q5_K_M (10.41 GB file, 12.6 GB memory) provide a good balance of size and performance. Higher quants like Q6_K (12.03 GB file, 14.2 GB memory) require more memory but offer better precision.
What GPU do you need for LocalAI functioncall phi 4 v0.3 i1?
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: no quant fits at an 8K context.
- 6 GB VRAM: the best quant that fits is IQ1_M (3.7 GB file, about 5.9 GB in use).
- 8 GB VRAM: the best quant that fits is IQ3_XXS (5.8 GB file, about 8.0 GB in use).
- 12 GB VRAM: the best quant that fits is Q4_1 (9.3 GB file, about 11.4 GB in use).
- 16 GB VRAM: the best quant that fits is Q6_K (12.0 GB file, about 14.2 GB in use).
Which LocalAI functioncall phi 4 v0.3 i1 quant should you choose?
Q4_K_M is the usual starting point for LocalAI functioncall phi 4 v0.3 i1: it balances file size and quality well. Here it is a 8.9 GB file.
If memory is tight, the smallest file is IQ1_S at 3.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
Frequently asked questions about LocalAI functioncall phi 4 v0.3 i1
How much VRAM does LocalAI functioncall phi 4 v0.3 i1 need?
About 11.1 GB at Q4_K_M with an 8K context window. That is the 8.9 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 LocalAI functioncall phi 4 v0.3 i1 on an 8 GB GPU?
Yes, with IQ3_XXS: the 5.8 GB file needs about 8.0 GB at 8K context. Larger quants in this repository do not fit in 8 GB.
What is the file size of LocalAI functioncall phi 4 v0.3 i1 GGUF?
It depends on the quant: IQ1_S is 3.4 GB, IQ1_M is 3.7 GB, IQ2_XXS is 4.2 GB, IQ2_XS is 4.6 GB, IQ2_S is 4.8 GB, IQ2_M is 5.2 GB and 18 more.
What context length does LocalAI functioncall phi 4 v0.3 i1 support?
The GGUF header lists a trained context length of 16,384 tokens (16K). The KV cache grows with the context you use: about 1.7 GB at 8K and 3.4 GB at 16K.
Where can I download LocalAI functioncall phi 4 v0.3 i1 GGUF?
The files are on Hugging Face in the mradermacher/LocalAI-functioncall-phi-4-v0.3-i1-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 LocalAI functioncall phi 4 v0.3 i1 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, using IQ1_S or IQ1_M quants which estimate 5.6–5.9 GB memory at 8k context.
Does this model support vision?
No, the model has no vision capability.
What license applies to this model?
The model is released under the Apache‑2.0 license.