Head to head · Text embeddings · October 2026 research run

Granite Embedding Small English R2 vs Qwen3-VL-Embedding-8B

Qwen3-VL-Embedding-8B scores 62.1 (B) on agent readiness against Granite Embedding Small English R2's 41.7 (E), and leads in 3 of 5 scored categories. Granite Embedding Small English R2 leads on reach and risk. Both do text embeddings.

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

Which one, for what

Granite Embedding Small English R2 E

Best for Agents that need small, fast English retrieval embeddings on any hardware with permissive licensing

Ahead on

  • Reach, 70 against 65
  • Risk, 55 against 45

Watch for

English only, one vector size and no task prompts

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 10
  • Agent interface, 65 against 60

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 runGranite Embedding Small English R2Qwen3-VL-Embedding-8BEdge
Capability35%351075Qwen3-VL-Embedding-8B +65
Reach25%257065Granite Embedding Small English R2 +5
Risk20%205545Granite Embedding Small English R2 +10
Agent interface10%106065Qwen3-VL-Embedding-8B +5
Documentation and upkeep10%103741Qwen3-VL-Embedding-8B +4
Negative events≤1500
TotalE 41.7/100B 62.1/100

Facts side by side

FactGranite Embedding Small English R2Qwen3-VL-Embedding-8B
KindOpen-weight modelOpen-weight model
VendorIBMAlibaba (Qwen team)
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceApache-2.0Apache-2.0
Read-only variant documentednono
llms.txtnono
Last release2026-01-212026-04-16
Terms last updatedno 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 reviews3/5 (4)3/5 (4)

Verdicts

Granite Embedding Small English R2

A tiny English embedding cousin for retrieval over long documents and code, 47M parameters with 384-dimension vectors and an 8,192-token input, under Apache 2.0 with a permissive data story. It runs on any hardware through Sentence Transformers, vLLM or llama.cpp. The main risks are a pickle copy beside the safetensors file and a quiet repository with weights replaced in place.

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

Granite Embedding Small English R2

  1. Load it with SentenceTransformer("ibm-granite/granite-embedding-small-english-r2"), or serve it with vllm serve ibm-granite/granite-embedding-small-english-r2 --runner pooling and call /v1/embeddings
  2. Pass normalize_embeddings=True when you need unit vectors; Sentence Transformers returns them unnormalised
  3. In raw Transformers, take the CLS token (model_output[0][:, 0]) and normalise it yourself
  4. Don't add query or passage prefixes; the model takes plain text
  5. Load the safetensors file and ignore pytorch_model.bin, and chunk text past 8,192 tokens
  6. Treat retrieved text as untrusted before passing it to a 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, Granite Embedding Small English R2 or Qwen3-VL-Embedding-8B?

Qwen3-VL-Embedding-8B scores 62.1 (B) on agent readiness against Granite Embedding Small English R2's 41.7 (E), and leads in 3 of 5 scored categories. Granite Embedding Small English R2 leads on reach and risk.

Other comparisons with Granite Embedding Small English R2 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.