Why Jewish Families Reused the Same Names

In Jewish genealogy, finding the right name is often the beginning of the problem rather than its solution. Which, for anyone ever studying Gemara, knows that in itself this is a very Jewish thing.

A researcher may discover three men called Moshe Cohen living in approximately the same place at approximately the same time. Two sisters may each have a son called Avraham. A child may apparently bear the same name as an uncle who died only a few years earlier. Several cousins may carry identical Hebrew names while appearing under entirely different names in civil records.

To someone unfamiliar with Jewish naming traditions, this can look like inconsistency, clerical confusion or even evidence that records have been incorrectly connected.

Frequently, it is none of those things.

Names in Jewish families carried religious, commemorative, linguistic and familial significance. The same naming traditions which can help reconstruct relationships can therefore also produce one of the most persistent problems in Jewish genealogical research:

the repeated appearance of the same names within closely related families.

Understanding why requires us to distinguish between a name as a cultural expression and a name as an identifier.

They are not always the same thing.

A name could preserve a person

Among Ashkenazi Jews, one of the most familiar naming customs was the practice of naming children in memory of deceased relatives.

The precise practice varied between families, places and periods, but its genealogical consequences can be considerable.

Suppose a man named Avraham dies leaving several adult children.

One daughter subsequently has a son and names him Avraham after her father. A year later, her brother has a son. He too may choose to name him Avraham after the same father. However, in this case there is a caveat, since the name is already "in use" they may opt out and choose a different name, another name of the deceased father, a derivate of the name Avraham or a similar meaning within a different name.

Nothing unusual has happened.

Within two years, however, the extended family contains two first cousins of approximately the same age, carrying the same or a similar name, commemorating the same person and quite possibly living in the same town.

If another sibling subsequently names a son Avraham, there may be three.

A genealogist encountering these children 150 years later may initially assume that the records refer to one individual whose age has been recorded inconsistently.

That assumption can dismantle an otherwise correct family reconstruction.

The duplication is not noise within the evidence.

It is evidence about the family.

Naming customs were not uniform across Jewish communities

It is important not to describe this as simply “the Jewish naming tradition.”

There is no single naming practice shared identically by all Jewish communities.

The convention of commemorating deceased relatives is particularly associated with Ashkenazi practice. In many Sephardi, Ethiopian, Asian and Mizrahi families, children have traditionally been named for living relatives as well, including grandparents.

Individual families also developed their own conventions.

Religious observance, migration, intermarriage, local culture and personal preference could all affect naming decisions. Customs could change between generations or after migration.

The correct methodological approach is therefore not to begin with a supposed universal rule and force the family into it.

Instead, the family's observed naming behaviour should itself be reconstructed.

If several generations consistently name children after grandparents, that pattern may become useful evidence. If another family appears not to follow such a pattern, the researcher should not invent one simply because a textbook says it was customary.

Custom provides context.

It does not provide proof.

The death of one generation could produce a cluster of names in the next

Repeated naming becomes particularly useful when chronology is considered.

Imagine a family containing five adult siblings. Their father, Moshe, dies in 1878.

Children born to those siblings before 1878 bear various names. Beginning in 1879, however, sons called Moshe suddenly appear in several branches of the family.

That clustering may be significant.

It does not prove that every child was named for the deceased grandfather. But it can provide a chronological clue, particularly when the father's death record has not survived.

The same principle can sometimes work in reverse.

If a family appears consistently to follow the Ashkenazi practice of naming children for deceased relatives, the birth of a child bearing a grandparent's name may suggest that the namesake had died by that point.

Again, this is not proof.

A naming pattern should never be allowed to overrule documentary evidence. But in fragmented families, particularly where nineteenth-century vital registers survive only selectively, naming patterns can help determine which hypothesis deserves further investigation.

That distinction between clue and conclusion is essential.

The same child could also have more than one name

Repetition is only one side of the problem.

The same individual may appear under several names.

A Jewish child might receive a Hebrew religious name while also being known by a Yiddish vernacular form. Civil authorities might record another linguistic equivalent. Migration could introduce another spelling or another version entirely.

A man appearing as Moshe in a Hebrew context might appear as Mojżesz in Polish documentation, Moishe in Yiddish usage, Моисей in Russian records, and Moses in

English-language documentation.

Those forms may refer to the same individual.

But they do not necessarily do so.

This is where Jewish genealogy becomes particularly vulnerable to circular reasoning.

A researcher knows that Moshe can correspond to Moses. A record for Moses is discovered. Therefore Moses is assumed to be Moshe.

The linguistic equivalence may be perfectly plausible while the genealogical identification is completely wrong.

Name equivalence establishes compatibility. It does not establish identity.

The individual must still be connected through other evidence: parents, spouse, occupation, age, locality, children, migration history, addresses or another combination of independent identifiers. In addition, it is common in Judaism for a child to carry more than one name, e.g. Moshe Ber or Josef Naftali Shmuel Natan... the list can go on.

Formal surnames did not eliminate the problem

The adoption of hereditary surnames across much of European Jewry did not suddenly produce stable modern identities.

Before fixed surnames became standard, individuals could be identified through patronymics, places of origin, occupations, family associations or other descriptors.

Even after hereditary surnames became compulsory, spelling remained variable.

A surname written in Hebrew characters could be rendered differently in Russian, Polish or German. An official hearing an unfamiliar surname might record it phonetically. Another clerk might transliterate it according to a different convention. A migrant might later simplify it, translate it or adopt a spelling better suited to the language of the destination country.

Consequently, genealogical identity frequently has to be established across families of name forms, rather than through exact spelling.

But this creates an uncomfortable combination.

Within one family, the same person may have several different recorded names.

At the same time, several different people within that family may have essentially the same name.

