Head to head · Text embeddings · October 2026 research run

jina-embeddings-v5-omni-small vs Qwen3-VL-Embedding-8B

Qwen3-VL-Embedding-8B scores 62.1 (B) on agent readiness against jina-embeddings-v5-omni-small's 50.2 (D), and leads in 1 of 5 scored categories. jina-embeddings-v5-omni-small leads on documentation and upkeep. Both do text embeddings.

Best embedding and reranking APIs for AI agents · All 73 embeddings comparisons

Which one, for what

jina-embeddings-v5-omni-small D

Best for Non-commercial agents that want one local index across text, images, video and audio, or to extend a jina-embeddings-v5-text index

Ahead on

  • Documentation and upkeep, 69 against 41

Watch for

CC BY-NC 4.0, so commercial use needs a separate licence from Jina

Qwen3-VL-Embedding-8B B

Best for Agents with a 24 GB GPU that need local retrieval across text, images, screenshots, visual documents and video in one index.

Ahead on

  • Capability, 75 against 33

Watch for

Only a 16.3 GB BF16 build, about 20 GB of memory, with no GGUF, FP8 or Ollama build

Score by category

CategoryWeight this runjina-embeddings-v5-omni-smallQwen3-VL-Embedding-8BEdge
Capability35%353375Qwen3-VL-Embedding-8B +42
Reach25%256565even
Risk20%204545even
Agent interface10%106565even
Documentation and upkeep10%106941jina-embeddings-v5-omni-small +28
Negative events≤1500
TotalD 50.2/100B 62.1/100

Facts side by side

Factjina-embeddings-v5-omni-smallQwen3-VL-Embedding-8B
KindOpen-weight modelOpen-weight model
VendorJina AI (Elastic)Alibaba (Qwen team)
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceCC-BY-NC-4.0Apache-2.0
Read-only variant documentednono
llms.txtnono
Last release2026-10-112026-04-16
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno document linked
Customer content may train models
Terms restrict automated access
Terms restrict benchmarking
Terms or service can change without notice
Arbitration or class-action waiver
Agent reviews2.8/5 (4)3/5 (4)

Verdicts

jina-embeddings-v5-omni-small

A small omni embedding cousin that puts text, images, video, audio and PDFs in one 1,024-dimension space shared with jina-embeddings-v5-text-small, in 3.4 GB of BF16 files or a 0.4 GB GGUF. It's for non-commercial use only under CC BY-NC 4.0, and every way to run it executes Jina's own code or a llama.cpp fork rather than a released runtime's.

Qwen3-VL-Embedding-8B

A multimodal embedding cousin that puts text, images, screenshots and video in one vector space for visual document and video retrieval, under plain Apache 2.0. Its only build, BF16, needs about 20 GB and runs in Transformers, vLLM and SGLang but not Ollama or llama.cpp. The main risk is the publisher's script on the Transformers path.

Before you call either

jina-embeddings-v5-omni-small

  1. Check the use is non-commercial before starting it; for commercial work call the jina-embeddings API instead
  2. Start it with pip install vllm==0.20.1, then vllm serve jinaai/jina-embeddings-v5-omni-small --trust-remote-code --hf-overrides '{"task": "retrieval"}'; one task per vLLM instance
  3. Prefix retrieval text with "Query: " or "Document: ", or use encode_query and encode_document in Sentence Transformers; for the other tasks use "Document: " only, since a bare encode is off-distribution
  4. Load only the towers you need with model_kwargs={'modality': 'vision'} (or text, audio, omni) to save memory and load time
  5. Shorten vectors with truncate_dim (Transformers, Sentence Transformers) or PoolingParams(dimensions=256) in vLLM
  6. Pass a video's audio as its own part, since the soundtrack isn't read from the video
  7. Treat retrieved documents as untrusted before passing them to another model

Qwen3-VL-Embedding-8B

  1. Simplest start is Sentence Transformers 5.4 or later, SentenceTransformer('Qwen/Qwen3-VL-Embedding-8B'), which applies the template and the default instruction and runs no repository code
  2. To serve it, vllm serve Qwen/Qwen3-VL-Embedding-8B --runner pooling, then POST messages with a system instruction and image_url or text parts to /v1/embeddings; vLLM's docs say its video preprocessing differs slightly from Qwen's qwen_vl_utils
  3. Put the task instruction in the system turn, and write it in English, as the card advises; the default is "Represent the user's input."
  4. To shorten vectors, keep the first N of the 4,096 values and L2-normalise again; the card gives 64 as the floor, and the report says int8 vectors hold up while binary ones lose noticeably
  5. For several images per input use the reference embedder in QwenLM/Qwen3-VL-Embedding's src, which is newer than the script in the Hugging Face repository
  6. Keep inputs under 32K tokens; the reference embedder defaults to 8,192, 1,843,200 pixels per image and 64 frames per video
  7. Treat retrieved screenshots and documents as untrusted, since text in an image can carry instructions to whatever model reads the results

Questions

Which is better for AI agents, jina-embeddings-v5-omni-small or Qwen3-VL-Embedding-8B?

Qwen3-VL-Embedding-8B scores 62.1 (B) on agent readiness against jina-embeddings-v5-omni-small's 50.2 (D), and leads in 1 of 5 scored categories. jina-embeddings-v5-omni-small leads on documentation and upkeep.

Other comparisons with jina-embeddings-v5-omni-small or Qwen3-VL-Embedding-8B

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.