You Cannot Speed Read a Textbook

Try this. Take any speed reading app, import a first-year statistics textbook, and start reading.

Somewhere in the second minute you will hit a sentence that goes: “the results are summarised in Table 3.1 Method n Mean SD Control 42 11.3 2.1 Treatment 41 14.8 2.4 which shows a clear effect”.

That is a table. It had rows and columns and headers, and it has been fed through a machine that only knows how to produce one word after another. The numbers survived. Everything that made them mean something did not.

Keep going and it gets worse. A two-column paper will start alternating between the left column and the right column mid-sentence. An equation will arrive as a stream of stray letters. And every figure the prose keeps referring to — as shown below, see Figure 4 — will simply not be there, because it was never text in the first place.

This is not a bug in one app. It is what the entire category does.

The flattening

RSVP works by removing a real cost. Reading normally, your eyes make four or five stops across a line, then a long backward sweep to find the start of the next one, and they get that sweep wrong often enough that regression eats about a fifth of your reading time. Show the words one at a time in a fixed spot and all of that mechanical overhead disappears.

To do that, the text has to be flat. One word, then the next, then the next. So the first thing every speed reader does — before you see anything — is take the document apart and throw the layout away.

For a novel that costs you nothing. A novel is a stream of words; the page it is printed on carries no information. Flattening it is lossless.

For a textbook it is not lossless at all. It is the loss.

What the layout was doing

Three things, none of which survive a flattening.

Position carries meaning. A table’s rows and columns are its argument. Move the cells into a sentence and you have kept every number and destroyed every relationship between them. The same is true of a matrix, a decision tree, a genealogy, a periodic table, a musical stave.

Some content is not words. An equation is notation, not language. There is no correct way to say ∫₀^∞ e^(-x²) dx = √π/2 one word at a time, and any tool that claims otherwise is guessing. Diagrams, photographs, spectra, micrographs, maps and circuit schematics are all in this category: the prose is about them, and without them the prose is about nothing.

Reading order is not always storage order. A two-column paper stores its text in whatever order the typesetting software emitted. Sometimes that matches how you read it. Often it does not, and the columns interleave — a sentence from the left, a sentence from the right, forever.

The usual advice is wrong

The standard answer is “don’t speed read technical material”. You will find it in every guide, including ours, and as far as it goes it is correct: comprehension degrades faster on dense material than on ordinary prose, and a paper you rush is a paper you will read twice.

But taken as a rule it is far too blunt, because a textbook is not uniformly dense. Open any chapter and you will find:

• Framing and motivation — ordinary expository prose
• Definitions and statements — dense, but short
• Worked examples — mixed
• Proofs and derivations — not prose at all
• Discussion, context, historical notes — ordinary again
• Exercises — a list

Most of a textbook chapter, by word count, is normal writing. The parts that genuinely need slow, careful attention are a minority of the page and a majority of the difficulty. Telling someone not to speed read the whole book because a quarter of it is mathematics is like telling them not to drive because some of the journey is a car park.

What you actually want is what you already do on paper: move quickly through the prose, stop dead at the mathematics, look at the figure the sentence just mentioned, then pick up speed again.

The reason nobody does that with a speed reader is that it takes three apps.

What it takes to do both

The reading is fast in the speed reader. The figures are in the PDF viewer. Your place is in neither, so every switch costs you thirty seconds of scrolling to find where you were.

In practice people give up and pick one. They read the textbook slowly in a PDF viewer, or they read a flattened version fast and skip the parts that matter. Both are worse than the thing they wanted.

The fix is not a better flattener. It is having the page and the stream be the same surface, so that moving between them costs nothing and neither one loses your place.

That is what ReadKinetic does now. Hold to read and the words come one at a time. Let go and you are standing on the page you had reached — for a PDF, the actual typeset page, drawn from your own file: columns where the typesetter put them, tables framed, equations as printed, plates at full size, two pages side by side on a wide screen. Tap any line and reading picks up from there.

There is no mode to enter and nothing to open. Stopping is the page.

The practice this makes possible

Once switching is free, a sensible way to read a chapter falls out on its own:

Run the prose at your normal pace. Framing, motivation, discussion — 350 to 500 words a minute for most people, faster once the vocabulary is familiar.

Stop at every definition. Not slow down: stop. A definition is a handful of words carrying the weight of the next thirty pages, and it deserves rereading rather than a lower WPM.

Let go at every figure. The page is already there and the figure is on it. Look at it, then start again from the sentence after.

Skip proofs on the first pass. Read the statement and the discussion after; come back to the derivation when you know whether you need it. This is what experienced readers of technical material do anyway, and it is the single largest time saving available.

Use the search, not your memory. “Where did they define regularity?” is a question you will ask fifty times. Searching the whole book and being taken to the page is thirty seconds saved, every time.

Where this still does not help

A scanned book is a stack of photographs. If a PDF has no text layer, nothing can read it to you — not this, not anything. Run it through OCR first. You can check a file here before you start.

Speed does not create familiarity. Below a certain level of vocabulary in a field, everything is high-density and everything needs the slow setting. Speed arrives with the vocabulary, not before it — which means the first textbook in a new subject is always slow, and that is correct.

Reading is not studying. Getting through the chapter faster gives you more time for retrieval practice and working the problems, which is what actually builds durable knowledge. It does not replace them. If you take the time you saved and spend it on more reading, you will forget most of it.

The honest summary

Speed reading is not wrong about textbooks. It is incomplete about them.

The technique does what it claims — it removes the mechanical cost of moving your eyes, and that cost is real. What it has never handled is that some books are not made of sentences alone, and that flattening those books throws away the half you cannot afford to lose.

You do not have to choose. You need the words and the page, in the same place, with your position held in both.

Try it on the textbook you have been avoiding.

Import the PDF. Read the prose at speed, stop at the equations, look at the figures where they are. Free, private, nothing uploaded.

Open ReadKinetic → · Reading textbooks and papers →

Keep reading: How to Read a Research Paper Fast · Speed Reading for Students · Does Speed Reading Hurt Comprehension? · How I Read for Medical School