DeepPresenter 9B needs about 7.2 GB of memory at Q4_K_M (a 5.6 GB file) with an 8K context window, so it fits on a 8 GB GPU. This repository has 2 quants, from 5.6 GB (Q4_K_M) to 17.9 GB (F16). Longer context needs more: at 32K tokens the KV cache alone adds about 4.3 GB.
DeepPresenter 9B – a 9B‑parameter model for automated slide creation
DeepPresenter 9B is a 9B‑parameter language model built on the qwen35 architecture. It is designed for automatic presentation generation and is the core model of the DeepPresenter framework.
Good at
- Generating structured slide decks from natural language
- Supporting agentic workflows for presentation creation
- Running on edge devices with lightweight quantizations
Limits
- No vision support
- Requires 262144 context tokens
- MIT license limits commercial use without attribution
Best for
- Creating PowerPoint presentations
- Automating slide deck generation
- Integrating with PPTAgent workflows
Who it’s for. Developers building presentation automation tools and researchers exploring agentic content generation. The model is suitable for users who need structured slide output from text prompts.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| Q4_K_M | 5.6 GB | 7.2 GB | Tight | Get file → | |
| F16 | 17.9 GB | 19.5 GB | Too big | Get file → |
For 8 GB VRAM, use the Q4_K_M quantization (file size 5.63 GB, estimated 7.2 GB memory at 8 k context). For higher quality with 16 GB VRAM, use F16 (file size 17.92 GB, estimated 19.5 GB memory at 8 k context).
What GPU do you need for DeepPresenter 9B?
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: no quant fits at an 8K context.
- 8 GB VRAM: the best quant that fits is Q4_K_M (5.6 GB file, about 7.2 GB in use).
- 12 GB VRAM: the best quant that fits is Q4_K_M (5.6 GB file, about 7.2 GB in use).
- 16 GB VRAM: the best quant that fits is Q4_K_M (5.6 GB file, about 7.2 GB in use).
- 24 GB VRAM: the best quant that fits is F16 (17.9 GB file, about 19.5 GB in use).
Which DeepPresenter 9B quant should you choose?
Q4_K_M is the usual starting point for DeepPresenter 9B: it balances file size and quality well. Here it is a 5.6 GB file.
New to quant names? Read GGUF quantization explained.
Specifications
Architecture from the GGUF header
Source
Frequently asked questions about DeepPresenter 9B
How much VRAM does DeepPresenter 9B need?
About 7.2 GB at Q4_K_M with an 8K context window. That is the 5.6 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 DeepPresenter 9B on an 8 GB GPU?
Yes, with Q4_K_M: the 5.6 GB file needs about 7.2 GB at 8K context. Larger quants in this repository do not fit in 8 GB.
What is the file size of DeepPresenter 9B GGUF?
It depends on the quant: Q4_K_M is 5.6 GB, F16 is 17.9 GB.
What context length does DeepPresenter 9B 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.3 GB at 32K.
Where can I download DeepPresenter 9B GGUF?
The files are on Hugging Face in the Forceless/DeepPresenter-9B-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 DeepPresenter 9B use?
Hugging Face lists the license as mit. 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 DeepPresenter 9B on 8 GB VRAM?
Yes, using the Q4_K_M quantization requires about 7.2 GB of VRAM at 8 k context, which fits within an 8 GB budget.
Does DeepPresenter 9B support image inputs?
No, the model has no vision capabilities and is text‑only.