llmrun
datalab-toQwen3_5ForConditionalGeneration

Chandra Ocr 2 — Hardware Requirements & GPU Compatibility

VisionFunctions

Chandra OCR 2 is Datalab's 5.3-billion-parameter vision-language model for OCR and document conversion, turning scanned pages and PDFs into markdown, HTML, or JSON while preserving layout. It runs on a Qwen3.5-based backbone mixing linear attention with periodic full-attention layers, and handles handwriting, forms, tables, and math across 90-plus languages. It is the second generation of Datalab's Chandra model, improved over the first release. At just over 5 billion parameters, it runs on a single consumer GPU once quantized. Context extends to 262,144 tokens, generous for multi-page documents. It carries a modified OpenRAIL-M license: free for research, personal use, and startups under $2 million in funding or revenue, but it bars competing against Datalab's own API, more restrictive than a standard permissive license. Published in March 2026, following the original Chandra.

5.3B params · dense262K contextopenrail1.4M downloads604 likes20.0K quant downloads
S

Runs great on a 24 GB GPU

Runs from8 GB Q4_K_M · 128KBest on24 GB Q4_K_M · ~180 tok/s · 256KMacs from8 GB Q4_K_M · ~20 tok/s

openrail

Reference GPU · RTX 4090 24 GB

Estimates, ±20% · how we estimate

Run Chandra Ocr 2

One recommended way. Every other method, OS and quant is in the step-by-step guide.Each way opens a step-by-step guide for your OS and quant.

Recommended

Ollama
one command · needs Ollama installed
$ollama run hf.co/prithivMLmods/chandra-ocr-2-GGUF:Q4_K_M

Q4_K_M fits fully on the RTX 4090 · 20.2 GB free · 16K context

Download: chandra-ocr-2.Q4_K_M.gguf3.07 GBprithivMLmods

install, OS, other quants

Ways to runOther ways

each opens step-by-step

Run in cloud

Your own private copy · Q4_K_M · 24 GB GPU

  • The easiest way to try this model
  • Running in a few minutes, easy setup
  • Chat right here or connect any app

$5+ bonus for new users

How Much VRAM Does Chandra Ocr 2 Need?

Select a quantization level; the listed hardware adheres to it.

QuantizationVRAM+32KOn RTX 4090 (reference)
2.7 GB3.2 GB2-bit · K-quant — 2-bit quantization with K-quant improvementsFits: 256K context · ~241 tok/s
2.8 GB3.3 GB3-bit small — 3-bit small quantizationFits: 256K context · ~236 tok/s
3.0 GB3.6 GB3-bit medium — 3-bit medium quantizationFits: 256K context · ~215 tok/s
3.1 GB3.6 GB4-bit · legacy — 4-bit legacy quantizationFits: 256K context · ~210 tok/s
3.6 GB4.2 GB4-bit medium — 4-bit medium quantization — most popular sweet spotFits: 256K context · ~180 tok/s
4.2 GB4.7 GB5-bit medium — 5-bit medium quantization — good quality/size tradeoffFits: 256K context · ~155 tok/s
4.8 GB5.3 GB6-bit, very good — 6-bit quantization, very good qualityFits: 256K context · ~135 tok/s
5.8 GB6.3 GB8-bit, near-lossless — 8-bit quantization, near-losslessFits: 256K context · ~114 tok/s

Selected Q4_K_M

4-bit medium quantization

3.8GBat 16K context

Weights
3.2 GB
KV cache
0.3 GB
Overhead
0.3 GB

Fits RTX 4090 (reference) · 20.2 GB free · ~180 tok/s

≥50 tok/s needs ≥280 GB/s · RTX 5090 ~319, RTX 3090 Ti ~180

Which Hardware Can Run Chandra Ocr 2?

Q4_K_M · 3.6 GB

Chandra Ocr 2 (Q4_K_M) requires 3.6 GB of VRAM to load the model weights. For comfortable inference with headroom for KV cache and system overhead, 5+ GB is recommended. Using the full 262K context window can add up to 5.2 GB, bringing total usage to 8.8 GB. 52 GPUs can run it, including NVIDIA GeForce RTX 5090, NVIDIA GeForce RTX 3090 Ti. 163 devices with unified memory can run Chandra Ocr 2, including Mac Studio (M3 Ultra, 256GB), Mac Studio (M3 Ultra, 512GB), MacBook Air 13" M3 (8 GB).

