Against the Speed of Reading

We are told, often and cheerfully, that the future of reading is faster. The book summarized in ninety seconds. The novel compressed into a paragraph by a machine that has read it, or claims to have. The reading app that promises to double your speed, as if a sentence were a road to be driven down rather than a room to be entered. We want to say, plainly, that we do not believe in any of it — and that this press exists, in part, to argue the opposite case. We publish deliberate fiction, and deliberate fiction is written to be read slowly. That is not a defect we have overlooked. It is the point.

The case for speed rests on a quiet assumption: that a book is information, and information is best delivered quickly. But a work of fiction is not information. It is an experience, and experiences do not compress. You cannot summarize the last page of a Chekhov story and hand a reader what the story actually did to them, any more than you can summarize a piece of music and call it listening. The thing a deliberate sentence does happens in time, at the reader's own pace, and it cannot be done for them by anyone else, human or otherwise.

This is why the fiction we publish asks for patience, and why we are not sorry about it. A story that withholds its meaning, that leaves a silence where an explanation might have gone, that requires the reader to sit with an ambiguity rather than resolve it — such a story is not failing to communicate. It is communicating in the only way that lasts. The reader who stays with it is not being inconvenienced. They are being trusted. And trust, once given, is the only thing that makes a reader willing to be changed by a book, rather than merely informed by it.

We are aware that this is a minority position in 2026, when attention is the scarcest thing most people have and every platform is built to harvest it. The machines that summarize books are not evil; they are merely indifferent to what a book is for. The danger is not that a reader will use them. The danger is that a reader will come to believe the summary is the book — that the point of reading is to get through it, to have read it, rather than to be changed by it. We have watched this happen. It is a quiet loss, and it is happening to people who do not know they are losing anything.

So we offer a small exercise, for anyone who wants to remember what reading was for. Take a story you love — one you have already read. Read its first page aloud, slowly, and stop. Do not go on. Ask what the first sentence is doing that the second sentence could not do, and what the second is doing that the first could not. Ask where the writer chose a short sentence and where they let one run long, and what each choice cost. Then read the page again, and notice what you missed the first time.

That noticing — the second pass, the thing you did not see until you looked twice — is the whole argument. It is the thing speed cannot give you, and the thing a summary will never contain. A book read twice is not the same book. A book read once, quickly, is not quite a book at all; it is a receipt for a book, proof that you were in the room without ever having sat down in it.

We read slowly here. We publish for readers who do. If that sounds like a small audience, it is — and we would rather be read well by a few than skimmed by many.

— The Editors