Handwritten text is significantly more complex than machine-printed: infinite variety of handwriting styles, ligatures (connected writing), blurry boundaries between characters, variability in pressure and angle. We encounter this on every project. Clients often come with a task: to recognize thousands of hand-filled forms per month with an error rate no higher than 5%. Standard OCR systems are powerless here. Over 5 years, we have implemented more than 30 projects for recognizing handwritten text for archival, medical, and corporate clients. Our experience confirms: proper preprocessing and choice of architecture solve 80% of the success. In one project for a medical center, we replaced manual entry of 5000 charts per day with automatic recognition — this reduced document processing costs by more than 60%, saving approximately $20,000 annually. Our HTR system achieved CER below 5% on these medical chart recognition tasks.
Choosing a Model for Russian Handwritten Text
Choosing an architecture depends on the language and data volume. TrOCR (Microsoft) is a transformer encoder-decoder for OCR. Encoder: ViT image processing, Decoder: autoregressive text generation. State-of-the-art on IAM handwriting dataset: CER 2.89% (large model). However, TrOCR is trained mainly on English, so for Cyrillic OCR it is better to use PaddleOCR with its SVTR_LCNet architecture, which leverages spatial transformer networks and attention mechanisms for robust recognition. PaddleOCR outperforms TrOCR on Cyrillic by a factor of 2 in CER, making it a better choice for Russian handwritten text.
from transformers import TrOCRProcessor, VisionEncoderDecoderModel
from PIL import Image
import torch
class HandwritingRecognizer:
def __init__(self, model_name: str = 'microsoft/trocr-large-handwritten'):
self.processor = TrOCRProcessor.from_pretrained(model_name)
self.model = VisionEncoderDecoderModel.from_pretrained(model_name)
self.model.eval()
self.device = 'cuda' if torch.cuda.is_available() else 'cpu'
self.model.to(self.device)
@torch.no_grad()
def recognize(self, image: Image.Image) -> str:
"""Recognition of a single line of text"""
pixel_values = self.processor(
images=image,
return_tensors='pt'
).pixel_values.to(self.device)
generated_ids = self.model.generate(
pixel_values,
max_new_tokens=128,
num_beams=4
)
return self.processor.batch_decode(
generated_ids,
skip_special_tokens=True
)[0]
PaddleOCR for handwritten Cyrillic text significantly outperforms TrOCR:
from paddleocr import PaddleOCR
ocr = PaddleOCR(
use_angle_cls=True,
lang='ru',
rec_algorithm='SVTR_LCNet',
rec_model_dir='./models/handwriting_rec'
)
Why Preprocessing Matters More Than Architecture
Handwritten text requires more aggressive preprocessing. Removing ruled background, binarization, cleaning artifacts — these steps critically affect the final CER. Below is a typical handwriting preprocessing pipeline.
import cv2
import numpy as np
from skimage import morphology
def preprocess_handwriting(image: np.ndarray) -> np.ndarray:
gray = cv2.cvtColor(image, cv2.COLOR_BGR2GRAY)
# Remove background lines (ruled paper)
horizontal_kernel = cv2.getStructuringElement(cv2.MORPH_RECT, (40, 1))
horizontal_lines = cv2.morphologyEx(gray, cv2.MORPH_OPEN, horizontal_kernel)
gray = cv2.subtract(gray, horizontal_lines)
# Otsu binarization
_, binary = cv2.threshold(gray, 0, 255,
cv2.THRESH_BINARY_INV + cv2.THRESH_OTSU)
# Remove small artifacts
cleaned = morphology.remove_small_objects(
binary.astype(bool), min_size=50
).astype(np.uint8) * 255
return cleaned
How We Perform Model Fine-Tuning
To adapt for corporate data, we use the following pipeline for neural network fine-tuning:
- Data annotation. We collect 500–2000 lines of handwritten text, transcribe them in Label Studio. Each line is a separate file with a text label. Label Studio annotation ensures high-quality ground truth.
- Augmentation. We apply random shift, rotation up to 5°, scaling 0.9–1.1, adding noise, and elastic distortion — this increases resilience to handwriting variations via self-supervised pretext tasks.
- Fine-tuning. For PaddleOCR we use RecModel with SVTR_LCNet, batch size 32, learning rate 1e-4, 100 epochs, employing CTC loss for alignment. We monitor CER metric on validation.
- Validation. We test on 10% of data (not used in training). If CER is above 10%, we add data or change hyperparameters.
- Export. The model is converted to ONNX or saved in PaddleOCR format for inference with beam search decoding.
Document Line Segmentation for Multi-Line Documents
Before recognition, a multi-line document must be split into lines. Our document line segmentation uses horizontal projection:
def segment_lines(binary_image: np.ndarray) -> list[np.ndarray]:
"""Horizontal projection for line segmentation"""
horizontal_projection = binary_image.sum(axis=1)
threshold = horizontal_projection.max() * 0.05
in_line = horizontal_projection > threshold
lines = []
start = None
for i, active in enumerate(in_line):
if active and start is None:
start = max(0, i - 5)
elif not active and start is not None:
end = min(len(in_line), i + 5)
line_img = binary_image[start:end, :]
if end - start > 10:
lines.append(line_img)
start = None
return lines
Preprocessing examples
For documents with colored lines (medical records), we use adaptive binarization with block size 21. For forms with gray background, we subtract the background using a circular kernel diameter=15. Parameters are selected for the specific template.
Fine-Tuning on Corporate Handwritten Data
For specific handwriting (medical records of a particular hospital, enterprise forms), fine-tuning is required. Without it, CER can reach 20-30%, which is unacceptable for document flow. We guarantee that after fine-tuning on 500–2000 lines, accuracy will increase to 90-95%. TrOCR fine-tuning typically requires a few hundred annotated images, while PaddleOCR fine-tuning for handwriting can leverage pre-trained checkpoints.
- Annotation of 500–2000 lines via Label Studio or CVAT.
- Fine-tuning TrOCR or PaddleOCR rec_model.
- CER decreases from 15–25% to 5–10% on domain-specific data.
| Dataset | Language | CER SOTA |
|---|---|---|
| IAM Online/Offline | English | 2.89% (TrOCR-Large) |
| CVL Database | English/German | 3.1% |
| Bentham Collection | English | 4.5% |
| HWR200 (Russian) | Russian | ~8% |
Understanding CER (Character Error Rate)
CER (Character Error Rate) is the proportion of errors at the character level. We use the CER metric to evaluate accuracy. For business processes, even 5% can mean hundreds of incorrectly recognized digits in reports. In one project for a medical center, we reduced CER from 18% to 4% by applying a combination of adaptive binarization and PaddleOCR fine-tuning. The result — automatic processing of 5000 charts per day instead of manual entry, and reduction of document processing costs by more than 60%. Reference CER values on public datasets (IAM Handwriting Database) are ~2.89%, but on real data fine-tuning is required.
Model Update Frequency
If operator handwriting changes or new fields are added, the model should be retrained every six months. We provide an incremental learning pipeline that allows updating weights in a few hours without full retraining. When the document template changes significantly (e.g., switching to a new form), adding 200–500 new annotated lines and running fine-tuning is sufficient.
Work Deliverables
- Requirements analysis and test run on 50 pages.
- Architecture selection (TrOCR / PaddleOCR / combined).
- Development of preprocessing and segmentation pipeline.
- Model fine-tuning (if needed) with validation.
- Integration via REST API or gRPC.
- Documentation (API reference, deployment guide).
- Access to model repository and training scripts.
- Operator training session (up to 4 hours).
- 3 months support after deployment.
Timeline and Cost
| Task | Timeframe |
|---|---|
| TrOCR integration for English | 1 week |
| Cyrillic handwriting recognition | 2–3 weeks |
| Fine-tuning for corporate documents | 4–7 weeks |
Cost is calculated individually — depends on data volume, required accuracy, and integration complexity. Typical project cost: $5,000–$15,000 for a complete HTR system. In one deployment, we cut annual document processing costs by $20,000. Project evaluation is free. Contact us for a test run on your samples. Our engineers will analyze your handwritten documents and propose the optimal solution. Get a consultation today.







