Our Verseless Bibles

Let me offer you a warning that will vastly improve your ability to understand Scripture, if you heed it. It’s a insight for every person who has ever asked, “How does this verse apply to my life?” Here it is: There are no verses in the Bible. Nope. Not a one. At least, not in the original, and that’s the Bible that matters.

First, a definition. A “verse” is a passage of Scripture distinguished from other passages of Scripture by a numerical address (e.g., John 3:16, famously). Those numbers, though, were not in the original, but were inserted nearly sixteen centuries later by French printer Robert Stephanus in 1551.


Beware the Numbers

There’s good news and bad news about verse numbers. The good news is it’s easier to find stuff. The bad news is it’s easier to get stuff wrong. Verse numbers tempt readers to take a passage as a collection of discrete statements having meaning and application in isolation from the larger work (“How does this verse apply to my life?”).

Take a verse like “The Lord will fight for you while you keep silent” (Ex. 14:14). It wasn’t meant by Moses as a stand-alone promise. Sure, the Red Sea narrative has plenty of relevance for New Testament believers, but this individual verse has no application to any Christian isolated from its context. Simply put, it’s not our promise.

In fact, standing on their own, most “verses” have absolutely no application to anyone’s life. That’s because most of the time the precise point of a verse cannot be found in the verse itself but in the relationship of that verse to verses above and below it. We can’t simply isolate a line or two and ask, “How can I stick this line into my life?”

Here’s why. God did not give us 66 books of short, pithy sayings to be applied piecemeal to our lives (with a few exceptions, e.g., much of Proverbs). Most of Scripture is narrative—story. Most of the rest—NT epistles, for example—is argument (making a case) or instruction. Each of these—narrative, argument, instruction—involves a flow of thought within the passage from the larger part to the smaller part.

Chapters help us understand a paragraph’s role in the larger narrative. Paragraphs help us understand what a sentence means. Sentences help us understand individual word meanings. The account taken as a whole, then, has instructive value, not necessarily a verse standing by itself. That’s why at Stand to Reason we follow the rule “Never read a Bible verse.” Always read a paragraph (at least) before drawing conclusions about meaning.


Beware Section Headings

The same warning goes for section titles added by Bible editors. Headings can be helpful, but they can be harmful, too, by severing material from the larger flow of thought that’s important to the meaning of a passage the heading has now isolated.

Take Jesus’ teaching on the Good Samaritan. Read Luke 10:30–37 without reading the six verses that precede the heading “The Good Samaritan” that you’ll find in some Bibles, and you’ll miss why Jesus told the Samaritan tale in the first place. Which means you’ll completely miss the point of the parable—and most do (hint: it’s not about loving your enemy)—because Jesus’ main point hinges on a critical phrase in verse 29.


Start Big, Then Get Small

So, beware. A really good idea almost five centuries ago had a bad consequence that can sabotage your understanding of Scripture. I suggest you ignore the artificial divisions (chapters, verses, headings) and focus on the larger narrative, argument, or instruction. Start big, then get small. Look at the larger flow of thought, then zoom in on the particulars.

blog post |
Greg Koukl

Give

Give

Give