The recipe, redesigned.

A recipe is a set of parallel processes with timing and dependencies. For five hundred years, we've written it down as a story.

Stories are read start to finish, once, sitting down. Cooking doesn't work like that. You stand, you juggle three things at different stages, your hands are wet, and the one fact you need — what goes into this pan, right now — is buried in paragraph four, two screens away from the ingredient list. So you scroll. Up to the amounts, down to the step, up again because you forgot whether the butter was melted or softened. The format fights the activity it exists to serve.

That's not a complaint about recipe writers. It's a complaint about a format — one nobody chose, one inherited from the cookbook and pasted onto the web unchanged.

In 2004, an engineer named Michael Chu quietly fixed it. On his blog, Cooking for Engineers, he drew each recipe as a table: ingredients down the left, in the order they're used; each step a cell spanning exactly the things it combines; everything converging, column by column, into one finished dish. The whole recipe in one look. No scrolling, no re-reading, no wondering which bowl. He drew every one by hand, and for twenty years that's roughly where the idea stayed.

We automated it. This is what it looks like:

Read it left to right: prep the ingredients, combine as the cells merge, done when everything has become one column. Read it top to bottom: your shopping list. The two questions you actually have in a kitchen — what do I need and what do I do next — answered by the shape of the thing rather than by searching prose.

And because a table is structure, not sentences, it can do what prose never could. You can't double a paragraph — but a table rescales itself to six servings, switches between cups and grams, lets you check off steps as pans hit the stove, and knows exactly which ingredients you still need to buy. Once a recipe has structure, it stops being a page you read and starts being a thing that works alongside you. That's the redesign — not prettier recipes, working ones.

One thing this doesn't replace: the writers. A table carries no technique, no context, none of the voice that makes a great recipe worth trusting in the first place. The story lives on their page; the cooking happens on yours. Every table converted from a link is credited and linked back to its source — that's the deal, and it's not negotiable.

RecipeTables turns any recipe into this format: paste a link, paste the text, or photograph a cookbook page. It's free, there are no ads, and converting is never gated — it runs on people who chip in rather than advertisers.