Field note · Document formats

What a Page Can Do That a Slide Can't

Every document format carries a hidden assumption about where it will be read. That assumption is now the most important thing about it — and most of the formats we still default to are assuming a room we're no longer standing in.

An argument that runs itself. Every figure below is live — drag it, filter it, break it.

01 — The hidden assumption

Formats aren't neutral containers

We talk about file formats as though they were luggage: pick one, put the content in, ship it. But each of them was designed against a specific picture of how it would be consumed, and that picture is baked into what the format will and won't let you express.

Pick one and watch what it takes for granted.

Interactive · Pick a format Click to compare

A slide assumes a projector. A document assumes a page. A PDF is a photograph of a document. A page assumes a browser — the one surface that is actually in front of everyone.

None of this is an argument that slides are bad. A slide deck is a magnificent instrument for a specific job: pacing a room. The problem is that we kept using it for jobs it was never built for — asynchronous reading, exploration, reference, anything that outlives the meeting — because it was the tool sitting on the shelf.

02 — The demonstration

The same content, frozen and alive

Below is one small dataset. Flip the switch and it becomes the same chart in two different formats — first as it would arrive inside a slide, then as it arrives inside a page. The content is identical. What you can do with it is not.

Interactive · Format comparison
Slide format. The chart is an image. The filters are drawn on, but they don't do anything — the author already chose the view, three weeks ago, for a different question than yours.
Not available in this format

Selected total

—

◆ Synthetic data   Figures are invented for demonstration and describe no real organisation.

The point isn't that interactivity is impressive. It's that the static version silently answers one question and quietly forecloses every other one. Every reader who arrives with a different question — and they always do — has to email you. The interactive version absorbs that entire round trip.

03 — What a static figure costs

A slide shows one scenario. A page shows the space.

When the underlying thing is a model rather than a fact, a static chart is a screenshot of one guess. The reader's real question is almost never "what did you assume?" — it's "what happens if you're wrong?"

Interactive · Illustrative model

Four inputs, one curve. In a deck this is four separate slides that someone has to rebuild every time a number moves — and by the time they do, it's a different number.

Expected lifetime

—

Lifetime value

—

Payback

—

◆ Illustrative   A toy model shown to demonstrate live recomputation. Not a forecast, not benchmark data, not advice.

04 — Depth without length

A page can hold more than it shows

Print formats force a single decision about depth. Include the caveat and you bloat the document; cut it and you've overclaimed. A page refuses the trade — it can be short for the reader who wants short and deep for the reader who wants deep, in the same object.

Consider the claim that , which sounds authoritative right up until you ask where the number came from.

It came from nowhere. That sentence is a plausible-sounding statistic with no source, invented here to make exactly this point. In a printed deck it would have sailed past unchallenged, because print has no affordance for "show me." A page does. The cheapest thing a page can do — and the thing almost nobody uses it for — is let a claim carry its own evidence one click away, so that a weak claim is visibly weak.

The same mechanism handles the reader you didn't design for: the one who needs the definition, the derivation, the raw table, the dissenting view. .

In a deck, every audience you accommodate lengthens the deck for every audience you don't. That's why decks converge on a lowest common denominator and why the appendix exists — an admission that the format couldn't hold the material. Progressive disclosure dissolves the problem: depth becomes opt-in rather than imposed, and the document stops being a negotiation between incompatible readers.

Three lines of JavaScript. No plugin, no viewer, no version. It works in an email preview pane on a phone in an airport.

05 — One artifact, every screen

The layout is a function, not a picture

A slide is a fixed rectangle. Open it on a phone and you get the same rectangle, smaller. A page is instructions for arranging content against whatever space it finds. Drag the handle.

Interactive · Drag to resize —

Same document, same file, no second version. The 16:9 rectangle has no equivalent move — which is why the mobile experience of a deck is a pinch-and-scroll apology.

06 — The catch

So why is everyone still sending PDFs?

Because the document changed faster than the shelf it sits on.

Every capability on this page has been available in browsers for a decade. What hasn't caught up is distribution. Try attaching this file to a calendar invite. Try dropping it in a shared drive and having it render for a colleague instead of downloading as a blob. Try sending it to someone who should see it but shouldn't see everything else you've made.

The formats that dominate professional communication are not winning on expressiveness. They're winning on delivery — on the fact that a PDF opens for everyone, everywhere, with no explanation. That's a real advantage and it's the entire advantage.

The documents changed. The shelves didn't.

Which is a solvable problem, and a much less interesting one than it looks. Rendering isn't hard. Access control isn't hard. The reason it hasn't happened is that the platforms holding our files were built around a filing-cabinet metaphor at a moment when the most valuable thing in the cabinet has become a small piece of software.