The 6th Commandment Translation Error Nobody Talks About

Watch

The 6th Commandment Translation Error Nobody Talks About

Open almost any English Bible and the Sixth Commandment looks like the shortest rule ever written: "Thou shalt not kill." Four words, no fine print. And for centuries, readers kept running into a paradox that would not go away. The same book that forbids killing also sends soldiers to war and describes people defending their homes at night. If all killing is banned, why does the rest of the story keep allowing it? Theologians argued about this for generations, and the debate dragged on and on. The uncomfortable answer is that the English translation is the problem, not the rule itself.

Ancient Hebrew is much more precise here. It has a separate word for each kind of taking a life, the way a modern legal code separates arson from an accident. The broad, everyday word is harag. It simply means to kill in general -- and the ancient texts use it for a soldier on a battlefield or a homeowner who strikes a nighttime intruder. And here is the part most people never heard: killing in justified defense or in war was called harag and carried zero bloodguilt. Bloodguilt is the old legal idea of being guilty for shed blood, the thing that makes a community owe a life for a life. Harag in a just case leaves you clean. You are not a murderer, and no debt is attached to you.

The Sixth Commandment never uses that word. It bans retzach: the intentional, unjust killing of an innocent life. That is a different verb with a completely different moral weight. An ambush, a revenge attack, the strong destroying the weak out of greed or rage -- that is retzach, and only that is what the commandment forbids. So the famous rule is not a blanket ban on force at all. It is the oldest protection of innocent life in the book, written in the sharpest legal language available.

Why did the mistranslation matter so much? Because one blurred word created endless debate around self-defense and soldiers in warfare. Whole arguments about pacifism, about whether a person may fight back at all, were built on a translation choice instead of on the original distinction. Restore the two verbs and the paradox dissolves on the spot: defense is never murder. The commandment bans the murder of the innocent and stays completely silent about justified defense, because in the original language those two things were never the same word. One short prefix of a letter changed a whole conversation for centuries. The fix is simple: read it as "Thou shalt not murder," and the shortest commandment suddenly makes complete sense.

The short version

FAQ

So does the Sixth Commandment forbid soldiers to fight or people to defend themselves?

No. The commandment bans retzach, the intentional unjust killing of an innocent person. General taking of life in justified defense or in war is a different word, harag, and it carried zero bloodguilt. The centuries of debate around self-defense and warfare came from the blurred translation, not from the original rule.

What exactly is bloodguilt?

Bloodguilt is the ancient legal idea of guilt for shed blood -- the status of someone who owes a life for a life. The Hebrew texts apply it to murder, not to justified killing. That is why the description of defense says it carried zero bloodguilt: acting to stop an unjust attack left a person legally clean.

If the original is so precise, why did the wrong wording stick?

Because the broad English verb "kill" looks simpler and shorter, and early translations froze it in place. Once the wording was printed for centuries, the debate attached itself to the English text. The original Hebrew distinction between harag and retzach never changed -- only the translation did, and that is the error nobody talks about.

Watch on YouTube →