Blog

What Should I Read in the Bible Today? Where to Start

Read Mark. It is the shortest gospel, it moves fast, and at four to seven minutes a chapter you can finish it in an hour or two. If you have five minutes, read Psalm 1 or Philippians 2. Below: what to read for your situation, where not to start, and how to keep going.

Disclosure: I own Ave, a daily Bible verse app. It comes up once at the end of this page and nowhere else.

Most pages that answer this question hand you a reading plan. That is usually the wrong answer, because a lot of people asking it have already abandoned one. So this page does two things. First, it gives you something specific to read today, chosen by what is actually going on with you rather than by a schedule. That is a decision you make once, not a commitment. Second, it covers what a workable plan looks like if you want to keep going after today.

Read this today

Pick whichever line below sounds most like you right now.

Reading times are ranges. The fast end assumes around 200 words a minute, which is normal careful reading. The slow end assumes 100 words a minute, a deliberately unhurried pace with room to stop and reread. Word counts are from a published book-by-book count of the full canon (source noted at the end).

You have never read the Bible before

Read Mark. 16 chapters, roughly 11,300 words. About 55 minutes at a brisk pace, closer to two hours if you take your time. Four to seven minutes a chapter.

Mark is the shortest of the four accounts of Jesus' life, and it is the most direct. There is no genealogy and no long theological opening. It starts with John the Baptist, gets to Jesus within about fifteen verses, and keeps moving. Almost every church and ministry that publishes a starting point recommends a gospel, and Mark is the one most often named, specifically because of its length.

Three chapters an evening gets you through the whole book in five or six sittings. That is the appeal. You finish something.

You have five minutes

Read one psalm, or one short letter split over a few days.

Psalms average around 200 words each, so most take one to two minutes. Psalm 1 is a reasonable place to open, because it functions as a kind of preface to the rest of the collection. After that, you can read them in order or open at random. They were written as prayer and poetry, and they hold up in isolation in a way that most of the Bible does not.

If you would rather read something with a beginning and an end:

  • Philippians. 4 chapters, about 1,630 words. Eight to sixteen minutes total, or a chapter a day for four days.
  • James. 5 chapters, about 1,740 words. Nine to seventeen minutes. Blunt and practical, and it assumes very little background.

If you want a longer list to pick from, twenty Bible verses worth knowing is a good place to browse.

You are going through something specific

There are passages that people have gone back to in hard stretches for a very long time, and it is reasonable to go to them now.

  • Grief or loss: Psalm 13, Psalm 88, or Lamentations (5 chapters, about 2,300 words, twelve to twenty-three minutes). Psalm 88 is worth knowing about because it does not resolve. It ends in the dark. Some people find that more useful than a psalm that ties itself up.
  • Pressure, anxiety, a situation you cannot change: Philippians. It is traditionally read as having been written from prison, which is part of why the parts about contentment land the way they do.
  • A long, unglamorous, difficult stretch: Ruth. 4 chapters, about 2,000 words, ten to twenty minutes. Famine, migration, widowhood, and the slow business of getting through.

One thing worth saying plainly: reading a passage is not going to fix your situation, and if what you are dealing with is bigger than a hard week, a passage is not a substitute for talking to someone who can actually help.

If you would rather pick by mood than by book, morning scriptures sorted by the kind of morning you are having is organized that way.

You want to understand what Christians actually believe

Read Luke, then Acts. They were written as two volumes by the same author. Luke is 24 chapters, about 19,500 words, roughly 100 minutes to just over three hours. Acts is 28 chapters, about 18,450 words, a similar length.

Luke covers the life and teaching of Jesus. Acts covers what the earliest Christian communities did next, how they spread, and what they argued about. Read together they are the closest thing in the Bible to a continuous narrative of where the religion came from.

If you want the argument rather than the story, Romans (16 chapters, about 7,100 words, thirty-five to seventy minutes) is where the theology gets laid out most systematically. It is a harder read and it rewards going slowly.

You do not have to believe any of this to read it. It is a foundational text for a large part of the world's art, law, and language, and reading it as a text is a legitimate reason to be here.

You have read a lot of it and you are bored of it

Read Ecclesiastes. 12 chapters, about 4,500 words, twenty-three to forty-five minutes. It is skeptical, repetitive on purpose, and considerably less tidy than most people expect anything in the Bible to be.

Also worth a look: Amos (9 chapters, about 3,000 words, fifteen to thirty minutes), or Job if you have a couple of hours.

Or change the unit instead of the book. Read a whole letter in one sitting rather than a chapter a day. Galatians takes eleven to twenty-two minutes end to end. The letters were written to be read aloud to a room in one go, and they feel like different documents when you read them that way.

Where not to start

Do not open at Genesis 1 and read straight through. It is the single most common way people stop.

Genesis itself is fine. It is 50 chapters and around 32,000 words, so two and a half to five and a half hours, and much of it is narrative you may already half know. Exodus keeps that going. Then comes Leviticus: 27 chapters of sacrificial procedure, purity regulations, and priestly instruction, written for a context you have no reference points for.

