laya multilingual F16 needs about 1.7 GB of memory at F16 (a 0.7 GB file) with an 8K context window, so it fits on a 4 GB GPU.
Non‑autoregressive multilingual decision model
laya multilingual F16 is a 0.322B parameter model that answers typed questions without generating text. It supports 100+ languages and reads up to 8,192 tokens. The GGUF file is 0.66 GB and requires about 1.7 GB of VRAM at full context.
Good at
- Fast, single‑pass multilingual question answering
- No hallucination or generation errors
- Low memory footprint for 8k context
Limits
- No vision or image input
- Context limited to 8,192 tokens
- Apache‑2.0 license only
Best for
- Routing multilingual requests in a server
- Providing quick answers in chat or ticket systems
- Testing non‑autoregressive models in MeshLLM
Who it’s for. Developers building multilingual chat or ticketing systems that need a lightweight, deterministic answerer. It is ideal for environments where generation is unnecessary and speed is critical.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| F16 | 0.7 GB | 1.7 GB | Fits | Get file → |
The only available quant is F16, 0.66 GB. It needs about 1.7 GB of VRAM at 8,192‑token context. This fits comfortably on 8 GB or higher GPUs. No other quants are provided.
What GPU do you need for laya multilingual F16?
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 1.7 GB in use).
Which laya multilingual F16 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 laya multilingual F16
How much VRAM does laya multilingual F16 need?
About 1.7 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 laya multilingual F16 on an 8 GB GPU?
Yes, with F16: the 0.7 GB file needs about 1.7 GB at 8K context. Larger quants in this repository do not fit in 8 GB.
What is the file size of laya multilingual F16 GGUF?
It depends on the quant: F16 is 0.7 GB.
What context length does laya multilingual F16 support?
The GGUF header lists a trained context length of 8,192 tokens (8K). The KV cache grows with the context you use: about 0.6 GB at 8K and 0.6 GB at 8K.
Where can I download laya multilingual F16 GGUF?
The files are on Hugging Face in the meshllm/laya-multilingual-F16-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 laya multilingual F16 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 this on 8 GB VRAM?
Yes. The F16 quant requires about 1.7 GB of VRAM at full 8,192‑token context, leaving ample headroom on an 8 GB GPU.
Does it support vision or image input?
No. The model only processes text and has no vision capabilities.
What is the maximum context length?
The model supports up to 8,192 tokens; the default limit is 1,024 tokens but can be increased with max_len=8192.