TIPO 200M needs about 1.4 GB of memory at F16 (a 0.4 GB file) with an 8K context window, so it fits on a 4 GB GPU.
TIPO 200M – 200M‑parameter LLaMA model for text‑to‑image prompt optimization
TIPO 200M is a 200M‑parameter LLaMA architecture model trained on Danbooru2023 and Coyo‑HD‑11M. It is designed for text presampling to improve text‑to‑image generation. The model supports vision capabilities and has a 2048‑token context window.
Good at
- Text presampling for T2I
- Vision‑enabled prompt refinement
- Small‑parameter efficient model
Limits
- No vision support beyond presampling
- Limited to 2048‑token context
- License type is other
Best for
- Enhancing prompt quality for T2I pipelines
- Running on low‑memory GPUs
- Fine‑tuning small LLaMA models
Who it’s for. Developers building text‑to‑image systems who need a lightweight model for prompt optimization. Researchers exploring vision‑enabled LLMs with modest parameter counts.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| F16 | 0.4 GB | 1.0 GB | Fits | Get file → |
The F16 quant is 0.41 GB and requires about 1.4 GB of VRAM at 8 k context. For 8 GB VRAM, F16 is suitable. If VRAM is lower, consider a lower‑precision quant, but only F16 is available in the file list.
What GPU do you need for TIPO 200M?
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 F16 (0.4 GB file, about 1.4 GB in use).
Which TIPO 200M quant should you choose?
F16 (0.4 GB) is the middle option in this repository. The unquantized model. It gives original quality and needs the most memory, so it is mainly for conversion or reference.
New to quant names? Read GGUF quantization explained.
Specifications
Architecture from the GGUF header
Source
Frequently asked questions about TIPO 200M
How much VRAM does TIPO 200M need?
About 1.4 GB at F16 with an 8K context window. That is the 0.4 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 TIPO 200M on an 8 GB GPU?
Yes, with F16: the 0.4 GB file needs about 1.4 GB at 8K context. Larger quants in this repository do not fit in 8 GB.
What is the file size of TIPO 200M GGUF?
It depends on the quant: F16 is 0.4 GB.
What context length does TIPO 200M support?
The GGUF header lists a trained context length of 2,048 tokens (2K). The KV cache grows with the context you use: about 0.5 GB at 8K and 0.1 GB at 2K.
Where can I download TIPO 200M GGUF?
The files are on Hugging Face in the KBlueLeaf/TIPO-200M-ft repository. The download buttons on this page open the file on Hugging Face. ggufmodels.com does not host any model files.
What license does TIPO 200M use?
Hugging Face lists the license as other. 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 TIPO 200M on 8 GB VRAM?
Yes, the F16 quant requires about 1.4 GB of VRAM at 8 k context, well within an 8 GB budget.
Does TIPO 200M support vision tasks?
Yes, the model has detected vision abilities and can be used for text presampling in T2I pipelines.
What is the context length of TIPO 200M?
The model supports a 2048‑token context window.