For most of my life, even asking whether the Bible was “God-given” would have felt borderline scandalous. Not heretical exactly, but close enough to make people shift uncomfortably in their seats. It simply wasn’t a real question. Asking it felt like inching toward the edge of a cliff, where even the simple act of looking down might cause you to fall. Bible 101 assumed it. Sunday School implied it. Youth group reinforced it. Seminary-bound students memorized verses for it. The Bible came from God – full stop. That wasn’t a doctrine you wrestled with; it was the ground beneath every other doctrine. To question it felt like pulling a load-bearing beam out of the house while insisting you were just “curious about architecture.” Everyone knew where that curiosity led. And so I never really asked. I didn’t need to. If anything, my task was to defend it, not examine it. After all, I’d been given reasons to trust that this book came from God like no other. But slowly, the structure beneath that conviction began to shift. It didn’t collapse. It didn’t even weaken beyond repair. But it began to loosen. Not because of a single argument or tension, but because the text itself often moved in ways I hadn’t been taught to expect. Although many of the tensions I encountered could still be managed with the lens I’d been given, they gradually began to make more sense without that lens. And that shifted the question I was asking. Instead of asking how to preserve what I’d inherited, I began asking why I had seen the Bible as a God-given book in the first place. And so, in this post, I want to revisit some of the reasons that once made that conviction feel so secure – and why, when I finally sat with them, they no longer carried the same weight.

To start, one of the reasons I was given most often, and reached for most naturally, came from Scripture’s own claims about itself. I was taught that the Bible doesn’t merely contain God’s word but is God’s word, and that it says as much in plain language. Verses like “all Scripture is inspired by God” (2 Timothy 3:16) and “no prophecy was ever produced by the will of man, but men spoke from God as they were carried along by the Holy Spirit” (2 Peter 1:20–21), were presented as straightforward assertions of divine authorship. If Scripture itself claimed to come from God, then surely that settled the matter (concerns about circular reasoning notwithstanding). But for a long time, I read those passages with a set of assumptions already in place: that “inspired” had more to do with origin than function; that when Paul¹⛰ Side Trail: I refer to 2 Timothy as written by Paul, since that remains the traditional attribution and the one most familiar to most readers. At the same time, the authorship of the Pastoral Epistles (1–2 Timothy and Titus) is widely debated in contemporary scholarship, with many scholars pointing to differences in vocabulary, style, and church structure as evidence of later authorship by a follower writing in Paul’s name. Others continue to defend Pauline authorship. For my purposes here, the question of authorship doesn’t really affect the point that much, which focuses more on how early Christians understood Scripture’s role rather than on who held the pen. spoke of “all Scripture,” he was referring to the entire Bible as we now have it; and that Peter’s²⛰ Side Trail: As with 2 Timothy, I refer to 2 Peter using its traditional attribution for the sake of familiarity. Here too, authorship is widely debated in contemporary scholarship. Many scholars point to differences in style and vocabulary, along with 2 Peter’s close relationship to Jude, as reasons to question Peter as the author, while others continue to defend the traditional view. As before, the authorship question doesn’t really affect the point being made, which concerns how early Christians spoke about prophecy and divine guidance rather than who wrote the letter. description of prophetic speech applied not just to prophets, but to all of the biblical authors as a whole. Yet, over time, those assumptions began to feel less obvious than I had once been taught. Paul, writing to Timothy, seems far more concerned with the usefulness of Israel’s sacred writings for teaching and formation than with defining a theory of how they came into being, and he is almost certainly referring to the Scriptures Timothy had known since childhood – not a future New Testament canon. Likewise, Peter’s words are explicitly about prophecy, not about the mechanics of authorship in general, and even then they emphasize divine involvement rather than divine dication. None of this made those texts untrue or insignificant, but it did make me realize how much interpretive weight I had been placing on them. What I once heard as clear, self-evident claims of divine authorship began to look more like seeds from which later doctrines grew – meaningful, even authoritative, but not as tidy or as conclusive as I had once assumed.

