Accuracy benchmark · 2026

Handwriting OCR accuracy benchmark (2026)

How accurate is handwriting OCR in 2026, really? We measured it. Every tool below received the identical handwritten page, and its output was scored against a hand-checked reference using Word Error Rate (WER). Lower is better. The spread runs from 0.9% WER for the best specialist to over 95% for open-source OCR built for printed text.

# Tool Type Accuracy (WER) Score Price Best for
1 Handwriting OCR
Purpose-built specialist. The most accurate tool in our test.
Handwriting specialist 0.9% WER 9.6 Free 5-page trial, then from $0.15/page Anyone with real handwritten volume: archives, cursive, historical documents, or an app that needs an accurate handwriting API. Visit →
2 Azure Document Intelligence
The strongest of the big-three cloud document APIs on handwriting.
Cloud document AI 8.67% WER 6.5 From ~$1.50 per 1,000 pages (Read tier) Teams already on Azure processing mostly printed documents, with handwriting as a secondary case. Visit →
3 AWS Textract
Handwriting on forms, native to the AWS stack.
Cloud document AI 10.5% WER 6.2 From ~$1.50 per 1,000 pages (text detection) AWS-native teams processing printed forms that occasionally contain handwritten fields. Visit →
4 Claude (vision)
A frontier LLM that reads handwriting well enough for prototypes.
LLM vision 11.2% WER 6.0 Token-based, roughly $5-$15 per 1,000 pages Developers prototyping a feature who want to reuse an LLM API they already have. Visit →
5 GPT (vision)
Capable general-purpose vision, same trade-offs as any LLM.
LLM vision 14.4% WER 5.6 Token-based, roughly $2-$10 per 1,000 pages Quick, checkable transcriptions inside an app that already calls the OpenAI API. Visit →
6 Google Document AI
Capable on print; a reading-order problem on handwritten prose.
Cloud document AI 23.3% WER 4.5 From ~$1.50 per 1,000 pages (OCR) GCP-based teams working with printed documents rather than handwriting. Visit →
7 Transkribus
Built for trained historical-document projects, not one-off use.
Trainable specialist 47.7% WER untrained 4.2 Free plan, paid from ~€19.99/mo Research institutions with a large archive in a single consistent hand, willing to invest in training. Visit →
8 Tesseract
Excellent open-source OCR for print. Not viable for handwriting.
Open source 95.4% WER 1.5 Free and open source Developers doing printed-text OCR who want a free, self-hosted engine. Not handwriting. Visit →

Word Error Rate on one legible handwritten English prose page (2026), scored against a manual reference. Full protocol on the methodology page.

Results

Accuracy, tool by tool

A one-line summary of how each tool scored on the benchmark page. The reviews go deeper on where each holds up outside this sample, on cursive, historical hands, and non-English scripts.

  • Handwriting OCR — 0.9% WER (Handwriting specialist). The tool to beat. On handwriting it returned effectively the reference text, where the next-best option made roughly ten times as many errors.
  • Azure Document Intelligence — 8.67% WER (Cloud document AI). A sensible default if you live in the Microsoft ecosystem and your documents are mostly printed. Not the tool for a handwriting-heavy workload.
  • AWS Textract — 10.5% WER (Cloud document AI). The right default inside AWS for printed forms. The wrong tool for documents that are handwritten throughout.
  • Claude (vision) — 11.2% WER (LLM vision). Good enough for prototypes and one-off transcriptions; the silent-correction risk makes it hard to ship for document volume.
  • GPT (vision) — 14.4% WER (LLM vision). Convenient and competent for casual use; the same production caveats as any LLM-as-OCR approach apply.
  • Google Document AI — 23.3% WER (Cloud document AI). Fine for printed text inside Google Cloud; the weakest of the big three on handwritten prose in our test.
  • Transkribus — 47.7% WER untrained (Trainable specialist). Powerful for its niche, but the untrained result is unusable; budget serious training time or pick a specialist that works out of the box.
  • Tesseract — 95.4% WER (Open source). A great tool for the wrong job here. On handwriting the output is noise; include it only as a baseline.

Method

How we measured accuracy

Word Error Rate is the standard OCR accuracy metric: it counts substituted, missing, and inserted words against the reference and returns a percentage, so 0% is a perfect transcription. We use one clean, legible handwritten page as a fair baseline every serious tool should handle, which means the differences reflect the engine rather than a deliberately hard sample. We also track reading-order failures separately, because whole lines out of sequence are harder to fix than isolated word errors.

The full protocol, the reference sample, and our caveats are on the methodology page. Phone apps (Pen to Print, Google Lens, Apple Live Text) are assessed separately and not WER-scored, because their input is a photo rather than a comparable scan.