BRIGHT EVIDENCE PACK / Emerging
Liquid AI releases small models for local text, vision and voice tasks
LFM3 brings downloadable models to everyday devices, with a focus on specialized applications. Hardware requirements, software integration and a custom commercial license still shape what developers can build.
Canonical Bright record · JSON evidence pack · Key-facts embed
Dates and assessment
- Source published
- 2026-10-27
- Bright published
- 2026-10-28
- Substantive update
- None recorded
- Evidence state
- Emerging
- Independent verification
- Not established by this source review
- Last source review
- 2026-10-28
The claim in context
The human problem
People and developers need more choice about where useful AI tasks are processed.
The prior constraint
Remote model services can require sending inputs off-device and dependence on provider infrastructure.
AI’s actual role
Downloadable small models generate text, interpret images and audio, and propose tool calls within applications.
The documented result
Liquid AI announced LFM3 on October 27, releasing an open-weight model family built around a small shared backbone. The launch covers text, vision, audio, combined multimodal input and decision models in roughly the two-billion-parameter range. The weights are available through the company’s Hugging Face collection, giving developers something they can download and evaluate now. Liquid’s announcement · Official collection
Why it may matter
Specialized local applications could reduce dependence on remote inference when the hardware, software and task fit.
Limitations
- Liquid says the text model’s weights take about 1 GB at four-bit precision. That is a compressed model-footprint claim, not a promise that the whole application needs only 1 GB of RAM. Runtime software, working memory, context and other components add to the total. The company’s own launch discussion reports additional cache memory for long contexts. Hardware fit needs to be measured with the actual model format, application and workload.
- A business could evaluate a model for extracting structured fields from a familiar type of document. A developer could explore voice commands or image questions within an application they control. Liquid supplies local inference options and describes fine-tuning on a single GPU to specialize the models. Bright has not run these models or verified their speed, quality or fine-tuning requirements. Model formats and guidance
- Keeping inference on a device can reduce how much content needs to leave it. Privacy still depends on the surrounding application: search tools, cloud storage, telemetry and external services may transmit information. A local language model connected to an online tool does not make the tool’s activity local. Teams need to check the full data path before promising private or offline operation.
- The text model card is more specific about intended use: local agents, tool calling, structured outputs and domain-specific fine-tuning. It recommends retrieval or search for knowledge-heavy work and discourages using the model for agentic coding or complex multi-step reasoning because of its small size. Those limits belong beside the performance claims when deciding whether to adopt it. Intended use and limitations
- LFM3-1.7B uses the custom LFM Open License v1.0. It is based on Apache 2.0 but adds a commercial-use condition tied to a $10 million annual-revenue threshold. Larger businesses need a separate commercial agreement with Liquid. Redistribution also carries license and attribution requirements, while qualified nonprofits have an exemption for non-commercial or research use. Readers planning commercial deployment should review the full terms for their circumstances. Liquid’s license
Original evidence
- Liquid AI · LFM3 release announcement · institution
- Liquid AI · LFM3-1.7B model card · repository
- Liquid AI · Official LFM3 collection · repository
- Liquid AI · LFM Open License v1.0 · institution
Attribution
Credit Bright AI Future and link the canonical Bright record.
- Link to the canonical Bright record.
- Keep material limitations with the claim they qualify.
- Link to the original evidence when repeating a substantive claim.
- Do not describe a source check or organization-reported result as independent verification.
Linked source material, quotations, trademarks and media remain subject to their owners’ terms. No reuse right is granted for third-party media.