Next was fulfilled prophecy, which often served as a kind of golden thread binding the Bible across the centuries. What God spoke through the prophets, God fulfilled through Christ. Jesus didn’t appear out of nowhere, but arrived in precise fulfillment of detailed forecasts. I was taught to read the prophets as if they were writing history in advance, predicting Jesus’ birth, betrayal, crucifixion, etc.³⛰ Side Trail: I saw passages like Micah 5:2 as predicting Bethlehem, Isaiah 9:6 as forecasting a divine child, Isaiah 53 as detailing the crucifixion, and Zechariah 9:9 as describing Jesus’ entry into Jerusalem. Even verses like Hosea 11:1 (“out of Egypt I called my son”) and Jeremiah 31:15 (Rachel weeping) were treated as previews of events in Matthew 2:13–18. Psalm 22 was read as a script for the crucifixion (Psalm 22:1, 7–8, 16–18; cf. Matthew 27:35, 39–43), and Zechariah 11:12–13 as a prediction of Judas’s betrayal (Matthew 26:14–15; 27:9–10). It felt airtight. But when I started engaging those texts in their own contexts, the thread began to feel less tightly stitched. Take Isaiah, for example. I had always heard that Isaiah predicted the virgin birth: “Behold, the virgin shall conceive and bear a son, and shall call his name Immanuel” (Isaiah 7:14). But in its original setting, the passage isn’t about a distant future messiah at all. It’s about a political crisis happening in Isaiah’s own time, and the “virgin” and her child are presented as a sign meant to reassure a specific king facing immediate danger – not as a coded reference to Jesus centuries later.⁴⛰ Side Trail: Isaiah 7:14 originally addressed King Ahaz during an eighth-century BCE crisis. Isaiah promised a nearby sign: a young woman(alma) in the king’s court would soon bear a child named Immanuel, and before the child grew up, Judah’s enemies would fall (Isaiah 7:15–16). The Hebrew term alma means “young woman,” not specifically “virgin.” It became “virgin” because the Greek Septuagint translated it as parthenos, a word that normally means “virgin.” The point was immediate reassurance, not a distant prediction. When Matthew later applies this verse to Jesus’ birth (Matthew 1:22–23), he isn’t claiming Isaiah foresaw a virgin conception centuries ahead; rather, he rereads the passage typologically, seeing Jesus as the fuller expression of “God with us,” extending an old promise into a new moment. Yet it wasn’t just in Isaiah. I began to see the same type of dynamic in other places often cited as “fulfilled prophecy” too, whether in Micah,⁵⛰ Side Trail: Micah 5:2 is not, in its original setting, a precise prediction of where a future messiah would be born. Most scholars see it as a poetic reminder of Israel’s golden age under David, spoken during a period of political turmoil. Bethlehem mattered because it was David’s hometown, a symbol of humble beginnings and hoped-for renewal, not because it pinpointed a future birthplace. Micah promises that God will raise up a new David-like ruler who will shepherd and strengthen Israel (Micah 5:2–4). When Matthew later applies the verse to Jesus (Matthew 2:5–6), he draws on this Davidic hope, rereading the older text in light of Jesus’ life. Hosea,⁶⛰ Side Trail: Hosea 11:1 is often cited as fulfilled prophecy because Matthew 2:15 applies its words “Out of Egypt I called my son” to Jesus’ return from Egypt after Herod’s death. Read this way, Hosea appears to predict a future messianic event. But in its original context, Hosea is not predicting the future at all; he is recalling the past. The “son” is Israel, and the reference is to the Exodus, not the Messiah. Mainstream scholarship understands Matthew as rereading Israel’s story through Jesus, not identifying a prediction Hosea intended to make. Zechariah,⁷⛰ Side Trail: Zechariah 9:9 is often presented as a direct prediction of Jesus’ triumphal entry, since the Gospels describe him riding into Jerusalem on a donkey (Matthew 21:4–5; John 12:14–15; cf. Mark 11:1–10; Luke 19:28–38). Read this way, the prophet appears to be forecasting a specific messianic moment centuries in advance. But in its original context, Zechariah is offering post-exilic Judah a poetic vision of hope: a humble, peace-bringing king who contrasts with violent rulers. Mainstream scholarship understands the Gospel writers as consciously shaping Jesus’ entry to echo this imagery, not uncovering a prediction Zechariah intended as a literal forecast. or even the Psalms.⁸⛰ Side Trail: Psalm 22 was originally a desperate prayer, not a hidden preview of the crucifixion. It opens with a cry of abandonment: “My God, my God, why have you forsaken me?” (Psalm 22:1) and goes on to describe a sufferer mocked by enemies, overwhelmed by fear, and pleading for rescue (Psalm 22:6–8, 12–18). These images reflect David’s own anguish, a raw lament rooted in his lived experience. When the Gospel writers echo this psalm in the crucifixion narrative (Matthew 27:35, 39–46; John 19:24), they aren’t claiming David foresaw Jesus’ death in detail. They recognize in Jesus’ suffering the same cries of abandonment and trust that shaped David’s prayer. That said, I came to see that the Gospel writers weren’t being dishonest or deceptive when they appealed to these passages. Rather, they were being deeply reverent yet theologically creative.⁹⛰ Side Trail: This approach is similar to the Jewish tradition of Midrash, which treats Scripture as a living text to be re-read, expanded, and applied to new moments rather than as a set of fixed predictions. Midrash often draws earlier passages into fresh situations to illuminate God’s ongoing work. The Gospel writers use Israel’s Scriptures in this way: Hosea 11:1, originally recalling the Exodus, becomes a lens for Jesus’ return from Egypt (Matthew 2:15); Jeremiah 31:15, a lament over exile, is re-applied to Herod’s violence (Matthew 2:17–18); and Psalm 22, a raw Davidic lament, is woven into the crucifixion narrative (Matthew 27:35–46). Their readings are reverent, imaginative, and rooted in a tradition that saw Scripture as continually speaking into the present. Less like they were trying to prove a set of ancient predictions and more like they were re-reading their present in light of their sacred past, weaving together hope and fulfillment in a way that made sense of their experience of Jesus.¹⁰⛰ Side Trail: This is an interpretive approach that appears throughout the Bible as a whole. The prophets do this when they reuse exodus imagery to describe Israel’s return from exile (Isaiah 40:3–5; Hosea 2:14–15). Chronicles retells Samuel–Kings with new emphases to speak hope into a post-exilic community (compare 2 Samuel 24 with 1 Chronicles 21). Daniel reworks earlier prophetic symbols to address life under foreign empires (Daniel 7’s beasts echo the nations of Isaiah 13–27). Even the New Testament writers reinterpret Israel’s Scriptures in fresh ways: Peter applies the language of Sinai to the church (1 Peter 2:9–10), and Paul uses the story of Sarah and Hagar as an allegory for life in the Spirit (Galatians 4:21–31). Across Scripture, writers weave together old and new, reading their moment through earlier texts to express what God was doing in their own day. Again, this didn’t shatter my lens or render it unuseable. But it did make me wonder whether it was the best lens to begin with.

