1 Chronicles Chapter 1 Read as one passage
1 Chronicles 1:2–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.
2Kenan, Mahalalel, Jared, 3Enoch, Methuselah, Lamech, Noah. 4The sons of Noah: Shem, Ham, and Japheth.
What the first hearers heard
To the Judeans who first heard Chronicles, this verse was one step in a roll call they already knew. It reminded them of three generations from Genesis 5. Each name called up a longer story: Kenan, Mahalalel and Jared, the fathers in the line that led to Enoch and Noah.
The bare list did three things for them:
- Continuity. The returned exiles had lost their king, their independence and, for a time, their temple. The list ties them to an unbroken line of human generations from Adam. Through Noah and Shem, that line led to Abraham and Israel (1:24–28).
- Selection. Chronicles leaves out Cain's descendants and follows only the line that leads forward. This is the book's way of tracing the line God's purpose ran through. It does not say the rest of humanity was unimportant. Chapter 1 goes on to list the nations as well.
- Familiar names. At least one of these names was still in use in their day: a Judahite named Mahalalel appears in Nehemiah 11:4. To them, the ancestors before the flood were not strangers. They belonged to the same family story as the hearers.
The verse makes no doctrinal statement. It is a link in a chain, and the hearers knew that the chain mattered.
From the study of 1 Chronicles 1:2.
Verse by verse
-
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 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
-
קֵינָ֥ן
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
The world behind it
A genealogy that assumes Genesis. Chronicles was probably written in the late Persian or early Greek period (about the 4th century BC). Its readers were the small community of Judeans who had returned from exile and lived around a rebuilt Jerusalem. The book opens with nine chapters of genealogies. The first verses (1:1–4) squeeze the ten generations from Adam to Noah in Genesis 5 down to bare names: Adam, Seth, Enosh; Kenan, Mahalalel, Jared; Enoch, Methuselah, Lamech; Noah. Then come Noah's three sons.
Why bare names work. Readers who knew Genesis would hear each name as shorthand for the fuller account behind it. In that culture a genealogy was not dry data. It established who belonged, where a people came from, and that their story stayed unbroken through disaster. After the exile, a line running straight back to Adam showed that Israel's story was still part of God's dealings with all humanity.
Ten generations before the flood. Other ancient peoples kept lists of the rulers before the flood too. The Sumerian King List names eight to ten kings with enormously long reigns before "the flood swept over". The Babylonian priest Berossus (3rd century BC) lists ten. Genesis 5 shares that framework: ten generations, very long lifespans, then the flood. The difference is that Genesis lists ordinary fathers and sons in a family line, not kings of cities.
Echoes with the line of Cain. The names in Genesis 5 closely resemble the line of Cain in Genesis 4:17–18 (Kenan / Cain, Mahalalel / Mehujael, Jared / Irad, Enoch, Methuselah / Methushael, Lamech). Chronicles leaves Cain's line out entirely and follows only the line through Seth.
From the study of 1 Chronicles 1:2.
Where scholars differ
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. קֵינָן, מַהֲלַלְאֵל, יֶרֶד
- 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.