Embeddings: how AI finds meaning in your files
What it is — in one coffee-break
An embedding turns a piece of text into a long list of numbers — typically 768 to 1,536 of them — arranged so that texts with similar meaning end up with similar numbers. "How to fix a flat tire" and "changing a punctured wheel" share no keywords, but their embeddings sit right next to each other. That one trick is what powers semantic search, "find similar documents," deduplication, and the retrieval step in every AI assistant that answers from your own files.
Embeddings are produced by an embedding model — a smaller, cheaper cousin of the chat models. You feed it text, it returns the numbers, you store them. Later, you embed a question the same way and ask "which stored texts are closest?"
When you actually need it (and when you don't)
You need embeddings the moment an AI system has to find the right information inside YOUR data — manuals, tickets, contracts, product descriptions — rather than the model's general training. That's the heart of every "chat with your documents" tool. You don't need them for pure generation tasks (write this email, summarize this page you're pasting in) — there's nothing to retrieve.
The practical decisions are smaller than the jargon suggests. Per the 2026 model comparisons: OpenAI's text-embedding-3-small ($0.02 per million tokens) is the safe default that's good enough for ~90% of applications; Jina v3 matches models nine times its price; and open-weight models like BGE-M3 — the one our own news pipeline runs locally, for free — are within a few benchmark points of the paid leaders. The differences between top models matter less than how you chunk your documents.
How to recognize good vs bad implementations
On the audits, the Embeddings element (Em) exposes a real strategy split among the big platforms. Gemini scores 9 — Google sells embeddings, storage and retrieval as one integrated stack. ChatGPT scores 8 with its own well-documented embedding models. Claude scores 3 — not an oversight but a choice: Anthropic expects you to bring your own embeddings, which is fine for developers and a trap for teams who assumed it was included. In workflow tools, look for whether embedding nodes support multiple providers (n8n scores 6.5 for exactly that flexibility) rather than locking you to one.
One gotcha every practitioner learns once: you cannot mix embeddings from different models. Switch models and you re-embed everything — so pick one and stick with it, and keep your ingestion pipeline able to re-run from scratch.
What this costs
Less than almost anything else in AI. Embedding 100,000 support articles (~150M tokens) costs about $3 on OpenAI's small model. Even heavy workloads rarely pass $100/month — the storage of the resulting vectors usually costs more than producing them. Self-hosting an open model drops the per-token cost to zero, at the price of running the hardware — the trade our own pipeline makes with BGE-M3 on a local machine.
Where to see it scored
Compare Em across platforms: Gemini (9), ChatGPT (8), Mistral (7), Claude (3 — bring your own). Embeddings feed the Vector store lesson — that's where the numbers live.