mxbai-embed-large-v1 needs about 2.0 GB of memory at F16 (a 0.7 GB file) with an 8K context window, so it fits on a 4 GB GPU.
mxbai-embed-large-v1 – a 0.33 B BERT model for sentence embeddings
The mxbai-embed-large-v1 model delivers high‑quality sentence embeddings. It is a 0.33 billion‑parameter BERT architecture trained on 512‑token contexts. The model is available in a 0.67 GB F16 GGUF file and supports Apache‑2.0 licensing.
Good at
- High‑quality sentence embeddings
- Fast inference with GGUF
- Supports binary quantization
Limits
- Requires 512‑token context
- No vision or multimodal support
- Only F16 quant available in GGUF
Best for
- Text retrieval systems
- Semantic search engines
- Embedding‑based clustering
Who it’s for. Developers building retrieval or search applications that need efficient sentence embeddings. The model is suitable for systems that can run GGUF files and have a GPU or CPU with sufficient memory.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| F16 | 0.7 GB | 1.2 GB | Fits | Get file → |
The only GGUF quant available is F16, 0.67 GB in size. It requires approximately 2 GB of VRAM at 8 k context. For lower VRAM budgets, consider using the native API with int8 or binary quantization, which is not provided as a GGUF file.
What GPU do you need for mxbai-embed-large-v1?
These figures add the file size, an fp16 KV cache at an 8K context window (worked out from this model’s own header) and about 0.5 GB for the runtime. They are estimates, so leave a little headroom, and expect to use less context or a smaller quant if you are right at the limit.
- 4 GB VRAM: the best quant that fits is F16 (0.7 GB file, about 2.0 GB in use).
Which mxbai-embed-large-v1 quant should you choose?
F16 (0.7 GB) is the middle option in this repository. The unquantized model. It gives original quality and needs the most memory, so it is mainly for conversion or reference.
New to quant names? Read GGUF quantization explained.
Specifications
Architecture from the GGUF header
Source
Frequently asked questions about mxbai-embed-large-v1
How much VRAM does mxbai-embed-large-v1 need?
About 2.0 GB at F16 with an 8K context window. That is the 0.7 GB file, plus the KV cache and roughly 0.5 GB of runtime overhead. Smaller quants need less and longer context needs more.
Can I run mxbai-embed-large-v1 on an 8 GB GPU?
Yes, with F16: the 0.7 GB file needs about 2.0 GB at 8K context. Larger quants in this repository do not fit in 8 GB.
What is the file size of mxbai-embed-large-v1 GGUF?
It depends on the quant: F16 is 0.7 GB.
What context length does mxbai-embed-large-v1 support?
The GGUF header lists a trained context length of 512 tokens (512). The KV cache grows with the context you use: about 0.8 GB at 8K and 0.1 GB at 512.
Where can I download mxbai-embed-large-v1 GGUF?
The files are on Hugging Face in the mixedbread-ai/mxbai-embed-large-v1 repository. The download buttons on this page open the file on Hugging Face. ggufmodels.com does not host any model files.
What license does mxbai-embed-large-v1 use?
Hugging Face lists the license as apache-2.0. Licenses can differ between the quantized files and the original model, so check the repository and the base model before commercial use.
Can I run mxbai-embed-large-v1 on 8 GB VRAM?
Yes, the F16 GGUF requires about 2 GB of VRAM at 8 k context, leaving ample headroom on an 8 GB GPU.
Does the model support multilingual text?
The model is trained on English data; multilingual support is not specified.
Is the model licensed for commercial use?
Yes, it is released under the Apache‑2.0 license, which allows commercial use.