LFM3 VL 2B
Use case: Reasoning. Check the memory fit and choose a setup path below.
This model needs a special runtime. Unsupported apps are clearly marked.
About LFM3 VL 2B
Catalogue summary: Liquid AI image understanding, OCR and visual reasoning model. Official QAD Q4_0 GGUF plus F16 vision projector totals 1.43GB. Plan for 8GB RAM at short context. Requires LFM3-enabled llama.cpp; video input is not yet supported.
LFM3 VL 2B has a 8 GB short-context RAM planning estimate based on its 1.43 GB GGUF. This is not a measured minimum or a guarantee at maximum context.
Use the official llama.cpp containing 19cce6919992fdffd92e0ac152caaf1e2b8f254e (PR 31252); start with -c 4096; use the matching F16 mmproj, no video input setup. The current low-bit files are not a stock LM Studio install.
Install path
Download formats for this model
These are quantizations of the same model. The RAM fit above uses Q4_0; larger files need more memory. File sizes exclude the runtime, context cache and optional vision projector.
Catalogue record
- Family: lfm
- Parameters: 1.92B
- Recommended quantization: Q4_0
- Short-context RAM estimate: 8 GB
- Catalogue model size: 1.43 GB
- Tags: vision, multimodal, light, reasoning
Practical limits
- Catalogue RAM is a minimum estimate, not a guarantee for every context length or runtime.
- Speed and memory use vary by quantization, backend, context length and system headroom.
- Verify architecture, licence and usage restrictions in the linked upstream material before deployment.
Reading the scores
LocalClaw /10 is an editorial catalogue rating. Community /5 comes from member reviews. Your machine fit is a separate memory and runtime assessment.
Capability profile
Repository catalogue ratings used by LocalClaw's editorial rubric. They are not a standardized third-party benchmark.
Technical notes
This model fits these next steps
Hardware fit is based on LocalClaw's RAM tier, model size and quantization metadata. Always leave memory headroom for your OS and runtime.
Related catalogue entries
Linked mechanically by family, shared tags and nearby RAM tier; this is not a quality ranking.