Skip to main content
Embedders convert text into vectors (lists of numbers) that capture meaning. These vectors enable semantic search, so “How do I reset my passcode?” finds documents mentioning “change PIN” even without keyword matches.

How It Works

  1. Insert: When you add content, each chunk is converted to a vector
  2. Store: Vectors are saved in your vector database
  3. Search: Queries are embedded and matched against stored vectors by similarity
Many vector database implementations, including PgVector, use OpenAIEmbedder when embedder is omitted. Provider-hosted implementations can differ. UpstashVectorDb uses Upstash hosted embeddings when embedder is omitted.

Configuration

Using with Knowledge

Batch Embeddings

Process multiple texts in a single API call to reduce requests and improve performance:
Embedders with batch support: OpenAI, Azure OpenAI, Gemini, Cohere, Voyage AI, Mistral, Fireworks, Together, Jina, Nebius, LangDB, vLLM.

Best Practices

Re-embed when changing models: Vectors from different embedders aren’t compatible. If you switch embedders, you must re-embed all content.
Test retrieval quality: Use sample queries to verify you’re finding the right chunks. Adjust chunking strategy or embedder if results are poor.
Match dimensions: Ensure your embedder’s output dimensions match what your vector database expects.

Supported Embedders

Choosing an Embedder

Key factors:
  • Hosted vs local: Local for privacy and no API costs; hosted for quality and convenience
  • Latency and cost: Smaller models are cheaper and faster; larger models often retrieve better
  • Language support: Ensure your embedder supports your content’s languages
  • Dimension size: Match your vector database’s expected embedding dimensions

Next Steps

OpenAI Embedder

Default embedder setup

Ollama Embedder

Local embeddings for privacy

Vector DB

Store your embeddings

Chunking

Prepare content for embedding