on

Can the Intel Core Ultra 200V (Arc 140V) (16 GB) run LFM2-VL 1.6B?

24Basic quality (D) · 24 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 58/100 (quality, fit, speed and memory use) sets the ranking.

Yes, it runs great

Runs great. At Q8_0 it needs about 3.1 GB of 9.1 GB usable, with an estimated speed of 41.2 tok/s.

Best quant
Q8_0
Generation speed
41.2 tok/s
Prompt processing
2,785 tok/s
First token (1K prompt)
0.4 s
Largest safe context
32K

Best app to run it on the Intel Core Ultra 200V (Arc 140V) (16 GB)

On Windows

llama.cpp

Command line + local API · runs on llama.cpp

  • Supports Intel Arc through SYCL and Vulkan.
  • Usually the first to support new model architectures.
llama-server -hf LiquidAI/LFM2-VL-1.6B-GGUF:Q8_0
  • LM Studio Point-and-click: search, download and chat in one window.
  • Jan Point-and-click: search, download and chat in one window.

On Linux

llama.cpp

Command line + local API · runs on llama.cpp

  • Supports Intel Arc through SYCL and Vulkan.
  • Usually the first to support new model architectures.
llama-server -hf LiquidAI/LFM2-VL-1.6B-GGUF:Q8_0
  • LM Studio Point-and-click: search, download and chat in one window.
  • Jan Point-and-click: search, download and chat in one window.

How we choose: the files published for this model, your operating system and GPU, whether it fits fully in memory, and published speed tests (MLX vs llama.cpp on Apple silicon, vLLM vs llama.cpp vs Ollama on NVIDIA). Details.

Download LFM2-VL 1.6B

Recommended for the Intel Core Ultra 200V (Arc 140V) (16 GB): Q8_0. Every other quantization has its own download link in the table below.

Quantized files · GGUF

Works in LM Studio, llama.cpp, Jan and Ollama. No sign-in needed.

Download the Q8_0 file (opens in a new tab)

huggingface.co/LiquidAI/LFM2-VL-1.6B-GGUF (opens in a new tab)

ollama run hf.co/LiquidAI/LFM2-VL-1.6B-GGUF:Q8_0

Original weights · Hugging Face

Full-precision files from Liquid AI, for fine-tuning, vLLM, Transformers.

huggingface.co/LiquidAI/LFM2-VL-1.6B (opens in a new tab)

No sign-in needed.

Links checked 3 days ago against Hugging Face, Ollama and GitHub.

How it’s rated

Quality 24Basic quality (D) · 24 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 58/100 (quality, fit, speed and memory use) sets the ranking.
How capable the model itself is at Q8_0, from its editorial quality tier scaled by the quantization or precision. It’s the same on any hardware that runs this variant. Scale: A+ 85+ · A 70+ · B 55+ · C 40+ · D under 40.
Runs Runs great
How well it runs on the Intel Core Ultra 200V (Arc 140V) (16 GB): speed, capped by how well it fits in memory. Runs great: 30+ tokens/s (or near the image, video or decision speed target) · Runs well: 10+ tokens/s · Slow: 3+ tokens/s · Very slow: under 3 · Won’t run: doesn’t fit even with offload. A tight fit or RAM offload caps it at Runs well; heavy offload caps it at Slow.

Match score

To order lists, each result also gets a match score out of 100 from four parts. It favors the most capable model that still runs well.

Model qualityEditorial quality tier of the model, scaled by the quantization or precision used.10.8 / 45
Memory fitFull marks when the model fits in the share of unified memory the GPU can use; fewer when it goes past that limit.25.0 / 25
SpeedGeneration speed against a 40 tokens/s target for LLMs, or render time against a target for image and video.15.0 / 15
Memory useRewards using the memory you have, so a bigger, better variant beats a tiny one that leaves most memory idle.7.9 / 15
Match score58.7 / 100

The match score orders results; it is not shown as a grade. Quality and Runs are the two ratings in the tables.

Every quantization on the Intel Core Ultra 200V (Arc 140V) (16 GB)

Quant Memory needed Available Speed Runs Quality Download
Q2_K 2.1 GB 9.1 GB 133 tok/s Runs great 16Basic quality (D) · 16 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 52/100 (quality, fit, speed and memory use) sets the ranking. GGUF files (opens in a new tab)
Q3_K_M 2.2 GB 9.1 GB 105 tok/s Runs great 20Basic quality (D) · 20 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 54/100 (quality, fit, speed and memory use) sets the ranking. GGUF files (opens in a new tab)
Q4_K_M 2.4 GB 9.1 GB 81.0 tok/s Runs great 22Basic quality (D) · 22 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 56/100 (quality, fit, speed and memory use) sets the ranking. GGUF (Q4_0) (opens in a new tab)
Q5_K_M 2.6 GB 9.1 GB 66.9 tok/s Runs great 23Basic quality (D) · 23 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 56/100 (quality, fit, speed and memory use) sets the ranking. GGUF files (opens in a new tab)
Q6_K 2.7 GB 9.1 GB 56.2 tok/s Runs great 23Basic quality (D) · 23 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 57/100 (quality, fit, speed and memory use) sets the ranking. GGUF files (opens in a new tab)
Q8_0 3.1 GB 9.1 GB 41.2 tok/s Runs great 24Basic quality (D) · 24 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 58/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
F16 4.6 GB 9.1 GB 19.0 tok/s Runs well 24Basic quality (D) · 24 of 100: how capable the model is at F16, whatever it runs on. Match score 57/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab) Original weights (opens in a new tab)

Memory figures assume 8K of context. Longer conversations or documents grow the KV cache.

Other hardware that runs it

Quick answers

How much memory does LFM2-VL 1.6B need on the Intel Core Ultra 200V (Arc 140V) 16GB?

At Q8_0 it needs about 3.1 GB. The Intel Core Ultra 200V (Arc 140V) 16GB has 9.1 GB usable.

How fast is LFM2-VL 1.6B on the Intel Core Ultra 200V (Arc 140V) 16GB?

About 41.2 tok/s at Q8_0, an estimate from the hardware’s memory bandwidth and the size of the model.

Which quantization of LFM2-VL 1.6B should I use on the Intel Core Ultra 200V (Arc 140V) 16GB?

Q8_0. Of the versions that fit, it is the one that runs best; when two run equally well, the check prefers the higher-rated one.

Estimates come from published hardware specs and our open formulas, not from running the model on your machine. Real speed varies with runtime, drivers and settings. Numbers marked “Measured” come from a linked benchmark.

Was this page helpful?