Was the Book of Enoch Banned From the Bible? What the Canon Actually Shows

Scroll through enough faith content and you'll eventually meet the claim: the Book of Enoch was banned from the Bible. Powerful people, the story goes, found it too dangerous — too revealing about angels, demons, and the origins of evil — and quietly removed it. Sometimes the video adds that the Ethiopian Bible is the real, original Scripture, and everyone else conspired to bury the truth.

It's a compelling story. Joe Rogan has discussed it. Millions of people have watched versions of it. And whether you're a lifelong Christian, a curious skeptic, or simply someone who likes a good historical mystery, the question deserves an honest answer rather than a defensive one.

So let's set the conspiracy framing aside and ask a more useful question: what does the historical record actually show?

You Can't Ban a Book That Was Never In

The word "banned" smuggles in an assumption — that Enoch was once inside the Bible and was later thrown out. That's the part worth testing first.

Here's what the evidence shows. The Book of Enoch never appears in the Hebrew Bible — the Scriptures of Judaism. It never appears in the Septuagint, the Greek translation of the Old Testament used by Greek-speaking Jews and the early church. And it never appears in the Catholic canon either, not even among the additional books Catholics include that Protestants don't (often called the Apocrypha — books like 1 and 2 Maccabees).

In nearly every canon list and every Bible tradition we possess, Enoch simply isn't there. Not removed — never included.

One tradition is the exception: the Ethiopian Orthodox Church, whose canon does contain Enoch. That single exception is the seed of the whole "banned" theory. But a book that was excluded from one collection and never admitted to the others wasn't banned. It was never adopted. The distinction matters, because "banned" implies a cover-up, while "never adopted" simply invites the next question: why not?

What the Book of Enoch Actually Is

Enoch is a real, fascinating ancient text — and understanding what kind of text it is clears up most of the confusion.

Scholars date the Book of Enoch to roughly the third through first centuries BC, compiled over time. Much of it focuses on angels, demons, and their origins, drawing on the cryptic passage in Genesis 6:

"When man began to multiply on the face of the land and daughters were born to them, the sons of God saw that the daughters of man were attractive. And they took as their wives any they chose... The Nephilim were on the earth in those days." — Genesis 6:1–4 (ESV)

The book takes that mysterious moment and runs with it, offering one ancient school of thought about where evil spirits came from. And it attaches its teaching to a famous name: Enoch, the great-grandfather of Noah — described in Genesis as "the seventh from Adam."

There's a problem with that attribution, and it's not a hidden one. Enoch lived, by the Bible's own chronology, in the distant pre-flood past. The book bearing his name was written thousands of years later. Scholars call this a pseudepigraphal work — literally "false writing," meaning a text attributed to someone who didn't write it.

This was a known literary practice in the ancient world. Attaching a revered name to your writing lent it borrowed authority. A modern parallel might help: imagine a novel published next year, but printed under the name of the apostle John instead of its actual author, and presented as his genuine eyewitness testimony. The name would add weight it hadn't earned. That's the shape of the issue with Enoch.

"But It's in the Dead Sea Scrolls"

This is the strongest objection, and it deserves a careful answer rather than a dismissive one.

The Dead Sea Scrolls — discovered near Qumran and among our earliest surviving manuscripts of biblical texts — do contain fragments of Enoch. They also contain the Book of Isaiah. So the natural question is: if both were sitting in the same library, why does one make the cut and the other doesn't?

The answer is that the community at Qumran didn't treat all its scrolls as equal. We can see this in how they used them. These scrolls included a genre of writing called Pesher commentary — verse-by-verse interpretation explaining how a sacred text was being fulfilled in the community's own day. They wrote this kind of running commentary on books like Isaiah and the Torah, the writings they held as authoritative.

They didn't write it for Enoch.

A shared shelf isn't a shared status. A scholar's library today might hold sacred Scripture, academic commentary, and a paperback novel side by side — and no one would conclude the owner valued them identically. The Qumran community kept Enoch, read Enoch, and clearly found it interesting. The evidence simply doesn't show they considered it Scripture.

The "Oldest Bible" Claim, Checked

A second viral talking point holds that the Ethiopian Bible is the oldest in the world — the original from which everything else was edited down. The dates don't support it.

