Fine-Tuning Cost Calculator
Estimate what a fine-tune costs to train and run, and when it pays for itself.
Estimate the cost and vector storage of embedding a document corpus for RAG.
Your corpus
Every month
The Embedding Cost Calculator estimates chunks, vectors, embedding tokens, one-off and monthly cost, and vector database storage for a retrieval corpus, across OpenAI, Cohere, Voyage, Google and open embedding models at float32, half, int8 or binary precision.
Building retrieval over your documents means splitting them into chunks, turning every chunk into an embedding vector, storing those vectors, and embedding every search query as it arrives. This calculator estimates each part before you commit to a model or a database.
Enter the number of documents and their average length, then the chunk size and overlap. You get the chunks per document, the total vectors, and the tokens embedded — including the overlap, which is embedded twice. Choose an embedding model from OpenAI, Cohere, Voyage, Google or an open model to load its price and dimensions, and add how much of the corpus changes each month and how many queries you serve.
The storage estimate is often the more important number. Raw vectors, an HNSW index and the chunk text are sized separately, and switching the stored precision from float32 to halfvec, int8 or binary shows how much memory your vector database server really needs.
Chunks per document and the extra tokens embedded twice by overlap.
Initial embedding plus re-embedding churn and query embeddings.
Raw vectors, HNSW index and chunk text sized separately.
float32, halfvec, int8 and binary, to see how much memory quantized vectors save.
Prices and dimensions load automatically and stay editable.
Its price per million tokens and vector dimensions fill in automatically.
Number of documents, average words per document, chunk size and overlap.
The share of the corpus re-embedded each month, and search queries served.
One-off and monthly cost, and the memory to size your vector database for.
text-embedding-3-small is priced at a few cents per million tokens, so embedding tens of thousands of documents usually costs less than a few dollars. Storage and hosting typically cost more than the embeddings themselves.
Between 256 and 1,024 tokens is typical, with 10 to 20 percent overlap. Smaller chunks give more precise matches; larger ones keep more context around each match.
Dimensions multiplied by bytes per value. A 1,536-dimension float32 vector is about 6 KB; the index and metadata add to that.
Yes. Half precision halves storage with almost no recall loss, int8 quarters it with a small loss, and binary vectors are tiny but usually need a re-ranking step.
Yes. Overlapping tokens are embedded in both neighbouring chunks, so heavy overlap raises both the embedding bill and the number of vectors stored.
What people who use the Embedding Cost Calculator think of it. Reviews come from visitors and are posted as written.
No ratings yet
Yours would be the first.
0 reviews
Newest first
No reviews yet
Be the first to rate the Embedding Cost Calculator. It takes half a minute and no account.
Write the first reviewEstimate what a fine-tune costs to train and run, and when it pays for itself.
Generate MCP server config for Claude Desktop, Claude Code, Cursor, VS Code and Windsurf.
Build detailed image prompts for Midjourney, Stable Diffusion and DALL-E.
Turn conversations.json from a ChatGPT or Claude export into readable Markdown files.
Estimate how many tokens your text costs before you send it.
Turn input and output pairs into a clean, consistent few-shot prompt block.
Add aspect ratio, stylize, chaos, style references and more to a Midjourney prompt.
Turn question and answer pairs into a JSONL training file for OpenAI, Llama or Gemini.