Embedding Models/Cohere Embed v4

Cohere Embed v4 by Cohere — 1536D

Multimodal embedding model for text, images, and PDFs. Supports flexible dimensions and 128K context length.

At a glance

Modalities

Dimensions

2K

Max tokens

128K

Parameters

Price / 1M tokens

Type

Dense

Matryoshka dimensions

25651210241536

Output types

Single VectorMulti Vector

Language support

🌍 Multilingual support (100+ languages)

Details

Release date 2025-01-01
License Proprietary
Model ID cohere-embed-v4
Provider Cohere

Tags

multimodal-embeddinglong-contextmatryoshka

What You Need to Know About Cohere Embed v4

Complete Specifications for Cohere Embed v4 by Cohere

Get detailed specifications for Cohere Embed v4, including output dimensionality of 1536 dimensions, maximum input token length, supported input modalities, and pricing per million tokens. This embedding model is designed for semantic search, text classification, clustering, and retrieval-augmented generation applications where understanding the relationship between texts is essential.

Pricing and Cost Efficiency for Cohere Embed v4

Review the pricing structure for Cohere Embed v4 and compare it against other embedding models from Cohere and competitors. Understanding embedding model costs is essential when scaling vector search and RAG applications to millions of documents. We provide transparent pricing to help you budget effectively.

Use Cases and Applications for Cohere Embed v4

Explore the ideal use cases for Cohere Embed v4. Whether you are building a semantic search engine, recommendation system, document classification pipeline, or multilingual retrieval system, understanding this model's capabilities and dimensionality will help you choose the right embedding strategy for your project.

How to Validate Cohere Embed v4 Before Production

Evaluate Cohere Embed v4 with representative documents and queries before committing to a production index. Measure retrieval quality at the model's supported dimensions, test the longest inputs your application accepts, and compare latency, storage, and reranking requirements. Keep preprocessing identical between documents and queries, verify the provider's current usage terms, and record the exact model version so future index rebuilds remain reproducible.