on

Can the Apple M1 (16 GB) run WeVisOne-VL 4B?

42Fair quality (C) · 42 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 65/100 (quality, fit, speed and memory use) sets the ranking.

Yes, it runs well

Runs well. At Q4_K_M it needs about 5.6 GB of 10.7 GB usable, with an estimated speed of 14.9 tok/s.

Best quant
Q4_K_M
Generation speed
14.9 tok/s
Prompt processing
334 tok/s
First token (1K prompt)
3.1 s
Largest safe context
41K

Best app to run it on the Apple M1 (16 GB)

On macOS

LM Studio

Desktop app · runs on llama.cpp, MLX

  • Point-and-click: search, download and chat in one window.

Open WeVisOne-VL 4B in LM Studio

  • llama.cpp Usually the first to support new model architectures.
  • Ollama Runs the Hugging Face GGUF with ollama run hf.co/…

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 WeVisOne-VL 4B

Recommended for the Apple M1 (16 GB): Q4_K_M. 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 Q4_K_M file (opens in a new tab)

huggingface.co/mradermacher/WeVisOne-VL-4B-GGUF (opens in a new tab)

ollama run hf.co/mradermacher/WeVisOne-VL-4B-GGUF:Q4_K_M

Original weights · Hugging Face

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

huggingface.co/tencent/WeVisOne-VL-4B (opens in a new tab)

No sign-in needed.

Official repo · GitHub

Reference code, inference scripts and docs from Tencent. The weights themselves download from Hugging Face.

github.com/Tencent/WeVisOne-VL (opens in a new tab)

git clone https://github.com/Tencent/WeVisOne-VL

Links checked 1 day ago against Hugging Face, Ollama and GitHub.

How it’s rated

Quality 42Fair quality (C) · 42 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 65/100 (quality, fit, speed and memory use) sets the ranking.
How capable the model itself is at Q4_K_M, 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 well
How well it runs on the Apple M1 (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.19.2 / 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.9.2 / 15
Memory useRewards using the memory you have, so a bigger, better variant beats a tiny one that leaves most memory idle.12.1 / 15
Match score65.5 / 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 Apple M1 (16 GB)

Quant Memory needed Available Speed Runs Quality Download
Q2_K 4.6 GB 10.7 GB 24.5 tok/s Runs well 31Basic quality (D) · 31 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 60/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q3_K_M 5.0 GB 10.7 GB 19.3 tok/s Runs well 37Basic quality (D) · 37 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 63/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q4_K_M 5.6 GB 10.7 GB 14.9 tok/s Runs well 42Fair quality (C) · 42 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 65/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q5_K_M 6.1 GB 10.7 GB 12.3 tok/s Runs well 43Fair quality (C) · 43 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 66/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q6_K 6.6 GB 10.7 GB 10.4 tok/s Runs well 44Fair quality (C) · 44 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 66/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q8_0 7.8 GB 10.7 GB 7.6 tok/s Slow 45Fair quality (C) · 45 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 66/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
F16 12.3 GB 10.7 GB 3.0 tok/s Very slowfar over GPU memory limit 45Fair quality (C) · 45 of 100: how capable the model is at F16, whatever it runs on. Match score 43/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

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?