M2

m2m100 418m

GGUFGGUF by cstrUpdated 2026-08-02
Download on Hugging Face
Parameters486M
Context—
Layers—
Architecturem2m100
Smallest quant0.3 GB
Quick answer

m2m100 418m needs about 1.1 GB of memory at Q8_0 (a 0.5 GB file) with an 8K context window, so it fits on a 4 GB GPU. This repository has 3 quants, from 0.3 GB (Q4_K) to 1.0 GB (F16).

Multilingual translation model with 418M parameters

m2m100 418m is a multilingual encoder‑decoder model for many‑to‑many translation. It supports 100 languages and can translate directly between any pair without an English pivot. The model is distributed under the MIT license.

Good at

  • 100‑language translation
  • direct many‑to‑many translation
  • no English pivot needed

Limits

  • No vision support
  • trained context tokens not specified
  • requires sentencepiece tokenizer

Best for

  • Translating documents between any two of 100 languages
  • Building multilingual chatbots
  • Creating translation datasets

Who it’s for. Developers needing a lightweight multilingual translation engine. Researchers working on cross‑lingual NLP tasks. Teams building translation services with limited GPU memory.

Quants & memory

QuantFileEst. memoryvs VRAMResultDownload
Q4_K0.3 GB 0.8 GB
Fits Get file →
Q8_00.5 GB 1.1 GB
Fits Get file →
F161.0 GB 1.6 GB
Fits Get file →

For 8 GB VRAM, use Q4_K (0.28 GB, ~0.8 GB memory at 8k context). For 16 GB VRAM, Q8_0 (0.53 GB, ~1.1 GB memory). For 32 GB VRAM, F16 (0.98 GB, ~1.6 GB memory). Estimates are approximate.

What GPU do you need for m2m100 418m?

These figures add the file size, an fp16 KV cache at an 8K context window 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 (1.0 GB file, about 1.6 GB in use).

Which m2m100 418m quant should you choose?

Q8_0 (0.5 GB) is the middle option in this repository. Close to lossless. It costs roughly twice the memory of a 4-bit file, so it suits cases where you have plenty of VRAM.

If memory is tight, the smallest file is Q4_K at 0.3 GB, with the quality trade-offs that come with fewer bits. The usual sweet spot between file size and quality, and the quant most people start with.

New to quant names? Read GGUF quantization explained.

Specifications

Architecture from the GGUF header

Architecturem2m100
Parameters486M

Source

Quantized bycstr
Licensemit
Downloads (HF)1,364
Last updated2026-08-02

Frequently asked questions about m2m100 418m

How much VRAM does m2m100 418m need?

About 1.1 GB at Q8_0 with an 8K context window. That is the 0.5 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 m2m100 418m on an 8 GB GPU?

Yes, with F16: the 1.0 GB file needs about 1.6 GB at 8K context. Larger quants in this repository do not fit in 8 GB.

What is the file size of m2m100 418m GGUF?

It depends on the quant: Q4_K is 0.3 GB, Q8_0 is 0.5 GB, F16 is 1.0 GB.

Where can I download m2m100 418m GGUF?

The files are on Hugging Face in the cstr/m2m100-418m-GGUF repository. The download buttons on this page open the file on Hugging Face. ggufmodels.com does not host any model files.

What license does m2m100 418m use?

Hugging Face lists the license as mit. 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 m2m100 418m on 8 GB VRAM?

Yes, the Q4_K quantization requires about 0.8 GB memory at 8k context, fitting within 8 GB VRAM.

Does this model support vision tasks?

No, it is a text‑only encoder‑decoder model.

What license applies to this GGUF model?

The model is distributed under the MIT license, same as the original upstream model.

Other GGUFs of m2m100_418M

Similar models

Browse all →

More from cstr

All by cstr →

Other tiny models

All tiny models →