Two Genealogies, One Jesus: Why Matthew and Luke Don't Agree After David

Anyone who has laid Matthew 1 and Luke 3 side by side has probably hit the same snag: both claim to trace Jesus’s genealogy, but after King David the names barely overlap. Even Joseph’s father gets a different name — Matthew calls him Jacob, Luke calls him Heli. Is this a straightforward error?

Laying the two genealogies side by side

Matthew 1 runs forward from Abraham through David and Solomon to Joseph. Luke 3 runs backward from Jesus through Joseph to Nathan (David’s son, and Solomon’s brother), and further back to Adam. Both genealogies pass through David, but they split at his sons: Matthew follows the royal line through Solomon, the throne’s actual heir; Luke follows the line through Nathan, a different son entirely.

This isn’t a scribal slip. It’s a signal that the two authors were tracing different lines from the start.

The ancient explanation: Julius Africanus and levirate marriage

The earliest surviving discussion of this problem comes from the third-century Christian writer Julius Africanus, in a letter to Aristides preserved by the church historian Eusebius in Historia Ecclesiastica 1.7. Africanus argued the divergence could be explained by levirate marriage — the practice commanded in Deuteronomy 25:5-10, where a man who died childless would have his brother marry his widow and raise up an heir in the dead man’s name. If Joseph’s biological father and legal father were half-brothers, and one died without an heir so the other married his widow, Joseph would be the biological son of one man and the legal (genealogical) son of the other — making him legitimately listed in both lines.

A modern alternative: Matthew traces Joseph, Luke traces Mary

A view that has gained wide traction in modern scholarship holds that the two genealogies were never meant to trace the same parent’s line at all — Matthew records Joseph’s legal, throne-succession line, while Luke records Mary’s line. Luke 3:23 hedges carefully, calling Joseph “the son, as was thought, of Heli” — language some scholars read as signaling that Heli was actually Joseph’s father-in-law, i.e., Mary’s father. Recording a son-in-law as a man’s “son” was not an unusual convention in the culture.

Raymond E. Brown, in his monumental study The Birth of the Messiah, surveys both explanations and concludes that while neither is conclusively provable, there is broad scholarly agreement that the two genealogies were deliberately tracing distinct lines of descent for distinct purposes.

Why two genealogies existed in the first place

The deeper question is why Matthew and Luke needed different kinds of genealogies at all. Matthew writes primarily for a Jewish audience and is concerned with establishing Jesus’s legitimate legal claim to David’s throne — hence the line through Solomon, the actual royal succession. Luke writes for a broader, Gentile-inclusive audience and is concerned with showing Jesus’s full humanity, rooted all the way back in Adam — hence the line extending past David and Abraham to the first human. Same person, two genealogies built to make two different theological points.

A short answer for the pulpit

When this comes up in conversation, here’s a compact response: “These genealogies aren’t contradicting each other — they’re proving different things. Matthew shows Jesus’s legitimate claim to David’s throne; Luke shows Jesus’s full solidarity with the human race, all the way back to Adam. The divergence after David has been explained since the third century through levirate marriage, or more recently by reading one genealogy as Joseph’s line and the other as Mary’s. Either way, what looks like a discrepancy actually reveals each Gospel writer’s distinct theological purpose.”

Sources

• Raymond E. Brown, The Birth of the Messiah, updated ed. (Yale University Press, 1993)
• Eusebius, Historia Ecclesiastica 1.7 (quoting the letter of Julius Africanus)
• Richard Bauckham, “The Two Genealogies of Jesus,” in Gospel Women (Eerdmans, 2002)

Comments

Loading comments…

Leave a comment

Comments are reviewed before being published. Only your name and comment are stored — no personal data collected.

Name (required)Write a comment (max 1,000 characters)

Submit comment