QW

Qwen3.8 2B Function Calling xLAM

QwenGGUF by tinyopsecUpdated 2026-11-01
Download on Hugging Face
Parameters1.94B
Context256K
Layers25
Architectureqwen35
Smallest quant1.0 GB
Quick answer

Qwen3.8 2B Function Calling xLAM needs about 2.2 GB of memory at Q4_K_M (a 1.3 GB file) with an 8K context window, so it fits on a 4 GB GPU. This repository has 12 quants, from 1.0 GB (Q2_K) to 3.9 GB (F16). Longer context needs more: at 32K tokens the KV cache alone adds about 1.7 GB.

Qwen3.8‑2B fine‑tuned for function calling and tool use

Qwen3.8‑2B Function Calling xLAM is a 1.94 billion‑parameter model fine‑tuned on Salesforce/xlam‑function‑calling‑60k. It supports reasoning and tool use via the xLAM pipeline. The model is available in multiple GGUF quantizations.

Good at

  • function calling
  • tool use
  • reasoning

Limits

  • No vision support
  • No benchmark evaluation
  • Single‑dataset fine‑tune

Best for

  • API integration
  • Chatbot with tool calls
  • Developer prototyping

Who it’s for. Developers needing a lightweight function‑calling LLM for integration into applications. The model is suitable for environments with limited GPU memory and for use cases that require deterministic tool invocation.

Quants & memory

QuantFileEst. memoryvs VRAMResultDownload
Q2_K1.0 GB 1.9 GB
Fits Get file →
Q3_K_S1.0 GB 2.0 GB
Fits Get file →
Q3_K_M1.1 GB 2.0 GB
Fits Get file →
Q3_K_L1.2 GB 2.1 GB
Fits Get file →
IQ4_XS1.2 GB 2.1 GB
Fits Get file →
Q4_K_S1.2 GB 2.2 GB
Fits Get file →
Q4_K_M1.3 GB 2.2 GB
Fits Get file →
Q5_K_S1.4 GB 2.3 GB
Fits Get file →
Q5_K_M1.5 GB 2.4 GB
Fits Get file →
Q6_K1.6 GB 2.5 GB
Fits Get file →
Q8_02.1 GB 3.0 GB
Fits Get file →
F163.9 GB 4.8 GB
Fits Get file →

For 8 GB VRAM, use Q4_K_M (1.31 GB file, ~2.2 GB memory). For 4 GB VRAM, use Q3_K_S (1.05 GB file, ~2 GB memory). For 2 GB VRAM, use Q2_K (0.99 GB file, ~1.9 GB memory).

What GPU do you need for Qwen3.8 2B Function Calling xLAM?

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 Q8_0 (2.1 GB file, about 3.0 GB in use).
  • 6 GB VRAM: the best quant that fits is F16 (3.9 GB file, about 4.8 GB in use).

Which Qwen3.8 2B Function Calling xLAM quant should you choose?

Q4_K_M is the usual starting point for Qwen3.8 2B Function Calling xLAM: it balances file size and quality well. Here it is a 1.3 GB file.

The Q8_0 file is 2.1 GB, about 1.6 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 1.0 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

Architectureqwen35
Parameters1.94B
Layers25
Trained context262,144 tokens
KV cache (fp16)50 KB per token

Source

Quantized bytinyopsec
FamilyQwen
Licenseapache-2.0
Downloads (HF)886
Last updated2026-11-01

Frequently asked questions about Qwen3.8 2B Function Calling xLAM

How much VRAM does Qwen3.8 2B Function Calling xLAM need?

About 2.2 GB at Q4_K_M with an 8K context window. That is the 1.3 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 Qwen3.8 2B Function Calling xLAM on an 8 GB GPU?

Yes, with F16: the 3.9 GB file needs about 4.8 GB at 8K context. Larger quants in this repository do not fit in 8 GB.

What is the file size of Qwen3.8 2B Function Calling xLAM GGUF?

It depends on the quant: Q2_K is 1.0 GB, Q3_K_S is 1.0 GB, Q3_K_M is 1.1 GB, Q3_K_L is 1.2 GB, IQ4_XS is 1.2 GB, Q4_K_S is 1.2 GB and 6 more.

What context length does Qwen3.8 2B Function Calling xLAM 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 Qwen3.8 2B Function Calling xLAM GGUF?

The files are on Hugging Face in the tinyopsec/Qwen3.8-2B-Function-Calling-xLAM-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 Qwen3.8 2B Function Calling xLAM 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 Qwen3.8‑2B on 8 GB VRAM?

Yes, the Q4_K_M quantization requires about 2.2 GB VRAM at 8 k context, which fits in 8 GB.

Does this model support vision tasks?

No, the model has no vision capabilities.

Is the model open source?

Yes, it is licensed under Apache‑2.0 and available on Hugging Face.

Similar models

Browse all →

More from tinyopsec

All by tinyopsec →

More Qwen models

All Qwen →

Other tiny models

All tiny models →