---
title: Jina models
description: This page collects all Jina models you can use as part of the Elastic Stack. Currently, the following models are available as built-in models: jina-embeddings-v3...
url: https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/4491/explore-analyze/machine-learning/nlp/ml-nlp-jina
products:
  - Machine Learning
---

# Jina models
This page collects all Jina models you can use as part of the Elastic Stack.
Currently, the following models are available as built-in models:
- [`jina-embeddings-v3`](#jina-embeddings-v3)


## `jina-embeddings-v3`

The [`jina-embeddings-v3`](https://jina.ai/models/jina-embeddings-v3/) is a multilingual dense vector embedding model that you can use through the [Elastic Inference Service (EIS)](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/4491/explore-analyze/elastic-inference/eis).
It provides long-context embeddings across a wide range of languages without requiring you to configure, download, or deploy any model artifacts yourself.
As the model runs on EIS, Elastic's own infrastructure, no ML node scaling and configuration is required to use it.
The `jina-embedings-v3` model supports input lengths of up to 8192 tokens and produces 1024-dimension embeddings by default. It uses task-specific adapters to optimize embeddings for different use cases (such as retrieval or classification), and includes support for Matryoshka Representation Learning, which allows you to truncate embeddings to fewer dimensions with minimal loss in quality.
For more info, refer to the [model card](https://huggingface.co/jinaai/jina-embeddings-v3) on Hugging Face.

### Dense vector embeddings

Dense vector embeddings are fixed-length numerical representations of text. When you send text to an EIS inference endpoint that uses `jina-embeddings-v3`, the model returns a vector of floating-point numbers (for example, 1024 values). Texts that are semantically similar have embeddings that are close to each other in this vector space. Elasticsearch stores these vectors in [`dense_vector`](https://docs-v3-preview.elastic.dev/elastic/elasticsearch/tree/main/reference/elasticsearch/mapping-reference/dense-vector) fields or through the [`semantic_text`](https://docs-v3-preview.elastic.dev/elastic/elasticsearch/tree/main/reference/elasticsearch/mapping-reference/semantic-text) type and uses vector similarity search to retrieve the most relevant documents for a given query. Unlike [ELSER](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/4491/explore-analyze/machine-learning/nlp/ml-nlp-elser), which expands text into sparse token-weight vectors, this model produces compact dense vectors that are well suited for multilingual and cross-domain use cases.

### Requirements

To use `jina-embeddings-v3`, you must have the [appropriate subscription](https://www.elastic.co/subscriptions) level or the trial period activated.

### Getting started with `jina-embeddings-v3` via the Elastic Inference Service

Create an inference endpoint that references the `jina-embeddings-v3` model in the `model_id` field.
```json

{
  "service": "elastic",
  "service_settings": {
    "model_id": "jina-embeddings-v3"
  }
}
```

The created inference endpoint uses the model for inference operations on the Elastic Inference Service. You can reference the `inference_id` of the endpoint in text_embedding inference tasks or search queries.
For example, the following API request ingests the input text and produce embeddings.
```json

{
  "input": "The sky above the port was the color of television tuned to a dead channel.",
  "input_type": "ingest"
}
```


### Performance considerations

- `jina-embeddings-v3` works best on small, medium or large sized fields that contain natural language.
  For connector or web crawler use cases, this aligns best with fields like title, description, summary, or abstract.
  Although `jina-embeddings-v3` has a context window of 8192 tokens, it's best to limit the input to 2048-4096 tokens for optimal performance.
  For larger fields that exceed this limit - for example, `body_content` on web crawler documents - consider chunking the content into multiple values, where each chunk can be under 4096 tokens.
- Larger documents take longer at ingestion time, and inference time per document also increases the more fields in a document that need to be processed.
- The more fields your pipeline has to perform inference on, the longer it takes per document to ingest.