Numbers 27:1 and Joshua 17:3 give Zelophehad's genealogy as Hepher → Gilead → Machir → Manasseh, making Hepher his immediate father. 1 Chronicles 7:14-15 lists Zelophehad as a son of Manasseh directly, with a different intermediate genealogy entirely. The two genealogies disagree about who Zelophehad's father was.
Proposed answers
People have answered this in several ways; GEBible presents them as equal peers.
1Then the daughters of Zelophehad, the son of Hepher, the son of Gilead, the son of Machir, the son of Manasseh, of the families of Manasseh the son of Joseph came near. These are the names of his daughters: Mahlah, Noah, Hoglah, Milcah, and Tirzah.
3But Zelophehad, the son of Hepher, the son of Gilead, the son of Machir, the son of Manasseh, had no sons, but daughters. These are the names of his daughters: Mahlah, Noah, Hoglah, Milcah, and Tirzah.
14The sons of Manasseh: Asriel, whom his concubine the Aramitess bore. She bore Machir the father of Gilead.15Machir took a wife of Huppim and Shuppim, whose sister’s name was Maacah. The name of the second was Zelophehad; and Zelophehad had daughters.
What follows is one scholar’s way of reading this disagreement— a critical-historical view that often concludes the texts genuinely disagree. It draws on the peer-reviewed sources listed below and stands as one position among the answers above, presented for transparency, not as GEBible’s position.
How critical scholarship weighs this: Genuinely disputed among scholars
This summarizes where critical scholarship tends to land on this tension — a report on the field’s center of gravity, not GEBible’s own ruling.
Numbers 27:1 and Joshua 17:3 give a four-generation line: Zelophehad son of Hepher son of Gilead son of Machir son of Manasseh, making Hepher his immediate father. 1 Chronicles 7:14-15 appears to list Zelophehad more directly under Manasseh, within a tangle of Manassite names that does not reproduce the Hepher-Gilead-Machir chain in the same form, naming Asriel and then "the second was Zelophehad."
The standard harmonization invokes the elasticity of Hebrew ben, which denotes "son" but routinely extends to "grandson" or "descendant" — the same usage that lets Matthew 1:1 call Jesus "son of David, son of Abraham," collapsing a millennium of generations. On this reading Chronicles telescopes the genealogy, naming Zelophehad as a Manassite descendant without intending to deny the fuller line preserved in Numbers and Joshua. This is a legitimate and well-attested feature of biblical genealogical style. Against it, the intuitive objection — that Chronicles calls Asriel and Zelophehad "sons" in one breath, so both must mean immediate son — does not hold, because telescoping within a single list is precisely what Chronistic genealogies do; the genre mixes immediate and remote descent freely and without flagging the shift, often for the purpose of asserting tribal-territorial claims rather than strict paternity.
The more serious point is textual. 1 Chronicles 7:14-19 is among the most corrupt passages in the Hebrew Bible. The Masoretic Text is grammatically broken — verse 14 opens with a string of names whose syntactic relationships are unclear, and the Aramaizing and Septuagintal witnesses preserve a partly different arrangement. Virtually every modern critical edition and commentary reorders or emends the verses to extract sense: Japhet's OTL commentary, Knoppers' Anchor Bible, and Klein's Hermeneia all devote extended discussion to reconstructing the Manassite list, and they do not agree on the result. Given that the received text here cannot be read with confidence, it cannot bear the weight of a precise genealogical contradiction. What the corruption does suggest is that the Chronicler (or his sources) worked from fragmentary, possibly variant Manassite traditions that were never fully reconciled with the Pentateuchal line; Knoppers reads the passage as reflecting genuine tension with the Numbers/Joshua genealogy at the level of source material rather than a clean alternative pedigree.
This is also a notably weak "contradiction" even at the surface. Numbers and Joshua are explicit and mutually consistent; Chronicles is abbreviated and textually unstable. Reading Chronicles' ben as "descendant" — the ordinary genre convention — removes any formal clash, because nothing in the Chronistic notice positively asserts that Hepher was not Zelophehad's father; it simply does not name the intervening links, or names them in a damaged sequence. The Zelophehad tradition is significant for an independent reason: it underwrites the daughters'-inheritance ruling (Numbers 27, 36; Joshua 17), a legal etiology the Chronicler had every reason to preserve, since Zelophehad's daughters are explicitly named in the surrounding Manassite material and the clan's territorial standing depended on it. Milgrom traces how the inheritance case generated supplementary legislation about intratribal marriage in Numbers 36, which is why the line was remembered at all.
The upshot: read with the standard understanding of telescoped genealogy and due caution about a badly corrupted text, the passages are reconcilable — Numbers and Joshua give the full pedigree, Chronicles an abbreviated or garbled one — and the apparent disagreement about "who was Zelophehad's father" dissolves into the difference between a complete and a compressed list. The residual uncertainty is text-critical, not doctrinal.
Where the critical reading lands: largely harmonizable via the ben="descendant" convention and telescoping; the real datum is a corrupt, variant Manassite genealogical tradition, not a factual conflict over paternity.
Sources for this reading
Sara Japhet, I & II Chronicles (Old Testament Library; Westminster John Knox, 1993) pp. 178-184on the corrupt Manassite genealogy
Gary N. Knoppers, I Chronicles 1-9 (Anchor Bible 12; Doubleday, 2003) pp. 456-470on the Manassite genealogy and its tension with Numbers/Joshua
Ralph W. Klein, 1 Chronicles (Hermeneia; Fortress, 2006) pp. 226-235on the text-critical problems of 1 Chronicles 7:14-191 Chronicles 7:14-19
Jacob Milgrom, Numbers (JPS Torah Commentary; Jewish Publication Society, 1990) pp. 230-234on Zelophehad's line and the inheritance ruling
Trent C. Butler, Joshua (Word Biblical Commentary 7; Word, 1983) pp. 190-192on Joshua 17:3Joshua 17:3
Gleason L. Archer, Encyclopedia of Bible Difficulties (Zondervan, 1982) on the flexible use of ben
Examining the tension
What follows is one scholar’s way of reading this disagreement — a critical-historical view that often concludes the texts genuinely disagree. It draws on the peer-reviewed sources listed below and stands as one position among the answers above, presented for transparency, not as GEBible’s position.
How critical scholarship weighs this: Genuinely disputed among scholars
This summarizes where critical scholarship tends to land on this tension — a report on the field’s center of gravity, not GEBible’s own ruling.
Numbers 27:1 and Joshua 17:3 give a four-generation line: Zelophehad son of Hepher son of Gilead son of Machir son of Manasseh, making Hepher his immediate father. 1 Chronicles 7:14-15 appears to list Zelophehad more directly under Manasseh, within a tangle of Manassite names that does not reproduce the Hepher-Gilead-Machir chain in the same form, naming Asriel and then "the second was Zelophehad."
The standard harmonization invokes the elasticity of Hebrew ben, which denotes "son" but routinely extends to "grandson" or "descendant" — the same usage that lets Matthew 1:1 call Jesus "son of David, son of Abraham," collapsing a millennium of generations. On this reading Chronicles telescopes the genealogy, naming Zelophehad as a Manassite descendant without intending to deny the fuller line preserved in Numbers and Joshua. This is a legitimate and well-attested feature of biblical genealogical style. Against it, the intuitive objection — that Chronicles calls Asriel and Zelophehad "sons" in one breath, so both must mean immediate son — does not hold, because telescoping within a single list is precisely what Chronistic genealogies do; the genre mixes immediate and remote descent freely and without flagging the shift, often for the purpose of asserting tribal-territorial claims rather than strict paternity.
The more serious point is textual. 1 Chronicles 7:14-19 is among the most corrupt passages in the Hebrew Bible. The Masoretic Text is grammatically broken — verse 14 opens with a string of names whose syntactic relationships are unclear, and the Aramaizing and Septuagintal witnesses preserve a partly different arrangement. Virtually every modern critical edition and commentary reorders or emends the verses to extract sense: Japhet's OTL commentary, Knoppers' Anchor Bible, and Klein's Hermeneia all devote extended discussion to reconstructing the Manassite list, and they do not agree on the result. Given that the received text here cannot be read with confidence, it cannot bear the weight of a precise genealogical contradiction. What the corruption does suggest is that the Chronicler (or his sources) worked from fragmentary, possibly variant Manassite traditions that were never fully reconciled with the Pentateuchal line; Knoppers reads the passage as reflecting genuine tension with the Numbers/Joshua genealogy at the level of source material rather than a clean alternative pedigree.
This is also a notably weak "contradiction" even at the surface. Numbers and Joshua are explicit and mutually consistent; Chronicles is abbreviated and textually unstable. Reading Chronicles' ben as "descendant" — the ordinary genre convention — removes any formal clash, because nothing in the Chronistic notice positively asserts that Hepher was not Zelophehad's father; it simply does not name the intervening links, or names them in a damaged sequence. The Zelophehad tradition is significant for an independent reason: it underwrites the daughters'-inheritance ruling (Numbers 27, 36; Joshua 17), a legal etiology the Chronicler had every reason to preserve, since Zelophehad's daughters are explicitly named in the surrounding Manassite material and the clan's territorial standing depended on it. Milgrom traces how the inheritance case generated supplementary legislation about intratribal marriage in Numbers 36, which is why the line was remembered at all.
The upshot: read with the standard understanding of telescoped genealogy and due caution about a badly corrupted text, the passages are reconcilable — Numbers and Joshua give the full pedigree, Chronicles an abbreviated or garbled one — and the apparent disagreement about "who was Zelophehad's father" dissolves into the difference between a complete and a compressed list. The residual uncertainty is text-critical, not doctrinal.
Where the critical reading lands: largely harmonizable via the ben="descendant" convention and telescoping; the real datum is a corrupt, variant Manassite genealogical tradition, not a factual conflict over paternity.
Sources for this reading