Field noteAug 23, 20261 min read1 source

Liquid AI releases long-context encoders designed for CPU inference

In one minute

The 230M and 350M LFM2.5 encoders target classification, routing, policy checks, retrieval, and multilingual PII detection.

Liquid AI released LFM2.5-Encoder models with 230 million and 350 million parameters and context up to 8,192 tokens. The intended uses include classification, routing, policy checks, retrieval, and PII detection. The PII variant covers 40 entity types across 16 languages.

Liquid AI reports that its base encoder processes an 8K-token input on CPU in roughly 28 seconds, compared with more than 90 seconds for ModernBERT-base in the company's test. That is a vendor comparison, and downstream accuracy still depends on fine-tuning and the target data.

The product class is useful around agents because many checks do not require generation. A local encoder can route requests, detect sensitive text, or classify traces without sending data to a frontier model. Teams should measure recall carefully: a cheap privacy classifier is valuable only when missed entities and uncertain cases have an escalation path.

Source

Evidence / sources

  1. 1huggingface.co/blog/LiquidAI/lfm2-5-encoders
All Field Notes

Next reads

Read next

Open the graph
  1. 01topicEncodersExplore the encoders topic hub.
  2. 02topicLocal ModelsExplore the local-models topic hub.
  3. 03topicRetrievalExplore the retrieval topic hub.
  4. 04archiveField NotesOpen the latest editorial analysis.
  5. 05source ledgerSource LedgerInspect the public source evidence graph.
Who read this page?Machine requests, hidden until opened

Loading the privacy-safe route aggregate...

Open the JSON contract