https://txtfetch.com/languages/russian/
Extract text from Russian documents, Cyrillic intact.
A born-digital Russian file needs no OCR. The real risks are a legacy encoding and a look-alike Latin character, not the script itself.
Русский · Cyrillic
what-already-works
A born-digital Russian file, a Word document or a modern PDF with a real text layer, needs no OCR. Tika reads its Unicode text layer directly. Every Cyrillic letter is its own fixed code point, kept exactly as written.
character-encodings
| encoding | seen in | note |
|---|---|---|
KOI8-R | Older Unix and Linux systems, and Russian email from the 1990s and 2000s. | An eight-bit Cyrillic encoding designed to degrade to readable transliteration over ASCII-only links. Read as UTF-8, it garbles completely. |
Windows-1251 (CP1251) | Older Word and Excel files, and Windows-authored email and text exports. | The default Cyrillic encoding on Windows for years. A different byte layout from KOI8-R, so a wrong guess garbles either way. |
common-pitfalls
- Cyrillic text turns into an unrelated run of symbols.
- KOI8-R or Windows-1251 bytes read as UTF-8, or the two Cyrillic encodings confused for each other. This is mojibake from a legacy Cyrillic encoding. Re-read the file with its real encoding. Fix garbled text from the wrong encoding →
- A search for a Russian word returns a false match on a visually identical Latin word, or misses a real Cyrillic match.
- Several Cyrillic letters (Р, С, Х, А) look identical to Latin letters (P, C, X, A) but are different Unicode code points. These are called homoglyphs. Don't assume a visual match means a character match. Compare the actual Unicode code points, not just the rendered shape.
- A capitalized Russian word doesn't match its lowercase form in a case-insensitive search.
- Some search and comparison tools default to ASCII-only case folding, and never learned Cyrillic's upper- and lower-case pairs. Use a Unicode-aware case-folding function, not an ASCII-only one, before comparing Russian text.
chunking-and-tokens
Russian words are separated by spaces, so word-count chunking works about as well for Russian as it does for English. Cyrillic letters are each one Unicode code point. They don't inflate the character count the way an Arabic presentation form or a Korean jamo sequence can. The chunk previewer's ~4-characters-per-token estimate is a fair guide for Russian text.
ocr-status
A scanned Russian document still needs OCR. Tesseract can read Cyrillic shapes structurally, but the standard OCR tier ships English trained data plus script detection only (TESSDATA_LANGS=eng osd). Script detection can tell a page isn't Latin, without accurately reading Cyrillic letters. For a scan where accuracy matters, request quality=premium, which routes a vision-language model instead of Tika. No accuracy figure is published for Russian OCR under either tier.
faq
- Does txtfetch detect or label the document's language?
- No. txtfetch extracts the text as written and hands it back as-is. It does not detect, tag, or translate a document's language. There is no language parameter to set.
- Can txtfetch OCR a scanned Russian document?
- The standard tier ships English trained data plus script detection only (TESSDATA_LANGS=eng osd). It can detect the page isn't Latin script, without reading Cyrillic accurately. Request quality=premium for a hard scan.
- Why does my Russian text show unrelated symbols instead of Cyrillic?
- The source file likely used KOI8-R or Windows-1251, and something read it as UTF-8. Re-reading it with the correct encoding fixes the mojibake.
- Why does a search match the wrong word when a Cyrillic and a Latin letter look the same?
- Р, С, Х, and А look identical to Latin P, C, X, and A but are different Unicode code points. Compare the actual code points, not just the rendered shape.
related-reading
Check your Russian scan first.
The free scan check tells you if a page needs OCR. It runs in your browser.
Check a scan →