How do I write a cookbook?
- Most cookbooks hold 75 to 120 recipes organized into six to ten chapters.
- Every recipe must be tested by someone other than the author.
- Headnotes are where the book's voice and usefulness live.
- Photography costs are the largest single expense in most cookbook budgets.
- Nonfiction cookbook proposals are sold on platform and concept as much as recipes.
A cookbook is an argument about how and why to cook something, supported by 75 to 120 tested recipes. Decide the point of view first, then build chapters that develop it. Headnotes carry the voice, recipe testing carries the trust, and photography carries the buying decision.
Chapter i·Why it matters
Recipe collections without a point of view do not sell, because the internet gives away recipes for free. What readers buy is a perspective: this is how a Sicilian grandmother makes it, this is weeknight cooking for people who work late. The recipes prove the argument; they are not the argument.
Chapter ii·What to include
- A one-sentence concept that explains who the book is for.
- Chapter structure that develops the concept rather than sorting by course.
- Recipes tested independently, ideally by strangers.
- Headnotes that add context, technique, or story, not filler.
- A consistent recipe format decided before writing 90 of them.
- A photography plan and budget, or a considered decision to go without.
Chapter iii·Example
A food writer reframed a general Italian cookbook as one hundred recipes from a single coastal town. The concept sold in three weeks after the general version had been passed on by eleven editors.
Chapter iv·Related questions
In WriteLoom
Somewhere to actually put the words
WriteLoom keeps recipes, testing notes, and chapter structure in one project so a hundred-recipe book stays navigable.
Not ready for a workspace yet? Get the free six-part series on winning the writing game: finishing drafts, editing in the right order, querying with real math, and launching on a runway.