What Are Bible Codes? Letter Patterns and Statistical Claims

Question?  -   Contact  -   Revised

Bible codes usually refers to claims that messages can be recovered by taking letters at equal intervals in a biblical text. Finding a word this way and demonstrating that it was deliberately encoded are different achievements. A striking display does not, by itself, prove that God exists, establish divine authorship or predict an event.

What Is Being Searched?

An equidistant letter sequence, or ELS, begins at a chosen letter and continues at a fixed interval. A negative interval reads backward. Spaces are excluded in the Genesis experiments discussed below. Displaying the text in rows can make selected sequences appear as nearby lines; the row arrangement is part of the presentation, rather than a sentence in the passage.

This differs from noticing a repeated phrase, a contrast between two scenes or a theme developed across a book. Those observations concern words and events in their readable context. An ELS search treats the text as a sequence of letters and needs a separate argument explaining why its results exceed what the search procedure could produce by chance.

The Genesis Experiment

In their 1994 paper, Doron Witztum, Eliyahu Rips and Yoav Rosenberg tested proximity between ELSs for names of rabbis and forms of their birth or death dates in Hebrew Genesis. Their significance test used a second list of 32 personalities. It compared the actual name–date pairings with many randomly permuted pairings, using defined measures of proximity.

The authors reported an overall significance level of 0.000016 in section 3. That number belongs to their specified statistical procedure and assumptions. It is not a calculated probability that God exists or that every claimed Bible code is genuine. Nor was this an advance forecast of an unknown event: the names and dates used as search targets were already available to the researchers.

What the Statistical Criticism Addresses

Brendan McKay, Dror Bar-Natan, Maya Bar-Hillel and Gil Kalai examined the experiment in Solving the Bible Code Puzzle. Their criticism concerned the test method and the freedom to choose names, spellings, appellations and date forms. A small reported significance level must be evaluated alongside how those inputs were selected.

In section 6 they deliberately adjusted an appellation list and obtained an impressive result in a Hebrew translation of War and Peace. This was a demonstration of flexibility, not an independent discovery that the novel contained supernatural codes. They separately reported independent experiments in section 10, including lists prepared with historians, which failed to detect the proposed phenomenon. Their conclusion was that the original result reflected choices in compiling the data rather than an encoded message.

The relevant dispute therefore extends beyond whether a computer can locate the displayed letters. Reproducing a display checks a search result; assessing the experimental design checks the conclusion drawn from it. This guide reports those researchers' findings and does not claim to have rerun their calculations.

Questions for a Claimed Prediction

Before accepting a new example, ask for enough information to make the claim testable:

  • Which exact text, spelling, starting point, interval limits and arrangement were used?
  • Were the target words, permitted variants and success criteria fixed before the search?
  • How many unsuccessful searches or alternative word choices accompanied the displayed success?
  • What comparison texts and independent tests were used?
  • For a prediction, was its specific meaning recorded before the event, including a clear condition under which it would fail?

A cluster interpreted after an event cannot establish advance prediction merely because readers can now associate its words with that event. Likewise, changing a spelling or a search limit requires accounting for that choice, rather than presenting the final selection as the only possible test.

Codes and Ordinary Bible Reading

Questions of biblical inspiration deserve arguments appropriate to that subject. In 2 Timothy 3:10–17, Scripture's stated usefulness concerns salvation through faith in Christ, teaching, correction and preparation for good works. The passage does not instruct readers to validate inspiration through skipped-letter searches. Luke 1:1–4 describes an ordered account related to transmitted testimony. These are examples of the texts' expressed purposes, not statistical tests of Hebrew Genesis.

A failed code claim does not decide every question about Scripture, and faith in Scripture does not validate every search result. For interpreting what a passage actually says, begin with its sentences, setting and argument; keep any proposed hidden-letter theory identifiable as an additional claim requiring its own evidence.

Sources and Further Study

Continue with context and interpretive claims or a passage-to-application reading workflow.

Recommended Articles
Hermeneutics: Context and Interpretation
Bible Study Rules: A Reading Workflow