Rohman
Almost everything written about how to read faster is written by someone selling a course. So here is the number they tend to leave out: when researchers put sixty people in front of an eye tracker and tested a leading one-word-at-a-time reader against ordinary reading, the app ran at 209 words per minute. Ordinary reading ran at 200.
Nine words a minute. Not significantly different. Comprehension, meanwhile, dropped from 72% to 60%.
That is the honest starting point for this, and it is still not an argument against the technique. It is an argument for knowing what the technique is for.
What RSVP Actually Does
Rapid Serial Visual Presentation flashes words one at a time at a fixed point on screen. Your eyes stop moving; the text moves through them instead.
It began as a laboratory method for studying attention, not a productivity product. The mechanism is genuine: by pinning every word to the same spot, RSVP removes saccades (the small jumps your eyes make between words) and regressions (the backward flicks you make when something did not land). Good readers also line up each word on its optimal recognition point, a real perceptual finding about where in a word the eye recognises it fastest.
So far so good. The problem is the arithmetic of what that saves you.
The 10% Ceiling
Your eyes are not the bottleneck. Fixations, the pauses where you process a word, take 200 to 250 milliseconds each. Saccades take 20 to 40. Eye movement accounts for roughly a tenth of your reading time; the other nine tenths is your brain doing the work.
Remove 100% of the eye movement and you recover about 10%. Yet RSVP tools routinely advertise two to four times faster. That extra speed has to come from somewhere, and it comes from the part you cannot safely cut: the processing time, and the regressions.
Those regressions matter more than they sound. They happen 10 to 15% of the time in normal reading, and when researchers experimentally prevented them, comprehension fell. Re-reading is not a bad habit you should train away. It is the repair mechanism that makes reading work, and RSVP removes it by construction.
Pick a Gear, Not a Number
The most useful reframe I found is that reading is not one speed you optimise. It has modes, and each has a natural rate.
Memorising runs around 138 wpm. Studying something you will be tested on, about 200. Ordinary comprehension reading sits at roughly 238 wpm for non-fiction. That's the measured average across 190 studies and more than 18,000 readers, not the 300 wpm figure that circulated through textbooks for a century on thin evidence. Skimming reaches about 450, and scanning for a single fact, about 650.
Notice where the marketed range begins. Speed-reading products sell 500 to 1,000 wpm as a reading speed, when 450 and up is already the territory of skimming and scanning. They are not making you read faster. They are quietly changing what "reading" means, and charging for it.
Rayner and colleagues went through this literature carefully and concluded that rates above 1,000 wpm are not achievable without severe loss of understanding. The durable gains come from something much less marketable: reading more, across varied material, until word recognition gets automatic.
Where It Genuinely Earns Its Place
None of that makes RSVP useless. It makes it specific.
It works on short, linear text, the same kind early studies used when they found it matched ordinary reading. It helps when the screen is small enough that a normal column is awkward. It is legitimately useful for some readers for whom ordinary saccadic reading is itself the difficulty. And it is good at one particular thing: pulling you through a backlog at a forced pace so you stop re-reading the same paragraph while thinking about something else.
That last one is the real draw, and it is a discipline benefit rather than a perceptual one. A pace you cannot drift away from is worth something on a Tuesday afternoon.
Where it fails is predictable from the mechanism. Dense technical prose overloads it. Tables, code, citations and footnotes are structurally incompatible with a strictly linear word stream. There's no "jump back to the header row" in a format that shows you one word. And anything you need to retain in literal detail is exactly where the measured comprehension gap showed up.
Contracts, manuals, anything you will be held to: read those the slow way.
Speed Reading a PDF
- Open the Speed Reader
- Drop in a PDF, Markdown or text file, or paste text straight in
- Start at 300 wpm and let the slow-start ramp ease you in
- Press space to pause the moment something does not land
Speed runs from 50 to 1,000 wpm, and the arrow keys nudge it 25 at a time while you read. That's the control that matters most: you want to be adjusting constantly, not picking a number once. Smart pausing adds a beat at punctuation so sentence boundaries still feel like boundaries. Chunk size shows up to three words at once, which suits familiar material better than one-word mode does.
A reasonable way to use it: run the first pass at a pace that feels slightly too fast, mark what you want to revisit, then go back and read those parts properly. Triage, then read. That plays to the format's strength and avoids its weakness entirely.
The file is parsed in your browser and never uploaded. For the documents people work through — unpublished drafts, case files, medical records, anything under NDA — that is not a small detail. A backlog is a strange reason to hand a stranger your reading list.
Two Things Worth Doing First
Crop the margins if you'll also read it normally. A journal PDF on a phone is mostly whitespace, and Crop PDF gets the text filling the screen.
Check it has a text layer, too. A scanned PDF has no words to stream, only pictures of words. Run OCR first and it becomes readable text.
The point of any of this is not to hit a number. It is to spend your slow, expensive attention on the parts that deserve it, and move briskly through the parts that do not.
Try the speed reader — your file stays in the browser.
