Kartu judul bertuliskan Moondream 3 vs LFM2.5-VL 3B: penalaran berbasis bukti versus jawaban langsung, dengan chip untuk 9B MoE dengan 2B aktif dan 3.1B dense, serta logo OrcaRouter di sudut.
Guides & Insights

Moondream 3 vs LFM2.5-VL 3B: Satu Menunjuk ke Jawaban, Satu Hanya Menjawab

Penulis

Elias Hawthorne

Tanggal Terbit

Model terbaru · 20Lihat semua model →
Benchmark: Artificial Analysis · diperbarui setiap hari
Kembali ke semua artikel

The most useful difference between M​oondream 3 Preview and LFM2.5-VL-3B is not in their benchmark tables. It is that M​oondream 3 Preview reasons about an image by pointing into it — its reasoning traces are grounded, referencing specific regions — while LFM2.5-VL-3B is explicitly a non-reasoning model that answers directly, a choice Liquid AI made to keep latency low for on-device work. Same image in, two entirely different things come out, and which one you want depends on whether a downstream system has to trust the answer or merely consume it.

Everything else follows from that fork. M​oondream 3 Preview is a sparse mixture-of-experts model at 9B total parameters with 2B active, released on 18 September 2025 by M​oondream, which was acquired by Prime Intellect in October 2026. LFM2.5-VL-3B is a dense 3.1B model — a 2.6B language backbone with a 400M SigLIP2 NaFlex vision encoder — released by Liquid AI on 12 August 2026 as a direct successor to LFM2-VL-3B. One is a specialist that was built to detect and point and can also answer questions. The other is a generalist that was built to answer and recently learned to point.

Tabrakan metrik yang harus Anda perhatikan lebih dahulu

Letakkan kedua angka acuan itu berdampingan dan perbandingannya tampak hampir seri. Tidak demikian, karena keduanya bukan pengukuran yang sama.

M​oondream's launch chart lists M​oondream 3 Preview at 91.1 on RefCOCO. Liquid AI reports LFM2.5-VL-3B at RefCOCO precision@1 of 87.9. RefCOCO accuracy and RefCOCO precision@1 are different statistics computed over the same dataset, and a 3.2-point gap between them tells you nothing about which model localises better. Anyone stacking those two figures in a bar chart is comparing a number to a differently-defined number.

• M​oondream 3 Preview grounding — RefCOCO 91.1, on a chart where frontier baselines (GPT-5, Gemini 2.5-Flash, C​laude 4 S​onnet) were queried through a template because they have no native grounding, and where some preview scores came from a 100-question sample rather than the full set. Vendor-reported and, as M​oondream says itself, not a fair fight.

• Grounding LFM2.5-VL-3B — presisi@1 RefCOCO 87,9, naik dari 57,1 pada LFM2-VL-3B sebelumnya, yang menurut Liquid disebabkan oleh penskalaan data grounding sintetis. Dilaporkan vendor, perbandingan dengan harness yang sama terhadap pendahulunya sendiri, yang merupakan sumbu yang lebih bermakna.

• Detection and pointing — M​oondream 3 Preview: native detect and point skills, structured coordinate output, part of the architecture. LFM2.5-VL-3B: grounding added by training, returned as coordinates the same way, with function calling also new to the VL line (ToolSandbox 26.4 to 59.5, BFCL v4 20.5 to 32.5).

The honest read: Liquid AI has a clean before-and-after on identical harnesses and M​oondream has a cross-model chart with template caveats. Neither gives you a head-to-head. If grounding accuracy is the deciding factor in your evaluation, your own labelled set is the only instrument that will settle it.

Apa yang harus Anda bayar untuk penalaran yang berpijak pada fakta

M​oondream's query skill runs in reasoning mode by default. The model works through the question and its trace references the regions of the image it is using, which you can inspect in the playground by hovering over the text. For anything where a human has to audit the answer — a defect call on a production line, a security incident, a medical triage flag — that property is worth a lot. It is the difference between a model that says "no" and a model that says "no, here." p>The cost is tokens. Reasoning mode generates a trace before the answer, and M​oondream's own documentation offers the escape hatch: pass reasoning=False for simple questions, because the company knows the mode is not free. That is a real architectural admission — a well-designed model would not need a flag to switch the thought off.

