The first thing you'll discover, when you actually sit down to make a family cookbook, is that your mother does not measure anything. Her chicken adobo is "soy sauce until it looks right." Her pie crust is "cold butter, about this much" — and she holds up two fingers. Her stuffing recipe lives, in its entirety, inside her head, where it has lived since 1974.
This is the real problem with family cookbooks. It isn't design or printing or even time. It's that the recipes you most want — the ones that taste like a specific kitchen on a specific Sunday — were never written down. They were performed. And the people who performed them are getting older, or already gone.
What follows is a workflow we've refined over hundreds of cookbooks. It's not the only way to do it, but it's the way that survives contact with reality: with relatives who don't answer the phone, with recipes that contradict themselves, with the brother-in-law who insists his version of the brisket is the real one.
Step 1: Decide what this cookbook is actually for
Before you do anything else — before you call anyone, before you buy software, before you spend a single hour on this project — decide who the cookbook is for and what it has to do.
There are roughly four kinds of family cookbooks, and the differences matter:
- The legacy book. Made for and about one specific person — usually a parent or grandparent. Maybe 30 to 60 of her recipes, with the story of where each came from. The audience is her children and grandchildren. This is the most common project we see.
- The reunion book. A community project across siblings, cousins, in-laws. Everyone contributes a few recipes. Often printed in a run of 20 to 50.
- The wedding-and-birth book. Given to a child who's leaving home, or a couple starting their own kitchen. Focused, around 25 recipes, with notes on what to make when.
- The memorial book. Compiled after a death, often within the first year. We've written a separate piece on this, but the workflow below applies.
The reason this matters: each book has a different reader, a different page count, and a different emotional register. A legacy book can be tender and slow. A reunion book has to handle Aunt Linda's six-page essay about her potato salad. Decide first, or you'll end up with a Frankenstein.
Step 2: Make the master recipe list before you call anyone
People will tell you, when you ask, that they have "no idea" what their mother used to make. This is almost never true. They've just never been asked to list it.
Sit down with a piece of paper and write out every dish you remember her cooking. Don't filter. Sunday roast, the burnt-edge brownies, the lentil soup she made when you were sick, the strange green Jell-O salad that appeared every Easter. Aim for 40 to 60 items.
Then send that list to your siblings, your father, your aunts. Ask them to add to it and to star the ones they most want preserved. You're not asking them to write recipes yet. You're asking them to vote.
What you'll get back is gold. You'll find out your sister has been thinking about the apricot bars for fifteen years. You'll discover your brother has no memory of the lentil soup but a violent attachment to a tuna casserole nobody else remembers. The overlaps are the must-haves. The disagreements are the interesting parts.
A good legacy cookbook holds 35 to 50 recipes. More than that and nobody cooks from it. Less and it feels thin in the hand.
Step 3: Get the recipes out of the cook's head
This is the hard part, and it's where most family cookbook projects die.
There are three ways to capture a recipe from someone who's never written one down:
Cook with them. Show up at their house with a notebook and a kitchen scale. Make the dish together. Weigh things as they go in. Time things. Note the visual cues — "until it looks like wet sand," "when it pulls away from the side." This is the gold standard. It's also expensive in time and travel, and it doesn't work if the cook lives across the country or can no longer stand at the stove for an hour.
Phone interviews. Call them and have them walk you through a recipe while you take notes. This works better than you'd expect, but it requires a real conversation, not a five-minute call. Plan for 30 to 45 minutes per recipe. Ask follow-up questions. The first pass will always be missing a step.
Video record them cooking. If you can be there, set up a phone on a tripod and let them cook while you ask questions. You'll capture not just the recipe but the way they hold the knife, the way they salt a pan from twelve inches above.
Whichever you choose, the rule is the same: ask for the story first, the recipe second. "How did you learn to make this?" gets you better information than "what's the recipe?" People remember procedures in context. They remember them through stories. When your aunt says, "well, my mother always used the heavy black pan, the one your great-grandfather brought over," you have just learned that the recipe needs cast iron — and you've learned why.
Step 4: Test every recipe before you print it
We can't stress this enough. The number-one regret we hear from people who self-publish a family cookbook is, "I wish we'd actually cooked from it first."
Recipes captured from a verbal source are always wrong the first time. The cook forgot a step. They underestimated a quantity because they've been doing it by feel for forty years. They left out the fact that you have to soak the beans overnight.
For each recipe, do a test cook. Have someone other than the original cook follow the written version exactly. Where it fails, write down where. Then call the cook back and clarify.
A few things you will almost certainly need to fix:
- Quantities by sight. "A handful of parsley" needs to become "1/4 cup, chopped." A "splash" of vinegar is a tablespoon, usually. A "good amount" of salt is more than you think.
- Pan size and heat. Almost no home cook will mention these unprompted. Ask. A 10-inch skillet on medium-high produces a very different result than a 12-inch on medium.
- Doneness cues. The crucial detail. "Until the edges pull away," "when it smells nutty," "when a knife comes out clean." These are how the cook actually knows. Get them on the page.
- Resting and cooling. Cooks who've been making a dish for decades forget to mention that the lasagna needs to sit for 20 minutes before you cut it.
Budget two to four months for testing. This is the longest phase of the project, and the one you can't skip.
Step 5: Write the headnotes
A recipe is a procedure. A recipe with a headnote is a piece of writing.
The headnote is the paragraph above the ingredient list that tells you what this dish is, where it came from, and why anyone should care. In a family cookbook, the headnote is the whole point. The recipe gets you fed. The headnote tells you whose kitchen you're standing in.
Good family-cookbook headnotes do three things:
- Locate the dish in a person and a place. "My mother made this every Sunday in the brick house on Elm Street, the one with the screened-in porch."
- Note something specific and sensory. Not "this was a family favorite" — that tells us nothing. Something more like, "the top would crack in three places, always, and she'd press the middle down with the back of a spoon."
- Tell you when to make it. Is this a Tuesday weeknight dinner or a Christmas-only project? Headnotes that orient the reader in the kitchen calendar get cooked from. The others sit on the shelf.
Keep them tight. 100 to 200 words. If you have a longer story — the family history of the dish, the immigration story behind the spice mix — give it its own page or sidebar. Don't bury it on top of the recipe where the cook can't find the flour.
Step 6: Photography (or no photography)
Here is the truth about family cookbook photography: it is harder than it looks, and a mediocre photo is worse than no photo.
You have three real options:
- No photos. Lean editorial, like a small Phaidon book. Works beautifully if your typography and layout are strong. Cheap to produce.
- Archival photos only. Black-and-white photos of the cook, of the kitchen, of the family table. These are emotional and they don't have to be perfectly composed. Scan everything at 600 dpi.
- One photo per recipe. The hardest option. Requires a real camera, real light, and a stylist's eye. If you go this route, shoot everything on the same surface in the same light. Consistency matters more than artistry.
A common, beautiful compromise: archival family photos throughout, plus one or two color food photos of the most iconic dishes — the wedding-cake recipe, the holiday roast. Used sparingly, they carry more weight.
Step 7: Design and layout
You do not need to be a designer. You do need to make a few decisions and then stop second-guessing them.
Trim size. 7x9 or 8x10 is standard. Smaller feels personal; larger feels like a reference book. We recommend 7x9 for legacy cookbooks. It sits well in the hand and on the counter.
Typography. Pick two typefaces — one serif for body text, one for headlines. That's it. No script fonts. No decorative fonts. The recipe has to be readable while you're cooking, with flour on your hands, in indifferent light.
Recipe format. Choose one and use it for every recipe. The standard works: title, headnote, yield and time, ingredients list (left column or top), method (right column or below). Don't get clever.
Section organization. Resist alphabetical. Organize the way a person cooks: starters, soups, weeknight, Sunday, holidays, sweets, the basics (her bread, her stock, her pie crust). The reader navigates by occasion, not by ingredient.
Tools that work for this if you're doing it yourself: Adobe InDesign (steep learning curve, professional result), Affinity Publisher (cheaper, almost as good), or Canva (limited but usable for a simple book). If you have any budget at all, hiring a book designer for 1,500 to 3,000 dollars will save you forty hours and produce something dramatically better.
Step 8: Print it
Three real paths here:
Print-on-demand. Services like Blurb, Lulu, and Mixam will print one book at a time, hardcover, for 35 to 80 dollars per copy. Quality is good, not great. Best for small runs of 5 to 25 copies.
Short-run offset. Real bookmaking. 50-copy minimum, usually. Better paper, better binding, dramatically better feel. Costs 25 to 45 dollars per copy at quantity. Best for reunion books where everyone wants one.
A specialized service. Companies that focus specifically on family cookbooks (Hearth is one; there are others) handle the recipe collection, design, and printing as one workflow. Expensive per copy, but the bottleneck isn't money — it's the months of work you don't have.
Whichever you choose, order one proof copy before you order the full run. Always. There will be a typo. There is always a typo.
Step 9: Make it easy to actually cook from
A cookbook lives in the kitchen. A book that can't lie flat, can't take a splash of olive oil, or has text in 9-point gray-on-cream — that book lives on a shelf.
Specs that matter:
- Lay-flat binding (smyth-sewn or otterbinding). Spiral works but cheapens the object.
- Coated, wipeable paper or, at minimum, uncoated paper heavy enough not to wrinkle.
- Type at 10 to 11 point for body, 12 to 13 for the ingredient list.
- High contrast. Dark text on light paper. Save the moody photography for the dividers.
If the cook in your family can't read the type without glasses, the book has failed.
Step 10: Give it on the right day
When you finish — and you will finish, eventually, after the third round of edits and the proof that came back with the wrong paper — give the first copy to the cook. Not at the holiday dinner with twelve people watching. Quietly. Just the two of you. Let her sit with it.
She will turn to the recipes you'd forgotten. She'll correct one of them. She'll cry, and then she won't, and then she'll start telling you a story about her own mother that you've never heard. That story is the next book.
Hearth captures the recipes and the stories behind them through AI phone interviews with the cook in your family, then prints the result as a hardcover book — for the families who want the book but don't have the months it takes to make one.