The researcher must therefore solve two apparently contradictory problems simultaneously:

different names may belong to the same person, while identical names may belong to different people.

That is why name matching alone is particularly dangerous in Jewish genealogy.

Patronymics can help — and mislead

Hebrew naming conventions can provide another layer of identification.

A man may be described as Moshe ben Avraham — Moshe, son of Avraham. A woman may similarly appear as the daughter of a named father.

This can be extremely valuable where several people share the same personal name.

But patronymics are not unique identifiers either.

If Avraham's sons repeatedly commemorate him in the next generation, the family may contain several cousins named Moshe whose fathers themselves bear recurring family names.

Furthermore, civil records may identify parents differently from religious documents. Hebrew names, vernacular names and official names may coexist.

A gravestone, marriage record, civil death certificate and immigration file may therefore describe the same person's parent using forms which look quite different on the page.

The researcher has to understand the linguistic relationship between the forms without allowing that relationship to substitute for evidence.

Naming patterns can expose relationships that records do not state

Used carefully, repetition can become extremely valuable.

Suppose two households appear in the same nineteenth-century town.

One contains children named:

Avraham, Chaim, Rivka and Lea.

A second household, whose relationship to the first is unknown, subsequently contains:

Chaim, Avraham, Lea and Moshe.

The repeated names prove nothing by themselves.

But suppose further investigation establishes that the fathers were of similar age, shared an unusual surname, belonged to the same registration community and repeatedly appeared together in administrative records.

The naming pattern now becomes part of a larger evidentiary picture.

Perhaps Avraham and Chaim were their parents. Perhaps Lea was a grandmother. Perhaps the repeated names preserve an earlier generation for which no surviving vital records have yet been located.

The names generate hypotheses.

The records must test them.

This is particularly useful when reconstructing Jewish families affected by migration, missing registers, war or the Holocaust, where the direct documentary chain may be incomplete.

Naming after someone is not evidence of descent from that person

This deserves stating explicitly because online family trees frequently make the opposite assumption.

A child bearing a particular name does not prove who the namesake was.

If a child called Mordechai is born shortly after a man called Mordechai dies, a commemorative connection may be plausible. If the deceased man was supposedly the child's grandfather, the pattern may strengthen an already documented relationship.

It cannot create that relationship.

Names could commemorate grandparents, great-grandparents, siblings, uncles, aunts, rabbis or other significant individuals. Children could also receive names for reasons that are no longer recoverable.

A naming hypothesis therefore belongs among supporting evidence, not foundational evidence.

The danger arises when researchers reverse the process:

The child was called X; therefore the grandfather must have been X; therefore this man called X must be the grandfather.

At that point the conclusion is being used to manufacture its own evidence.

Repeated names become particularly dangerous after migration

Migration often magnifies the problem.

Imagine three cousins named Moshe from the same extended family.

One migrates to Britain and becomes Morris.

Another reaches the United States and becomes Moses.

A third moves to Palestine and increasingly uses Moshe in official documentation.

Several decades later, their records appear to describe three clearly differentiated men.

But another family might produce the opposite situation.

Mojżesz, Moszek and Mojsze in Polish records may all subsequently appear as Morris in English.

Three apparently distinct men have become three men with the same Anglicised name.

Dates of birth may not rescue the researcher. Historical records frequently contain discrepancies in ages and dates, particularly across migration systems.

Nor can birthplace necessarily resolve the problem. All three cousins may quite correctly have reported the same town.

This is why identity reconstruction requires convergence across multiple characteristics.

Holocaust-era research makes the problem more acute

The consequences become particularly serious when researching families affected by the Holocaust.

Entire generations may disappear from the documentary chain. Survivors may report relatives from memory decades later. Testimony may use nicknames rather than official names. Married surnames may be unknown. Dates may be approximate.

The same deceased relative may consequently appear under several different forms across testimonies and memorial sources.

At the same time, commemorative naming after the war can produce a new generation carrying the names of murdered relatives.

A name may therefore connect generations emotionally and historically while simultaneously making documentary identification more complicated.

This is one reason Holocaust-related genealogy should rarely depend upon a single database or memorial record. Names need to be placed back into households, places and chronology.

Build the family before identifying the person

When repeated names become confusing, the solution is often to stop concentrating on the individual.

Reconstruct the family around them.

Identify siblings.

Identify spouses.

Record children in chronological order.

Establish addresses.

Track occupations.

Note witnesses and informants.

Map migration.

Record religious names separately from civil names.

Compare the naming patterns across collateral branches.

A person who is almost impossible to distinguish by name may become unmistakable once placed within the correct network.

This is particularly important where two people share not only a name but also an approximate age and birthplace.

The question then ceases to be:

Which Moshe is this?

It becomes:

Which Moshe had this wife, these parents, these children, this occupation, this address and this documented sequence of movements?

That is a much more answerable question.

Similar names are evidence of possibility, not identity

Jewish naming traditions can be extraordinarily useful to genealogists.

They can preserve memories of generations for which little documentation survives. They can suggest relationships between collateral branches. They can provide chronological clues. They can help connect Hebrew, Yiddish and civil identities.

But their usefulness depends upon restraint.

A repeated name is a clue.

A naming pattern is evidence worth considering.

A linguistic equivalent can establish that two records are compatible.

None of those things, by itself, proves that two people are the same person or that two families are related.

The central problem is therefore not that Jewish families repeatedly used the same names.

It is that modern researchers are accustomed to treating names as identifiers.

Historically, names performed many other functions. They commemorated. They connected generations. They expressed religious and cultural belonging. They adapted to language and migration. They preserved people who were no longer alive.

For genealogical purposes, that makes them enormously valuable.

It also makes them dangerous.

The name may tell us where to look. The family around the name tells us whom we have found.