snowflake-arctic-embed-l-v2.0
by Snowflake
Multilingual text embeddings with Matryoshka truncation for cheaper retrieval
Snowflake/snowflake-arctic-embed-l-v2.0mixpeek://text_extractor@v1/snowflake_arctic_embed_l_v2Deploy snowflake-arctic-embed-l-v2.0
Single-tenantMixpeek has no managed extractor for this model. On a single-tenant deployment you upload the weights and a custom plugin serves them next to the rest of your pipeline.
Overview
Arctic Embed 2.0 (Large) is Snowflake's open retrieval embedding model. Its headline trait is that it is multilingual without giving up English quality: it stays competitive on English MTEB retrieval while adding strong cross-lingual retrieval (MIRACL, CLEF) in one model, so you don't run a separate encoder per language.
Its second trait is practical: it is trained with Matryoshka Representation Learning, so a full 1024-dim vector can be truncated to 256 dims with only a few points of retrieval loss. That is a 4× cut in vector storage and memory with no re-embedding: you store the short vector and search it directly. On Mixpeek, Arctic Embed 2.0 is a strong default for multilingual document and transcript search where storage budget matters.
Architecture
~568M-parameter multilingual encoder (GTE-multilingual base) producing 1024-dim embeddings with an 8192-token context window. Trained with Matryoshka Representation Learning so the first 256 / 512 dimensions are themselves usable embeddings, plus contrastive training with hard negatives and a multilingual + English data mix tuned to avoid the usual multilingual-vs-English quality tradeoff. Mean pooling over token states; compare with cosine.
Mixpeek SDK Integration
// No extractor parameter takes a Hugging Face model id (checked against
// GET /v1/discovery/extractors, which returns 13), so snowflake-arctic-embed-l-v2.0 runs
// on your side and the output is upserted through POST
// /v1/namespaces/{namespace_id}/documents/upsert. On Enterprise the other
// path is to upload the weights instead: POST /v1/namespaces/{id}/models
// accepts the huggingface format and a custom plugin loads them.
const res = await fetch(
"https://api.mixpeek.com/v1/namespaces/ns_your_namespace/documents/upsert",
{
method: "POST",
headers: {
Authorization: "Bearer API_KEY",
"Content-Type": "application/json",
},
body: JSON.stringify({
collection_id: "col_your_collection",
documents: [
{
document_id: "asset-00412",
// The vector name has to match a vector index on the collection.
vectors: { "text-embedding": yourVector },
payload: { source_key: "archive/2026/asset-00412" },
},
],
}),
},
);
// Managed alternative, if this exact model is not the requirement:
// text_extractor@v1 runs intfloat/multilingual-e5-large-instruct
// (1024-d) over a bucket, with no inference of your own.Capabilities
- Strong English retrieval AND broad multilingual / cross-lingual retrieval in one model
- Matryoshka dims: truncate 1024 → 256 for ~4× smaller vectors, minimal recall loss
- 8192-token context for long documents
- Open weights (Apache-2.0), self-hostable
- Drop-in 1024-dim dense vectors for any vector store
Use Cases on Mixpeek
Benchmarks
| Dataset | Metric | Score | Source |
|---|---|---|---|
| MTEB Retrieval (English) | nDCG@10 | - | Competitive with strong English-only models of similar size; see report for the full table. |
| MIRACL (multilingual) | nDCG@10 | - | Strong multilingual retrieval without an English-quality regression: the model's core claim. |
Explore on Mixpeek
Compare alternatives in this category
Hand-picked tools & platforms compared
Deep-dive technical guide
See how Mixpeek runs models as extractors
Store & search embeddings at scale
Usage-based pricing for pipelines
Compare models, APIs & infrastructure
Specification
Research Paper
Arctic-Embed 2.0: Multilingual Retrieval Without Compromise
arxiv.orgBuild a pipeline with snowflake-arctic-embed-l-v2.0
Add this model to a processing pipeline alongside other extractors. Combine with retrieval stages for end-to-end search.
Run it on your own data, free