By VRAM tier · typical GPUs and Macs at Q4_K_M
8 GB · RTX 4060Q4_K_M · 3.8 GB · ~48 tok/s · 128K8 GB tier →
12 GB · RTX 3060 12GBQ4_K_M · 3.8 GB · ~64 tok/s · 256K12 GB tier →
16 GB · RTX 5060 Ti 16GBQ4_K_M · 3.8 GB · ~80 tok/s · 256K16 GB tier →
24 GB · RTX 4090referenceQ4_K_M · 3.8 GB · ~180 tok/s · 256K24 GB tier →
Mac 32 GB · Mac Mini M4Q4_K_M · 3.8 GB · ~23 tok/s · 256KMacs →
Mac 64 GB · Mac Studio M4 MaxQ4_K_M · 3.8 GB · ~105 tok/s · 256KMacs →

Alternatives to Chandra Ocr 2

Similar models

4
ModelScoreVRAMtok/sWhy it is similar
Gemma 4 E2BGoogle—3.5 GB~191same size
Gemma 3n E2B ITGoogle—5.9 GB~183same size
Qwen2.5 Omni 3BAlibaba—6 GB~180same size
T5gemma 2B 2B Ul2Google—6 GB~178same size

Specifications

Publisher
datalab-to
Parameters
5.3B
Architecture
Qwen3_5ForConditionalGeneration
Context Length
262,144 tokens
Vocabulary Size
248,320
Release Date
2026-03-16
License
openrail

Frequently Asked Questions

How much VRAM does Chandra Ocr 2 need?

Chandra Ocr 2 requires 3.6 GB of VRAM at Q4_K_M, or 11.1 GB at BF16. Full 262K context adds up to 5.2 GB (8.8 GB total).

VRAM = Weights + KV Cache + Overhead

Weights = 5.3B × 4.8 bits ÷ 8 = 3.2 GB

KV Cache + Overhead ≈ 0.4 GB (at 2K context + ~0.3 GB framework)

Fit ratings and hardware model lists check this model with room for a 16K-token context, which needs a little more memory.

KV Cache + Overhead ≈ 5.6 GB (at full 262K context)

VRAM usage by quantization

3.6 GB
8.8 GB

Learn more about VRAM estimation →

What's the best quantization for Chandra Ocr 2?

For Chandra Ocr 2, Q4_K_M (3.6 GB) offers the best balance of quality and VRAM usage. Q5_0 (3.8 GB) provides better quality if you have the VRAM. The smallest option is Q2_K at 2.7 GB.

VRAM requirement by quantization

Q2_K
2.7 GB
Q4_0
3.1 GB
Q4_K_S
3.5 GB
Q4_K_M ★
3.6 GB
Q5_K_S
4.1 GB
BF16
11.1 GB

★ Recommended — best balance of quality and VRAM usage.

Learn more about quantization →

Can I run Chandra Ocr 2 on a Mac?

Yes — MacBook Air 13" M3 (8 GB) and 145 other Macs can run Chandra Ocr 2. Apple Silicon uses unified memory, so the model shares RAM with the system. At Q4_K_M you need at least 3.6 GB of usable unified memory (RAM minus macOS overhead).

Can I run Chandra Ocr 2 locally?

Yes — Chandra Ocr 2 can run locally on consumer hardware. Popular tools include Ollama, LM Studio, and llama.cpp.

How fast is Chandra Ocr 2?

At Q4_K_M, Chandra Ocr 2 can reach ~1315 tok/s on AMD Instinct MI350X. On NVIDIA GeForce RTX 4090: ~180 tok/s. Speed depends mainly on GPU memory bandwidth. Real-world results typically within ±20%.

tok/s = (bandwidth GB/s ÷ model GB) × efficiency

Example: NVIDIA B200 → 8000 ÷ 3.65 × 0.65 = ~1425 tok/s

Estimated speed at Q4_K_M (3.6 GB)

~1425 tok/s
~180 tok/s
~1425 tok/s
~1315 tok/s

Real-world results typically within ±20%. Speed depends on batch size, quantization kernel, and software stack.

Learn more about tok/s estimation →

What's the download size of Chandra Ocr 2?

At Q4_K_M, the download is about 3.18 GB. The full-precision BF16 version is 10.59 GB. The smallest option (Q2_K) is 2.25 GB.

Which GPUs can run Chandra Ocr 2?

52 consumer GPUs can run Chandra Ocr 2 at Q4_K_M. Top options include AMD Radeon RX 6700 XT, AMD Radeon RX 6800, AMD Radeon RX 6800 XT. 52 GPUs have plenty of headroom for comfortable inference.

Which devices can run Chandra Ocr 2?

163 devices with unified memory can run Chandra Ocr 2 at Q4_K_M (3.6 GB), including AMD Ryzen AI 9 HX 370 (Strix Point) Laptop, ASUS Ascent GX10, Beelink GTR9 Pro (Ryzen AI Max+ 395, 128 GB), Framework Desktop (Ryzen AI Max+ 395, 128 GB). Apple Silicon Macs use unified memory shared between CPU and GPU, making them well-suited for local LLM inference.