YaiGlobalArabic OCR

Full results

Every task, every baseline, every measure — including the three where a competitor leads.

These are the complete per-task tables. Read them alongside the methodology, which explains where each baseline figure came from and why three of the four task comparisons should carry less weight than the first.

1. Image-to-text recognition

3,760 samples · 17 systems · twelve corpora. CER and WER are lower-is-better; chrF is higher-is-better. Δ columns are relative differences against YaiGlobal.

Image-to-text, ordered by CER.
#SystemFamilyCER ↓WER ↓chrF ↑Δ CER
1YaiGlobal ParserOurs12.50%25.00%85.23—
2Gemini 2.0 FlashClosed13.00%32.00%77.95−3.85%
3AIN-7BOpen20.00%28.00%78.33−37.50%
4GPT-4oClosed31.00%55.00%61.01−59.68%
5GPT-4o-miniClosed43.00%71.00%47.21−70.93%
6Azure Document Intelligence OCRClosed52.00%69.00%50.97−75.96%
7TesseractFramework54.00%84.00%39.62−76.85%
8EasyOCRFramework58.00%89.00%45.47−78.45%
9LlamaParseClosed69.00%83.00%48.35−81.88%
10PaddleOCRFramework79.00%102.00%16.73−84.18%
11Gemma3Open105.00%145.00%30.02−88.10%
—Landing AIClosed115.00%——−89.13%
—Qwen2.5-VL-7BOpen120.00%——−89.58%
—SuryaFramework495.00%——−97.47%

The distribution matters more than the ranking. The mean CER across the baselines is 126.19% and the median 74.00%. Only three systems achieve a CER below 31%. Arabic image-to-text is not a task most current systems perform adequately, and the small competitive group at the top should temper any reading of this as a broad consensus.

2. Handwriting

Four handwritten corpora: KHATT, ADAB, Muharaf and OnlineKhatt. These are included in the image-to-text aggregate above, as they are in the published baselines, but analysed separately because they exercise a materially different capability.

Handwritten subsets, ordered by CER.
#SystemCER ↓WER ↓Δ CERΔ WER
1YaiGlobal Parser14.50%37.25%——
2Gemini 2.0 Flash22.00%53.50%−34.09%−30.37%
3AIN-7B26.00%47.25%−44.23%−21.16%
4GPT-4o40.00%75.00%−63.75%−50.33%
5Qaari50.50%69.50%−71.29%−46.40%
6GPT-4o-mini50.75%86.00%−71.43%−56.69%
7Tesseract75.75%115.50%−80.86%−67.75%
8Azure Document Intelligence OCR76.50%89.50%−81.05%−58.38%
9PaddleOCR80.50%104.75%−81.99%−64.44%
10Qwen2.5-VL-7B160.75%179.50%−90.98%−79.25%
11Qwen2-VL-7B165.50%275.00%−91.24%−86.45%
12Surya610.75%672.75%−97.63%−94.46%

Compare row by row against the table above it. Azure OCR moves from 52.00% to 76.50%; Tesseract from 54.00% to 75.75%; Qwen2.5-VL-7B from 120.00% to 160.75%. Systems tuned for printed Arabic do not transfer to handwriting. More on what that means in practice →

3. Table structure recognition

456 samples · 14 systems. TEDS (Tree-Edit-Distance-based Similarity) scores the recovered table tree against the reference, so it penalises a wrong row span as well as a wrong character.

Table structure recognition, ordered by TEDS.
#System or pipelineFamilyTEDS ↑Δ TEDS
1YaiGlobal ParserOurs97.99—
2LlamaParseClosed90.55+8.22%
3GPT-4oClosed85.76+14.26%
4Gemini 2.0 FlashClosed83.08+17.95%
5AIN-7BOpen75.94+29.04%
10Surya + MarkerFramework50.15+95.39%
11EasyOCR + DoclingFramework49.10+99.57%
12EasyOCR + Img2TableFramework39.09+150.68%
13Tesseract + Img2TableFramework38.64+153.60%
14Tesseract + DoclingFramework28.23+247.11%

Against the mean of the thirteen baselines (61.57), Δ = +59.15%. Every one of thirteen table types scored above 93.

