# Transcribe Yiddish Genealogy Records

Read handwritten Yiddish letters, community records, and vital documents written in Hebrew script, translate them to English, and connect every ancestor into one family archive.


Yiddish was the daily language of Eastern European Jewish life for centuries - the language of letters home, community organizations, burial-society records, and the personal papers that survived emigration. For researchers tracing Ashkenazic ancestry, Yiddish documents are often the closest link to the world their families came from. But Yiddish is written in Hebrew script, runs right to left, and uses a vocabulary and spelling system distinct from both Hebrew and the Germanic languages it is related to.

Most people today cannot read Yiddish, even those with a Hebrew background. The gap between the document and the researcher is real.

KleioBase reads Yiddish records and translates them into English, then connects every person, date, and place into one family archive. The reading is step one - the connected archive is the point.

## How KleioBase reads Yiddish records

You upload a scan or photo of the document. KleioBase reads the Yiddish text - written in Hebrew script, right to left - and produces a transcription alongside an English translation. It then extracts the structured details relevant to genealogy: names, dates, places, and the relationships and events the document describes.

Yiddish spelling was not standardized until the mid-20th century (YIVO orthography), so 19th- and early 20th-century documents show wide spelling variation for the same word. Yiddish also borrows extensively from Hebrew, Aramaic, Slavic languages, and German, and those borrowings appear in different forms depending on the writer's background and the date of the document. KleioBase reads the document as written and translates the meaning rather than requiring a standardized input.

## From a scan to a connected profile

Reading the document is step one of four:

1. **Upload** the scan or photo.
2. **Process** it - KleioBase reads the Yiddish text, translates it, and extracts the people and events.
3. **Review** the result. Personal letters and informal records are harder than standardized forms - the handwriting is more variable and the vocabulary less predictable. The review step is where you catch errors and add context you bring from knowing the family.
4. **Confirm** it - KleioBase creates or updates person profiles and links the document to them.

Once confirmed, the document is part of your connected archive. The uncle mentioned in a 1910 letter becomes the same person as the grandfather in a 1905 vital record when you confirm the connection. As your archive grows, KleioBase surfaces likely duplicates and flags where a generation has no documents yet.

## Why Yiddish records are hard, and how the review step helps

Yiddish presents a layered challenge: Hebrew script, right-to-left reading direction, pre-standardization spelling variation, a vocabulary drawn from multiple source languages, and handwriting styles that range from elegant book-hand to barely legible personal scrawl. Names are particularly tricky - a man named "Moishe" in his Yiddish letters might appear as "Moisei" in a Russian civil record, "Morris" in an American immigration record, and "Moses" in an English-language document. Connecting those names across your archive is work that requires human judgment.

KleioBase gives you a first reading and an English translation, then puts you in control. You review the result, correct what needs correcting, and only then confirm it to your archive. Nothing is added automatically. That workflow - a readable first pass at a script most people cannot read, plus a connected archive that grows with every confirmation - is what makes Yiddish documents part of a family history rather than a separate pile of paper.

Canonical: https://kleiobase.com/transcribe/yiddish-records