Standard recipe format: the three ways recipes are written, and the one that fits on a page

Every recipe you have ever read uses one of three formats. Cookbooks and culinary schools teach the standard format; old family cards and food blogs drift into thenarrative format; a few technical writers use the action format. All three share the same flaw. This page explains each, then shows the fourth option that fixes the flaw: the grid.

1. The standard recipe format

The standard format has three parts, in this order:

• Header: title, yield, prep time, cook time, sometimes a one-line description.
• Ingredient list: every ingredient with its quantity, listed in the order it is used.
• Method: numbered steps, each starting with a verb ("Whisk", "Fold", "Bake").

Culinary schools call this the "standardized recipe" and it is genuinely good at what it was designed for: shopping and scaling. You can read the ingredient list at the store and you can double it without reading the method. Its weakness shows up at the stove: the amounts live in one place and the actions in another, so you keep re-reading both to work outhow much of this goes in now.

2. The narrative recipe format

"Cream a stick of butter with a cup of sugar, then beat in two eggs…" — amounts and actions woven into paragraphs. This is how recipes were written before the twentieth century and how a grandmother writes them on a card. It reads beautifully and is the worst format to cook from: there is no way to see the shopping list, no way to find your place after looking away, and quantities hide mid-sentence.

3. The action recipe format

A hybrid: each numbered step lists only the ingredients that step needs, right next to the instruction. It solves the "how much goes in now" problem of the standard format, at the cost of the shopping list — the ingredients are scattered across the steps — and it gets long, because every step repeats its own mini ingredient list.

The flaw they all share

Cooking is a tree, not a list. Wet ingredients combine, dry ingredients combine, the two meet, and the result goes in the oven. Prose can only present that one sentence at a time, so you rebuild the tree in your head every time you cook the dish. The reason so many web recipes come with a "Jump to Recipe" button is that the format itself makes people scroll.

4. The grid (tabular) recipe format

In 2004 an engineer named Michael Chu drew the tree as a table on his siteCooking for Engineers. Ingredients with amounts run down the left. Each step is a cell to the right that spans the rows it combines. The final step spans everything. The table's shape is the method:

Read it top-left to bottom-right. Melt the butter, mix in the sugar, mix in the eggs, fold in the flour, bake. You can see that the eggs go in after the sugar without reading a sentence, and you can see how much of each thing there is at the moment you need it. It keeps the standard format's shopping list (the left column) and the action format's "what goes in now" (the cells), and adds what neither has: the whole structure in a single glance.

Which format should you use?

• Publishing a cookbook or blog: standard format, because readers and search engines expect it — and add the grid as the printable version.
• Cooking at the stove, taping a card inside a cupboard, teaching someone: the grid, because it is the only format you can read without losing your place.
• Preserving a family recipe: keep the handwritten narrative card for the memory, and make a grid to actually cook from.

Turn any recipe into the grid format

You do not have to redraw anything. Photograph a recipe card or cookbook page, or paste a link to a recipe page, and GridRecipe converts it into the grid — the first one free, no account needed. Prefer to type? The free builder makes the table for you, and there is a blank printable template if you want to write it by hand.