LFM3-1.7B vs Qwen 3.7 Max

Liquid AI · US  |  Alibaba · China · Updated June 2026

Quick verdict

Pick LFM3-1.7B for very small open-weight text model - about 1.73b parameters with a 256k-token context for on-device use or liquid says it can power agentic applications that used to need 9b parameters. Pick Qwen 3.7 Max for long-horizon agentic coding (swe-bench pro 60.6, terminal-bench 2.0 69.7) or 1m-token long-document and full-codebase analysis. Choose LFM3-1.7B if you need self-hosting or data privacy; Qwen 3.7 Max if you want a managed API.

LFM3-1.7B (Liquid AI, US) and Qwen 3.7 Max (Alibaba, China) line up two different AI ecosystems against each other — a comparison that is as much about cost philosophy and openness as raw capability. LFM3-1.7B is liquid AI's October 27, 2026 on-device text model - about 1.73B parameters and 256K context, with open weights under a license capped at $10M annual revenue. Qwen 3.7 Max is alibaba's agent-first frontier model — a 1M-token context and long-horizon coding at about half the cost of US flagships. They diverge most on price, context window and open vs. closed weights — each quantified below from the models' real specs.

Key differences at a glance

Side-by-side specs

SpecLFM3-1.7BQwen 3.7 Max
ProviderLiquid AI (US) Alibaba (China)
ReleasedOctober 27, 2026 May 20, 2026
Context window256K tokens (~384 pages) 1M (~1,500 pages)
Price (in/out)Open weight (self-host / free) $2.5/$7.5 per 1M tokens
Open weight?Yes — self-hostable No — API only
Modalitiestext text, code
SWE-Bench VerifiedNot published Not published
MRCR v2 @ 1MNot published Not published

Who wins what

Very small open-weight text model - about 1.73B parameters with a 256K-token context for on-device use

LFM3-1.7B

Open weights make this possible at all — Qwen 3.7 Max is API-only, so it cannot leave the vendor's servers.

Liquid says it can power agentic applications that used to need 9B parameters

LFM3-1.7B

Liquid AI's October 27, 2026 on-device text model - about 1.73B parameters and 256K context, with open weights under a license capped at $10M annual revenue — and its weights are open while Qwen 3.7 Max is API-only.

Part of a six-model LFM3 family covering text, vision, audio, omni and decision tasks

LFM3-1.7B

Qwen 3.7 Max is comparatively weak here — text-only — no vision input (the Plus variant adds images)

Long-horizon agentic coding (SWE-Bench Pro 60.6, Terminal-Bench 2.0 69.7)

Qwen 3.7 Max

Its 1M window holds about 3.9× more than LFM3-1.7B's 256K tokens in a single prompt.

1M-token long-document and full-codebase analysis

Qwen 3.7 Max

LFM3-1.7B is comparatively weak here — no published per-token API price found

MCP tool orchestration and multi-hour autonomous runs

Qwen 3.7 Max

LFM3-1.7B is comparatively weak here — liquid says it is not recommended for agentic coding or complex multi-step reasoning because of its size

Lowest cost at scale

LFM3-1.7B

Its weights are open, so at volume you pay for your own hardware instead of Qwen 3.7 Max's $2.5/$7.5 per 1M tokens.

Largest single-prompt input

Qwen 3.7 Max

Its 1M window is about 3.9× larger than LFM3-1.7B's 256K tokens, fitting roughly 1,500 pages in one prompt.

Which should you pick?

A cost-sensitive startup shipping high volume

→ LFM3-1.7B

At Open weight (self-host / free) it undercuts Qwen 3.7 Max, and on millions of tokens that margin decides the monthly bill.

Someone analysing very long documents or codebases

→ Qwen 3.7 Max

Larger 1M window fits more in one prompt.

A team with data-privacy or self-hosting needs

→ LFM3-1.7B

Open weights let you run it on your own hardware; Qwen 3.7 Max is API-only.

Anyone whose priority is very small open-weight text model - about 1.73b parameters with a 256k-token context for on-device use

→ LFM3-1.7B

It is specifically built for that.

Anyone whose priority is long-horizon agentic coding (swe-bench pro 60.6, terminal-bench 2.0 69.7)

