1 Chronicles Chapter 1 Read as one passage
1 Chronicles 1:1–4
Put together from the study of each verse: what each one meant, in order, with the background, words and debates of the whole passage said once.
1Adam, Seth, Enosh, 2Kenan, Mahalalel, Jared, 3Enoch, Methuselah, Lamech, Noah. 4The sons of Noah: Shem, Ham, and Japheth.
What the first hearers heard
For the community in Persian-era Jerusalem, these three names did several things at once:
- They summoned Genesis. The Chronicler does not retell creation or the Flood. He expects readers to know them, and the names alone are enough to bring those stories to mind.
- They set Israel inside humanity. Before Israel is ever mentioned, the reader is taken back to the first human. Israel is one branch of the human family God made, not a people standing outside it. Chapter 1 goes on to list the other nations (Edom, the Ishmaelites and others) as relatives within one family tree.
- They showed selection without comment. By going straight from Adam to Seth, the list follows the line Genesis traces from creation to Noah. The Chronicler's whole work keeps doing this: from Adam to Israel, from Israel to Judah and Levi, from Judah to David, all leading to the Temple community of his own day.
- They offered continuity after a break. The exile had threatened to cut Israel off from its past. A register that runs unbroken from Adam to the families who came back (1 Chr 9) told them that the line had not been broken.
The resonance of the names (Human, Appointed, Mortal Human) would have been audible to Hebrew speakers, but the Chronicler does not draw it out. Its main job is to establish the line.
From the study of 1 Chronicles 1:1.
Verse by verse
-
1Adam, Seth, Enosh,
Full study →"Adam. Seth. Enosh." There is no verb, no "begat", no sentence. Just three names, one after another, like the first entries in a family register.
To a Hebrew listener each name meant something:
- Adam is the name of the first man, and it is also the ordinary word for a human being, humankind. The book opens, in effect, with the word "Humanity".
- Seth was the child given after Abel's murder. Genesis explains the name with a pun: God "set" or "appointed" another child in Abel's place (Gen 4:25). Placing him straight after Adam silently skips Cain and Abel. Only the line that leads on to Noah, and eventually to Israel, is followed.
- Enosh is another Hebrew word for man. In poetry it usually stresses how frail and mortal humans are ("what is man, that you are mindful of him?"). Genesis links his lifetime to the moment people "began to call on the name of the LORD" (Gen 4:26).
So the verse works like a shorthand. Three names call up the first chapters of Genesis: creation, the loss of Abel, God giving another child, and the beginning of worship. It assumes the reader knows those stories. It is also the opening line of a genealogy that runs for nine chapters, from the first human down to the people living in Jerusalem after the exile. The point is that Israel's story starts with the whole human race and has never been cut off from it.
-
2Kenan, Mahalalel, Jared,
Full study →"Kenan, Mahalalel, Jared": three generations named one after another, with nothing else said.
The Chronicler names the fourth, fifth and sixth links in the line that runs from Adam to Noah. He gives no "fathered", no ages and no stories, only names in a row. He does this because he expects his readers to know Genesis 5. There Kenan son of Enosh fathers Mahalalel at seventy. Mahalalel fathers Jared at sixty-five. Jared fathers Enoch, the man who "walked with God".
To a Hebrew ear the names carried meanings English hides. Mahalalel sounds like "praise of God". Jared sounds like "descent" or "going down". Kenan echoes the name Cain, though its exact meaning is uncertain. The names do not form a sentence or a hidden message. What the verse conveys is continuity: one unbroken line of human generations from the first man toward the flood, and through Noah's son Shem, eventually to Israel.
-
3Enoch, Methuselah, Lamech, Noah.
Not studied yet. Study this verse
-
4The sons of Noah: Shem, Ham, and Japheth.
Full study →Noah, Shem, Ham, and Japheth.
The Hebrew is four names and one "and." Verses 1–4 are a bare roll call from Adam to Noah, ten generations without a verb, a number or a story. The reader is expected to fill in Genesis 5 from memory. With Noah the list stops running in a single line and divides: the three names after him are his sons, the three heads of all the peoples on earth after the flood. The Hebrew never says "sons." It assumes you already know. (The Greek translation and several English versions supply "the sons of Noah" for clarity.)
To a Hebrew ear the names said something too. Noah recalls "rest" and "relief." Shem is the word for "name, renown." Ham could sound like "hot" and was a poetic name for Egypt. Japheth recalls the blessing "may God make room for him." The order Shem, Ham, Japheth is the familiar one. But in the verses that follow, the Chronicler goes through them backwards: Japheth's far-off peoples first (v. 5), then Ham's (v. 8), and Shem's line last (v. 17), because Shem's line leads to Abraham and Israel. So this short verse sets up the whole map of humanity that the chapter is about to draw. Israel's story is placed inside the story of every nation.
Where popular teaching often drifts
in v1
The 'hidden gospel' in these names isn't in the Hebrew
- What's often taught
- The meanings of the ten names from Adam to Noah, read in order, form a sentence that foretells the gospel: 'Man (is) appointed mortal sorrow; (but) the Blessed God shall come down teaching (that) his death shall bring (the) despairing rest.' This is taken as evidence of a coded message built into the genealogy.
- What the text supports
The first names hold up fairly well: Adam is the word for 'human', Seth is linked in Genesis 4:25 to the verb 'set, appoint', and Enosh is a word for 'man' that is often used of mortal humanity. So the opening of the chain, the part found in this verse, is not invented.
The chain only becomes a gospel sentence through the names in verses 2–4, and there the meanings are forced. Kenan is most likely related to Qayin (Cain), not to qînâ, 'lament'. Methuselah most plausibly means 'man of the spear' or 'man of Shelah', not 'his death shall bring'. Lamech has no secure meaning at all. Hebrew also does not join a list of names into a sentence with no verbs or connecting words. The connecting words ('is', 'but', 'that') have to be added in English.
When Genesis explains a name in this line (Seth in 4:25, Noah in 5:29), it ties the name to the circumstances of the child's birth, not to a hidden message. The genealogy's real job in Chronicles is to trace an unbroken line from the first human to Israel.
- Where the English feeds it
- English transliterates the names, so most readers depend on popular lists of 'name meanings'. Those lists often give a single confident meaning for names whose origin is uncertain or disputed.
in v2
The 'gospel hidden in Genesis 5 names' isn't in the Hebrew
- What's often taught
- A popular teaching holds that the meanings of the ten names from Adam to Noah spell out a hidden gospel sentence: 'Man (is) appointed mortal sorrow; (but) the Blessed God shall come down teaching (that) His death shall bring (the) despairing rest.' Kenan, Mahalalel and Jared supply 'sorrow', 'the Blessed God' and 'shall come down'.
- What the text supports
The teaching is partly right: several of these names do carry meanings a Hebrew speaker would hear. Mahalalel sounds like 'praise of God', and Jared sounds like 'descent'. The sentence still depends on choices the evidence does not support:
- Kenan = 'sorrow' has little lexical support. Standard lexicons link the name to Cain (Qayin) and suggest 'smith' or 'acquired', while marking it uncertain. 'Sorrow' seems to come from treating it like a different word, qinah, 'lament'.
- Mahalalel = 'the Blessed God' turns a name that praises God ('praise of God') into a title for God. It was an ordinary name: a Judahite after the exile bore it (Nehemiah 11:4).
- Jared = 'shall come down' turns a noun-like name ('descent') into a future-tense prophecy. Grammatically it is not a verb in the future.
- The names do not join into a Hebrew sentence. The hidden message only appears after picking one English gloss per name from a range of options, sometimes contested ones, and adding connecting words.
Only one name in the list has its meaning explained by the Bible itself: Noah, 'this one will comfort us' (Genesis 5:29). Chronicles presents these names as a bare line of generations, with no hint of a hidden message.
- Where the English feeds it
- English Bibles render names by sound, so readers can't check what the names mean and fall back on name-meaning tables. Older tables, such as 19th-century Bible-name dictionaries, often give several speculative meanings for one name. That leaves room to pick the meanings that make a sentence.
in v4
Noah's three sons are not three races
- What's often taught
- Noah's three sons were the ancestors of three races: Shem of Asian or Middle Eastern peoples, Ham of African peoples, Japheth of Europeans. The lists that follow this verse are taken as a racial map of humanity.
- What the text supports
The lists in 1 Chronicles 1:5–23 (taken from Genesis 10) group peoples by region, language and political ties, not by skin colour or physical type:
- Canaan is listed under Ham (1:8, 13), yet the Canaanites spoke a Semitic language closely related to Hebrew and lived next door to Israel.
- Elam is listed under Shem (1:17), yet Elamite was not a Semitic language.
- Assyria/Asshur comes under Shem (1:17), yet Genesis 10:11 has Nimrod, from Ham's line, building Nineveh.
- Sheba and Havilah appear in both Ham's line (1:9) and Shem's line (1:22–23).
This is how ancient peoples drew up lists of nations: kinship language describes alliances and geography. In this verse the three brothers are simply named side by side, with no ranking. The "curse" behind much racial teaching comes from Genesis 9:25, which curses Canaan, not Ham. The Chronicler leaves even that episode out.
- Where the English feeds it
- English translations do not cause this reading. The problem is that "Semitic" (a word coined from Shem in the 18th century) and "Hamitic" (a 19th-century racial label scholars have since abandoned) have made the sons' names sound like racial categories.
Every word
-
אָדָ֥ם
ʾādām · H0121G
Adam; human being, humankind · v1
The first human, used here as a personal name (it has no 'the' in front of it). Any Hebrew hearer would also hear the everyday word for 'human, humankind', so the history of Israel opens with the word for humanity itself.
-
שֵׁ֖ת
shēt · H8352
Seth · v1
Adam's third son, born after Abel was murdered. Genesis 4:25 links the name to the verb shat, 'he has set, appointed': God 'set' another child in Abel's place. Listing him straight after Adam quietly leaves out Cain and Abel and follows only the line that leads on to Noah.
-
אֱנֽוֹשׁ׃
ʾĕnôsh · H0583
Enosh · v1
Seth's son. The name is the same as a poetic Hebrew word for 'man, mortal humankind' (as in Psalm 8:4, 'what is man'). Genesis 4:26 ties his lifetime to the moment when 'people began to call on the name of the LORD'. So the list opens with 'Human' and, two names later, comes back to 'Human' again.
-
קֵינָ֥ן
qênān · H7018
Kenan · v2
The fourth name in the line from Adam: Enosh's son and Mahalalel's father (Genesis 5:9–14). Here it is a bare name, with no 'father of' and no ages. The Chronicler expects his readers to know the Genesis account already.
-
מַהֲלַלְאֵ֖ל
mahălal'ēl · H4111G
Mahalalel · v2
The fifth name: Kenan's son and Jared's father (Genesis 5:12–17). The name praises God and most likely means 'praise of God'. A Hebrew hearer would have caught the 'praise' and the 'El' (God) in it. In the list, though, it simply marks the next generation.
-
יָֽרֶד׃
yāred · H3382G
Jared · v2
The sixth name: Mahalalel's son and Enoch's father (Genesis 5:15–20). The vowel is lengthened (yāred, not the usual yered) because the word ends a verse, which is normal Hebrew pronunciation at a pause. The name sounds like the verb 'go down, descend'.
-
נֹ֥חַ
Nōaḥ · H5146
Noah · v4
The tenth and last name in the line from Adam (vv. 1–4), and the hinge of the list. The name sounds like the Hebrew root for "rest" (nuaḥ), and Genesis 5:29 plays it against "comfort" (naḥam). Here it closes the single line of descent and opens the branching one.
-
שֵׁ֖ם
Shēm · H8035
-
חָ֥ם
Ḥām · H2526
-
וָיָֽפֶת׃
wāYāpheth · H3315
and Japheth · v4
"And" (the attached letter wa-) plus the third son. It is the only joining word in vv. 1–4, so it marks the three brothers off as a group. Japheth's line, the peoples of the far north and west (the Aegean and Anatolia, modern Turkey), is listed first in v. 5.
The world behind it
When and for whom. Chronicles was most likely written in the late Persian period (roughly 400–330 BCE) for the small Jewish community around Jerusalem in the Persian province of Yehud. They had come back from exile in Babylon, had no king, and lived under a foreign empire. The book retells Israel's history from Adam to the decree of the Persian king Cyrus that allowed them to return (2 Chr 36:22–23).
Why open with nine chapters of names. In the ancient Near East, and in Israel after the exile, family records were not idle trivia. They settled who belonged, who could serve as a priest, and who had a claim to land. Ezra 2:62 records priests who were barred from serving because they "searched for their family records but could not find them." A genealogy that starts with Adam tells this fragile community that they stand in an unbroken line going back to creation.
How the list works. 1 Chronicles 1:1–4 compresses Genesis 5 into bare names: ten generations from Adam to Noah, then Noah's three sons. Throughout chapter 1 the Chronicler names the side branches first and then follows the main line (Japheth and Ham before Shem; Ishmael before Isaac; Esau before Jacob). The field narrows step by step from all humanity to Israel (2:1). Neighbouring cultures also kept lists of figures from before the Flood: the Sumerian King List gives eight or ten kings before the Flood, and the Babylonian priest Berossus gives ten. Genesis 5 and this verse, by contrast, trace ordinary human ancestors, not kings descended from the gods.
Where the book stands. In the traditional order of the Hebrew Bible given in the Talmud (Bava Batra 14b), and in most printed Hebrew Bibles, Chronicles comes last. That means the Hebrew Bible ends as it began, with Adam, retelling everything from the first human to the return from exile. (Some major medieval manuscripts, such as the Aleppo and Leningrad codices, put Chronicles at the start of the Writings, the third section of the Hebrew Bible, instead.)
From the study of 1 Chronicles 1:1.
Where scholars differ
in v1
Does the name/word Enosh carry the idea of human frailty?
-
Yes: it comes from a root meaning 'to be weak, sick'.
There is a Hebrew verb *ʾānash*, seen in the adjective *ʾānûsh*, 'incurable' (Jer 17:9; 30:12). Poetic uses of *ʾĕnôsh* often set human weakness against God (Ps 103:15; Job 7:17; Isa 51:12). Older lexicons such as BDB lean this way.
-
No: it is simply a common Semitic word for 'people, humankind', and the frailty comes from the contexts it is used in, not from the word itself.
Cognates in Aramaic (*ʾĕnāsh*), Ugaritic and Arabic (*ʾins*) mean 'people' with no hint of weakness. Modern lexicons such as HALOT treat any connection to 'be weak' as uncertain. The frailty tone shows up mainly in poetry where it is set against God.
in v1
What happened in Enosh's day according to Genesis 4:26?
-
The beginning of true worship of YHWH.
The plain reading of the Hebrew *huḥal* is 'it was begun'. Most modern translations and commentators take it this way, and it fits the contrast between Cain's line and Seth's.
-
The beginning of profaning God's name (idolatry).
Some ancient Jewish interpreters (rabbinic midrash, some Aramaic translations) read the same verb as coming from *ḥll*, 'to profane'. This reading is not the natural sense of the verse, and Chronicles does not take up the question.
in v2
How are the Seth line (Genesis 5) and the Cain line (Genesis 4) related, given how alike their names are?
-
They are two versions of one older list of ancestors, kept separately and later placed side by side.
The names nearly match: Kenan/Cain, Mahalalel/Mehujael, Jared/Irad, Enoch/Enoch, Methuselah/Methushael, Lamech/Lamech. Some appear in a different order. Comparable ancient lists of rulers before the flood existed in several versions.
-
They are two separate family lines, and the likeness is deliberate, to contrast them.
Genesis presents Cain's line as violent (Lamech's boast, 4:23–24) and Seth's line as the one through which people 'call on the name of the LORD' (4:26). The two Lamechs and two Enochs are portrayed very differently. Chronicles keeps only the Seth line, which suggests it read them as two lines.
in v2
What does the name Jared mean?
-
'Descent', from the Hebrew verb yarad, 'to go down'.
The sound fits the Hebrew. Jubilees 4:15 and 1 Enoch 6:6 already read it this way in the Second Temple period, linking it to the Watchers coming down.
-
A non-Hebrew name, perhaps related to an Akkadian word for 'servant', or simply of uncertain meaning.
Several names in Genesis 4–5 look older than Hebrew or borrowed from neighbouring languages. The 'descent' reading may be a later play on the sound rather than the original meaning.
in v4
Which son was the eldest?
-
Shem was eldest; the standard order reflects birth order.
The order Shem–Ham–Japheth is constant (Gen 5:32; 6:10; 10:1; 1 Chr 1:4), and Shem was 100 two years after the flood (Gen 11:10).
-
Japheth was eldest.
Genesis 10:21 can be read "Shem… the brother of Japheth the elder" (so the Greek translation and the KJV). Shem would then be listed first because of his importance, not his age.
-
Ham was youngest, or the order is about importance, not age.
Genesis 9:24 calls the son who acted against Noah "his youngest (or 'lesser') son." Some take this to mean Ham, while others think it means Canaan. The Hebrew of 10:21 is ambiguous either way.
in v4
What do the names Ham and Japheth originally mean?
-
Hebrew wordplay meanings: Ham = "hot"; Japheth = "enlarge" (Gen 9:27) or "beautiful."
Wordplay within Genesis, and the poetic use of Ham for Egypt in the Psalms.
-
Borrowed or foreign origins (Ham from an Egyptian word for Egypt; Japheth from the Greek Iapetos).
Similarity of sound only. Most lexicons (HALOT) treat these links as unproven.
Sources
- BDB s.v. אָדָם, אֱנוֹשׁ, שֵׁת
- HALOT s.v. אָדָם, אֱנוֹשׁ, שֵׁת, שׁית
- Sara Japhet, I & II Chronicles (Old Testament Library, 1993)
- Gary N. Knoppers, I Chronicles 1–9 (Anchor Bible 12, 2004)
- Ralph W. Klein, 1 Chronicles (Hermeneia, 2006)
- Robert R. Wilson, Genealogy and History in the Biblical World (1977)
- Claus Westermann, Genesis 1–11: A Commentary
- Babylonian Talmud, Bava Batra 14b (order of the Writings)
- Josephus, Antiquities 1.68–71
- STEPBible / Tyndale House tagged Hebrew text (lemma and Strong's data)
- BDB s.v. קֵינָן, מַהֲלַלְאֵל, יֶרֶד
- HALOT s.v. קֵינָן, מַהֲלַלְאֵל, יֶרֶד
- Genesis 4:17–26; 5:9–20
- Nehemiah 11:4; Proverbs 27:21
- Luke 3:36–37
- 1 Enoch 6:6; Jubilees 4:15
- Septuagint, 1 Chronicles 1:2 and Genesis 5
- Sumerian King List (antediluvian section); Berossus, Babyloniaca (as preserved in later authors)
- Gordon Wenham, Genesis 1–15 (WBC)
- Sara Japhet, I & II Chronicles (OTL)
- BDB s.v. נֹחַ, שֵׁם, חָם, יֶפֶת
- HALOT s.v. נֹחַ, שֵׁם, חָם, יֶפֶת
- Ralph W. Klein, 1 Chronicles (Hermeneia)
- Gary N. Knoppers, I Chronicles 1–9 (Anchor Bible)
- Septuagint (Rahlfs) 1 Paralipomenon 1:4
- Jubilees 8–9; 1QapGen (Genesis Apocryphon)
- David M. Goldenberg, The Curse of Ham: Race and Slavery in Early Judaism, Christianity, and Islam (2003)
Original-language data: STEPBible TAHOT/TAGNT (CC BY 4.0).
1 of these verses not studied yet; their meaning appears here once they are.