text enccoder needs about 5.0 GB of memory at Q6_K (a 3.3 GB file) with an 8K context window, so it fits on a 6 GB GPU. This repository has 4 quants, from 2.4 GB (Q4_0) to 5.1 GB (Q8_K_XL). Longer context needs more: at 32K tokens the KV cache alone adds about 4.8 GB.
3.3B Qwen3 text encoder for coding and tool use
text enccoder is a 3.3B parameter Qwen3 model focused on text encoding. It supports coding and tool‑use tasks. The model is released under the Apache‑2.0 license.
Good at
- Coding tasks
- Tool integration
- Text encoding
Limits
- No vision support
- Large context requires 8k+ tokens
- Requires 4–7 GB VRAM for 8k context
Best for
- Code generation
- Automated tool workflows
- Text embedding
Who it’s for. Developers needing a lightweight text encoder for coding and tool‑use scenarios. The model is suitable for integration into LLM pipelines that require efficient text representation.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| Q4_0 | 2.4 GB | 4.1 GB | Fits | Get file → | |
| Q6_K | 3.3 GB | 5.0 GB | Fits | Get file → | |
| Q8_0 | 3.5 GB | 5.2 GB | Fits | Get file → | |
| Q8_K_XL | 5.1 GB | 6.8 GB | Fits | Get file → |
For 8 GB VRAM, Q4_0 (2.37 GB) or Q6_K (3.31 GB) are suitable. If more memory is available, Q8_0 (3.52 GB) or Q8_K_XL (5.06 GB) provide higher precision. Memory estimates are approximate.
What GPU do you need for text enccoder?
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 (3.5 GB file, about 5.2 GB in use).
- 8 GB VRAM: the best quant that fits is Q8_K_XL (5.1 GB file, about 6.8 GB in use).
Which text enccoder quant should you choose?
Q6_K (3.3 GB) is the middle option in this repository. Very close to the original quality for most uses, at a clearly larger size than 4-bit.
If memory is tight, the smallest file is Q4_0 at 2.4 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 text enccoder
How much VRAM does text enccoder need?
About 5.0 GB at Q6_K with an 8K context window. That is the 3.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 text enccoder on an 8 GB GPU?
Yes, with Q8_K_XL: the 5.1 GB file needs about 6.8 GB at 8K context. Larger quants in this repository do not fit in 8 GB.
What is the file size of text enccoder GGUF?
It depends on the quant: Q4_0 is 2.4 GB, Q6_K is 3.3 GB, Q8_0 is 3.5 GB, Q8_K_XL is 5.1 GB.
What context length does text enccoder support?
The GGUF header lists a trained context length of 40,960 tokens (40K). 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 text enccoder GGUF?
The files are on Hugging Face in the coolrna/text_enccoder repository. The download buttons on this page open the file on Hugging Face. ggufmodels.com does not host any model files.
What license does text enccoder 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 Q4_0 on 4 GB VRAM?
Q4_0 requires about 4.1 GB VRAM at 8k context, so 4 GB VRAM is insufficient.
Does this model support image input?
No, the model has no vision capabilities.
What license applies to this model?
The model is released under the Apache‑2.0 license.