LiquidAI releases six LFM3 models built for specialized, on-device AI
The family includes LiquidAI’s first model combining sight, sound and speech. Its efficiency pitch rests on company-reported hardware figures and benchmarks.
Loading page…
The family includes LiquidAI’s first model combining sight, sound and speech. Its efficiency pitch rests on company-reported hardware figures and benchmarks.
Listen to this story
LiquidAI’s six-model LFM3 lineup, released October 27, 2026, gives developers separate text, vision, audio, multimodal and decision options built from a shared 1.7B-parameter base. The company is targeting local deployment and specialization: weights are downloadable, models can be adapted on one GPU, and the text model offers a 256K-token context window while fitting in about 1 GB at four-bit precision. LiquidAI reports benchmark gains, but those results are company-reported and may not predict performance in a specific workflow.
LFM3-1.7B scored 38.42 on WebArena-Verified versus 3.02 for its predecessor, LFM2.5-2.6B; LiquidAI reported the benchmark results.
LFM3-VL-2B averaged 71.4 across 62 vision benchmarks, up from 57.6 for its 3.1B-parameter predecessor.
LFM3-Audio-2B supports transcription, speech generation and translation across 18 languages.
LiquidAI is promising specialized AI without a large general-purpose model. On October 27, 2026, it released LFM3, six models sharing one foundation for text, vision, audio and decision tasks. The company says each can be adapted on a single GPU and deployed on-device; its performance comparisons remain company-reported results.
All six models have downloadable weights on Hugging Face. Rather than asking developers to use every capability at once, LiquidAI offers separate text, vision and audio models, a combined model, and two decision variants. They all branch from LFM3-1.7B-Base and sit around the two-billion-parameter size range.
Omni is a first for the company. LiquidAI presents it as an alternative to assembling separate systems for speech recognition, visual understanding, language and speech generation. It also says the model can turn what it sees and hears into tool calls, connecting mixed-media input to actions in software.
The text model has a 256K-token context window—the amount of material it can work with at once. LiquidAI says it fits in about 1 GB at four-bit precision, a compressed numerical format. That size claim applies to the text model, not to the entire multimodal lineup.
Underneath, LFM3 mixes three kinds of processing across 24 layers: short convolutions, attention over a nearby window, and global attention. The design combines local processing with layers that connect information across the input. LiquidAI selected the architecture using a search covering 14 device-and-software combinations, including phones, Raspberry Pi 5, laptops and cloud hardware.
Training also reflects the focus on agents. The base model was trained on 22 trillion tokens. The final 3.5 trillion-token stage used curated data with more records of agent actions and tool calls, while extending the context window to 256K tokens.
LiquidAI reports that LFM3-1.7B outperforms LFM2.5-2.6B with 35% fewer parameters. Its clearest cited agent comparison is WebArena-Verified, where the new model scores 38.42 against its predecessor’s 3.02. Those figures describe the company’s benchmark evaluation, rather than a guarantee about a developer’s particular workflow.
The vision model follows the same smaller-model argument. LiquidAI reports an average score of 71.4 across 62 vision benchmarks, up from 57.6 for LFM2.5-VL-3B. Parameter count falls from 3.1 billion to 1.9 billion. Its new vision encoder also compresses each pair of sampled video frames into one temporal slice, halving that sequence’s length.
For developers, the launch includes model-loading examples using Hugging Face’s Transformers library. LiquidAI also links fine-tuning notebooks and the base checkpoint for teams doing their own additional training. The stated path is to choose the inputs an application needs, adapt the corresponding model on one GPU, and deploy it where the application runs.
Loading discussion...
Join the conversation
Share a task where your preference would make a difference.
Be the first to share a perspective or an experience.
Reader comments
Newest comments first. Replies stay oldest first.