Then there was the concept of Scripture’s unity. The idea that forty authors, writing over fifteen hundred years in three languages, could produce one coherent book – what else but divine authorship could account for that? From Genesis to Revelation, I was told, ran a single narrative with God as the master storyteller. And to be fair, I still think that vision has beauty. There are patterns, echoes, and themes that ripple across the pages. Themes like covenant, exile, return, and redemption.¹¹⛰ Side Trail: The Bible is full of patterns and echoes: covenant promises shaping Abraham’s story (Genesis 12:1–3), exiles and returns defining Israel’s history (2 Kings 25; Ezra 1:1–4), and the hope of redemption running from the prophets (Isaiah 40:1–5) to the New Testament’s picture of renewal (Revelation 21:1–5). While the Scriptures don’t always line up into a single, tidy storyline, they do carry recurring themes that speak across their many voices. But when I looked closer, not all of it held together as seamlessly as I had once thought. Proverbs and Ecclesiastes seem to offer differing takes on how the world works.¹²⛰ Side Trail: Proverbs often teaches that wisdom leads to stability and blessing: “the righteous will never be uprooted” (Proverbs 10:30) and “those who are diligent prosper” (Proverbs 12:24). Ecclesiastes, however, pushes back, observing that “the race is not to the swift” and that time and chance affect everyone (Ecclesiastes 9:11). One book paints a world that is ordered and predictable; the other sees a world marked by ambiguity and frustration. Job seems to challenge the reward-and-punishment framework of Deuteronomy.¹³⛰ Side Trail: Deuteronomy promises that obedience brings blessing and disobedience brings hardship (Deuteronomy 28:1–14, 15–68), laying out a clear reward-and-punishment pattern. But Job is portrayed as “blameless and upright” (Job 1:1), and yet he suffers terribly without cause. His friends defend the Deuteronomic logic, insisting he must have sinned (Job 4:7–8), but the narrative ultimately rejects their certainty. God declares that the friends have not spoken rightly (Job 42:7) and restores Job without tying his suffering to wrongdoing. Job stands as a protest against simple formulas, complicating the neat moral equations of Deuteronomy. The Gospels, while harmonious in many ways, also diverge in chronology, detail, and emphasis.¹⁴⛰ Side Trail: John places the temple cleansing early in Jesus’ ministry (John 2:13–22), while the Synoptics put it in his final week (Mark 11:15–19; Matthew 21:12–17; Luke 19:45–48). Matthew and Luke include birth narratives with different characters, settings, and timelines (Matthew 1–2; Luke 1–2), while Mark and John begin elsewhere. Jesus’ last words on the cross vary from Gospel to Gospel (Matthew 27:46; Luke 23:46; John 19:30). Even the resurrection accounts differ in who goes to the tomb and what they see (Mark 16:1–8; Matthew 28:1–10; Luke 24:1–12; John 20:1–18). These variations reflect distinct theological portraits rather than a single, synchronized biography. Paul and James seem to disagree on faith and works.¹⁵⛰ Side Trail: Paul insists that a person is “justified by faith apart from works of the law” (Romans 3:28; Galatians 2:16), emphasizing trust in Christ rather than adherence to the Mosaic law. James, however, argues that “faith without works is dead” and even says a person is “justified by works and not by faith alone” (James 2:17, 24). Paul warns against relying on the law for righteousness; James warns against a faith that produces no change. Their voices highlight different concerns and create genuine tension within the New Testament’s witness. These tensions were never huge obstacles for me, but they did challenge the idea of a perfectly unified plotline. What I once heard as a symphony started to sound more like jazz, with conversation, dissonance, and improvisation between movements. I know many thoughtful scholars and theologians still hold to a unified view of Scripture, often in more nuanced ways. But for me, the question became: had I assumed unity because I saw it in the text, or because I was told it must be there? And if I had to harmonize tensions in order to preserve unity, was I really reading the Bible on its terms – or mine?

