God or Father? Why FHB Reveals the Name Behind 'God'

By Kevin White — founder of Spirit Media Publishing and lead steward of the Father's Heart Bible. Updated June 12, 2026.

Pick up almost any English Bible and three letters do nearly all the heavy lifting for the divine: G-o-d. So when a reader opens the Father's Heart Bible and finds that 'our Father' created the heavens and the earth starting at Genesis 1:1, where earlier Bibles read 'God,' the honest question is — did FHB add something to Scripture? The answer is no. The Hebrew and Greek behind the page were never that flat. They carry distinct names for God, and those names fall on different lips for different reasons. For the first time in English, FHB lets you see on the page which references mean the personal, covenant God who calls Himself our Father, and which mean the generic word for deity. The distinction was always there. We simply stopped hiding it.

Key takeaway: The original languages never used one flat word for God — Hebrew distinguished the personal covenant name (YHWH, "I AM") from the generic word for deity (Elohim). FHB makes that visible, reading "our Father" where the text means the personal, covenant God.

Jump to: Why 'our Father' · What the translations pointed to · Job's turning point · The apostles did it first · The names that answer belonging

Why FHB Renders God as Our Father

FHB renders the personal references to God as 'our Father' because the original languages used more than one name, and they were never interchangeable. Elohim is the generic, plural-form word for deity — the Mighty One, the word you could use of any god. YHWH is the personal covenant name, the self-given 'I AM' God speaks over Himself at the burning bush. One is a category; the other is an introduction. Where the text reaches for that covenant name, FHB lets the Person be seen as our Father rather than hiding Him inside a word that could mean any deity at all.

You can hear the difference in Scripture's own pages. The personal name is self-given and relational: at the burning bush God answers, 'I AM WHO I AM' (Exodus 3:14) — an introduction, not a label. The generic word, Elohim, can name the true God or, grammatically, any god at all. So FHB asks one reverent question of every divine reference: is the text reaching for the category, or for the covenant? Where it reaches for the covenant Person, we read 'our Father' — interpretation made visible, not invention.

Glimpses of the Father Across Scripture

And once you see it, you see it everywhere. The covenant name carries the Father's heart from Genesis to the Prophets:

• Our Father forms the man from the dust (Genesis 2:7).
• He tells Moses, 'I did not make myself known to them by my name as Father' (Exodus 6:3).
• He proclaims His own heart as 'compassionate and gracious, slow to anger' (Exodus 34:6).
• He is confessed in the Shema, 'our Father is one' (Deuteronomy 6:4).
• He is named by runaway Hagar, 'my Father who sees me' (Genesis 16:13).
• He provides on the mountain as 'The Father Will Provide' (Genesis 22:14).
• He wins Carmel as the people fall and cry, 'Our Father, he is God!' (1 Kings 18:39).

In every one, earlier Bibles print 'the LORD' — and the Hebrew underneath is the personal covenant name.

The scale of it is striking. In most English Bibles the personal name stands behind 'the LORD' some 6,500 times — more often than the word 'God' itself (about 4,300 times in the King James). The Father's Heart Bible renders that same covenant name 'our Father' in nearly all of them — close to 6,500 times — while reserving plain 'God' for only the few hundred places the text truly means the generic deity. Where other Bibles hand you a title thousands of times, FHB hands you the Father.

Why the Father in Genesis 1 — and Not the Son or the Spirit?

It is the question that has to be asked first: if the covenant name belongs to a Person of the Trinity, why read it as the Father rather than the Son or the Spirit? Genesis 1 answers on its own terms. The Spirit is already named where the text marks Him — 'the Spirit of our Father was hovering over the surface of the waters' (Genesis 1:2) — and when the divine counsel speaks in the plural, FHB names the whole Trinity: humanity is made 'in the image of the Father, Son, and Holy Spirit' (Genesis 1:27). FHB identifies the Son and the Spirit precisely where Scripture establishes their presence. But the commanding, creating voice — 'Let there be light' (Genesis 1:3) — belongs to the One the others are sent by.

And that is the deciding clue. Scripture marks the arrival of the Son in the incarnation and the arrival of the Spirit at Pentecost, and it is just as clear that the Father is the One who sends them both — the Father sends the Son (John 8:42), and the Father sends the Spirit (John 14:26). The Son and the Spirit are fully God and present from eternity; the three are truly one. But the voice that sends is the Father's. So the covenant voice had to be a Person of the Trinity, and it is neither the sent Son nor the sent Spirit — which leaves only the Father. This is the rule FHB follows across the whole canon: where the text establishes the Son or the Spirit, FHB names them; every other call of the covenant presence is our Father, the One who sends. Until now, no English Bible gave that sending Father His voice.

The Distinction the Great Translations Already Pointed To

We owe an immense debt to the translation tradition, and FHB says so without reservation. The King James, the ESV, the NIV, the NASB, the New Living Translation, The Passion Translation, and the great versions before and after them carried God's word into English with care that has fed the church for centuries — we would not be here without them. And they already pointed at the very distinction FHB completes: when the Hebrew says YHWH, the personal covenant name, the translators set it in small capitals as 'LORD'; when it says Elohim, they print ordinary 'God.' That typographic whisper is faithful scholarship. FHB simply follows that seed to its warm conclusion, letting the Person the small caps were guarding be seen plainly as our Father.

