Best reranker in 2026: Qwen3, bge, mxbai, Jina, GTE and the hosted APIs compared
Every reranker vendor publishes a table in which its own model wins, and the tables use different datasets, so the numbers cannot be lined up across vendors. This page only sets scores side by side when they come from one run, says whose run it was, and says plainly which models have no number that can be compared.
The short answer
- Self-hosting on a GPU and want the best open model: Qwen3-Reranker-4B. In both runs below it is at or near the top, and it is Apache 2.0.
- Small, CPU-friendly, multilingual: bge-reranker-v2-m3 is the standard baseline; the GTE rerankers are smaller still, and Hindsight’s hs-rerank-1 (MIT, 114M) is smaller again but comes with no scores we can quote.
- No GPU and no ops: a hosted API. Cohere Rerank 5 and Voyage rerank-3 are the established ones, zerank-2 the cheapest per token.
- Commercial product, open weights: check the licence first. Jina’s weights are non-commercial.
Which numbers can be compared
A score only means something next to scores from the same run: the same datasets, the same candidate lists from the same first-stage retriever, the same cut-off. Two numbers from two vendors’ pages are not on one scale, even when both say “nDCG@10” or “BEIR”. This page uses two runs that cover several models at once, and both were run by a vendor with a model of its own in the table, so read them as strong hints and confirm on your own labelled queries (how).
Three families have no run to put here. GTE: Alibaba publishes its reranking results as a chart, so there is no table to line up. Cohere: no benchmark table has been published for Rerank 5. hs-rerank-1: Hindsight’s model card shows its results as an image only. They are compared below on size, licence, price and fit instead.
Qwen3 against bge-reranker-v2-m3
This is Qwen’s own run, from the Qwen3-Reranker model cards: the retrieval subsets of MTEB (English, Chinese, multilingual and code) and MLDR for long documents, each reranking the same top 100 candidates.
| Model | MTEB-R | CMTEB-R | MMTEB-R | MLDR | MTEB-Code |
|---|---|---|---|---|---|
| Qwen3-Reranker-8B | 69.02* | 77.45 | 72.94 | 70.19 | 81.22 |
| Qwen3-Reranker-4B | 69.76* | 75.94 | 72.74 | 69.97 | 81.20 |
| Qwen3-Reranker-0.6B | 65.80* | 71.31 | 66.36 | 67.28 | 73.42 |
| bge-reranker-v2-m3 | 57.03 | 72.16 | 58.36 | 59.51 | 41.38 |
The 4B and 8B lead bge-reranker-v2-m3 on every column, and the gap is widest on code. The 0.6B is the exception that matters if you work in Chinese: on CMTEB-R it scores 71.31 against bge’s 72.16, so shrinking to 0.6B costs the lead there. The 8B is not clearly better than the 4B: it is ahead only on Chinese, level on multilingual, long documents and code, and behind on English.
Qwen3, mxbai and Jina on one BEIR run
This is Jina’s 2026 evaluation, from the jina-reranker-v3.5 model card. Jina re-ran six models under one protocol (nDCG@10): 13 BEIR datasets, MIRACL for multilingual retrieval, RTEB for professional domains (legal, finance, code, medical) and Struct-IR for structured data, each reranking the top 100 candidates from jina-embeddings-v5-text-small. The table shows four of them; bge-reranker-v2-m3 was not in the run.
| Model | BEIR | MIRACL | RTEB | Struct-IR |
|---|---|---|---|---|
| jina-reranker-v3.5 (0.6B) | 63.20 | 74.11 | 70.95 | 48.3 |
| mxbai-rerank-large-v2 (1.5B) | 62.45 | 69.65 | 70.81 | 43.0 |
| Qwen3-Reranker-4B | 62.28 | 76.56 | 77.68 | 55.6 |
| Qwen3-Reranker-0.6B | 56.94 | 67.12 | 68.41 | 41.9 |
On plain English BEIR the top three are within a point of each other, so that benchmark cannot pick between them. The differences show up elsewhere: Qwen3-Reranker-4B leads on multilingual, professional-domain and structured retrieval by clear margins. Jina’s own model tops BEIR in Jina’s own run; its weights are non-commercial, so for a product the practical comparison is Qwen3 against mxbai.
Size, licence and where each runs
| Model | Size | Licence | Languages | Run it on |
|---|---|---|---|---|
| Qwen3-Reranker | 0.6B / 4B / 8B | Apache 2.0 | 100+ | GPU recommended |
| bge-reranker-v2-m3 | 568M | Open weights | 100+ | CPU or GPU |
| mxbai-rerank-large-v2 | 1.5B | Apache 2.0 | 100+ | GPU recommended |
| jina-reranker-v3.5 | 0.6B | Non-commercial weights | Multilingual | Hosted API, or weights for research |
| hs-rerank-1 | 114M | MIT | 8, incl. Chinese, Japanese and Korean | CPU (int8 ONNX) or GPU |
| GTE rerankers | 149M / 306M | Apache 2.0 | English / 70+ | CPU, small GPU or browser (English) |
Sizes and licences are from each model’s own page here, which cite the vendors’ model cards; hs-rerank-1 has no page of its own, so its row comes straight from its model card. “Open weights” means the licence is not restated on this page; check the card before shipping.
Hosted APIs
You pay per token instead of running a GPU. None of these vendors publishes a comparable benchmark, so the table gives what can be checked: the price and the context length.
| API | Price per million tokens | Context | Benchmark |
|---|---|---|---|
| Cohere Rerank 5 Pro / Fast | $0.05 / $0.02 | 32,768 tokens | None published |
| Voyage rerank-3 / lite | $0.05 / $0.02 | 32,000 tokens | Voyage’s own evaluations only |
| zerank-2 | $0.025 | 32,768 tokens | ZeroEntropy’s own run only |
Per-token and per-search prices are billed differently, so the cheapest sticker price is not always the cheapest bill. The cost calculator works it out for your documents per query and queries per month.
How to decide
- Pick two candidates from this page: one open model you could host and one hosted API.
- Label 30–50 real queries from your own users with the passages that answer them.
- Run both and compare nDCG@10 on your labels, with the same candidate list. This is the only comparison that predicts your result; the evaluation guide walks through it.
- Check that reranking is the bottleneck. If the right passage is never in the candidates, no reranker helps; see why reranking didn’t help.
See the whole market in one table
Every model and hosted API, with the protocol behind each score, and a one-click jump to the browser demo.
Compare all models → Choose by scenario →