Next was its miraculous preservation, the idea that the Bible’s very survival was proof of its divine origin. That a collection of texts so ancient and sprawling could endure for millennia was no accident, it was providence. And yes, there is something astonishing about that survival. But again, when I looked more closely, the picture became more complex. We don’t have the original manuscripts. We have thousands of copies, sometimes with meaningful variations.¹⁶⛰ Side Trail: What we have are thousands of handwritten copies (some very early, others much later) with differences that range from small spelling changes to meaningful variations. Some manuscripts include longer endings to books (like Mark 16:9–20), added phrases (as in the Johannine Comma, 1 John 5:7–8), or alternate wordings that affect how a passage is read (Luke 22:43–44; John 7:53–8:11). Most variations don’t change core teachings, but their number and significance remind us that the Bible’s text was copied by real people over many centuries, not handed down as a flawless, uniform transcript. Some well-known passages, like the story of the woman caught in adultery, don’t appear in the earliest copies.¹⁷⛰ Side Trail: The story of the woman caught in adultery (John 7:53–8:11) is missing from the oldest and most reliable Greek copies, and when it does appear, it sometimes shows up in different places (after John 7:36, at the end of John, or even in Luke). The longer ending of Mark (Mark 16:9–20) shows a similar pattern. These differences don’t erase the stories’ value, but they do show that certain beloved passages entered the biblical tradition later, reminding us that Scripture grew through a long, complex process of transmission and editing. The canon itself wasn’t decided overnight but evolved over centuries, shaped by debate, geography, theology, and power.¹⁸⛰ Side Trail: The canon itself didn’t appear fully formed but took shape over many centuries. Early Christians used a wide range of writings (letters, gospels, sermons, and apocalypses) and different regions favored different collections (Colossians 4:16; 1 Thessalonians 5:27). Some books we now consider central, like Hebrews, James, and Revelation, were debated for generations, while texts like the Shepherd of Hermas and 1 Clement were widely read and sometimes included. Church leaders gradually discerned which writings best reflected apostolic teaching (as in Irenaeus’s defense of four Gospels around AD 180) and which did not. Councils such as Hippo (393) and Carthage (397) ratified what long practice had already shaped. Again, that didn’t disprove anything, but it did reframe what kind of preservation was involved. Maybe it’s not so much a miracle of divine control as a miracle of communal devotion. The Bible was passed down, not sealed in stone, but carried in the hands of people who believed it mattered. That’s still meaningful, just in a different register.

