David and Goliath: Did Elhanan Really Kill Goliath?
Short answer: 1 Samuel 17 presents David, the youngest son of Jesse, defeating the Philistine champion Goliath in the valley of Elah, and the rest of Scripture treats that victory as David's. 2 Samuel 21:19, in the World English Bible, reads that Elhanan the son of Jaare-Oregim the Bethlehemite killed Goliath the Gittite, the staff of whose spear was like a weaver's beam. The most widely accepted resolution is that the Hebrew text of 2 Samuel 21:19 has suffered a scribal corruption, and that the parallel in 1 Chronicles 20:5 preserves the better reading: Elhanan killed Lahmi, the brother of Goliath. Either way, the Bible does not present two different men killing the same giant in the same battle.
What 1 Samuel 17 Actually Narrates
1 Samuel 17 opens with the Philistines gathered at Socoh, which belongs to Judah, and encamped between Socoh and Azekah, in Ephesdammim, while Saul and Israel camped in the valley of Elah. The narrative is unhurried. It gives geography, troop movements, and the daily routine of a champion who came out morning and evening for forty days. This is not a legend told in a single sentence. It is a sustained account with named places, named armies, and a named Israelite king. The chapter is written as history, and it expects to be read as history.
The account also gives Goliath's equipment in detail: a bronze helmet, a coat of scale armor weighing five thousand shekels of bronze, bronze greaves, a bronze javelin, and a spear whose staff was like a weaver's beam with an iron spearhead of six hundred shekels. That kind of specificity is not how ancient storytellers invented a monster. It is how a battlefield report remembers a real opponent. The chapter is interested in the actual size of the threat, because the size of the threat measures the courage of the boy who faced it and the God who delivered him.
The central dialogue is theological before it is military. Goliath defied the armies of the living God; David answered that the battle is Yahweh's, and that all the assembly would know that Yahweh does not save by sword or by spear. David refused Saul's armor, took five smooth stones and his sling, and ran toward the battle line. He struck the Philistine on the forehead, the stone sank in, and Goliath fell face down on the ground. David then cut off his head with Goliath's own sword. The narrative is emphatic that this was David's act.
The aftermath matters for the question at hand. David took Goliath's head to Jerusalem and put his armor in his own tent. Later, in 1 Samuel 21:9, the priest at Nob says to David, as the World English Bible renders it, that the sword of Goliath the Philistine, whom you killed in the valley of Elah, was there wrapped in a cloth behind the ephod. That verse is a direct, independent, later reference inside Scripture to David as the one who killed Goliath. The Bible itself interprets 1 Samuel 17 as David's victory.
What 2 Samuel 21:19 Says, and What It Does Not Say
2 Samuel 21 is a summary of four battles with Philistine descendants of the giant, set in David's later reign. In the first, David grew faint and Abishai rescued him, and David's men swore he would not go out to battle again. The section then lists Sibbecai killing Saph, Elhanan killing Goliath the Gittite, and Jonathan the son of Shimei killing a man with six fingers on each hand and six toes on each foot. The chapter is a roster of individual combat victories, not a retelling of the Elah valley.
The problem is plain. 2 Samuel 21:19 as it stands in the Masoretic text attributes the killing of Goliath the Gittite to Elhanan. If this were the only verse in the Bible about Goliath, no one would see a difficulty. The difficulty arises because 1 Samuel 17, 1 Samuel 21:9, and the whole David tradition say otherwise. A careful reader should notice that the tension is created by one verse, not by two competing narratives of equal weight. The burden of explanation falls on the single difficult line.
Several features of the verse itself are telling. It describes the staff of the Philistine's spear as being like a weaver's beam - the same distinctive detail applied to Goliath in 1 Samuel 17. It also identifies the man as Goliath the Gittite, using the same ethnic label. It is as if the text wants us to recognize this figure as Goliath. But the presence of that same spear detail in a later battle is exactly what the Chronicler's parallel handles differently, and that difference is the key to the whole discussion.
Nothing in 2 Samuel 21:19 describes a valley, a champion's challenge, a forty-day standoff, Saul, or David as a youth. It describes a skirmish in a later war, during David's reign, when David was already king and already faint with exhaustion. Whatever else this verse is, it is not a second account of the Elah valley. Reading it as a rival version of 1 Samuel 17 requires importing details the verse does not contain and ignoring the setting it plainly gives.
The Chronicler's Parallel: Lahmi, Brother of Goliath
1 Chronicles 20:4-8 covers the same four Philistine battles. In the World English Bible, 1 Chronicles 20:5 reads that Elhanan the son of Jair killed Lahmi the brother of Goliath the Gittite, the staff of whose spear was like a weaver's beam. The Chronicler is clearly parallel to 2 Samuel 21, using the same spear image, the same setting, and the same warrior names. But where 2 Samuel has Elhanan killing Goliath, Chronicles has Elhanan killing Lahmi the brother of Goliath.
This is the strongest single piece of evidence available. Two Hebrew accounts of the same events differ at exactly one point, and one of them explicitly removes the contradiction with 1 Samuel 17 by naming a different man, Lahmi, and identifying him as Goliath's brother. If Chronicles preserves the earlier or better reading, then 2 Samuel 21:19 has lost a word or two in copying. The two verses are not two traditions; one is a damaged copy of the other.
Scribal corruption of this kind is well attested in the transmission of the Hebrew Bible. Letters that look alike get confused, words get dropped when a copyist's eye jumps to a similar word nearby, and a line can lose a short phrase. The Hebrew of 2 Samuel 21:19 is widely judged to be difficult, and the standard scholarly proposal is that the original read something like Elhanan son of Jair killed Lahmi, the brother of Goliath the Gittite, and that a copyist's error dropped the words for brother and Lahmi, leaving the sentence as we now have it.
This explanation does not require treating Scripture as unreliable. It requires recognizing that the Bible has been copied by hand for centuries, that the Masoretic text is a carefully preserved but not a magically perfect copy, and that God in his providence gave us the parallel account in Chronicles as a control. The honest position is that 2 Samuel 21:19 as it stands is a textual problem, and that 1 Chronicles 20:5 gives us the most likely original sense. Christians who hold a high view of Scripture can say this without embarrassment.
Did David Kill Goliath, or Did Elhanan?
The Bible's answer to the identity of Goliath's killer is consistent and repeated. 1 Samuel 17 is devoted to the account. 1 Samuel 21:9 refers back to David as the one who killed Goliath in the valley of Elah. 1 Samuel 17 also preserves the song of the women of Israel, which credited Saul with thousands and David with ten thousands, and that song became proverbial. The rest of the Old Testament simply assumes David killed the giant.
Even 2 Samuel itself, in the chapters around our problem verse, never contradicts the David tradition. 2 Samuel 22, David's song of deliverance, speaks of Yahweh as his rock and deliverer, the God who trained his hands for war. The whole arc of David's rise presupposes the Elah valley. If Elhanan had killed Goliath and David had not, the most famous story in Israel's memory would be misattributed, and the writers of Samuel, who are not shy about recording David's failures, would have had no reason to hide it.
It is also worth noticing what 2 Samuel 21:19 does not claim. It does not say Elhanan killed Goliath in the valley of Elah. It does not say Elhanan killed him as a youth, or with a sling, or in a challenge that decided a war. It places the deed in a later campaign, under David's kingship, and the man is tagged as a Gittite with a huge spear, which is exactly how the Elah Goliath is described. The overlap of description, not of event, is what creates the confusion.
A faithful reader can therefore say with confidence: David killed Goliath in 1 Samuel 17. Whether 2 Samuel 21:19 originally said the same thing through a copying error, or whether it named Lahmi the brother of Goliath as Chronicles has it, no part of Scripture teaches that Elhanan killed the Goliath of the Elah valley. The apparent contradiction is real on the surface of the Masoretic text, and it has a documented, non-destructive resolution.
How Ancient Copyists Created - and Preserved - This Reading
Before printing, every copy of Scripture was made by hand. Copyists worked from manuscripts, in low light, over long hours, and the Hebrew letters for brother and for the name Lahmi could be lost if the eye skipped from one similar word to the next. This is called haplography, and it happens in every manuscript tradition. The existence of such a slip does not mean the scribes were careless; it means they were human, and it means God preserved his word through a process that includes the later correction we see in Chronicles.
The Masoretic scribes who standardized the Hebrew text also preserved marginal notes called tiqqun sopherim, recording places where earlier scribes had altered the text. They were not hiding problems; they were cataloguing them. This instinct is important. The same community that copied the text also flagged its difficulties. The church inherits both: a text to be read carefully and a tradition of honest attention to its hard places.
It is also significant that the ancient translations show awareness of the problem. The Septuagint, the Greek translation of the Hebrew Scriptures, handles 2 Samuel 21:19 in a way that reflects the same difficulty, and some witnesses read the name in a form that preserves the brother relationship. The translators were working with a Hebrew text that already had the awkward line, and they wrestled with it. This is not a modern discovery invented by skeptics.
For the reader today, the practical upshot is that the Bible we have is trustworthy in its teaching while the manuscript tradition has small, identifiable rough spots. We do not need to pretend the rough spots are not there, and we do not need to abandon the text because they are. We can do what the church has always done: compare Scripture with Scripture, prefer the reading that fits the whole canon, and keep reading. The David-and-Goliath account is not threatened by a scribal slip in a list of battles.
Why This Question Keeps Coming Back
The Elhanan problem is a favorite of skeptics because it looks like a clean contradiction on the surface: two names, one giant, one deed. It is also a favorite test case for believers because it forces a decision about how to handle difficult texts. Do we ignore the verse, explain it away with a strained harmonization, or look honestly at the Hebrew, the Greek, and the parallel in Chronicles? The third option is the only one that honors both the text and the reader.
There is also a spiritual reason the question recurs. The David story is beloved precisely because it is a picture of the weak defeating the strong, the shepherd boy facing the armored giant, the future king hidden in a field. If the story were suddenly reassigned to a minor warrior named Elhanan, something would be lost - not just a fact, but a pattern. The Bible's use of David as a type of Christ, the anointed one who defeats the enemy on behalf of his people, depends on David being the one who stood in the valley.
Different faithful Christians weigh the evidence differently. Some are convinced the text should be read as it stands and that the difficulty is unresolved, though they still see no threat to the doctrine of Scripture. Others accept the haplography explanation as probable. Still others point to the Chronicler as decisive and treat 2 Samuel 21:19 as a corrupted copy. These are differences about textual criticism, not about the gospel, and Christians should extend charity where the evidence is not absolute.
What is not a legitimate option is pretending there is no problem or dismissing anyone who raises it as an enemy of the faith. The Bible itself gives us the parallel in Chronicles, and it gives us a community that has always paid attention to such things. The right posture is confidence joined to honesty: confident that Scripture's central claims stand, and honest that this verse requires care. That posture is what makes a Bible teacher worth listening to.
What This Episode Teaches About God
The theological center of 1 Samuel 17 is not the sling and not the stone. It is David's words before the fight, that the battle is Yahweh's and that he saves not by sword or spear. Goliath trusted his armor and his size. Israel trusted their king and their formation, and both failed them. David trusted the name of Yahweh of Armies, the God of the armies of Israel, whom Goliath had defied. The whole story is constructed to put human strength in the wrong column and God's deliverance in the right one.
That theme is not disturbed by the Elhanan question. If anything, the later battles in 2 Samuel 21 reinforce it. There David grows faint and needs Abishai to rescue him. The giant-killers of that chapter are named men like Sibbecai and Elhanan, ordinary soldiers doing their work under David's reign. The point of the section is that the Philistine threat, including the remnant of the giants, was subdued, not by one hero forever, but by Yahweh giving victories through many hands. David's own strength failed, and God carried the kingdom anyway.
This is why the New Testament can take up the David pattern without hesitation. Jesus is the son of David who faces the enemy alone, who is struck and falls and rises, and who wins a victory his people receive rather than achieve. The shadow of the shepherd boy in the valley is not diminished if a later soldier named Elhanan killed a different giant, or even if a copyist's error confused the names. The pattern stands because God established it, not because every line of every battle list came through the copying process without a scar.
So the pastoral application is not complicated. Read 1 Samuel 17 as what it claims to be: the account of how Yahweh delivered Israel through David. Read 2 Samuel 21 with 1 Chronicles 20 beside it, and note that the Chronicler names Lahmi, the brother of Goliath. Do not build your faith on the absence of difficulties, and do not lose it over one. Build it on the God who does not save by sword or spear, and who has preserved for us, through a human and sometimes messy process, everything we need for faith and life.
Biblical fidelity check
The passage establishes that David, the son of Jesse, defeated the Philistine champion in the valley of Elah, that he did so in the name of Yahweh, and that Israel credited the victory to him. It does not establish that 2 Samuel 21:19 is free of textual difficulty, and it does not require us to treat the Masoretic reading as beyond question. 1 Chronicles 20:5 gives a parallel that names Lahmi the brother of Goliath, and honest readers must reckon with that parallel rather than ignore it.
A common misreading runs like this: since 2 Samuel 21:19 says Elhanan killed Goliath, the Bible contradicts itself and the David story is legend. This is wrong on two counts. First, it treats one difficult verse as decisive over an entire narrative, a direct later reference in 1 Samuel 21:9, and a parallel account in Chronicles. Second, it assumes that a copying error proves the event did not happen, which does not follow. The faithful reading honors the whole canon, prefers the reading that fits it, and leaves room for Christians to differ on the details of the textual solution.
Other passages that speak to 1 Samuel 17:1-58
The wider story of David's reign and the battles that followed Elah is told across several connected passages. 2 Samuel 7:12-16 Prophecy: Will David’s Throne Last Forever? shows what God promised the shepherd who killed the giant. 2 Samuel Bible Study Guide: David’s Kingdom, Sin, and the Promise of Christ traces the rest of his reign, including the Philistine wars of 2 Samuel 21. 1 Chronicles 10: Saul's Death and the Kingdom Given to David explains how the kingdom passed from Saul to David. And 1 Chronicles 1: Adam to Edom's Chiefs sets the genealogical context for the Chronicler's later account of the same battles.
Frequently asked questions
Did Elhanan kill Goliath?
As the Masoretic text of 2 Samuel 21:19 stands, it says Elhanan killed Goliath the Gittite. Most conservative and critical scholars alike judge this to be a scribal corruption, because 1 Chronicles 20:5 records the same battle and says Elhanan killed Lahmi the brother of Goliath, and because 1 Samuel 17 and 1 Samuel 21:9 both credit David with killing Goliath in the valley of Elah. The likely original reading named Lahmi, and a copyist's eye skipped the words for brother and Lahmi.
Does this contradiction undermine the Bible's reliability?
It does not, though it does require honesty. A copying error in one verse is not the same as a false teaching. The doctrine of Scripture concerns what God has spoken and what the Bible teaches; it does not claim that every later copy is flawless. The presence of a recognized textual problem, with a parallel that preserves the better reading, is exactly the kind of thing careful readers expect in a book copied by hand for centuries. The central claims of 1 Samuel 17 remain intact.
Who was Lahmi in the Bible?
Lahmi appears only in 1 Chronicles 20:5, where he is called the brother of Goliath the Gittite, and where Elhanan the son of Jair kills him. He is one of several Philistines described as descendants of the giant in that section, alongside Sippai and the man with six fingers and six toes. His brief mention matters because it supplies the name that the corrupted reading in 2 Samuel 21:19 appears to have lost, resolving the apparent contradiction with the David story.