Qwen3 Sex needs about 6.0 GB of memory at Q8_0 (a 4.3 GB file) with an 8K context window, so it fits on a 6 GB GPU. This repository has 2 quants, from 4.3 GB (Q8_0) to 8.1 GB (BF16). Longer context needs more: at 32K tokens the KV cache alone adds about 4.8 GB.
Qwen3 Sex – a 4.02B parameter conversational model fine‑tuned from Qwen3‑4B‑Instruct‑2507
Qwen3 Sex is a 4.02B parameter causal language model based on Qwen3‑4B‑Instruct‑2507. It supports a native context length of 262,144 tokens and is fine‑tuned for dialogue. The model is released under the Apache‑2.0 license.
Good at
- Tool usage
- Instruction following
- Long‑context understanding
Limits
- No vision support
- Adult content warning – for users 18+ only
- No thinking mode
Best for
- Interactive chat applications
- Tool‑integrated workflows
- Long‑form dialogue generation
Who it’s for. Developers building conversational agents that require tool integration and long‑context handling. The model is suitable for academic research and non‑commercial use, with a strict 18‑year‑old user restriction due to adult content.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| Q8_0 | 4.3 GB | 6.0 GB | Fits | Get file → | |
| BF16 | 8.1 GB | 9.8 GB | Too big | Get file → |
The Q8_0 quantized file is 4.28 GB and requires approximately 6 GB of VRAM at an 8 k context. The BF16 quantized file is 8.05 GB and needs about 9.8 GB of VRAM at the same context. Choose Q8_0 for 8 GB VRAM setups and BF16 if more memory is available.
What GPU do you need for Qwen3 Sex?
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 Q8_0 (4.3 GB file, about 6.0 GB in use).
- 8 GB VRAM: the best quant that fits is Q8_0 (4.3 GB file, about 6.0 GB in use).
- 12 GB VRAM: the best quant that fits is BF16 (8.1 GB file, about 9.8 GB in use).
Which Qwen3 Sex quant should you choose?
Q8_0 (4.3 GB) is the middle option in this repository. Close to lossless. It costs roughly twice the memory of a 4-bit file, so it suits cases where you have plenty of VRAM.
New to quant names? Read GGUF quantization explained.
Specifications
Architecture from the GGUF header
Source
Frequently asked questions about Qwen3 Sex
How much VRAM does Qwen3 Sex need?
About 6.0 GB at Q8_0 with an 8K context window. That is the 4.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 Sex on an 8 GB GPU?
Yes, with Q8_0: the 4.3 GB file needs about 6.0 GB at 8K context. Larger quants in this repository do not fit in 8 GB.
What is the file size of Qwen3 Sex GGUF?
It depends on the quant: Q8_0 is 4.3 GB, BF16 is 8.1 GB.
What context length does Qwen3 Sex 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.2 GB at 8K and 4.8 GB at 32K.
Where can I download Qwen3 Sex GGUF?
The files are on Hugging Face in the evildevlive/Qwen3-Sex 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 Sex 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 Sex on 8 GB VRAM?
Yes, the Q8_0 quantized model requires about 6 GB of VRAM at 8 k context, which fits within an 8 GB GPU. The BF16 version would exceed that limit.
Is this model safe for all audiences?
No. The model is explicitly flagged for users 18 years and older due to potential adult content. Use only in compliant environments.
What is the difference between Q8_0 and BF16 quantizations?
Q8_0 is a lower‑precision quantization that reduces file size and VRAM usage, while BF16 retains higher precision at the cost of larger memory requirements.