Then there was the claim about historical accuracy. If the Bible could be shown to be historically reliable – if it got its facts straight about cities, kings, and timelines – then surely its larger claims could be trusted too. This gave my prior views a sense of groundedness. And yes, there’s a real historical core to much of Scripture.¹⁹⛰ Side Trail: The Bible reflects real places like Jerusalem, Samaria, Babylon, and real empires like Assyria and Rome (2 Kings 18:9–13; Luke 2:1–2). Figures such as Hezekiah, Cyrus, and Pontius Pilate appear both in the text and in archaeological or historical records (2 Chronicles 32:1–9; Ezra 1:1–4; Matthew 27:2). Events like the Babylonian exile are well attested (2 Kings 24–25), and New Testament letters address real communities like Corinth, Philippi, and Thessalonica (1 Corinthians 1:2; Philippians 1:1; 1 Thessalonians 1:1). While not everything functions as straightforward history, the biblical story is rooted in the real world. But over time I noticed that some of the more sweeping historical claims didn’t seem to hold up so well under scrutiny: the Exodus story, as I’ve alluded to before, doesn’t seem to line up well with the archaeological record;²⁰⛰ Side Trail: The Bible describes a vast population leaving Egypt and wandering in the wilderness for forty years (Exodus 12–14; Numbers 14:33–34). Yet archaeologists have not found clear evidence of a large, sustained migration through the Sinai. No widespread encampments, pottery remains, or material traces that match the scale the text describes. Because of this, many scholars think the story may preserve older memories of smaller groups leaving Egypt, or later theological reflection shaped into a national origin story. Its spiritual meaning endures, even if the archaeological picture is complex. likewise, the conquest of Canaan doesn’t seem to reflect the kind of widespread destruction we’d expect if Joshua’s account were accurate;²¹⛰ Side Trail: Joshua 6–11 portrays a unified Israel rapidly overtaking major cities, burning them, and driving out their inhabitants. But archaeological work at key sites like Jericho, Ai, and Hazor shows a mixed picture. Jericho’s walls were likely not standing in the period the Bible places the conquest, Ai appears to have been unoccupied, and Hazor’s destruction layers don’t neatly align with Joshua’s timeline. Many scholars therefore think Israel’s emergence was more gradual through settlement, migration, and social shift, rather than a single, decisive military campaign. the census in Luke doesn’t seem to neatly align with what we know of Roman administration.²²⛰ Side Trail: Luke says Caesar Augustus ordered “all the world” to be registered and that everyone had to travel to their ancestral towns (Luke 2:1–4). But Roman censuses didn’t require people to move long distances, and there’s no record of an empire-wide census in that period. Quirinius did conduct a census in Judea, but it took place in AD 6, about a decade after Herod the Great died (Luke 1:5), creating a well-known chronological tension. These gaps suggest Luke may be shaping the story theologically rather than reporting exact administrative history. Again, I’m aware all of this has long been known and addressed by scholars whose work is worthy of serious thought. But for me, it wasn’t that I found these tensions unresolvable, but that I started to wonder why I felt the need to resolve them in the first place. Had I confused the Bible’s historical feel with historical precision? Was I asking it to play a role it wasn’t intended to play?

