AI Agent News/stories/google-releases-embeddinggemma-2-an-open-multimodal-embedding-model.md

Search

Google releases EmbeddingGemma 2, an open multimodal embedding model

Google has released EmbeddingGemma 2, an Apache 2.0 licensed open-weight model that maps text, code, images, video and audio into one 768-dimensional embedding space. It is built for on-device search and retrieval-augmented generation, with 270 million parameters for text and code and 740 million for full multimodal support.

Source: www.infoq.com/news/2026/10/embeddinggemma-2-multimodal/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=AI%2C+ML+%26+Data+Engineering

EmbeddingGemma 2 is based on Gemma 4 and is designed to run on consumer hardware such as phones and laptops, with low-latency output for search, RAG, classification and clustering. Developers can load only the encoders they need, starting at 270 million parameters for text and code and scaling to 740 million for full multimodal support. Google says the model significantly outperforms EmbeddingGemma 1 on code search and technical retrieval.

Because all media types share one embedding space, a single index can match a text query against documents, screenshots, recordings and video. The model supports Matryoshka Representation Learning, so vectors can be shortened to save storage. Google's example puts a million 768-dimensional vectors at bfloat16 at about 1.5 GB, and 128 dimensions at about 250 MB, a sixfold reduction.

Google recommends truncating only when storage or search speed requires it, since at 128 dimensions the model keeps about 90% of quality for text but only around 75% for image, video and speech retrieval. The model is available on Hugging Face.

Why it matters if you build agents

Agents that search code, documents and media can use one local index instead of maintaining separate embedding spaces for each media type. Truncating vectors trades retrieval quality for storage, and the loss is larger for non-text media. Reddit commenters quoted in the article warned that task prefixes affect recall and that truncated vectors should be sliced before normalizing, so check both before indexing.

Get stories like this every weekday

One short email with the day's agent tooling news.

Subscribe