Army or Host? What Joshua 24 Taught Me About Why Bible Translations Differ

I was recently working through Joshua 24 — the covenant renewal at Shechem, where Joshua gathers the tribes of Israel one last time before he dies and reminds them who God is and everything God has done for them. It’s a magnificent chapter. But two questions stopped me cold while I was reading it, and chasing down the second one taught me something I think every Christian needs to hear about why our English Bibles don’t always say the same thing.

Reading the Renewal at Shechem

Joshua 24 opens with Joshua summoning all the tribes of Israel to Shechem. He stands before them as God’s spokesman and begins reciting Israel’s history — not Joshua’s own commentary on that history, but the LORD’s own retelling of it, word for word:

“And Joshua said to all the people, ‘Thus says the LORD, the God of Israel: Your fathers lived beyond the Euphrates, Terah the father of Abraham and of Nahor, and they served other gods. Then I took your father Abraham from beyond the River and led him through all the land of Canaan, and made his offspring many. I gave him Isaac.’” — Joshua 24:2–3 (ESV)

Notice that phrase, “Thus says the LORD.” That’s a recognized formula in the Old Testament — a messenger formula. Once Joshua uses it, everything that follows for the next several verses isn’t Joshua talking. It’s God talking, with Joshua simply relaying it word for word, the way a courier reads a king’s letter aloud without adding his own commentary. That’s why you get lines like “I took your father Abraham” and “I gave him Isaac” — that’s the LORD speaking in the first person, straight through verse 13.

When God Says “I” — and Then “He”

Here’s where it gets interesting. Read verse 7 closely:

“But they cried to the LORD, and he put darkness between you and the Egyptians and made the sea come upon them and cover them, and your eyes saw what I did in Egypt. And you lived in the wilderness a long time.” — Joshua 24:7 (ESV)

In the span of one verse, the LORD refers to himself as “he” and then immediately as “I.” Same verse, same speaker, no transition, no new voice stepping into the conversation.

That’s not a contradiction, and it’s not sloppy editing. It’s a known feature of Hebrew called illeism — a speaker referring to himself in the third person. It shows up elsewhere in the Old Testament, and it’s especially common in covenant and treaty documents like this one, where the speaker recites his own past deeds almost as a matter of legal record. The pattern in verse 7 is: the divine name gets used (“they cried to the LORD”), the next clause continues that third-person reference back to the name just used (“he put darkness”), and then the verse snaps right back to first person (“what I did in Egypt”). Name, then he, then I — one speaker the entire time.

It might be tempting to read something more into that “he” — maybe a hint at the Trinity, maybe a second divine person standing alongside the first speaking in “I.” But the text itself isn’t making that distinction. Joshua 24:2–13 is one unified divine speaker, Yahweh, talking about himself in two grammatical postures within a covenant recital. The chapter doesn’t start differentiating persons of the Godhead on its own; that’s a question you can only raise by bringing later New Testament revelation to the passage — a real and worthwhile question, just not one Joshua 24 is built to answer by itself.

A Side Path to Joshua 5

That question sent me back a few chapters earlier, to a stranger Joshua actually meets face to face — the commander of the army of the LORD at Gilgal, just before the conquest of Jericho:

“And he said, ‘No; but I am the commander of the army of the LORD. Now I have come.’ And Joshua fell on his face to the earth and worshiped and said to him, ‘What does my lord say to his servant?’” — Joshua 5:14 (ESV)

This figure is different from the unified “I”/“he” of Joshua 24. He’s a distinct person Joshua can see, address, and fall down before — and Joshua is allowed to worship him, which no created angel would ever permit. Compare how an angel reacts to worship in Revelation:

“Then I fell down at his feet to worship him, but he said to me, ‘You must not do that! I am a fellow servant with you and your brothers who hold to the testimony of Jesus. Worship God.’” — Revelation 19:10 (ESV)

Some careful readers connect the commander at Gilgal to other “Angel of the LORD” appearances throughout the Old Testament, and from there to texts like John 1:18 — “No one has ever seen God; the only God, who is at the Father’s side, he has made him known” — and 1 Corinthians 10:4, where Paul says the rock that followed Israel in the wilderness “was Christ.” If those texts are right that visible, active engagement with Israel belonged especially to the eternal Son, then the commander Joshua meets at Gilgal may be a preincarnate appearance of Christ himself. That’s a real and important conversation. But it’s a different conversation from Joshua 24, where no second figure ever appears on the scene at all. I don’t want to flatten the two together — they’re answering different questions about two different texts.

