on

Can the Apple M2 Pro (32 GB) run surya ocr 2.5?

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

Yes, it runs great

Runs great. At F16 it needs about 3.8 GB of 21.4 GB usable, with an estimated speed of 71.9 tok/s.

Best quant
F16
Generation speed
71.9 tok/s
Prompt processing
6,110 tok/s
First token (1K prompt)
0.3 s
Largest safe context
256K

Best app to run it on the Apple M2 Pro (32 GB)

On macOS

LM Studio

Desktop app · runs on llama.cpp, MLX

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

Open surya ocr 2.5 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 surya ocr 2.5

Quantized files · GGUF

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

huggingface.co/datalab-to/surya-ocr-2.5-gguf (opens in a new tab)

ollama run hf.co/datalab-to/surya-ocr-2.5-gguf

Original weights · Hugging Face

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

huggingface.co/datalab-to/surya-ocr-2.5 (opens in a new tab)

No sign-in needed.

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

How it’s rated

Quality 15Basic quality (D) · 15 of 100: how capable the model is at F16, whatever it runs on. Match score 50/100 (quality, fit, speed and memory use) sets the ranking.
How capable the model itself is at F16, 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 Apple M2 Pro (32 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.6.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.4.1 / 15
Match score50.8 / 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 M2 Pro (32 GB)

Quant Memory needed Available Speed Runs Quality Download
Q2_K 2.7 GB 21.4 GB 503 tok/s Runs great 10Basic quality (D) · 10 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 47/100 (quality, fit, speed and memory use) sets the ranking. GGUF files (opens in a new tab)
Q3_K_M 2.8 GB 21.4 GB 396 tok/s Runs great 12Basic quality (D) · 12 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 48/100 (quality, fit, speed and memory use) sets the ranking. GGUF files (opens in a new tab)
Q4_K_M 2.8 GB 21.4 GB 306 tok/s Runs great 14Basic quality (D) · 14 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 49/100 (quality, fit, speed and memory use) sets the ranking. GGUF files (opens in a new tab)
Q5_K_M 2.9 GB 21.4 GB 253 tok/s Runs great 14Basic quality (D) · 14 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 49/100 (quality, fit, speed and memory use) sets the ranking. GGUF files (opens in a new tab)
Q6_K 3.0 GB 21.4 GB 213 tok/s Runs great 14Basic quality (D) · 14 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 49/100 (quality, fit, speed and memory use) sets the ranking. GGUF files (opens in a new tab)
Q8_0 3.1 GB 21.4 GB 156 tok/s Runs great 15Basic quality (D) · 15 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 50/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
F16 3.8 GB 21.4 GB 71.9 tok/s Runs great 15Basic quality (D) · 15 of 100: how capable the model is at F16, whatever it runs on. Match score 50/100 (quality, fit, speed and memory use) sets the ranking. 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 surya ocr 2.5 need on the M2 Pro 32GB?

At F16 it needs about 3.8 GB. The M2 Pro 32GB has 21.4 GB usable.

How fast is surya ocr 2.5 on the M2 Pro 32GB?

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

Which quantization of surya ocr 2.5 should I use on the M2 Pro 32GB?

F16. 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?