This is the well-documented stalling point. Pastors, Bible teachers, and ministry writers describe the same pattern independently: people start in January, get through Genesis on familiarity, get through Exodus on momentum, and stop somewhere in Leviticus in February. Nobody publishes a hard number on it, and you should be suspicious of anyone who does, but the pattern is reported often enough and consistently enough to take seriously.

The structural reason matters more than the anecdote. The Bible is a library, not a book. The Protestant canon holds 66 separate documents (Catholic and Orthodox Bibles include additional books, which is why two contents pages do not always match). They were written across centuries, in three languages, by many hands, in at least half a dozen genres: narrative, law, poetry, proverb, prophecy, letter, and apocalyptic.

The order they sit in is not chronological, and it is not a reading order. The books are grouped roughly by type. Genesis is first because it opens the story, not because anyone determined it was the best entry point. Nothing inside the book instructs you to read it front to back, and the front-to-back habit is a printing convention you have imported from every other book you own.

One more thing worth knowing. The personal reading plan is one model among several, not the default. Catholic, Orthodox, Anglican, and Lutheran churches largely use a lectionary, a fixed calendar of readings that a whole congregation works through together across a year or three. In those traditions, "what should I read today" already has an answer, supplied by the church calendar rather than chosen by the reader. Neither model is the standard one.

If you want to keep going

The honest version of why plans fail is that most of them are too big.

A standard one-year plan asks for three to four chapters a day, which is twelve to twenty minutes. That is genuinely manageable, right up until you miss four days and find yourself fourteen chapters behind. At that point the plan stops being a schedule and becomes a debt. Most people do not pay off a fourteen chapter debt. They quietly close it.

The failure does not stay contained either. Bible teachers who have watched this happen year after year report the same outcome: people who fall off a one-year plan usually do not downgrade to a smaller plan, they stop reading daily at all. That is the actual cost, and it is why picking a smaller plan first is not a compromise.

Here is roughly what is on offer and what each one costs you per day:

  • Canonical. Genesis to Revelation in order. Three to four chapters a day, twelve to twenty minutes, one year. Reaches Leviticus in February.
  • Chronological. The same content rearranged into approximate event order. Similar daily load, around twelve to fifteen minutes.
  • Blended or genre-based. Several short readings a day pulled from different parts of the Bible. More variety, more flipping around.
  • Ninety day. Twelve to sixteen chapters a day, forty-five to ninety minutes. That is a project, not a habit.
  • Two year. One to two chapters a day, five to ten minutes. Much easier to sustain.
  • New Testament only, a chapter a day. 260 chapters, about five minutes a day, finished in under a year.

A workable first plan is short, specific, and forgiving.

Short means five to ten minutes, chosen so that a bad day still fits inside it.

Specific means naming the book. "Mark, one chapter" is a plan. "Read the Bible more" is an intention, and intentions do not survive Tuesdays.

Forgiving means no catching up. If you miss Tuesday, read Wednesday's chapter on Wednesday. A plan you cannot fall behind on is a plan you cannot fail, and that turns out to matter more than coverage.

And finish something. One short book completed does more for whether you keep reading than forty days of a year-long plan you eventually abandon.

That is the compressed version. Building a Bible reading habit that actually sticks covers the mechanics properly: when to read, how to attach it to something you already do, and what to do on the days you do not want to.

What to do with what you read

Reading without understanding is the other common way this ends. People read three chapters, get nothing, conclude the Bible is not for them, and stop. Usually the problem is not the reader and not the text, it is that a paragraph written to a specific group of people about a specific situation was read as a standalone sentence.

Four steps, and none of them take long:

1. What does it say? Read it twice. Slowly the second time. Notice the small words: "therefore," "but," "so that." They almost always point backwards to something you have skipped. 2. Who was it written to, and why? Open the chapter. Read five verses either side. You are looking for the situation: who is speaking, who is listening, what has just happened. This step is where most misreadings die. 3. What does it mean? Say the verse in your own words, out loud, without any religious vocabulary. If you cannot, you have not understood it yet. That is useful information, not a failure. 4. What do you do with it today? One thing. Specific. Not a takeaway, a hook you can act on before the day is out.

Where careful readers genuinely disagree about a passage, and there are plenty of those, it usually means the text is doing something more complicated than it appears, not that you have missed something obvious. Traditions have argued over some of these lines for centuries.

If you want to see this worked through on specific passages rather than described, Bible verses with reflection and explanation does it verse by verse.

The short version

You do not need a plan today. You need one book, about ten minutes, and a decision you only have to make once. Mark, chapter one, is a perfectly good answer.

If the deciding is the friction, that is the problem Ave was built around: it sends one verse a day with a plain English explanation on tap, so there is nothing to choose. Taking the decision out of it is most of what makes a daily habit survive.