The convention is not ours to claim; it is theirs to be thanked for. Reference works describe it the same way: where you see 'LORD' in small capitals, the underlying word is the covenant name (Blue Letter Bible catalogs how the names work). The translators handed us the contrast in small caps; FHB takes them at their word and lets the Father step out from behind the convention. Honoring the tradition and completing it are not in tension; one made the other possible.

Read Job 42 in the Father's Heart Bible. Open the chapter where Job finally meets the Father and watch the names change before your eyes.

Job's Turning Point: From the Almighty to the Father

The book of Job is forty-two chapters of people talking about God — and that is exactly the point. Yet Job has carried a clear Father-heart revelation all along, hidden in plain sight and mostly unseen until FHB let its divine names be read for what they are. Job's friends never run out of theology. Eliphaz presses him, 'Submit to God now and be at peace with him… if you return to the Almighty you will be restored' (Job 22:21,23). Zophar demands, 'Can you fathom the deep things of God? Can you find the limit of the Almighty?' (Job 11:7). Notice the vocabulary: God, the Almighty — a power to be appeased, real but kept at a distance. Job knows about God; what he has not yet had is a face. The turning point is not a better argument. It is an encounter.

Then God answers out of the storm, and everything shifts. By the end Job can say, 'My ears had heard of you, but now my eyes have seen you' (Job 42:5). Hearing became seeing. And here is what the Hebrew itself does — not FHB, the Hebrew: in the same chapter the friends' generic words give way to the covenant name, YHWH, for the God who finally speaks and restores. The distinction was already in the original; FHB simply refuses to flatten it. So the verses earlier Bibles print with 'the LORD' read, in FHB, 'After our Father had spoken these words to Job' (42:7), and 'our Father restored his fortunes' (42:10). The friends had spent the whole book appeasing the Almighty; Job finally met the Father. Earlier he knew Him as God; now he knows Him as Father — and the Hebrew said so all along.

Read it slowly and the shift is unmistakable: the argument ends not with a verdict but with a face.

The Apostles Did This First

If surfacing the Person behind the name feels like a modern liberty, the New Testament will surprise you: the apostles did it first, and with the most sacred name of all. Joel promised, 'everyone who calls on the name of the LORD' — the covenant name, YHWH — 'will be saved.' When Paul reaches for that promise in Romans, he applies it directly to Jesus: 'everyone who calls on the name of the Lord will be saved.' He took the Old Testament covenant name and assigned it, without apology, to the Son. That is the engine of New Testament interpretation: the first Christians read the divine names of the Hebrew Scriptures and resolved them to the Persons of the Trinity. FHB stands in that exact stream — doing the same interpretive work the apostles modeled, only now visibly, on the page.

Lay the two verses side by side. Joel writes it of YHWH (Joel 2:32); Paul writes it of Jesus (Romans 10:13). Same sentence, same salvation, a name moved deliberately from the Father's covenant title to the Son. The apostles could do this because they were sure the God of Israel was never a generic deity but a Father revealing Himself in a Son by the Spirit. This is why FHB's method is accurate rather than novel: it reads the names the way the New Testament authors already read them. We are not editing the text; we are continuing the apostolic habit of letting the personal God be personally named. If you want to see the same instinct in the Spirit's cry, read what 'Abba, Father' really means.

The Names That Answer Our Need to Belong

Type the honest questions people actually ask into a search bar and you find the ache under the theology. 'What is God's name in the Bible?' 'What's the difference between God and the LORD?' 'Is God the Father the same as God?' Underneath every one is a deeper hunger — not for trivia, but for belonging. We were made by a Father to need a Father, and a generation starved of that word is trying to find Him in books that keep calling Him a distant 'God.' The difference between 'God' and 'the LORD' is precisely the difference FHB makes visible: the generic deity versus the covenant Father. The names were never academic — they answer the question the human heart is actually asking.

This is no small need. In the United States alone, about one in four children — roughly eighteen million — grow up without a father in the home, and a heart that has never heard 'father' as a safe word will struggle to recognize Him when a Bible keeps Him at arm's length as 'God.' The remedy is not a sociology lecture; it is the text itself: when Scripture finally calls Him 'our Father' on the page, the fatherless heart has something true to read. The very first temptation worked the opposite way, reframing the Father as a far-off deity — the serpent never says 'Father,' only 'Did God really say…' (Genesis 3:1; I trace this in the oldest lie). FHB answers that oldest lie by giving the name back.

So open Job 42 for yourself, and read it the way Job finally saw it — the friends arguing about the Almighty, then the narrator daring to say 'our Father.' That is the whole invitation of this translation: not a new God, but the One who was always there, calling Himself by name. The next time your eyes land on 'God' in any Bible you love, ask the question the Hebrew asks — category, or covenant? Then come see the answer in the Father's Heart Bible, and join the family learning to read His name as their own.