LFM2.5-VL-3B tidak memiliki padanan. Model ini dirancang sebagai model non-penalaran, dan Liquid AI terus terang soal komprominya: menjawab secara langsung menjaga latensi tetap rendah untuk penggunaan waktu nyata dan di perangkat. Tidak ada jejak untuk diperiksa dan tidak ada mode untuk dinonaktifkan. Di antrean kasir saat memindai barcode, atau ponsel yang menerjemahkan menu, itu adalah keputusan rekayasa yang tepat dan ketiadaan jejak bukanlah cacat.

So the question is not which is better. It is whether anything downstream of your model reads the reasoning. If a human does, M​oondream's grounded traces are the feature you are buying. If only a program does, you are paying for tokens nobody will read.

Di mana 3.1B sebenarnya unggul

Klaim ukuran LFM2.5-VL-3B bukanlah taktik pemasaran. Model ini berjalan dengan memori di bawah 3,3 GB pada 228 token per detik di Apple M5 Max, dan 116 token per detik di AMD Ryzen AI Max+ 395, dengan ekspor GGUF, ONNX, dan MLX yang dipublikasikan bersama checkpoint native-nya. Itu adalah model yang bisa Anda pasang di laptop, dan Liquid AI juga menyediakannya sebagai WebGPU Hugging Face Space yang berjalan di tab peramban.

M​oondream 3 Preview has a smaller active parameter count — 2B against 3.1B — but the comparison is not symmetric, because a MoE checkpoint has to be fully resident even though only a fraction of it fires. The 9B of weights need somewhere to live. M​oondream's own answer to that is Photon, its local inference engine, which runs the model on N​VIDIA GPUs from Ampere onward and on Apple Silicon Macs. Different constraint: LFM2.5-VL-3B is small enough to fit anywhere, M​oondream 3 Preview is fast in the compute sense but large in the memory sense.

• Context — both 32K tokens. Genuine convergence, and worth noting given the two-year jump from the 2K windows of the previous M​oondream generation.

• Languages — LFM2.5-VL-3B lists sixteen: English, Arabic, Chinese, French, German, Italian, Japanese, Korean, Portuguese, Spanish, Vietnamese, Thai, Indonesian, Hindi, Russian, Polish, and doubled its vocabulary to 128,000 to support non-Latin scripts. M​oondream 3 Preview's card leads on visual capability rather than a language list; treat multilingual VQA as something to test rather than something promised.

• Document reading — LFM2.5-VL-3B: DocVQA 91.1, ChartQA 81.3, OCRBench v1 84.2, OCRBench v2 English 47.5, MMMU 48.4. M​oondream 3 Preview: DocVQA 88.3, ChartQA 86.6, POPE 89.0. Different harnesses, vendor-reported on both sides.

• Apa yang LFM2.5-VL-3B beri tahu Anda untuk tidak dilakukan — kartu Liquid AI mengatakan dengan jelas bahwa model ini tidak direkomendasikan untuk tugas konteks panjang atau yang intensif penalaran seperti desain web visual atau pertanyaan teknis tentang cetak biru. Kalimat itu lebih berguna daripada sebagian besar tabel tolok ukur.

Deployment, dan di mana router berperan

Neither of these models is served through OrcaRouter, and it is worth saying so directly rather than dancing around it: both are open-weight checkpoints you run yourself, and M​oondream 3 Preview's hosted endpoint — M​oondream Cloud — is being shut down on 13 November 2026 following the Prime Intellect acquisition, with unspent credits refunded.

Yang diubah oleh hal itu adalah bentuk keputusannya. Tim yang menjadikan VLM yang dihosting sendiri sebagai standar biasanya berakhir dengan model kedua yang dihosting untuk kasus-kasus yang ditangani dengan buruk oleh model lokal, dan pada titik itu, pekerjaan integrasi menjadi masalahnya: dua SDK, dua skema autentikasi, dua kebijakan percobaan ulang, dan gangguan vendor yang menjadi gangguan Anda.

