The Book of Daniel presents itself as the work of a Judean exile living in sixth-century BCE Babylon, under Nebuchadnezzar and his successors. The mainstream critical dating places the book's completion around 165–164 BCE — during the persecution of Judean Jews under the Seleucid king Antiochus IV Epiphanes, some four hundred and thirty years after its claimed setting.
That conclusion is not an assumption imposed on the text. It is the result of reading the text closely. The scholar John J. Collins, whose commentary is the standard reference, reached the 165 BCE date as the outcome of examining Daniel's historical, literary, and theological evidence — not as a premise decided in advance. The single most decisive piece is the seam shown above.
The fingerprint01 — The seam in chapter 11
Daniel 11 narrates the wars between the "king of the north" (the Seleucids) and the "king of the south" (the Ptolemies) in remarkable, granular detail — marriages, betrayals, campaigns, the desecration of the Temple — tracking the career of Antiochus IV with the precision of a historian, not the haze of a seer four centuries removed. Then, at verse 40, it turns to genuine prediction: Antiochus will launch a final campaign and fall in the land of Judea, between the sea and the holy mountain.
He did no such thing. Antiochus died in Persia, in the east, around 164 BCE, on campaign — not in Judea. As the commentator Carol Newsom observes, the author shows no knowledge of Antiochus's actual eastern campaign of late 165, nor of the rededication of the Temple in December 164, nor of the king's death at about that same time. The text is accurate up to a point and then wrong — and the point where it turns wrong marks the moment the author was writing. Everything before was history; everything after was a guess that failed.
Darius the Mede — the second tell
Daniel places a ruler named "Darius the Mede" over Babylon between Belshazzar and Cyrus the Great. No such king existed. Babylon fell to the Persians under Cyrus, not to a separate Median kingdom, and there is no historical record of this Darius. A genuine sixth-century eyewitness at the Babylonian court is unlikely to invent the very ruler he served under; a second-century author reconstructing the imperial past from a distance, and needing a distinct "Median" kingdom to fill out his four-kingdoms scheme, is exactly who would.
Why the exile, specifically02 — The date was load-bearing
Here is the core of the question. An author in 165 could have set his book anywhere. Why the sixth-century exile? Because the exile is the only vantage point from which the book's argument works. Two structural devices require it.
The four-kingdoms scheme
Daniel's visions (chapters 2 and 7) lay out a fixed sequence of empires — Babylon, Media, Persia, Greece — each giving way to the next, until a divine kingdom shatters them all. For that sequence to read as prophecy fulfilled, the seer must stand at kingdom one: in Babylon, at the beginning. Positioned there, the whole four-century span unspools as foresight, arriving precisely at the Greek crisis the author actually inhabits. Set the seer any later and the runway of manufactured prediction collapses.
The seventy weeks / 490-year clock
Chapter 9 takes Jeremiah's prophecy of "seventy years" of exile and reworks it into seventy weeks of years — 490 years — a countdown running from the exile to the crisis of the author's own day. The arithmetic only functions if the clock is started at the exile. The date is not decoration; it is the zero-point of the book's own timeline, the anchor without which the countdown to Antiochus cannot be drawn.
So 600 was not chosen at random, nor merely for atmosphere. It was chosen because the exilic seer is the necessary instrument of the argument — the position from which four centuries of known history can be delivered as vision, and from which the clock ticking toward the author's present can be set running. The date is the machinery.
The book had to begin in Babylon, because only from Babylon could the future be written backward.
The reading: constructed to persuade03 — The argument for intent
Assemble the pieces. A first-person narrative set four centuries before its composition. A false attribution to an ancient, revered figure. A survey of history dressed as prediction, precise until the instant of writing. A fabricated Median king to complete a schematic sequence. An instruction, in chapter 12, that the words be "sealed until the time of the end" — a device that conveniently explains why a supposedly sixth-century book had never been heard of until the second. And, framing it all, a purpose the text barely conceals: to reassure Jews suffering under Antiochus that their deliverance was foreseen, ordained, and near.
Each element points the same direction. The backdating is not incidental to the message; it is the message's engine. The persuasive force of "this was all foretold" depends entirely on the reader believing the words are old. Strip away the false date and the comfort evaporates. The construction, in other words, is built to make a reader accept as divine foreknowledge what the author knew to be recent composition. On its face, that is deception in the service of authority — history manufactured into prophecy to carry a weight it did not earn.
"A recognized convention, not a forgery"
A substantial body of scholarship reads pseudepigraphy differently. James VanderKam calls it a kind of "reverse plagiarism" — writing something yourself and crediting it to another — rather than fraud. James Charlesworth argues many such authors believed they were genuine mouthpieces, transmitting real revelation in the voice of the tradition's founder. On this view, writing in the name of Enoch, Moses, or Daniel was an accepted literary device, and ancient audiences often recognized it as such rather than being deceived. If the convention was transparent, then "deception" is the wrong charge — no one was fooled, because everyone knew the rules.
The convention argument is strongest for openly framed "testaments" and visions. Daniel resists it on its own specifics. It does not present as transparent homage: it constructs a detailed false historical setting, invents a king, and — crucially — seals the book "until the end" to explain its own late arrival, a move that only makes sense if the audience is meant to accept its antiquity as real. And the failed prediction in chapter 11 is not a literary flourish; it is a genuine attempt at foresight that missed, which tells us the author expected to be believed. A device meant to be seen through does not need to hide its own newness or risk a falsifiable forecast. Daniel does both. Whatever the convention permitted elsewhere, this book was built to be taken as what it was not.
This brief establishes two things: that Daniel was composed late and dated backward, and that the construction points toward intended persuasion. It does not argue an anti-Persian motive — and honesty requires saying why. Daniel's antagonist is Antiochus the Greek. In its own scheme, Persia is the tolerable middle empire, not the enemy. So the question of whether any of this literature was aimed against the Zoroastrian world is a separate inquiry, to be judged on its own evidence, not smuggled in here on the strength of the backdating alone.
The date is proven and the machinery is clear. Daniel was written c. 165 BCE and set c. 600 BCE. The exilic vantage was chosen because the four-kingdoms sequence and the seventy-weeks countdown both require a seer standing at the start of the imperial succession. The chapter 11 seam and the invented Darius the Mede confirm composition at the second-century vanishing point.
The intent is argued, not assumed. The weight of the construction — false setting, sealed-until-the-end device, a falsifiable prediction that failed — supports reading the backdating as deliberate persuasion. The convention counter-case is real and is named here rather than ignored; Daniel's specific features answer it, but the honest posture is that intent is argued from the evidence, not declared settled.
Next: File 02 carries the same test to Isaiah — the pre-exilic framing of exilic and post-exilic material within a single scroll.