Review mixed-language documents with bilingual OCR

Choose one installed recognition language for each upload. A single pass may work when one language dominates, but pages with mixed scripts or reading directions often need separate crops or passes. Recombine the reviewed results without transliterating names or changing source-language terms.

Drop a mixed-language document

Identify the scripts and dominant language before choosing the model

Browse your files
Mixed-language image or PDF20 MB maximum
No file chosen yet

Recognition settings

Choose the primary language in your document.

Private by design. Files are processed in temporary storage and removed when processing finishes. Avoid sensitive uploads when online processing is not appropriate.

Language-aware review for pages with more than one script

Recognize a mixed-language document using installed language data and verify script changes, names, punctuation, and reading order.

Good candidatePages with a dominant installed language and limited secondary-script content.
Language riskUnsupported packs, script switching, transliteration, and mixed reading directions can produce plausible substitutions.
Capability boundaryAvailable languages are detected from the server at runtime; unsupported choices are never offered.
OCR.now social preview for Bilingual OCR with a source-specific recognition workflow

OCR.now exposes only language packs actually installed on the server. A single selected model can create a draft, but mixed scripts may need separate passes and deliberate recombination.

Only installed language packs are offered. The workflow helps decide whether one model preserves the page or whether regions must be recognized and recombined separately.

Set the limits of this task with How to Choose an OCR Language Model, then use A Reviewable Workflow for Mixed-Language OCR to review uncertainty. Related inputs may be better handled by Image to Text or Handwriting to Text.

When separate language passes are safer

Use separate script-specific recognition when one model consistently damages the other script. Choose a specialist or human transcription workflow for unsupported languages, historical scripts, or legally consequential multilingual documents.

Test one combined pass against script-specific regions

Identify every script and reading direction before recognition.

Run separate crops when one language model damages the other script.

Keep names and untranslated terms in their source form during review.

Inspect transitions between languages and directions

Review pointLikely failureValidation action
Script coverageThe chosen model lacks one writing systemInventory every script and confirm an installed language pack
DirectionRight-to-left and left-to-right runs reorderCheck copied text, numbers, punctuation, and region sequence
NamesDictionary expectations replace proper nounsProtect names and compare them character by character

Mixed-script page scenario

For a bilingual notice with English headings and Chinese body text, test a combined page pass and focused script-specific crops. Compare which method preserves names, numbering, and line order. Recombine by visible region rather than translating or rewriting text to make the output sound fluent.