jina embeddings v5 omni small text matching needs about 1.8 GB of memory at Q4_K_M (a 0.4 GB file) with an 8K context window, so it fits on a 4 GB GPU. This repository has 14 quants, from 0.2 GB (IQ1_S) to 1.2 GB (F16). Longer context needs more: at 32K tokens the KV cache alone adds about 3.8 GB.
Multimodal embedding model for text, image, video, and audio
jina-embeddings-v5-omni-small-text-matching is a multimodal embedding model that accepts text, images, video, and audio. It produces 1024‑dimensional embeddings aligned with the text‑only version, enabling indexing with text and querying with any modality.
Good at
- Text‑matching embeddings
- Multimodal input support
- Compact model size
Limits
- No vision support in some quantizations
- Requires "Document: " prefix for text
- License is cc‑by‑nc‑4.0
Best for
- Search engines with multimodal queries
- Cross‑modal retrieval systems
- Embedding generation in low‑resource environments
Who it’s for. Developers building search or recommendation systems that need to index text and query with images, video, or audio without reindexing. Suitable for teams that can comply with a cc‑by‑nc‑4.0 license.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| IQ1_S | 0.2 GB | 1.6 GB | Fits | Get file → | |
| IQ1_M | 0.2 GB | 1.7 GB | Fits | Get file → | |
| IQ2_XXS | 0.2 GB | 1.7 GB | Fits | Get file → | |
| IQ2_M | 0.3 GB | 1.7 GB | Fits | Get file → | |
| Q2_K | 0.3 GB | 1.7 GB | Fits | Get file → | |
| Q3_K_M | 0.3 GB | 1.8 GB | Fits | Get file → | |
| IQ4_XS | 0.4 GB | 1.8 GB | Fits | Get file → | |
| IQ4_NL | 0.4 GB | 1.8 GB | Fits | Get file → | |
| Q4_K_M | 0.4 GB | 1.8 GB | Fits | Get file → | |
| Q5_K_S | 0.4 GB | 1.9 GB | Fits | Get file → | |
| Q5_K_M | 0.4 GB | 1.9 GB | Fits | Get file → | |
| Q6_K | 0.5 GB | 1.9 GB | Fits | Get file → | |
| Q8_0 | 0.6 GB | 2.1 GB | Fits | Get file → | |
| F16 | 1.2 GB | 2.6 GB | Fits | Get file → |
For 8 GB VRAM, use IQ1_S (0.21 GB file, 1.6 GB memory) or IQ1_M (0.22 GB file, 1.7 GB memory). If 12 GB VRAM is available, Q4_K_M (0.40 GB file, 1.8 GB memory) offers higher precision. Larger VRAM allows Q8_0 (0.64 GB file, 2.1 GB memory) for best performance.
What GPU do you need for jina embeddings v5 omni small text matching?
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 (1.2 GB file, about 2.6 GB in use).
Which jina embeddings v5 omni small text matching quant should you choose?
Q4_K_M is the usual starting point for jina embeddings v5 omni small text matching: it balances file size and quality well. Here it is a 0.4 GB file.
The Q8_0 file is 0.6 GB, about 1.6 times the size of Q4_K_M. It keeps the weights closer to the original, which only matters if you have the memory to spare.
If memory is tight, the smallest file is IQ1_S at 0.2 GB, with the quality trade-offs that come with fewer bits. Use it only when memory is very tight. Expect a clear drop in quality, which is usually worse on small models and easier to live with on large ones.
New to quant names? Read GGUF quantization explained.
Specifications
Architecture from the GGUF header
Frequently asked questions about jina embeddings v5 omni small text matching
How much VRAM does jina embeddings v5 omni small text matching need?
About 1.8 GB at Q4_K_M 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 jina embeddings v5 omni small text matching on an 8 GB GPU?
Yes, with F16: the 1.2 GB file needs about 2.6 GB at 8K context. Larger quants in this repository do not fit in 8 GB.
What is the file size of jina embeddings v5 omni small text matching GGUF?
It depends on the quant: IQ1_S is 0.2 GB, IQ1_M is 0.2 GB, IQ2_XXS is 0.2 GB, IQ2_M is 0.3 GB, Q2_K is 0.3 GB, Q3_K_M is 0.3 GB and 8 more.
What context length does jina embeddings v5 omni small text matching support?
The GGUF header lists a trained context length of 32,768 tokens (32K). The KV cache grows with the context you use: about 0.9 GB at 8K and 3.8 GB at 32K.
Where can I download jina embeddings v5 omni small text matching GGUF?
The files are on Hugging Face in the jinaai/jina-embeddings-v5-omni-small-text-matching-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 jina embeddings v5 omni small text matching use?
Hugging Face lists the license as cc-by-nc-4.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, the IQ1_S and IQ1_M quantizations fit within 8 GB VRAM with an estimated 1.6–1.7 GB usage.
Does the model support vision?
Yes, it accepts images, video, and audio when loaded with the appropriate multimodal projector.
What license applies?
The model is released under cc‑by‑nc‑4.0, which allows non‑commercial use with attribution.