• The Garima Gospels, an Ethiopian manuscript, date to around 500 AD. They're genuinely remarkable — the earliest illuminated (illustrated) Gospels we have. But "first illustrated" is not the same as "first" or "oldest."
• The Codex Vaticanus dates to the early 300s and contains nearly the entire Old and New Testaments in Greek — roughly two centuries before the Garima Gospels.
• The Latin Vulgate, a complete Bible, dates to the early 400s.
• The first complete Ethiopian Bible we possess dates to the 14th or 15th century — over a thousand years after Codex Vaticanus.

The likeliest explanation isn't a conspiracy. It's that "the oldest illuminated Gospels" got compressed, over many retellings, into "the oldest Bible" — a small slip that snowballed into a sweeping claim.

So What Was the Criteria?

If you reject the early communities' judgment, a fair follow-up lands back on you: by what criteria would you include a book instead?

For the early church and synagogue, two standards did most of the work. First, proximity to the events — writings as close as possible to what they described. Second, authorized authorship — for the Old Testament, recognized prophets and figures; for the New Testament, an apostle or a close associate of one. By both standards, a text written centuries after Enoch's lifetime, under a borrowed name, with no apostolic connection, fell short.

There's also a content problem worth naming. In places, Enoch sits awkwardly against the rest of Scripture — for instance, on the timing and nature of when angels fell. Different communities weighed these tensions, but the disagreements were substantive, not arbitrary.

"Doesn't Jude Quote Enoch, Though?"

Yes — and this is the most interesting wrinkle, because it's true and often misunderstood. The New Testament letter of Jude really does quote Enoch directly:

"It was also about these that Enoch, the seventh from Adam, prophesied, saying, 'Behold, the Lord comes with ten thousands of his holy ones, to execute judgment on all and to convict all the ungodly...'" — Jude 14–15 (ESV)

That's a near-quotation of 1 Enoch 1:9. So does quoting Enoch make the whole book inspired Scripture?

The key is a distinction that's easy to miss: the difference between what is true and what is inspired. Anything inspired is, by definition, true. But something can be true without the entire work it comes from being inspired.

The New Testament does this elsewhere. The apostle Paul quotes the pagan poet Epimenides — in Titus, and again at Athens in Acts 17, where the line he borrows comes from a hymn praising Zeus. No one reasonably concludes that Paul therefore endorsed Zeus or treated that hymn as Scripture. He took one true line and used it to connect with his audience.

Jude appears to be doing the same: lifting a genuine, fitting line his readers would recognize, without baptizing the entire book it came from. A reference is not an endorsement of the whole.

The Question Underneath the Question

There's a pastoral observation in the source material that's worth carrying out of the historical weeds, and it applies to believer and skeptic alike.

Notice how much energy these debates pour into things we can't actually settle — the precise identity of the Nephilim, whether ancient "watchers" were something stranger. Two verses speak directly to that pull:

"The secret things belong to the LORD our God, but the things that are revealed belong to us and to our children forever." — Deuteronomy 29:29 (ESV)

And Paul's caution to Timothy:

"...nor to devote themselves to myths and endless genealogies, which promote speculations rather than the stewardship from God that is by faith." — 1 Timothy 1:4 (ESV)

The point isn't that curiosity is bad — curiosity is exactly what brought you to this question. It's a caution about proportion. It's possible to spend so much attention on what can't be known that we never explore what can be. One speaker in the source put the test sharply: if you settled the identity of the Nephilim tomorrow, what would it actually change?

Where This Leaves Us

The honest verdict is less dramatic than the viral version, and more durable. The Book of Enoch wasn't smuggled out of the Bible by frightened authorities. It was an ancient, influential, pseudonymous text that most Jewish and Christian communities read with interest and declined to treat as Scripture — for reasons we can still examine in the manuscript record today.

That's not a story of suppression. It's a story of discernment, carried out in daylight, with evidence we can still weigh for ourselves. And weighing it — rather than inheriting either the conspiracy or the dismissal secondhand — is the more interesting path anyway.

Curious how the canon came together, or what other "lost books" claims actually hold up? Those are exactly the kinds of questions worth bringing to your own study. Start exploring with your next question.