Flagship dossier / Old Testament

Who Killed Goliath?

David, Elhanan, Lahmi, and the textual relationship between Samuel and Chronicles.

1 Samuel 172 Samuel 21:15–221 Chronicles 20:4–8
High confidence
Exegis conclusion

David killed Goliath; Elhanan killed Lahmi, Goliath’s brother. The Samuel line most likely suffered a small scribal corruption that Chronicles preserves or corrects.

01

The precise difficulty

First Samuel 17 repeatedly identifies David as the man who struck and beheaded Goliath of Gath. Yet the traditional Hebrew text of 2 Samuel 21:19 says Elhanan son of Jaare-oregim the Bethlehemite struck Goliath the Gittite, whose spear shaft was like a weaver’s beam. First Chronicles 20:5 says Elhanan son of Jair struck Lahmi, the brother of Goliath. Did two men kill the same giant, was Goliath a title, or has one line been damaged in copying?

The issue is not solved by observing that battle traditions vary. The clauses share distinctive wording, and Chronicles appears to preserve or clarify elements that yield a coherent distinction: David killed Goliath; Elhanan killed Goliath’s brother Lahmi.

02

Relevant passages

03

Historical and literary context

The four-giant notice in 2 Samuel 21 concludes a collection of wars and royal deliverances. Its purpose is corporate: David and his servants extinguish Philistine champions. First Chronicles retells the list after David’s wars, smoothing several difficult expressions.

Names and patronymics in Samuel’s textual tradition are sometimes unstable. Jaare-oregim contains the word weavers, which also appears later in the same verse. Bethlehemite in Hebrew can be read with letters resembling the object marker plus Lahmi. Repetition and visual similarity create a plausible route for scribal displacement.

The Chronicler often used a form of Samuel older than the medieval manuscript that later became the Masoretic base. Therefore Chronicles may preserve an earlier reading, or it may make an informed editorial correction. Either way, it is an ancient textual witness rather than a late apologetic invention.

The idea that Goliath was a dynastic title or that Elhanan was David’s former name lacks direct textual support. Two different Goliaths are possible in abstraction but unlikely because the distinctive spear description links the lines.

04

Textual and translation issues

How the Hebrew may have become compressed

The Samuel line contains difficult combinations: 'Bethlehemite' and 'weavers' are close to words needed for 'Lahmi' and 'the brother of.' A scribe’s eye may have skipped or redistributed consonants because 'weaver’s beam' follows. Chronicles reads smoothly: Elhanan son of Jair struck Lahmi, brother of Goliath the Gittite.

The King James solution

The KJV prints 'the brother of' in italics in 2 Samuel 21:19, signaling words supplied by translators rather than found in the Masoretic text. That harmonization agrees with Chronicles in meaning, but readers should know its textual basis. Many modern versions place the phrase in the text with a note or translate the extant Samuel wording and footnote Chronicles.

05

Major interpretive positions

A copyist omission in Samuel

The earliest recoverable line matched the sense preserved in Chronicles: Elhanan killed Lahmi, Goliath’s brother; Samuel’s received line lost or confused several words.

Strengths
  • Explains all three accounts with one localized and graphically plausible corruption.
  • Fits known instability in Samuel’s textual transmission.
  • Accounts for the shared spear description without inventing a second Goliath.
Weaknesses
  • No surviving Hebrew Samuel manuscript preserves the full proposed wording.
  • The precise sequence of scribal changes is reconstructed.
  • Chronicles might be editorially harmonizing rather than copying an older reading.

Chronicles intentionally clarifies Samuel

The Chronicler knew both the David tradition and Samuel’s difficult line and rewrote the latter to identify a brother named Lahmi.

Strengths
  • Fits Chronicles’ practice of adapting sources.
  • Does not require a lost Samuel manuscript identical to Chronicles.
  • Explains the reader-facing coherence of the later account.
Weaknesses
  • Leaves the received Samuel claim historically conflicting on its surface.
  • Cannot show whether the Chronicler had independent information.
  • Calling it correction does not establish which wording was earliest.

Two Goliaths or a title

David and Elhanan killed different warriors called Goliath, perhaps a title or recurring name.

Strengths
  • Allows the Masoretic Samuel wording to stand without emendation.
  • Names can recur among people from the same city.
  • Keeps Elhanan’s act distinct from David’s.
Weaknesses
  • No text says Goliath is a title.
  • The weaver’s-beam phrase strongly echoes David’s opponent.
  • Chronicles explicitly interprets the victim as Goliath’s brother, not another bearer of the name.

David and Elhanan are one person

Elhanan is an alternate personal name for David, whose ancestry is associated with Bethlehem.

Strengths
  • Would make both men the same killer.
  • Biblical figures sometimes have multiple names.
Weaknesses
  • Elhanan is listed separately among David’s warriors.
  • The patronymics do not align.
  • No narrative or genealogy identifies David with Elhanan.
06

Exegis conclusion

David killed Goliath; Elhanan killed Lahmi, Goliath’s brother. The Samuel line most likely suffered a small scribal corruption that Chronicles preserves or corrects.

First Samuel’s extended narrative cannot reasonably be read as uncertain about its protagonist. Chronicles supplies a coherent parallel within the same four-giant list, and its wording explains how Samuel’s consonants and the repeated weaver language could become confused.

This is a textbook case where the doctrine of Scripture should encourage textual work rather than conceal it. The extant Masoretic wording of Samuel presents a conflict; comparing an ancient parallel allows the likely original sense to be recovered. The event’s substance and the identity of David’s victim are multiply attested.

Confidence: High. High confidence concerns the identities of the two defeated warriors. The exact scribal history and whether Chronicles copied an older source or editorially corrected it remain uncertain.

07

Short, pastoral, and academic answers

Short answer

David killed Goliath in 1 Samuel 17. Elhanan later killed Goliath’s brother Lahmi, as 1 Chronicles 20:5 states. The Hebrew line in 2 Samuel 21:19 most likely lost or confused a few words during copying; its unusual wording contains the very terms that could produce the error. Some translations restore the sense from Chronicles and mark it in a footnote.

Pastoral answer

A copied line can be damaged without making the Bible a deception. We possess multiple witnesses precisely so they can be compared. Here the difficult reading is visible, the parallel is ancient, and the likely correction is modest.

Faith does not need translators to hide italic words or footnotes. Careful notes show respect for Scripture because they let readers see where evidence is strong and where the path of transmission must be reconstructed.

Academic answer

The MT of 2 Samuel 21:19 attributes the killing of Golyat haggitti to Elhanan ben-Yaare-oregim bet hallahmi. First Chronicles 20:5 has Elhanan ben-Yair striking Lahmi ahi Golyat haggitti. The correspondence suggests corruption involving the object marker, 'Lahmi,' 'brother of,' and the intrusion or duplication of 'weavers.'

The Chronicler may preserve a superior Vorlage or perform a contextual emendation based on 1 Samuel 17. Both options yield the same historical judgment with different text-historical accounts. Title theories and David-Elhanan identity lack comparative support.

08

Annotated cross-references

09

Recommended reading