You don't have to choose between speed and comprehension

Speed reading earned its bad reputation. But the research kills a technique, not the idea — because "reading" was never one thing to begin with.

When people hear "speed reading," a quiet flinch is almost universal. It sounds like a trick — the kind of productivity-hack promise that always comes with a hidden cost. Read faster, sure, but at what? Retention? Pleasure? The actual act of thinking about what you just read?

That flinch is earned. For fifty years speed reading has been sold as a technique you can apply to any text: skim the page in a Z-shape, train your peripheral vision, expand your chunk size. The research on those techniques is consistent — above about 500 words per minute, comprehension craters. You can absolutely move your eyes across a page at 1,000 wpm. You just can't remember much of what you saw.

So it's tempting to conclude the whole category is bunk. But that conclusion smuggles in an assumption: that "reading" is one thing, and speed is a dial you can turn without changing what you're doing.

It's not. And once you notice that, the design space opens up.

Reading is three different activities wearing the same hat

Sometimes you're reading for pleasure — a novel, a long piece of journalism, a well-crafted essay. You want to savor it. Speed is irrelevant. Slowness is a feature.

Sometimes you're reading to learn something dense — a textbook chapter, a technical spec, a legal document. Your goal is a mental model. You'll stop, backtrack, look things up, stare at the ceiling. Speed is worse than irrelevant; rushing through a passage you didn't understand is throwing away time, not saving it.

And sometimes — the hidden third category — you're reading the way you'd fast-forward a familiar audiobook. Important enough to have on your radar, not dense enough to deserve full attention. Most news. Most blog posts. Most memos. Most of the pile in your save-for-later list. You want the ideas to land and the interesting bits to stand out enough that you know where to slow down. You don't need to remember every sentence.

That third mode is where speed reading's reputation is most unfairly trashed. The research that kills traditional speed reading was run on comprehension-demanding material. But a lot of daily reading doesn't demand deep comprehension — it demands sufficient comprehension. Enough to know what's there. Enough to decide whether to come back. Enough to be conversant without being fluent.

For sufficient comprehension, speed isn't a corner you cut. It's a tool.

Change the medium, not the reader

Rapid serial visual presentation — RSVP — displays words one at a time at a fixed point on screen, advancing at a rate you set. The key insight isn't that it's fast; it's that your eyes stop moving. The saccades and fixations that fragment attention are gone, along with the constant hunt for the start of the next line. One word lands on one focal point, and more of your mind is free for the meaning.

There's a detail most apps skip. In every word, one letter is tinted red — the Optimal Recognition Point, the spot your eye naturally lands on to recognize a word fastest. Velo computes it per word and holds it locked to the same pixel, so your gaze never re-aims. That's the difference between a gimmick and something you can do for twenty minutes without a headache.

The research on RSVP is more interesting than the research on eye-movement speed reading. At very high rates comprehension does suffer, especially on unfamiliar material — but the fall-off is gentler, and on familiar-genre content a practiced reader holds 400–600 wpm with comprehension indistinguishable from their natural rate. Roughly 2–3× a typical reader, without the Z-shaped self-deception.

And RSVP rewires the experience. It's closer to how you consume audio: a rhythm, a texture, a current you're standing in. Some things work beautifully in it — journalism, narrative nonfiction, well-structured essays. Some things don't, and we'll get to that, because it matters.

Now turn the dial the other way

Here's the part the speed-reading industry never noticed about its own technique.

Everything that makes RSVP fast — one word, one focal point, no visual field to wander across — also makes it the most focusing way to read that exists. Turn the rate down instead of up and RSVP becomes an attention aid: a way to stay present inside a dense passage you'd otherwise skim, or inside any passage, on the days your brain won't hold still.

If you've ever read the same paragraph four times and retained nothing — if your eyes slide off the page while your mind goes somewhere else — the failure usually isn't comprehension. It's that a full page is a wide-open field, and your attention can wander anywhere in it. RSVP closes the field. The next word appears exactly where you're already looking. There's nowhere for your focus to go but forward — and you can set the pace slower than you read on paper and finish more, because you never lose the thread.

Nobody sells this, because "read slower, comprehend more" doesn't fit on a speed-reading landing page. It's the feature I ended up caring about most.

What we built

Velo has two ways to read, because those relationships with a text deserve different surfaces.

RSVP, for when the article is long and you want to plow through — or when you want the focus lock, at whatever speed. 50 to 1,000 wpm; you drive.

Reader, for when you want to read the way you've always read. Quiet, still, paginated, yours — with highlights and notes.

Between them sits Scrub — not a third way to read so much as a hand on the stream. RSVP's classic weakness is that a word stream has no geography: miss a beat and there's nothing to glance back at. In Scrub the text flows as a horizontal ribbon under your finger, as fast or slow as you drag — like scrubbing an audio waveform. Rewind a sentence, skim ahead, find your place, let go, and you're reading again.

What makes any of this worthwhile is the bridge. Pause RSVP at word 1,847 of a 50,000-word book and switch to Reader, and you're at word 1,847 of the Reader view. No mental bookmark, no "where was I." The switch takes under 100 milliseconds, and every surface — RSVP, Reader, the scrubber between them — shares a single word-level position. Not through clever bookkeeping, but because they're all views of the same underlying structure: every book gets parsed into a content tree — chapters, paragraphs, footnotes, images, emphasis — and each surface renders from that tree.

That sounds like an implementation detail. It's the whole point. Most reading apps feel like something's missing because they treat reading as one thing. Velo treats it as more than one thing sharing a substrate, so you can change your mind about how to read mid-chapter without losing your place.

It also means Velo can take on the ugliest input there is: the two-column, footnoted, scanned academic PDF. The import pipeline detects chapters, links footnotes, strips running headers, resequences columns, and OCRs scans — because a mode-switching reader is only as good as what it can actually open.

Where it fails, honestly

RSVP is wrong for poetry. It's wrong for prose whose pleasure is in the sentence. It's wrong for equations, tables, and figures — anything whose meaning lives in spatial layout. A speed-reading app that pretends otherwise is lying to you.

Velo's answer isn't a workaround; it's the architecture. The moment you hit a theorem or a figure, one tap drops you into Reader mode at the exact word, layout intact. Both ways of reading exist because no single one fits a whole book. And when you come back to a book after a week, an on-device "catch me up" recap (Apple Intelligence, on the Mac today) re-enters you without re-reading — computed on your machine, because your library and your highlights are nobody's training data.

What speed reading gets right, once you drop the dogma

Not every book deserves to be read. Not every article deserves an hour. Not every text you engage with deserves the same level of engagement.

The honest version of speed reading — the version nobody sells, because it's less marketable than "a novel in 30 minutes" — is matching the medium to the material. Some things slow down. Some things speed up. Some things you bounce between at will. If you keep a read-later graveyard in Pocket or a highlights pipeline in Readwise, you already know the collecting isn't the problem. The processing is.

That's what Velo is: not a productivity tool, exactly, but a reading app that takes seriously the fact that you read differently at different times — while the apps have been quietly insisting you shouldn't.

It started as a weekend fork of a tiny MIT-licensed demo that flashed words on a screen. Some 1,400 commits later it's a native app for iPhone, iPad, and Mac that I use every day.

Velo is on the App Store now. The free tier is genuinely free — import three of your own books or articles, plus an unlimited public-domain library, no account required. If the ideas in this essay sound like how you actually read, come try them.

Read quickly. Comprehend deeply.

— Ben

← More writing & guides