NeoMME*: an efficient Multimodal-native and Multilingual Encoder

H Company released NeoMME, a family of 260M and 800M multilingual multimodal encoders that process text and images with a single bidirectional Transformer, trained from scratch with a masked discrete-diffusion objective. The models achieve state-of-the-art performance on the ViDoRe v3 Pareto frontier for nDCG@10 and model size, with the 260M model encoding about 51 pages per second on an NVIDIA L40S GPU, and reduce late-interaction index storage by 255× while retaining over 95% of baseline nDCG@10. All checkpoints are available under the Apache 2.0 license on Hugging Face Transformers.

Feature Extraction • 0.3B • Updated • 70 NeoMME: an efficient Multimodal-native and Multilingual Encoder Team Article /blog TL;DR We introduce NeoMME , a family of 260M and 800M multilingual multimodal encoders. Unlike many generative visual language models, NeoMME does not use a separate pretrained vision tower or a causal language model. A single bidirectional Transformer processes both text tokens and raw image patches, and we train the entire model from scratch with a masked discrete-diffusion objective. We fine-tuned NeoMME for visual document retrieval using ColPali's page-image approach. NeoMME -Retriever returns dense and late-interaction embeddings in one forward pass. Both model sizes lie on the ViDoRe v3 Pareto frontier for nDCG@10 and model size. At a matched 2048×2048 image input size on an NVIDIA L40S GPU, the 260M model encodes about 51 pages per second, or about twice ColModernVBERT's throughput. Hierarchical token pooling and asymmetric quantization reduce late-interaction index storage from roughly 1.5 MB to 6 kB per page 255× smaller while retaining more than 95% of baseline nDCG@10. NeoMME is available in Hugging Face Transformers. We release all model checkpoints under the Apache 2.0 license. Why another multimodal encoder? Many recent visual document retrievers are adapted from pretrained generative visual language models. A separately pretrained vision encoder produces visual features, which a projector maps into the language model's input space. A causal decoder then processes the combined image and text representations. Retrieval, classification, and token labeling do not generate text autoregressively, so they do not require a causal decoder or the parameter and compute overhead of this architecture. ModernBERT https://huggingface.co/blog/modernbert brought efficient architecture and training improvements to bidirectional encoders. For visual document retrieval, ModernVBERT https://huggingface.co/blog/paultltc/modernvbert applied a bidirectional ModernBERT-style text encoder while retaining a separate pretrained SigLIP2 vision tower. We wanted to push this even further by designing and training a multimodal encoder without having to carry over the parameter and compute overhead of a VLM. NeoMME pronounced "nee-oh-me", IPA /ˈniː.oʊ.mi/ is a multilingual, multimodal foundation encoder that generates vector representations for input text and/or images using a single Transformer encoder. It is not based on an existing pretrained vision tower, text encoder, or text decoder. Images and text use the same computational path, so NeoMME can more easily support pretraining, fine-tuning, parallelization, and serving across both modalities. NeoMME encoder backbone One Transformer for images and text NeoMME comes in two sizes, 260M https://huggingface.co/Hcompany/NeoMME-260M and 800M https://huggingface.co/Hcompany/NeoMME-800M . Both variants share the same architecture: Native multimodal inputs: text inputs use factorized token embeddings, while images are divided into a grid of non-overlapping 32×32 patches and projected with a small MLP. Both enter the same Transformer encoder. Dynamic image resolution: images keep their aspect ratio and size. This allows the model to use more tokens on a high-resolution, information-dense document page than on a smaller image with less content. Long bidirectional context: both models have a context length of 16,384 tokens enough for up to two standard 3840×2160 4K UHD images . Most layers use symmetric sliding-window attention, while every sixth layer and the final layer use global attention. A modern encoder stack: NeoMME uses recent encoder improvements such as grouped-query attention, query-key normalization, gated attention, 2D rotary position embeddings, and squared-ReLU MLPs, among others. Multilingual text: we trained a BPE tokenizer with a 131k-token vocabulary from scratch on multilingual text, code, mathematics, and machine-produced image transcripts. Learning from images through masked text We pretrain NeoMME from scratch as a discrete masked-diffusion text denoiser. For each text-only example, we sample a corruption rate uniformly between 0 and 1. Each eligible text token is then independently masked at that rate. Multimodal examples use corruption rates between 0.3 and 1. The image patches remain visible while NeoMME reconstructs masked text. With light masking, the model can often recover a missing word from the surrounding text alone. For example, "cat" is a plausible completion of "The MASK sat on the mat," even without an image. But high masking forces the model to learn image-grounded descriptions with little to no signal from the non-masked input text tokens. Pretraining mixes multilingual text, code, mathematics, natural images, and document images. Each model processes about 524 billion packed input tokens, including 290 billion tokens from text-only examples. This text budget is relatively small compared with ModernBERT's 2 trillion training token budget. Hence, we chose the NorMuon optimizer to improve data efficiency during training. NeoMME -Retriever To get a meaningful downstream evaluation of the backbone, we fine-tune NeoMME for visual document retrieval using the page-image methodology introduced by ColPali https://huggingface.co/blog/manu/colpali . While traditional text-based retrieval consists of retrieving text chunks, NeoMME -Retriever ranks document page screenshots and bypasses all the preprocessing OCR steps necessary to extract text from PDFs. Treating the pages as images preserves layout, charts, tables, font type and size, and other visual clues that cannot be captured even by a perfect OCR model. A dual-head design for dense and late-interaction retrieval NeoMME -Retriever reuses the NeoMME backbone but adds two jointly trained heads on top of it for retrieval: - The dense head averages the backbone's hidden state vectors into a normalized vector mean pooling . Dense embeddings are most common today: they are compact and work naturally with approximate nearest-neighbor ANN techniques for fast retrieval. - The late-interaction head projects each text token or image patch from the backbone's output hidden states to a 128-dimensional normalized vector. Compared to dense embeddings, the finer granularity preserves local matches between individual query tokens and image regions. Omar Khattab, who introduced late-interaction in ColBERT, explains why the term is more precise than "multi-vector." It describes the granularity and learnability of the scoring function, not simply the number of stored vectors.To learn more about late-interaction, we recommend reading this crash course by Amélie Chatelain. One NeoMME -Retriever forward pass returns both representations, which gives you flexibility no matter your use case and infrastructure. We recommend using late-interaction embeddings in general since they are more powerful and can be used easily with open-source libraries like NextPlaid https://github.com/lightonai/next-plaid . However, if you have a very large corpora, you can run a single forward pass with NeoMME -Retriever to get the dense embedding, retrieve a small number of documents through an ANN index, and then use late-interaction to rerank the retrieved candidates. Competitive retrieval at compact model sizes We report nDCG@10 on ViDoRe v3. NeoMME -Retriever-260M reaches 0.523, the highest score among evaluated models strictly below 800M parameters. It is within 0.002 nDCG@10 of ColQwen2.5 while using about 14× fewer parameters. NeoMME -Retriever-800M reaches 0.556, within 0.009 nDCG@10 of the similarly sized Vultron Retriever Flash 0.8B https://huggingface.co/vultr/VultronRetrieverFlash-Qwen3.5-0.8B . Both NeoMME -Retriever models lie on the model-size Pareto frontier. ViDoRe v1 and v2 use nDCG@5. On both benchmarks, NeoMME -Retriever-260M outperforms ColModernVBERT and the twice-larger ColSmol-500M. NeoMME -Retriever-800M outperforms ColPali v1.3 while using 3.6 times fewer parameters. | Model details | ViDoRe nDCG@k | ||| |---|---|---|---|---| | Model | Params. | v3 @10 | v2 @5 | v1 @5 | | <300M | |||| | †‡‡ ColSmol-256M https://huggingface.co/vidore/colSmol-256M † NeoMME -260M‡ 0.523 0.522 0.860 ColSmol-500M https://huggingface.co/vidore/colSmol-500M ‡†† Vultron Flash https://huggingface.co/vultr/VultronRetrieverFlash-Qwen3.5-0.8B † 0.565 0.604 0.882 NeoMME -800M‡ ColQwen2.5-v0.2 https://huggingface.co/vidore/colqwen2.5-v0.2 † 0.524 0.601 0.895 ColPali v1.3 https://huggingface.co/vidore/colpali-v1.3 †† Scores from MTEB. ‡ Results from our own evaluations. Making high-resolution retrieval practical for late-interaction Late-interaction storage scales linearly with the number of vectors in the output embedding. Higher-resolution images contain more patches, so they produce larger embeddings. For example, a 2048×2048 square page produces embeddings containing 4,200 vectors with NeoMME -Retriever, or about 2.1 MB in float32. Across the ViDoRe v3 benchmark, the measured average is about 1.5 MB per document. To reduce the storage footprint of the late-interaction index, we combine two complementary compression methods: Hierarchical token pooling https://www.answer.ai/posts/colbert-pooling.html clusters similar document vectors in a given multi-vector embedding and replaces each cluster with its mean, hence reducing the number of vectors stored for each page. Asymmetric quantization https://www.mixedbread.com/blog/asymmetric-quant quantizes document embeddings to int8 or binary. Because query embeddings are not stored and only generated on-the-fly, they can be kept at a higher precision. We tested this setup on ViDoRe v3. With a pooling factor 10 and int8 queries and documents, storage decreased from about 1.5 MB to 39 kB per page, a 39× reduction, while keeping more than 99% of the baseline nDCG@10. A more aggressive configuration uses pooling factor 8, int8 queries, and binary documents. That version uses 6 kB per page 255× smaller and keeps more than 95% of the original retrieval quality. Users can pick a compression setting from that frontier based on storage budget and required retrieval quality. Fast inference for cheaper multimodal corpus indexing Before you can search a corpus, a retriever model must turn your documents into embeddings, which will be stored in a vector store like Qdrant, Weaviate, or Milvus. Faster encoding makes building and adding new documents to the index faster, thus reducing the GPU uptime and compute cost required. So we measured image encoding speeds for NeoMME -Retriever against other multimodal document retrievers. We used preprocessed image tensors and calibrated the batch size separately for each model and image size. At a matched 2048×2048 input size on one NVIDIA L40S, NeoMME -Retriever-260M encodes about 51 pages per second, nearly twice ColModernVBERT's 26 pages per second. Both 260M and 800M NeoMME -Retriever models are also faster than the other models we compared on smaller input images. Try NeoMME -Retriever yourself NeoMME -Retriever 260M https://huggingface.co/Hcompany/NeoMME-260M-Retriever and 800M https://huggingface.co/Hcompany/NeoMME-800M-Retriever returns dense and multi-vector embeddings together. The example below scores two text queries against two document-page images with MeanMaxSim late interaction and dense cosine similarity. Click to see the complete 🤗 transformers example snippet accelerate is an optional dependency needed only when using device map="auto". pip install -U accelerate "transformers @ git+https://github.com/huggingface/transformers.git@main" "sentence-transformers =6.0.0" python from typing import Any, Literal import requests import torch from PIL import Image from sentence transformers.util import cos sim, mean maxsim from transformers import BatchFeature, NeoMMEForRetrieval, NeoMMEProcessor def encode messages: list list dict str, Any , task: Literal "query", "document" , - BatchFeature: return processor.apply chat template messages, task=task, tokenize=True, return dict=True, return tensors="pt", processor kwargs={"padding": "longest"}, model name = "Hcompany/NeoMME-260M-Retriever" processor = NeoMMEProcessor.from pretrained model name model = NeoMMEForRetrieval.from pretrained model name, device map="auto" Document images our corpus image urls = "https://github.com/tonywu71/colpali-cookbooks/blob/6ef1332da6bcb48c7ef1f19b25bfa555be7031a8/examples/data/shift kazakhstan.jpg?raw=true", "https://github.com/tonywu71/colpali-cookbooks/blob/6ef1332da6bcb48c7ef1f19b25bfa555be7031a8/examples/data/energy electricity generation.jpg?raw=true", documents = Image.open requests.get url, stream=True .raw for url in image urls Queries queries = "Quelle partie de la production pétrolière du Kazakhstan provient de champs en mer ?", "Which hour of the day had the highest overall electricity generation in 2019?", document messages = {"role": "user", "content": {"type": "image", "image": document} } for document in documents query messages = {"role": "user", "content": query} for query in queries inputs documents = encode document messages, "document" .to model.device inputs text = encode query messages, "query" .to model.device with torch.inference mode : document outputs = model inputs documents query outputs = model inputs text late scores = mean maxsim query outputs.embeddings, document outputs.embeddings, a mask=inputs text "attention mask" , b mask=inputs documents "attention mask" , dense scores = cos sim query outputs.dense embeddings, document outputs.dense embeddings Expected: late scores 0, 0 late scores 0, 1 and late scores 1, 1 late scores 1, 0 . print late scores, dense scores Fine-tuning with Sentence Transformers We provide separate dense https://huggingface.co/Hcompany/NeoMME-260M-Retriever-ST-dense and late-interaction https://huggingface.co/Hcompany/NeoMME-260M-Retriever-ST-late checkpoints for fine-tuning with Sentence Transformers v6 https://huggingface.co/blog/multi-vector-encoder . Following the same pattern as text encoders such as ModernBERT, Sentence Transformers loads the backbone through NeoMMEModel https://huggingface.co/docs/transformers/main/en/model doc/neomme transformers.NeoMMEModel rather than the dual-head class. Sentence Transformers currently supports one retrieval head per model, so each checkpoint lets you fine-tune the dense or late-interaction head independently. To train both heads together, use https://huggingface.co/docs/transformers/main/en/model doc/neomme transformers.NeoMMEForRetrieval NeoMMEForRetrieval NeoMMEForRetrieval with a custom Trainer . From retrieval to visual RAG Visual document retrieval can be used as the first stage of a visual retrieval-augmented generation RAG system. Unlike text RAG, which retrieves extracted text chunks, visual RAG retrieves the original page images and sends them to a visual language model. The model can then use tables, plots, diagrams, and page layout that text extraction may flatten or omit. Here is how visual RAG works: - Indexing: Convert each PDF page to an image, generate an embedding with a retrieval model, and store the embeddings in a vector store. - Retrieval: Generate an embedding for the user's query with the same model and retrieve the top-k most relevant pages. - Generation: Append the images after the query in the chat message e.g. , {query}{img 1}{img 2}...{img k} and send it to a VLM to generate the answer. You can test visual RAG directly with NeoMME -Retriever in our HF Space: 🤗 tonywu71/neomme-retriever-demo https://huggingface.co/spaces/tonywu71/neomme-retriever-demo . Conclusion NeoMME replaces separate pretrained image and text encoders with one long-context bidirectional Transformer. We train it from scratch to process both multilingual text tokens and raw 32×32 image patches. NeoMME -Retriever is a fine-tuned version of NeoMME for visual document retrieval. One forward pass produces both dense and late-interaction representations. The 260M model outperforms all evaluated models strictly below 800M parameters and, at a matched 2048×2048 input size, encodes pages at about 2× ColModernVBERT's throughput. To reduce the large storage footprint of late-interaction embeddings for high-resolution documents, we experimented with hierarchical token pooling and asymmetric quantization and managed to reduce the late-interaction embeddings from roughly 1.5 MB to 6 kB per page, a 255× compression, while retaining more than 95% of the baseline nDCG@10. We release all NeoMME model checkpoints and a day-zero Hugging Face Transformers implementation to allow practitioners to build efficient multimodal and multilingual representation models on top of our work. Acknowledgements NeoMME began as a side quest between two good friends. We worked with limited time and compute, and we decided to share the results so the community can build on them. We thank H Company for supporting the work and providing the compute used to train NeoMME . Citation @misc{lac2026neommesingletowermultimodalnativemultilingual, title={NeoMME: A Single-Tower Multimodal-Native Multilingual Foundation Encoder for Efficient Fine-Tuning and Inference}, author={Aurélien Lac and Tony Wu}, year={2026}, eprint={2609.01657}, archivePrefix={arXiv}, primaryClass={cs.IR}, url={https://arxiv.org/abs/2609.01657}, }