T5 Base needs about 0.9 GB of memory at Q5_0 (a 0.1 GB file) with an 8K context window, so it fits on a 4 GB GPU. This repository has 4 quants, from 0.1 GB (Q4_0) to 0.4 GB (F32).
T5 Base encoder, 0.11B parameters, 512 token context
T5 Base encoder is a 0.11 billion parameter model trained on 512 token context. It is available in multiple quantizations and licensed under apache-2.0. The model is suitable for text encoding tasks.
Good at
- text encoding
- coding tasks
- audio-to-audio generation
Limits
- 512 token context
- no vision support
- license requires attribution
Best for
- embedding generation
- code analysis
- audio-to-audio prep
Who it’s for. Developers needing a lightweight text encoder for code or audio generation. The model fits in low‑memory environments and supports multiple quantizations.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| Q4_0 | 0.1 GB | 0.6 GB | Fits | Get file → | |
| Q5_0 | 0.1 GB | 0.6 GB | Fits | Get file → | |
| Q8_0 | 0.1 GB | 0.6 GB | Fits | Get file → | |
| F32 | 0.4 GB | 1.0 GB | Fits | Get file → |
For 8 GB VRAM, Q4_0 or Q5_0 (0.07 GB or 0.08 GB) are suitable, each using about 0.9 GB memory at 8 k context. For higher precision, Q8_0 (0.12 GB) or F32 (0.44 GB) can be used if memory allows.
What GPU do you need for T5 Base?
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 F32 (0.4 GB file, about 1.2 GB in use).
Which T5 Base quant should you choose?
Q5_0 (0.1 GB) is the middle option in this repository. Closer to the original model than 4-bit, for a moderate increase in size. A good pick when you have memory to spare.
If memory is tight, the smallest file is Q4_0 at 0.1 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 T5 Base
How much VRAM does T5 Base need?
About 0.9 GB at Q5_0 with an 8K context window. That is the 0.1 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 T5 Base on an 8 GB GPU?
Yes, with F32: the 0.4 GB file needs about 1.2 GB at 8K context. Larger quants in this repository do not fit in 8 GB.
What is the file size of T5 Base GGUF?
It depends on the quant: Q4_0 is 0.1 GB, Q5_0 is 0.1 GB, Q8_0 is 0.1 GB, F32 is 0.4 GB.
What context length does T5 Base support?
The GGUF header lists a trained context length of 512 tokens (512). The KV cache grows with the context you use: about 0.3 GB at 8K and 0.0 GB at 512.
Where can I download T5 Base GGUF?
The files are on Hugging Face in the callgg/t5-base-encoder-f32 repository. The download buttons on this page open the file on Hugging Face. ggufmodels.com does not host any model files.
What license does T5 Base 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, Q4_0 or Q5_0 quantizations use about 0.9 GB memory at 8 k context, fitting comfortably in 8 GB VRAM.
Does this model support vision tasks?
No, the model is an encoder with no vision capabilities.
What license applies to this model?
The model is licensed under apache-2.0, requiring attribution.