→ Qwen 3.7 Max

That is its strongest area.

An enterprise with regional data-residency rules

→ LFM3-1.7B or Qwen 3.7 Max

Origin (US vs China) affects where data is processed and which compliance regime applies — check the provider's terms for your region.

LFM3-1.7B: where it fits

Liquid AI's October 27, 2026 on-device text model - about 1.73B parameters and 256K context, with open weights under a license capped at $10M annual revenue. Released October 27, 2026 by Liquid AI, it is built for very small open-weight text model - about 1.73B parameters with a 256K-token context for on-device use, liquid says it can power agentic applications that used to need 9B parameters, part of a six-model LFM3 family covering text, vision, audio, omni and decision tasks, and supports 16 languages.

Its trade-offs are real: lFM Open License v1.0 covers commercial use only below $10M annual revenue; larger firms need a paid license, liquid says it is not recommended for agentic coding or complex multi-step reasoning because of its size, text-only; vision and audio need other LFM3 checkpoints, and no published per-token API price found. As an open-weight model, its running cost is your own hardware rather than a per-token fee.

Qwen 3.7 Max: where it fits

Alibaba's agent-first frontier model — a 1M-token context and long-horizon coding at about half the cost of US flagships. Released May 20, 2026 by Alibaba, it is built for long-horizon agentic coding (SWE-Bench Pro 60.6, Terminal-Bench 2.0 69.7), 1M-token long-document and full-codebase analysis, mCP tool orchestration and multi-hour autonomous runs, and frontier intelligence at roughly half the price of US flagships.

Its trade-offs: text-only — no vision input (the Plus variant adds images), closed-weight, API-only — no self-hosting, trails GPT-5.5 and Claude Opus on the hardest one-shot reasoning, and chinese-jurisdiction data-residency considerations. At $2.5 in / $7.5 out per million tokens, it sits in the mid price band.

The bottom line for this matchup

The defining split here is open vs. closed. LFM3-1.7B gives you weights you control — self-host it, fine-tune it, keep data in-house, pay only for hardware. Qwen 3.7 Max gives you a managed, always-updated API with no infrastructure to run. Teams with GPUs, privacy requirements, or huge volume often favour the open model; teams that want zero ops and the latest capabilities favour the closed one. Capability is close enough that this operational question, not the benchmark, usually decides it.

Want both LFM3-1.7B and Qwen 3.7 Max without two subscriptions? LumiChats gives you these plus 40+ models under one ₹69/day pass (about $1/day) — draft with one, cross-check with the other.

See pricing

Frequently asked questions

Is LFM3-1.7B or Qwen 3.7 Max better for coding?

Public SWE-Bench figures are not available for either model, so the honest test is your own repository — run an identical real bug through both. By design, LFM3-1.7B leans toward very small open-weight text model - about 1.73b parameters with a 256k-token context for on-device use while Qwen 3.7 Max leans toward long-horizon agentic coding (swe-bench pro 60.6, terminal-bench 2.0 69.7), and that positioning usually predicts which feels better on your codebase.

Which is cheaper, LFM3-1.7B or Qwen 3.7 Max?

LFM3-1.7B is open-weight, so self-hosting means no per-token fee (you pay for hardware instead), while Qwen 3.7 Max is API-metered at $2.5/$7.5 per 1M tokens. For most teams without GPUs, the API model is cheaper to start; at very high volume, self-hosting can win.

Which has the bigger context window?

Qwen 3.7 Max — 1M vs 256K tokens, about 3.9× larger. Useful only if the model actually reasons over the full window, which not all do.

Can I use both LFM3-1.7B and Qwen 3.7 Max together?

Yes — a multi-model platform like LumiChats gives you LFM3-1.7B, Qwen 3.7 Max and 40+ others under one ₹69/day pass (about $1/day), so you can draft with one and cross-check with the other instead of buying two subscriptions.

Which is newer, LFM3-1.7B or Qwen 3.7 Max?

LFM3-1.7B — released October 27, 2026, about 5 months after Qwen 3.7 Max.

Related comparisons

Specifications and benchmarks reflect publicly reported figures as of June 2026 and may change as providers release updates. Always verify on your own workload.