What did pull me back into Joshua 5, though, was a single phrase: “the commander of the army of the LORD.” That phrase is where the real lesson of this post starts.

One Hebrew Phrase, Two English Words

“Commander of the army of the LORD” comes from a tight, three-word Hebrew construct chain: שַׂר־צְבָא־יְהוָה (sar-tseva-YHWH). Each word carries its own weight:

• שַׂר (sar) — “chief, commander, captain, ruler, official.” It’s a general word for someone in authority. Military commanders, court officials, and princes all get called this. Context decides which one is meant.
• צָבָא (tseva) — “army, host, war, military service.” This is the very same word behind the divine title “the LORD of hosts” (Yahweh Tseva’ot), and it’s used just as naturally for an ordinary human army.
• יְהוָה (YHWH) — the covenant name of God, “the LORD,” rooted in the Hebrew verb “to be” and tied to God’s self-revelation at the burning bush in Exodus 3:14.

Strung together with hyphens (called maqqephs in Hebrew, binding the words into one unit), the phrase reads literally “commander-of-army-of-YHWH” — one compact title, not three loose nouns floating next to each other.

Here’s the detail that started this whole rabbit trail: read this same verse in the King James Version, and it doesn’t say “army.” It says “host” — “I am captain of the host of the LORD.” Same Hebrew word, tseva, translated two different ways, four hundred years apart. So which translation team got it wrong?

Neither one did.

Why “Host” Became “Army”

The difference isn’t about the Hebrew at all. Both translation teams understood tseva exactly the same way — an army, a military force. The difference is about English, specifically about how much English itself has shifted in four hundred years.

In 1611, “host” was simply the everyday English word for an army. It came into English through Old French from the Latin hostis, and in Early Modern English it was the plain, ordinary term for a body of soldiers — not poetic, not archaic, not a special “Bible word.” When the King James translators hit tseva meaning “army,” “host” was just the natural English word sitting closest at hand.

By the time the ESV was translated, that word had drifted. In everyday English now, “host” mostly means someone hosting a party, a biological host, or it survives in set phrases like “a host of problems” or “heavenly host.” It’s no longer the live word anyone reaches for to describe an actual fighting force. So in a narrative scene like Joshua 5:14, where the figure standing in front of Joshua is a literal military commander, “army” communicates clearly to a modern reader, while “host” risks sounding like a leftover phrase from another century — or even slightly comic.

What I find most instructive is that the ESV doesn’t scrub “host” out of the Bible everywhere. It keeps the title “the LORD of hosts” fully intact almost everywhere it appears as a divine title — like David’s words to Goliath:

“Then David said to the Philistine, ‘You come to me with a sword and with a spear and with a javelin, but I come to you in the name of the LORD of hosts, the God of the armies of Israel, whom you have defied.’” — 1 Samuel 17:45 (ESV)

That’s because “the LORD of hosts” has become a fixed, weighty theological title — not a plain descriptive noun anymore. So the actual rule the ESV translators were applying wasn’t “modernize every old word wherever it appears.” It was something more careful: update the word when it’s functioning as an ordinary description in a narrative scene, and preserve it when it’s functioning as an established title carrying its own theological freight. That’s a deliberate decision about clarity for today’s reader. It’s not a disagreement about what the underlying Hebrew word means.

What This Means for You

If you’ve ever opened two different Bible translations side by side and felt a flicker of doubt — “wait, which one is right?” — I want you to take something specific away from this. Most of the differences you’ll find between faithful translations like the KJV, ESV, NASB, or NIV aren’t disagreements about what the Hebrew or Greek actually says. They’re decisions about how to carry an ancient word into living, current English so you understand it the way the original audience understood their own language. The men who translated tseva in 1611 and the men who translated it again four centuries later were reading the exact same Hebrew text. English moved. The meaning didn’t.

That should give you confidence, not hesitation, the next time your Bible says something slightly different from your friend’s. It’s worth doing exactly what I did here: looking up the original word, checking what it actually means, and asking why a particular translation team chose the English word they chose. You don’t need to know Hebrew to do this — free tools like Blue Letter Bible or the NET Bible’s translator notes will get you most of the way there in a few minutes.

And if you want to dig deeper into Joshua, the conquest narrative, or how to study a passage like this one for yourself, I’d genuinely love to talk with you about it. Reach out — I mean that.