Most people think this commandment is about swearing. And if that’s all it is, it’s easily the simplest of the 10 to keep. Watch your mouth in public, avoid a few words, and you’re done by breakfast.
So why does the mildest-sounding commandment come with the heaviest warning attached to it?
“You shall not take the name of the LORD your God in vain, for the LORD will not hold him guiltless who takes his name in vain.” (Exodus 20:7)
No other commandment is written like this. This one adds a sentence that sounds almost like a threat. God is signalling something serious at stake here—something more serious than careless language.
Most readers aim at the wrong target. The commandment is broader, deeper and far more uncomfortable than a rule about bad words.
What the Words Actually Say
Three words in this verse have been flattened in translation, and recovering them changes the whole commandment.
“Take” doesn’t mean “say”
The Hebrew verb is nasa. It means to lift, to carry, to bear. It’s the word used for carrying a load, lifting up a banner, or bearing a burden. It isn’t the ordinary word for speaking.
So the commandment isn’t first about pronouncing a word. It’s about carrying something. The picture behind it is a servant wearing his master’s uniform, or a soldier bearing his king’s standard into a field where everyone can see it. Israel’s high priest literally carried the names of the tribes on his shoulders and over his heart (Exodus 28:12, 29). To bear a name is to represent someone.
Old Testament scholar Carmen Joy Imes has argued this case at length in her study of the commandment. Her point: Israel was given God’s name in the way a nation is given a flag. The commandment isn’t chiefly “do not say it carelessly”. It is closer to “do not carry it emptily”.
“In vain” means empty, worthless, false
The Hebrew word is shav. It covers emptiness, nothingness, worthlessness and falsehood all at once. English has no single word for it.
Notice where else it appears. In the Deuteronomy version of the 9th commandment, the false witness gives shav testimony (Deuteronomy 5:20). The same word links the misuse of God’s name to lying in court—which is a strong hint about what the 3rd commandment is mainly aimed at.
What’s a “name” in the Bible?
In modern English a name is a label. It tells people what to call you and very little else.
In Hebrew thought a name is much closer to a reputation and a revealed character. When God changes someone’s name in Scripture, He’s changing what they are. When Scripture says people “called on the name of the LORD”, it doesn’t mean they pronounced a syllable; it means they appealed to everything He had shown Himself to be.
God gave His name at the burning bush—“I AM WHO I AM” (Exodus 3:14)—and then unfolded what it meant at Sinai: merciful, gracious, slow to anger, abounding in steadfast love, and by no means clearing the guilty (Exodus 34:6–7).
So “the name of the LORD” is shorthand for God’s self-disclosure and public reputation. That’s what this commandment protects.
It’s worth asking why God gave a name at all. In the ancient world, knowing a god’s name was thought to give you leverage over him. Names were used in incantations and spells precisely because a name was a handle—something you could take hold of to make a deity act. Against that background, the burning bush is remarkable. God gives His name, and the name He gives is “I AM WHO I AM”—a name that grants access while refusing every attempt at control.
That’s the gift the 3rd commandment protects. God made Himself available to be called upon, and He did it without making Himself manageable. Misusing the name is therefore an attempt to take back the leverage He declined to give—to make His authority serve our purposes after all.
Put the three together and the commandment reads something like this: do not lift up, carry or invoke the revealed character of God for empty, false or worthless purposes. That’s a far wider net than a rule about exclamations.
Why Does This Commandment Come Third?
The order of the first table isn’t accidental, as we argued in the introduction to this series.
| COMMANDMENT | THE QUESTION IT SETTLES | WHAT IT PROTECTS |
|---|---|---|
| First | Whom do we worship? | The true God, against rivals |
| Second | How do we worship? | The true God, against our inventions |
| Third | By what name do we invoke Him? | The true God, against our misuse of His reputation |
| Fourth | When do we come to Him? | The true God, against a life with no room for Him |
There’s a logic here that’s worth sitting with. God’s name isn’t something we discovered. He gave it. He didn’t have to. He gave it so people could call on Him. And appeal to Him.
That makes misuse of the name a particular kind of ugliness. It’s not a stranger being rude about someone. It’s taking a gift that was handed to you lovingly, and using it for something cheap.
Four Ways This Commandment Is Broken
Here is where the commandment stops being comfortable. The four rise in seriousness, and most sermons stop at the first.
| WHAT IT LOOKS LIKE | WHY IT’S A BREACH | |
|---|---|---|
| Empty speech | Using “God”, “Lord” or “Jesus” as filler, shock or punctuation, meaning nothing by it | The name is being lifted up for no purpose at all—the plainest meaning of shav |
| False oaths | Swearing by God’s name and lying; making promises in His name with no intention of keeping them | “You shall not swear by my name falsely, and so profane the name of your God” (Leviticus 19:12) |
| False claims about God | Saying “God told me”, “God wants this”, “God is on our side” when He has said no such thing | Speaking presumptuously in God’s name was a capital offence in Israel (Deuteronomy 18:20) |
| Carrying the name badly | Bearing the name “Christian” while living in a way that contradicts it | “The name of God is blasphemed among the Gentiles because of you” (Romans 2:24) |
Why false oaths mattered so much
The 2nd row can look old-fashioned to modern readers, so it helps to understand how much weight it carried.
In the ancient world there were no identity documents, no notaries, no filing systems and, for most people, no written contracts. Land boundaries, debts, marriages, inheritance disputes and criminal trials were all settled by human testimony. And what secured the testimony was an oath sworn in a god’s name, on the understanding that the god would deal with anyone who lied.
That means the divine name wasn’t a religious ornament sitting off to one side of society. It was the load-bearing beam under the whole justice system. Remove the fear of swearing falsely and courts stop working, property becomes whatever the strongest man says it is, and no agreement can be relied on.
Douglas Stuart notes in his commentary on Exodus that this is why the commandment sits in the 1st table rather than the 2nd, even though its effects are so obviously social.
The one nobody preaches about
The third row deserves its own paragraph, because it’s arguably the commonest serious breach of this commandment in the modern church. And it’s seldom ever named as such.
God takes an extraordinarily severe view of people who attach His name to their own opinions. Jeremiah spends a whole chapter on it. The prophets, God says, prophesy in His name; He didn’t send them, He didn’t speak to them, and they say “declares the LORD” anyway (Jeremiah 23:21, 31). The offence isn’t that they were wrong about the future. It’s that they made God the author of something He never said.
The modern versions are easy to list. And uncomfortable to read.
- A preacher who claims divine authority for his own preferences.
- A leader who tells a congregation God has revealed something that conveniently aligns with his own plans.
- A movement that attaches “God’s will” to a political programme.
- A person who ends an argument with “the Lord laid it on my heart”, knowing it can’t be questioned.
Kevin DeYoung has observed that this commandment is broken far more often in churches than in bars. The people most likely to invoke God’s name are the people most likely to invoke it emptily.
The one that lasts all week
The fourth row is where nasa—carrying—pays off completely.
Ezekiel records God’s complaint about His exiled people: wherever they went among the nations, they profaned His holy name, because people looked at them and drew conclusions about Him (Ezekiel 36:20–23). Israel did nothing verbal to earn this. They simply carried the name badly.
If you’re a Christian, you’re a name-carrier. You’re wearing the uniform in office, and while stuck in traffic, caught in a family argument, or responding to rudeness in the comment section. Michael Horton points out this makes the 3rd commandment the most public of the 10—it’s broken in front of an audience, even by people who’re not saying anything about God at all.
This also explains something Christians often find painful. Ask people why they reject Christianity and a great many won’t name a doctrine. They’ll likely name a Christian—or a church, or a scandal. That isn’t a shallow objection to brush aside. It’s the 3rd commandment stating its own case. God warned His reputation would travel through the conduct of the people who bear His name. And it does.
The right response is neither defensiveness nor despair. It is to take seriously the name we carry isn’t ours to spend.
Why the Warning Attached?
“The LORD will not hold him guiltless.” Why here, and not on any of the other 9?
Two reasons seem right.
First, because the name is all we have. We don’t see God. We have His name—His revealed character, the thing we call on. The name we love, trust, pray to. And tell others about. Empty the name and we don’t damage a doctrine; we damage the bridge. Philip Ryken puts the matter plainly in his work on Exodus: to abuse the name is to attack God at exactly the point where He has made Himself available.
Second, because no human court can settle the damage. Murder leaves a body. Theft leaves a loss. This sin leaves nothing any human can prosecute. And it doesn’t leave a visible victim. So God announces He will handle this one Himself. The warning isn’t disproportionate. It’s filling a gap human justice cannot reach.
Does This Forbid All Oaths?
Jesus said something on this subject that sounds absolute: “Do not take an oath at all” (Matthew 5:34). Some Christians conclude believers should never swear—in a courtroom, in the armed forces, at a wedding.
That’s not what He meant, and the rest of Scripture makes the case.
Why Reformed churches allow lawful oaths
God swears. “Since he had no one greater by whom to swear, he swore by himself” (Hebrews 6:13). Whatever Jesus was forbidding, He wasn’t forbidding something His Father does.
Paul swears. He calls God as his witness more than once (Romans 1:9; 2 Corinthians 1:23). He wasn’t disobeying his Lord in the same letters where he preaches Him.
The law commanded it. Israel was told to swear by God’s name (Deuteronomy 6:13)—truthfully, which is exactly the point.
Context explains the prohibition. In Jesus’ day people swore by heaven, by earth, by Jerusalem and by their own head, building a ladder of oaths where some were binding and some were technically escapable. Read Matthew 23:16–22 and you can see the system working.
His actual demand is higher, not lower: “Let what you say be simply Yes or No” (Matthew 5:37). A person whose word is reliable doesn’t need to reinforce it.
So a Christian may take an oath in court or on entering office—soberly, rarely, and only about things that are true. What’s forbidden is the casual oath, the decorative oath, or the oath that isn’t meant.
A Word About Bad Language
Coarse language is a real issue in Scripture, but it isn’t mainly this commandment’s issue. Paul addresses crude and filthy talk in Ephesians 4:29 and 5:4, but he does so on different grounds: such speech doesn’t build anyone up, and it doesn’t fit people who belong to God.
That gives us a useful distinction. A crude word that has nothing to do with God is a matter of Christian speech, and it isn’t trivial. But “Oh my God” used as an exclamation of surprise—by a Christian, about nothing—is a breach of the third commandment, however mild it sounds and however universally it’s said. The name is being lifted up for nothing. That’s the definition.
We’re not recommending that anyone become the person who polices this in conversation. We’re recommending we notice it in our own mouth.
What the Commandment Requires
Following the rule that governs this whole series: where a sin is forbidden, the opposite duty is commanded.
| WHAT IT FORBIDS | WHAT IT THEREFORE REQUIRES |
|---|---|
| Empty use of God’s name | Reverent use of it—in prayer, praise, blessing and confession |
| False oaths and broken vows | Truthfulness so ordinary that oaths become unnecessary |
| Claiming God’s authority for our own views | Careful, accurate speech about God, and honesty about what we do not know |
| Living in a way that discredits the name | Living so that people think better of God because of us |
| Silence when the name is treated as nothing | Honouring the name publicly, in ordinary company |
| Indifference to how God is spoken of | Praying “hallowed be your name” and meaning it |
That last row is worth noticing. When Jesus taught His disciples to pray, the very first request was about the third commandment. Not our needs. Not even God’s kingdom. The first petition is that God’s name would be treated as holy (Matthew 6:9). The third commandment isn’t merely a rule to obey; it’s something we’re told to ask God to accomplish.
The One Who Carried the Name Perfectly
Everything in this commandment converges on Jesus, and in a way that is easy to miss.
He said, near the end of His life, “I have manifested your name to the people whom you gave me out of the world” (John 17:6). That’s the third commandment kept positively—a life that carried God’s reputation and left it enhanced rather than emptied.
And then the reversal. At His trial, the high priest tore his robes and declared, “He has uttered blasphemy” (Matthew 26:65). The one man in history who never took God’s name in vain was condemned to death for exactly that offence, by the men whose job it was to protect the name.
Paul draws the conclusion in Philippians: because of His obedience, God gave Him the name above every name, at which every knee will bow, to the glory of God the Father (Philippians 2:9–11). The commandment that guards God’s name ends by pointing to a Person who is the name.
How This Commandment Is Actually Kept
Not by editing your vocabulary, though that may follow.
Every Christian was baptised into the name of the Father, Son and Holy Spirit (Matthew 28:19). That isn’t decorative language. It means the name has been placed on us, the way a family name is placed on a child. We will carry it today whether we’re aware of it or not.
So the question this commandment asks isn’t “what did you say?” but “what does your life say about the God whose name you wear?” Sinclair Ferguson note we tend to think of holiness as private, when Scripture keeps treating it as advertising. People who will never read a Bible will form a view of God this week, and some of them will form it by watching us.
That’s a heavy thought. It should be. It is also why the commandment ends in prayer rather than in effort. Hallowed be your name—in the world, in the church, and in me.
Next in this series: the fourth commandment, and the hardest question in the Decalogue for Christians—what happened to the Sabbath?
Tough Questions, Honest Answers
Are substitutes like “gosh”, “jeez” or “gee” still breaking the commandment?
These are called minced oaths—words invented precisely so people could express the feeling without saying the name. “Gosh” stands in for God, “jeez” for Jesus, “crikey” for Christ. Because the name itself isn’t spoken, we assume they don’t fall under the commandment in the direct way that “Oh my God” does. And Christians of good conscience use them without difficulty. The honest question is what’s happening in the heart, since a substitute chosen to carry the same force is doing much the same work.
Why do Jews write “G-d” and avoid pronouncing the divine name? Should Christians do the same?
The practice comes from a deep reverence for the third commandment: rather than risk misusing the name, Jewish tradition substitutes Adonai (“Lord”) or HaShem (“the Name”) when reading aloud, and avoids writing the name where it might be erased or discarded. That’s why most English Bibles print “LORD” in capital letters wherever the Hebrew has the divine name—the convention is inherited from that reverence. Christians aren’t bound to the practice, and the New Testament shows the apostles speaking and writing the name of Jesus constantly and publicly. But the instinct behind it deserves respect rather than amusement. A church that has grown casual about the name could learn something from people who haven’t.
Should Christians say “Yahweh” or “Jehovah”?
The Hebrew text preserves four consonants, often written YHWH, without the vowels, since Hebrew was originally written without them. “Jehovah” arose in the Middle Ages by combining those consonants with the vowels of Adonai, the word readers substituted aloud—so it is a hybrid rather than a pronunciation anyone ever used. “Yahweh” is most scholars’ best reconstruction, though it remains a reconstruction. Neither form is forbidden, and no blessing attaches to getting the syllables right. Notice the apostles, writing in Greek, simply used Kyrios, “Lord”, and the New Testament doesn’t treat the exact pronunciation as a matter of obedience.
What is blasphemy, and is it the unforgivable sin?
Blasphemy means speech that insults, mocks or falsely represents God, and it is the extreme end of what this commandment forbids. The passage that troubles people is Jesus’ warning that blasphemy against the Holy Spirit will not be forgiven (Mark 3:28–30). Read in context, He says this to men who were watching Him cast out demons and attributing His work to Satan—a settled, knowing, hardened rejection of the Spirit’s testimony, not a moment of anger or a season of doubt. The Reformed answer to anyone frightened they’ve committed it is straightforward: the person who fears this sin has not committed it, because those who have are precisely those who do not care.
Is bad language a sin even when God’s name isn’t involved?
Yes, though on different grounds than this commandment. Paul tells the Ephesians to let no corrupting talk come out of their mouths, but only what builds up and gives grace to those who hear (Ephesians 4:29), and he lists filthy and crude talk as out of place for God’s people (Ephesians 5:4). The test he gives is useful because it is not a word list: does this speech build anyone up? That means the same word can be lazy contempt in one mouth and an honest expression of horror in another, and it also means cruelty in perfectly polite language is the greater problem. Cultures differ sharply on which words are coarse, so charity is needed both ways.
If I made a promise to God and broke it, have I taken His name in vain?
If the promise was made rashly or was never seriously meant, then yes—that is close to the heart of what this commandment forbids. Ecclesiastes puts it bluntly: when you make a vow to God, do not delay in fulfilling it, and it is better not to vow than to vow and not pay (Ecclesiastes 5:4–5). But there is a second half to the answer that many anxious Christians need. Some vows should never have been made, and keeping a sinful or reckless promise compounds the fault rather than repairing it—Jephthah’s vow in Judges 11 is Scripture’s warning, not its model. The right response to a broken vow is confession, not despair. And the right response to the pattern is to stop making them: let our yes be yes.
Is it wrong to use God’s name in comedy, film or fiction?
A novel or a film that portrays a character misusing God’s name isn’t itself breaking the commandment, any more than a novel depicting a theft is stealing. Scripture reports blasphemy without committing it. The distinction is between depicting and endorsing—between showing how people speak and inviting the audience to join in the contempt. Where it becomes a real question is for Christians who write and perform, and there the test is whether the name is being lifted up for something, or for nothing. As for what to watch, this is an area where believers will judge differently, and it is worth deciding thoughtfully rather than drifting.
CONTINUE THE SERIES: THE TEN COMMANDMENTS
This post is part of our series working through the Ten Commandments. It follows Why God Gave the 10 Commandments—And Why These 10?, The First Commandment: Why Does God Demand Exclusive Worship?, and The Second Commandment: Why Does God Forbid Idols?.
Related Reads
- Why God Gave the 10 Commandments—And Why These 10?
- The First Commandment: Why Does God Demand Exclusive Worship?
- The Second Commandment: Why Does God Forbid Idols?
- Why Is God Jealous? Does That Make Him Evil?
- The Unpardonable Sin: What Is the Blasphemy Against the Spirit?
- Freemasonry and Christianity: Are They Compatible?
