# OpenAI vs Voyage AI embeddings: which one for your RAG?

> OpenAI's text-embedding-3 models and Voyage AI's Voyage 4 family compared on what matters for retrieval: quality on your documents, price, vector size, query and document modes, and switching cost. With a head-to-head benchmark.

Published 2026-10-06, updated 2026-11-14 by Truvec team. Canonical: https://truvec.dev/blog/openai-vs-voyage-embeddings/

OpenAI's embedding models are the default in most RAG tutorials and frameworks. Voyage AI builds embedding models focused on retrieval, and teams often consider it as the alternative. If you're choosing between them, or thinking of switching, the choice deserves more than a glance at a [leaderboard](/blog/mteb-benchmark-validate-embedding-model-before-switching/).

This post compares the two families on the points that matter in production. The last section is a head-to-head benchmark of five models: OpenAI text-embedding-3-small and 3-large against Voyage 4 Lite, Voyage 4 and Voyage 4 Large.

## The line-ups

| | OpenAI | Voyage AI |
|---|---|---|
| Models | text-embedding-3-small, text-embedding-3-large | Voyage 4 Lite, Voyage 4, Voyage 4 Large |
| List price per 1M tokens | $0.02 (small), $0.13 (large) | $0.02 (Lite), $0.06 (4), $0.12 (Large) |
| Dimensions (as run in Truvec) | 1,536 (small), 3,072 (large) | 1,024 |
| Query vs document mode | Same embedding for both | Separate `query` and `document` input types |

Prices are list prices at the time of writing; check the providers' pricing pages.

## Differences that matter

**Price tiers.** Both have a cheap model at the same list price. Voyage adds a middle tier, which matters when the cheap model isn't good enough and the large one costs more than you want to pay.

**Vector size.** OpenAI 3-large produces 3,072 dimensions, three times Voyage's 1,024. At a million chunks that's about 12 GB of raw vectors against 4 GB, which matters if your vector database keeps them in memory. OpenAI's v3 models can return shortened vectors (the `dimensions` parameter), trading some quality for size; test the shortened size if you plan to use it.

**Query and document modes.** Voyage embeds questions and passages differently when told which is which. This asymmetry suits retrieval, where short questions are matched against long passages. OpenAI uses one embedding for both, which is simpler but gives the model less to work with.

**Ecosystem.** OpenAI is supported everywhere by default. Voyage is supported by the major frameworks and vector databases too, but if you already run everything on OpenAI, adding a second provider means a second key, a second bill and a second set of rate limits.

**Switching cost.** Vectors from different models aren't compatible. Switching means re-embedding the whole corpus and re-indexing it. That cost is a reason to compare carefully before you commit, not a reason to never switch.

## How to decide

1. Run both families on your own documents, at the top *k* you use in production.
2. If the results are within the noise (a couple of points with 100 questions), choose on price, vector size and operations. Staying on the provider you already use is a valid tie-breaker.
3. If one family is clearly ahead, check that the lead holds across question types, using the example questions where the models disagree.
4. Compare the mid-tier models too. "Large vs large" isn't the only fair fight: a cheaper model that ties with an expensive one is the better buy.

The benchmark below compares the five models on developer documentation and support articles.

## Benchmark: OpenAI vs Voyage AI on a technical knowledge base

