Skip to content

Qwen3 Embedding 4B

Qwen3 Embedding 4B is a mid-tier 4-billion-parameter text embedding model producing 2560-dimensional vectors over a context of 32.8K tokens, designed for multilingual semantic search and code retrieval that balances quality with operational cost.

index.ts
import { embed } from 'ai';


const result = await embed({
  model: 'alibaba/qwen3-embedding-4b',
  value: 'Sunny day at the beach',
})
OverviewAboutProvidersThroughputLatencySimilarFAQ

Frequently Asked Questions

  • What output dimensionality does Qwen3 Embedding 4B produce?

    The model outputs 2560-dimensional vectors by default. Matryoshka Representation Learning allows prefix truncation to smaller sizes if storage or query-speed budgets require it.

  • How does the 4B model differ architecturally from the 0.6B and 8B variants?

    All three variants use a dual-encoder structure and share the same context window of 32.8K tokens. The 4B model uses 36 layers (compared to 28 in the 0.6B) and produces 2560-dimensional vectors, wider than the 0.6B's 1024 dimensions but narrower than the 8B's 4096.

  • What multilingual coverage does Qwen3 Embedding 4B support?

    Qwen3 Embedding 4B covers more than 100 natural languages plus multiple programming languages, enabling cross-lingual and code-retrieval tasks within a single embedding space.

  • Can instruction prefixes change what the model retrieves?

    Yes. The model supports custom instruction prefixes at query time to guide the embedding toward a specific retrieval task, such as legal document search vs. general knowledge retrieval.

  • Is this model appropriate for code-retrieval tasks alongside natural language?

    Yes. The Qwen3 Embedding models explicitly include code in their language coverage, so hybrid corpora of code and prose can be embedded in the same vector space.

  • How does chunking strategy affect retrieval quality at context of 32.8K tokens?

    Longer passages embedded as single units can yield better recall for complex queries, but very long inputs near the ceiling of 32.8K tokens may dilute specificity. Experiments with paragraph-level vs. section-level chunking are worthwhile for your specific domain.