{"slug": "embeddinggemma-2-expands-beyond-text-to-support-code-images-video-and-audio", "title": "EmbeddingGemma 2 Expands Beyond Text to Support Code, Images, Video, and Audio", "summary": "Google released EmbeddingGemma 2, an open-weight multimodal embedding model built on Gemma 4 and licensed under Apache 2.0, which maps text, code, images, video, and audio into a single 768-dimensional embedding space. The model scales from 270 million parameters for text and code to 740 million for full multimodal support, runs on consumer hardware such as mobile devices and laptops, and Google says it \"significantly outperforms EmbeddingGemma 1 on code search and technical retrieval.\" EmbeddingGemma 2 is available on Hugging Face, and its Matryoshka Representation Learning support lets developers truncate embeddings from 768 to 128 dimensions, cutting storage for a million vectors from roughly 1.5 GB to 250 MB at a cost of about 90% retained quality on text versus around 75% on image, video, and speech retrieval.", "body_md": "Based on Gemma 4 and released under the Apache 2.0 license, [Google's EmbeddingGemma 2 is a compact, open-weight, multimodal embedding model](https://blog.google/innovation-and-ai/technology/developers-tools/embeddinggemma-2/) designed to make semantic search and retrieval-augmented generation (RAG) more efficient while optimizing performance for on-device deployment.\n\nDesigned to run on consumer hardware such as mobile devices and laptops, EmbeddingGemma 2 delivers low-latency semantic representations for on-device applications, like search, retrieval-augmented generation (RAG), classification, and clustering.\n\nThanks to its multimodal capabilities, EmbeddingGemma 2 supports a wide range of retrieval tasks, including finding relevant documents, screenshots, and recordings in response to a query, searching source code using natural language, and retrieving video content based on textual descriptions.\n\nEmbeddingGemma 2's key feature, Google says, is its ability to represent text, code, images, video, and audio in a unified 768-dimensional embedding space. This enables developers to build retrieval systems that search across different media types without maintaining separate, incompatible embedding spaces for different media types.\n\nDespite coming from different modalities, the embeddings generated by EmbeddingGemma 2 occupy the same dimensional space and can be compared on their semantic similarity.\n\nThe model allows developers to load only the encoders required for their applications, scaling from 270 million parameters for text and code to 740 million for full multimodal support. According to Google, the model \"significantly outperforms EmbeddingGemma 1 on code search and technical retrieval, making it ideal for local codebase indexing and agentic code search\".\n\nEmbeddingGemma 2 supports [Matryoshka Representation Learning](https://huggingface.co/blog/matryoshka) (MRL), which allows embeddings to be truncated into shorter, unit-length vectors, reducing storage requirements. For example, storing a million 768-dimensional vectors at bfloat16 precision takes roughly 1.5 GB of memory, while truncating them to 128 dimensions requires just 250 MB, bringing a sixfold reduction. However, this implies a retrieval quality trade-off. Google therefore recommends using truncation only when storage or search speed require it. At 128 dimensions, the model retains approximately 90% of quality with text, but performance drops to around 75% for image, video, and speech retrieval.\n\nCommenting on the announcement, [Reddit user Distinct-Target7503 highlighted the model's multimodal capabilities](https://www.reddit.com/r/unsloth/comments/1wz6qri/comment/peangxf/) while questioning the extent of its improvements for text-only tasks:\n\nThe impressive thing about this one is that it can embedd images and audio in a shared semantic space, but for text only it is not a massive improvement.\n\nMeanwhile, Reddit user [Open-Adhesiveness-86 cautioned developers about the importance of using the model correctly](https://www.reddit.com/r/LocalLLaMA/comments/1wz5va3/comment/pe9clts/):\n\nTwo things that bit me on the first embeddinggemma and probably still apply: the task prefixes aren't optional, indexing docs with the query prefix instead of \"title: none | text: \" noticeably hurt recall. And if you truncate for MRL, slice first then L2-normalize the shorter vector, normalizing at 768 and then cutting gives you off-norm vectors.\n\n[EmbeddingGemma was introduced last year](https://www.infoq.com/news/2025/09/embedding-gemma/) with a focus on \"offline and privacy-sensitive scenarios, such as searching across personal files locally, running mobile RAG pipelines with Gemma 3n, or building domain-specific chatbots\". [EmbeddingGemma 2 is available on Hugging Face](https://huggingface.co/google/embeddinggemma-2).", "url": "https://wpnews.pro/news/embeddinggemma-2-expands-beyond-text-to-support-code-images-video-and-audio", "canonical_source": "https://www.infoq.com/news/2026/10/embeddinggemma-2-multimodal/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=global", "published_at": "2026-10-19 10:00:00+00:00", "updated_at": "2026-10-19 10:17:26.062526+00:00", "lang": "en", "topics": ["artificial-intelligence", "machine-learning", "large-language-models", "ai-research", "ai-tools"], "entities": ["Google", "EmbeddingGemma 2", "Gemma 4", "EmbeddingGemma 1", "Hugging Face", "Matryoshka Representation Learning"], "also_reported_by": [], "alternates": {"html": "https://wpnews.pro/news/embeddinggemma-2-expands-beyond-text-to-support-code-images-video-and-audio", "markdown": "https://wpnews.pro/news/embeddinggemma-2-expands-beyond-text-to-support-code-images-video-and-audio.md", "text": "https://wpnews.pro/news/embeddinggemma-2-expands-beyond-text-to-support-code-images-video-and-audio.txt", "jsonld": "https://wpnews.pro/news/embeddinggemma-2-expands-beyond-text-to-support-code-images-video-and-audio.jsonld"}}