Real benchmark generated by Truvec (benchmark #8, run 2026-11-14). Raw data: [benchmark.json](https://truvec.dev/blog/openai-vs-voyage-embeddings/benchmark.json), [benchmark.csv](https://truvec.dev/blog/openai-vs-voyage-embeddings/benchmark.csv). Full report with every question: [report.pdf](https://truvec.dev/blog/openai-vs-voyage-embeddings/report.pdf).

- Corpus: Docker documentation: manuals, FAQs, billing and support pages (https://github.com/docker/docs), 261 documents, 1,944 chunks
- Chunking: recursive, 1000 chars, 200 overlap
- Golden set: 100 questions generated by gpt-5.6-luna, human-reviewed
- Retrieval: top 5 by cosine similarity; models ranked by MRR, then recall@k

### Key results

- **Voyage 4 Large** ranks first, with an MRR of 0.922 and a hit rate of 99.0% in the top 5.
- One model is within 0.02 MRR of the winner (Voyage 4): on this corpus they are practically tied.
- Hit rate ranges from 95.0% to 100.0% across the 5 models.
- Cheapest model within 2 points of the winner's hit rate: **Voyage 4 Lite**, $0.0067 to embed this corpus against $0.04.
- Fastest to embed a query: **OpenAI text-embedding-3-small** (4.8 ms per query, measured in batch from our servers).

### Retrieval quality

| Rank | Model | Provider | Hit rate@5 | Recall@5 | MRR | nDCG@5 | Precision@5 |
| --- | --- | --- | ---: | ---: | ---: | ---: | ---: |
| 1 | Voyage 4 Large | voyage | 99.0% | 97.5% | 0.922 | 0.924 | 20.6% |
| 2 | Voyage 4 | voyage | 100.0% | 99.5% | 0.915 | 0.929 | 21.2% |
| 3 | Voyage 4 Lite | voyage | 99.0% | 97.5% | 0.893 | 0.907 | 20.6% |
| 4 | OpenAI text-embedding-3-large | openai | 99.0% | 97.5% | 0.867 | 0.885 | 20.6% |
| 5 | OpenAI text-embedding-3-small | openai | 95.0% | 93.5% | 0.769 | 0.807 | 19.8% |

### Hit rate by position

| Model | Top 1 | Top 2 | Top 3 | Top 4 | Top 5 |
| --- | ---: | ---: | ---: | ---: | ---: |
| Voyage 4 Large | 87.0% | 94.0% | 99.0% | 99.0% | 99.0% |
| Voyage 4 | 85.0% | 95.0% | 99.0% | 99.0% | 100.0% |
| Voyage 4 Lite | 81.0% | 95.0% | 99.0% | 99.0% | 99.0% |
| OpenAI text-embedding-3-large | 79.0% | 88.0% | 94.0% | 98.0% | 99.0% |
| OpenAI text-embedding-3-small | 63.0% | 84.0% | 92.0% | 94.0% | 95.0% |

### Cost, speed and size

| Model | Price / 1M tokens | Embed the corpus | 1,000 queries | Query embedding | Search p95 | Vectors |
| --- | ---: | ---: | ---: | ---: | ---: | ---: |
| Voyage 4 Large | $0.12 | $0.04 | $0.0024 | 18 ms | 61 ms | 7.6 MB |
| Voyage 4 | $0.06 | $0.02 | $0.0012 | 44 ms | 56 ms | 7.6 MB |
| Voyage 4 Lite | $0.02 | $0.0067 | $0.0004 | 15 ms | 25 ms | 7.6 MB |
| OpenAI text-embedding-3-large | $0.13 | $0.04 | $0.0026 | 13 ms | 124 ms | 22.8 MB |
| OpenAI text-embedding-3-small | $0.02 | $0.0067 | $0.0004 | 4.8 ms | 32 ms | 11.4 MB |

### Score separation

| Model | Relevant chunk | Best distractor | Gap |
| --- | ---: | ---: | ---: |
| Voyage 4 Large | 0.653 | 0.607 | 0.046 |
| Voyage 4 | 0.692 | 0.646 | 0.046 |
| Voyage 4 Lite | 0.665 | 0.622 | 0.044 |
| OpenAI text-embedding-3-large | 0.687 | 0.650 | 0.037 |
| OpenAI text-embedding-3-small | 0.715 | 0.687 | 0.027 |

### Example questions

Rank of the first relevant chunk per model ("miss": not in the top 5).

| Question | Voyage 4 Large | Voyage 4 | Voyage 4 Lite | OpenAI text-embedding-3-large | OpenAI text-embedding-3-small |
| --- | ---: | ---: | ---: | ---: | ---: |
| When both JIT and SCIM are enabled, how are organization roles and account deactivation handled? | 1 | 1 | 2 | 5 | miss |
| When multiple Compose files are supplied with `-f`, how are their service settings combined, and which file takes precedence? | 1 | 2 | 3 | 1 | 4 |
| What command builds the Docker image for the Spring Boot hello world app, and how can I check the size of the resulting image? | 2 | 3 | 2 | 1 | 5 |
| How can I combine multiple Compose files, and what issue might arise as the configuration becomes more complex? | 2 | 3 | 2 | 1 | 1 |
| How do I push an image to Docker Hub, and what tagging restriction applies? | miss | 5 | miss | miss | 1 |
| Which organizational roles and subscription plans are needed to create organization access tokens in Docker? | 1 | 1 | 1 | 4 | miss |
| Which Docker Desktop versions are supported under the Pro, Team, and Business plans? | 1 | 1 | 1 | 2 | 3 |
| What tasks can Docker Compose perform for a multi-container application besides starting its services? | 2 | 2 | 3 | 1 | 1 |

### Notes

- The corpus is a subset of the public Docker documentation (Apache 2.0), taken from github.com/docker/docs at commit 553482c: the Desktop, Docker Hub, Compose, accounts, security and subscription and billing manuals, the FAQs, the support pages and the getting-started guides. Release notes and pages shorter than 600 characters were left out, and pages were cut at 40,000 characters.
- Several posts on this blog use this corpus and the same 100 questions, each with its own selection of models. A model can differ by a question between two of these runs: questions are embedded again at each run, and vector search is approximate.
- With 100 questions, a gap of a couple of points between two models is within the noise.

### Metric definitions

- **Hit rate**: Share of questions with at least one relevant chunk in the top k results. The most direct answer to "does the right passage reach the LLM?".
- **Recall**: Share of the relevant chunks found in the top k, averaged over questions. Matters when an answer spans several chunks.
- **MRR**: Mean reciprocal rank: 1 when the first relevant chunk is ranked first, 1/2 when second, 0 when missing. Rewards putting the answer at the top.
- **nDCG**: Normalized discounted cumulative gain: how close the ranking of all relevant chunks is to the ideal ranking.
- **Precision**: Share of the top k results that are relevant. Low precision means more noise sent to the LLM.