Lastly, and perhaps the most personally moving reason I’d held onto, was the Bible’s power to transform. I was told, and had often felt, that the Bible changes lives. That it comforts the broken, convicts the proud, inspires justice, invites grace, etc. And I still believe that – know it, even. Some of the most intimate, soul-shaping moments of my life have come while engaging Scripture. But over time, I realized that transformation, while real, isn’t unique to the Bible. Sacred texts from other traditions also change lives. So do works of philosophy, poetry, and art. Perhaps most of all, however, is that although the Bible has been used to heal, it’s also been used to wound. To liberate, but also to oppress.²³⛰ Side Trail: The same text that calls for loving one’s neighbor (Leviticus 19:18; Luke 10:27) has been invoked to defend slavery (Ephesians 6:5), to silence women (1 Timothy 2:11–12), or to condemn entire groups. Prophetic calls for justice and mercy (Micah 6:8; Isaiah 58:6–7) have often been overshadowed by selective readings used to judge or exclude. The Bible’s power cuts both ways, depending on how and why it is interpreted. The question for me wasn’t whether the Bible could transform, but what kind of transformation it invited, and how. I came to suspect that maybe the transformative power of the Bible doesn’t primarily lie in affirming where it comes from, but in wrestling with what it says. That doesn’t make it less sacred in my eyes, just sacred in a different way.

All that said, I realize this may barely be scratching the surface for some, while for others it may feel like hitting an iceberg on a ship you never intended to board (RIP Titanic). In either case, the main takeaway for me was this: as I stepped back and looked at everything, what shifted wasn’t the idea that the Bible was sacred – it was the framework I’d used to explain why. None of these felt like a knockdown argument against the way I used to approach the Bible. And to this day, I still don’t think they are. There are thoughtful, faithful answers to each one. But together, they made me pause. Most of all, however, they eventually made me see that my way of seeing the Bible had been shaped not only by the Bible itself, but by the lens I had inherited from the tradition that formed me. A tradition that, as sincere as it was, often seemed to support its views by shaping the text to fit its framework rather than the other way around.

But where had this way of seeing the Bible come from in the first place? Why did it feel so natural, so unquestioned, so self-evident? Over time, I began to see that the lens I carried had been shaped long before I ever opened Scripture for myself. It came with its own history, one that had already worked its way into the air I breathed. So that’s where I want to turn next: to trace the history behind the lens and how I absorbed it long before I ever recognized it as a lens at all.

Until then, thanks again for reading and – as always – stay curious, seek truth, and love well.