This is the case OrcaRouter's routing DSL is built for. You compose several models into a single call — the 3.1B local model answers what it can, a hosted model takes the residue — behind one key for more than 200 models, with provider list price passed through at zero markup and automatic failover when an upstream degrades. Since neither M​oondream 3 Preview nor LFM2.5-VL-3B is in that catalogue, the routing layer sits above them rather than replacing them: it is how you keep the cheap local path cheap without making a vendor outage your outage.

Fork lisensi, yang lebih tajam daripada tolok ukur

Dua filosofi lisensi yang berbeda, dan perbedaannya lebih penting bagi keputusan produk daripada selisih skor 3 poin.

M​oondream 3 Preview ships under the Business Source License 1.1 with an Additional Use Grant (No Third-Party Service). Internal and production use, personal projects, research, benchmarks, fine-tunes, merges, quantisations, weight deltas, and use inside a product that does not substantially overlap M​oondream's paid offerings are all permitted. Selling a hosted API that exposes similar vision capabilities, managed "M​oondream-as-a-service", or embedding the weights in a paid SDK that delivers comparable capabilities requires a separate agreement. M​oondream 3.1 moved to the M​oondream Model License 1.0, which states the same rule more cleanly: component of your product is allowed, access to M​oondream itself as the product is not. Edge devices, customer-controlled VPCs, and running the model on leased cloud or neocloud GPUs are all explicitly on the allowed side.

LFM2.5-VL-3B is under Liquid AI's own LFM Open License v1.0. Read it before you ship, as you would any bespoke licence, but the families are different in kind: M​oondream's restriction targets one specific business — reselling the model — while Liquid's is a broad open licence with its own terms.

If you are a domain-specific builder, both are fine and the licence question is a formality. If your business is anywhere near "we host vision models for other people," M​oondream's licence is the constraint you read first and LFM's is the one you probably clear.

Mana yang harus dipilih

A two-column comparison scoreboard titled Moondream 3 vs LFM2.5-VL 3B — the scoreboard, with matched rows for total parameters, active parameters, reasoning mode, context length, deployment footprint and licence, and a footer stating that both sets of figures are vendor-reported and that RefCOCO 91.1 and RefCOCO precision@1 87.9 are different statistics.

Choose M​oondream 3 Preview if the answer has to be inspectable. If a human reviews the output, if the trace needs to show which part of the image drove the decision, if detection and pointing are the primary product rather than a feature — that grounded reasoning is the whole reason to pay 9B of memory for a 2B-active model. Budget for Photon or a GPU, and plan around the hosted endpoint closing.

Pilih LFM2.5-VL-3B jika model harus berada di perangkat. Jika Anda mengirim ke ponsel, laptop, kotak lantai pabrik, atau tab peramban, dan beban kerjanya satu giliran, throughput tinggi, dan latensi rendah — membaca layar, mentranskripsikan dokumen, mendeteksi objek dalam aliran — maka model dense 3,1B yang menjawab tanpa berpikir adalah tepat yang Anda inginkan, dan 228 token per detiknya pada M5 Max adalah angka yang menentukan.

Pick both if you have the budget for it, and route between them: LFM2.5-VL-3B on every frame because it is nearly free to run, M​oondream 3 Preview on the frames where a grounded answer is worth waiting for.

The Liquid AI release post for LFM2.5-VL-3B dated August 12 2026, showing the headline, the description of the model as a non-reasoning vision-language model that answers directly to keep latency low for real-time and on-device applications, and the start of the evaluations and what's-new sections.The OrcaRouter model catalogue showing the search and filter rail, the count of 210 models across 16 providers on one API key and one bill, the OpenAI-compatible endpoint instructions, and model cards with their providers and modalities.

Yang tidak dapat diberitahukan oleh angka-angka kepada Anda adalah apakah ada di antaranya yang bermasalah di lapangan: insiden AI dan kegagalan agen yang terdokumentasi seputar model di kelas ini dikumpulkan di OrcaRouter AI Incident Archive, tempat setiap entri memuat sumbernya sendiri, tingkat keparahan, tingkat keyakinan, dan penanda sengketa.

Dibandingkan dalam artikel ini1

Terdeteksi dari artikel ini · Benchmark: Artificial Analysis · diperbarui setiap hari