QW

Qwen3.8 4B Function Calling xLAM Unsloth

QwenGGUF by ermiaazarkhaliliUpdated 2026-08-21
Download on Hugging Face
Parameters4.33B
Context256K
Layers33
Architectureqwen35
Smallest quant2.0 GB
Quick answer

Qwen3.8 4B Function Calling xLAM Unsloth needs about 4.4 GB of memory at Q4_K_M (a 2.8 GB file) with an 8K context window, so it fits on a 6 GB GPU. This repository has 6 quants, from 2.0 GB (Q2_K) to 4.6 GB (Q8_0). Longer context needs more: at 32K tokens the KV cache alone adds about 4.4 GB.

Qwen3.8 4B Function Calling xLAM Unsloth – 4.33B parameter model with 262,144‑token context

Qwen3.8 4B Function Calling xLAM Unsloth is a LoRA fine‑tuned version of Qwen3.8‑4B. It supports native function calling and has a 262,144‑token context length. The model is available in several GGUF quantizations.

Good at

  • Native function calling
  • Reasoning with chain‑of‑thought
  • Large context handling

Limits

  • No vision support
  • No benchmark evaluation performed
  • Requires 8‑k context for memory estimates

Best for

  • Instruction following with function calls
  • Reasoning tasks with long context
  • Deploying on consumer GPUs

Who it’s for. Developers needing a 4B model that can call external tools and handle long documents. Suitable for applications that require reasoning and function calling without specialized wrappers.

Quants & memory

QuantFileEst. memoryvs VRAMResultDownload
Q2_K2.0 GB 3.6 GB
Fits Get file →
Q3_K_M2.3 GB 3.9 GB
Fits Get file →
Q4_K_M2.8 GB 4.4 GB
Fits Get file →
Q5_K_M3.2 GB 4.8 GB
Fits Get file →
Q6_K3.6 GB 5.2 GB
Fits Get file →
Q8_04.6 GB 6.2 GB
Fits Get file →

For 8‑GB VRAM use Q4_K_M (2.78 GB file, ~4.4 GB memory at 8k context). For 12‑GB VRAM use Q5_K_M (3.16 GB file, ~4.8 GB memory). For 16‑GB VRAM use Q6_K (3.56 GB file, ~5.2 GB memory).

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

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 Q3_K_M (2.3 GB file, about 3.9 GB in use).
  • 6 GB VRAM: the best quant that fits is Q6_K (3.6 GB file, about 5.2 GB in use).
  • 8 GB VRAM: the best quant that fits is Q8_0 (4.6 GB file, about 6.2 GB in use).

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

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

The Q8_0 file is 4.6 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 Q2_K at 2.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
Parameters4.33B
Layers33
Trained context262,144 tokens
KV cache (fp16)132 KB per token

Source

Quantized byermiaazarkhalili
FamilyQwen
Licenseapache-2.0
Downloads (HF)951
Last updated2026-08-21

Frequently asked questions about Qwen3.8 4B Function Calling xLAM Unsloth

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

About 4.4 GB at Q4_K_M with an 8K context window. That is the 2.8 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 4B Function Calling xLAM Unsloth on an 8 GB GPU?

Yes, with Q8_0: the 4.6 GB file needs about 6.2 GB at 8K context. Larger quants in this repository do not fit in 8 GB.

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

It depends on the quant: Q2_K is 2.0 GB, Q3_K_M is 2.3 GB, Q4_K_M is 2.8 GB, Q5_K_M is 3.2 GB, Q6_K is 3.6 GB, Q8_0 is 4.6 GB.

What context length does Qwen3.8 4B Function Calling xLAM Unsloth support?

The GGUF header lists a trained context length of 262,144 tokens (256K). The KV cache grows with the context you use: about 1.1 GB at 8K and 4.4 GB at 32K.

Where can I download Qwen3.8 4B Function Calling xLAM Unsloth GGUF?

The files are on Hugging Face in the ermiaazarkhalili/Qwen3.8-4B-Function-Calling-xLAM-Unsloth-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 4B Function Calling xLAM Unsloth 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 quantization requires about 4.4 GB of VRAM at 8k context, which fits in 8 GB.

Does this model support vision tasks?

No, it is a text‑only model with no vision capability.

Is there a benchmark score available?

No benchmark evaluation has been run on this checkpoint.

Other GGUFs of Qwen3.8-4B-Distill

Similar models

Browse all →

More from ermiaazarkhalili

All by ermiaazarkhalili →

More Qwen models

All Qwen →

Other small models

All small models →