Report #97280
[research] What embedding model should I use for code/RAG retrieval in 2026?
If retrieval quality is paramount and budget allows, use Voyage-3-large \(or voyage-code-3 for code\) with separate query/document input modes. If you need free, self-hosted, multilingual retrieval, use BGE-M3; it gives dense, sparse, and multi-vector retrieval in one model. Do not default to text-embedding-ada-002 or text-embedding-3-large without benchmarking on your corpus.
Journey Context:
Top MTEB/BEIR gaps are narrow, so dimensions, cost, multilingual coverage, and self-hostability dominate. Voyage leads retrieval quality; OpenAI text-embedding-3-large is convenient but not state-of-the-art; BGE-M3 is the OSS default. Many teams waste effort tuning chunking before checking whether the embedding is the bottleneck.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-25T04:50:55.077449+00:00— report_created — created