Two observations. The ordering by family is clean — purpose-built parsers lead, general closed models follow, open-weight models trail them, OCR-plus-pipeline combinations trail everything — which reverses the image-to-text ordering, where LlamaParse and Landing AI performed poorly at raw transcription. Table structure rewards an explicit geometric model of the page. Second, the spread within the framework family shows the downstream pipeline matters as much as the engine feeding it: the same EasyOCR output scores 49.10 through Docling and 39.09 through Img2Table. Table fidelity is a property of the whole chain.

4. End-to-end PDF-to-Markdown

33 manually annotated multi-page PDFs · 11 systems. The closest proxy in KITAB-Bench for deployment conditions: recognition, reading-order and structural errors all accumulate into one output. MARS is the equally weighted combination of chrF (text fidelity) and TEDS (table fidelity).

End-to-end conversion, ordered by MARS.
#System or pipelineFamilychrF ↑TEDS ↑MARS ↑Δ MARS
1YaiGlobal ParserOurs79.8180.1279.97—
2LlamaParseClosed82.5170.3676.43+4.63%
3Gemini 2.0 FlashClosed75.7555.5565.65+21.81%
4Landing AIClosed68.1462.5365.33+22.41%
5GPT-4oClosed69.6260.6165.12+22.80%
6GPT-4o-miniClosed56.5952.6954.64+46.36%
7EasyOCR + DoclingFramework57.4651.1254.29+47.30%
8AIN-7BOpen56.5249.3252.92+51.12%

A baseline leads on text fidelity here. LlamaParse records chrF 82.51 against our 79.81 — we are 3.27% lower. We lead on MARS because table fidelity is 13.87% higher (80.12 against 70.36), and MARS weights the two equally. Note also that our text and table fidelity are within 0.31 points of each other, while LlamaParse's differ by 12.15 — a system that is good at text and weaker at structure.

This task uses 33 documents. Differences computed on it are not statistically robust.

5. Layout detection

1,700 pages, the Arabic BCE-Arabic-v1 pool · 6 systems. Class-aware IoU matching with standard object-detection metrics.

Layout detection on the Arabic portion of the benchmark.
#SystemmAP@0.5 ↑mAP@0.5:0.95 ↑Precision ↑Recall ↑F1 ↑
1YaiGlobal Parser0.6110.4500.9160.7110.801
2LlamaParse0.4350.3610.8760.5860.702
3DETR (Docling)0.7500.5660.6260.7250.654
4Surya0.5060.3810.751——

Two of the three losses are on this table. DETR in Docling leads on localization (mAP@0.5 0.750 against 0.611, we are 18.53% lower) and on recall (0.725 against 0.711, 1.93% lower). We lead on precision by 46.33% and on F1 by 22.48%.

The shape of the layout result

Precision is high and stable — from 0.750 on footnotes to 0.983 on page footers, with seven of eight categories above 0.86. Recall is the variable component, from 0.428 on captions to 0.949 on page headers. The parser is consistently right about what it detects and inconsistently complete about what it detects — its failures are omissions rather than misclassifications.

Layout performance by element category.
CategoryF1Note
Page header0.944Fixed position, repeats across pages
Page footer0.912Precision 0.983
Table0.863Precision above 0.95
Section header0.798Precision above 0.95
Body text0.795Over 6,082 instances
Caption—Precision 0.901, recall 0.428 — the weak point
Footnote—Precision 0.750, recall 0.500; only 54 instances, estimate is noisy

Captions are the clear weak point, with a precision-recall gap of 0.473 over 1,230 instances — roughly six captions in ten are not detected as captions. The practical consequence is specific: an undetected caption is not lost text, it is very likely absorbed into the adjacent body-text region, but its association with the figure or table it describes is lost. That degrades figure-aware retrieval specifically.

Run it on your own documents

These tables describe someone else's corpus. Send us the hardest page in yours — the water-damaged scan, the marginalia, the table that spans a fold — and we will run it and show you the output alongside the reference.

Talk to YaiGlobal →

Scope. Vendor-conducted evaluation on four of the nine KITAB-Bench tasks, 5,949 samples, seventeen baselines. Most baseline figures are quoted from the published KITAB-Bench paper; LlamaParse and Landing AI were measured internally and LlamaParse is the strongest baseline on three of four tasks — see provenance. Image-to-text aggregates are unweighted macro averages over twelve subsets; the sample-weighted CER is 14.08%. Source: Heakl et al., Findings of ACL 2025, arXiv:2502.14949.