LI

lid-fasttext-fasttext-lid176

LidGGUF by cstrUpdated 2026-08-02
Download on Hugging Face
Parameters33M
Context—
Layers—
Architecturelid-fasttext
Smallest quant0.1 GB
Quick answer

lid-fasttext-fasttext-lid176 needs about 0.6 GB of memory at F16 (a 0.1 GB file) with an 8K context window, so it fits on a 4 GB GPU.

FastText LID-176: 176‑language language identifier in GGUF format

FastText LID‑176 is a lightweight language identification model covering 176 languages with ISO 639‑1 codes. It uses a hierarchical softmax architecture and is optimized for fast inference. The GGUF build is 0.07 GB and requires about 0.6 GB of VRAM at 8 k context.

Good at

  • Fast inference on 176 languages
  • Compact 0.07 GB file size
  • Hierarchical softmax for efficient scoring

Limits

  • Requires CC‑BY‑SA‑3.0 license
  • No vision or multimodal support
  • No context length specified

Best for

  • Post‑ASR language tagging
  • Embedded language detection
  • Low‑resource inference

Who it’s for. Developers needing a small, fast language identifier for 176 languages. Suitable for integration into ASR pipelines or lightweight applications where memory is limited.

Quants & memory

QuantFileEst. memoryvs VRAMResultDownload
F160.1 GB 0.6 GB
Fits Get file →

The only available quant is F16, 0.07 GB. It fits comfortably in 1 GB VRAM and uses about 0.6 GB at 8 k context. No other quantization is provided, so use F16 for all deployments.

What GPU do you need for lid-fasttext-fasttext-lid176?

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 (0.1 GB file, about 0.6 GB in use).

Which lid-fasttext-fasttext-lid176 quant should you choose?

F16 (0.1 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

Architecturelid-fasttext
Parameters33M

Source

Quantized bycstr
FamilyLid
Downloads (HF)1,111
Last updated2026-08-02

Frequently asked questions about lid-fasttext-fasttext-lid176

How much VRAM does lid-fasttext-fasttext-lid176 need?

About 0.6 GB at F16 with an 8K context window. That is the 0.1 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 lid-fasttext-fasttext-lid176 on an 8 GB GPU?

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

What is the file size of lid-fasttext-fasttext-lid176 GGUF?

It depends on the quant: F16 is 0.1 GB.

Where can I download lid-fasttext-fasttext-lid176 GGUF?

The files are on Hugging Face in the cstr/fasttext-lid176-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 lid-fasttext-fasttext-lid176 use?

Hugging Face lists the license as cc-by-sa-3.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 model on 1 GB VRAM?

Yes, the F16 build is 0.07 GB and uses about 0.6 GB at 8 k context, well within a 1 GB VRAM budget.

Does it support vision tasks?

No, it is a language identification model only.

What license does it use?

CC‑BY‑SA‑3.0; redistribution requires the same license and attribution to Facebook.

Similar models

Browse all →

More from cstr

All by cstr →

More Lid models

All Lid →

Other tiny models

All tiny models →