# Transcribe Hebrew Genealogy Records

Read handwritten Hebrew vital records, ketubot, and community registers, translate them to English, and connect every ancestor into one family archive.


Jewish genealogy research leads quickly to documents in Hebrew - a script that most researchers today cannot read, combined with dating systems and naming conventions that differ significantly from standard civil records. A ketubah, a community pinkas, or a burial-society register holds exactly the kind of family detail that does not appear in government vital records, but getting that information out of the document is a real barrier.

KleioBase reads Hebrew 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 Hebrew records

You upload a scan or photo of the record. KleioBase reads the Hebrew handwriting - including the square script used in formal documents and the cursive Hebrew script common in informal records and letters - and produces a transcription alongside an English translation. It then extracts the structured details a genealogist needs: names (in both their Hebrew form and transliteration), dates converted from the Hebrew calendar to Gregorian, places, and the relationships the record describes.

Ketubot follow a standardized Aramaic legal formula with Hebrew and local-language additions for the specific names, places, and dates. Community pinkasim are more varied in format and handwriting. Cemetery records range from inscribed stone text to handwritten burial-society ledgers. KleioBase reads each document type and gives you the extracted data for review.

## From a scan to a connected profile

Reading the record is step one of four:

1. **Upload** the scan or photo.
2. **Process** it - KleioBase reads the Hebrew script, converts dates, translates the text, and pulls out the people and events.
3. **Review** the result. Hebrew naming patterns - patronymics, honorific names, and names used only in religious contexts versus civil contexts - mean the same person can appear under several different names across documents. The review step is where you reconcile those variations.
4. **Confirm** it - KleioBase creates or updates person profiles and links the record to them.

Once confirmed, the record is part of your connected archive. As your archive grows, KleioBase surfaces likely duplicate profiles to merge and gaps in the record chain where a generation has not yet been documented.

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

Hebrew handwriting varies enormously by region, period, and the individual writer. Ashkenazic cursive Hebrew looks very different from Sephardic cursive Hebrew, and both differ from printed square-script documents. Names present an additional challenge: the same man might be "Avraham" in a Hebrew document, "Abram" in a Russian civil record, and "Abraham" in an American immigration form. Dates in the Hebrew calendar require conversion, and the conversion depends on knowing the exact day - not just the year.

KleioBase gives you a first reading and an English translation, then shows you the result for review. You correct what needs correcting, confirm what is right, and only then does it enter your archive. Nothing is added automatically. That workflow - a readable first pass combined with a connected archive that grows with every confirmation - is what turns a folder of Hebrew documents into a family history you can actually build on.

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