To make a family cookbook, gather the recipes that matter from your relatives, save the original handwriting by scanning each card, write down the story behind every dish — when it was made, by whom, for what occasion — and add a photo of the dish and the table. Then group the recipes by section or generation and bind them into one book. The recipe is only half of it; the story and the handwriting are what make it your family's.

Every family has dishes that mean something. The Bessie Beef that only one aunt knows how to make. The potato goulash with smoked sausage that filled the kitchen every winter. The leg of lamb with mint jelly that meant it was a real occasion. Sunday dinners at grandma's. The crab sauce grandpa guarded like a secret. None of it lives in a tidy book. It's scattered across index cards, the backs of envelopes, a stained page torn from a magazine, and a few things nobody ever wrote down at all.

A grandmother's recipe is more than a list of ingredients. It's her handwriting — the way she wrote "a heaping spoon," the line she crossed out, the splash of gravy on the corner. Type it up and you keep the food. Keep the card and you keep her.

This matters even more when a family is spread across countries. For families separated by immigration and distance, the food of home is one of the few threads that still connects everyone. A cousin in another country who cooks the same dish from the same recipe is, for one evening, back at the same table. A family cookbook is how you hand that thread to the next generation. Here is how to build one.

How to Build Your Family Cookbook, Step by Step

Step 1

Gather the recipes from your relatives

What to do: Send a simple message to the family: "I'm making a cookbook of our recipes — send me the ones you'd be sad to lose." Ask for photos of the cards, not retyped versions. Some recipes will arrive complete; others will be "a bit of this, until it looks right." Write those down anyway, exactly as the person says them.

Why it works: Recipes hide in different places — one aunt's recipe box, a cousin's phone, a memory nobody has spoken aloud in years. Asking everyone at once turns a scattered archive into one collection, and it nudges relatives to dig out dishes you didn't even know existed.

Start today: Message three relatives and ask for one recipe each — the dish you most associate with them.

Step 2

Save the original handwriting

What to do: Before you type anything, scan or photograph the original card in good, even light. Lay it flat, fill the frame, and keep the file at full resolution. Save a copy in two places — your phone and a backup folder or drive. Do this for the stained, half-faded ones especially; those are the most fragile.

Why it works: The handwriting is the part that can't be reproduced. A clean typed recipe is easy to cook from, but the scanned card — the heaping spoon, the crossed-out line, the splash of gravy on the corner — is the part that makes a grandchild stop and feel like she's standing in the kitchen. Keep both: the scan for feeling, the typed version for cooking.

Start today: Photograph one handwritten recipe card flat, in daylight, and save it twice.

Step 3

Write down the story behind each dish

What to do: For every recipe, ask the person who makes it a few simple questions: When did you first cook this? Who taught you? What occasion was it for? Who always asked for seconds? Write the answers down right next to the recipe. Two or three sentences is enough — "Grandma made the leg of lamb with mint jelly only when the whole family came; it meant it was a real occasion."

Why it works: The story is what turns a recipe collection into a family cookbook. Anyone can find a goulash recipe online. Only your family knows it was potato goulash with smoked sausage, cooked every Sunday, by the one person whose kitchen everyone gravitated to. The story is the difference between food and memory.

Start today: Pick one dish and write three sentences about who made it and when.

Step 4

Add a photo of the dish and the table

What to do: Pair each recipe with two kinds of photo where you can: the finished dish, and the people around it. Cook the dish and snap it before everyone digs in. Then dig through old albums for a shot of a Sunday dinner, a holiday table, the kitchen the dish came from. If there's no old photo, the dish on a plate today is plenty.

Why it works: A recipe tells you how. A photo tells you why it mattered. Seeing the crab sauce next to a faded picture of grandpa at the head of the table connects the taste to the person — and that's the whole point of a family cookbook.

Start today: Find one old photo of a family meal and set it aside for its matching recipe.

Step 5

Organize by section or by generation

What to do: Once you have the recipes, give them an order. Two approaches work well. By section: starters, mains, holiday dishes, sweets — the classic cookbook layout. By generation: grandma's recipes, then your parents', then the ones you've added. Pick whichever tells your family's story better, and write a short intro for each part.

Why it works: Structure makes a cookbook usable, not just sentimental. Organizing by generation, in particular, shows how a family's table changed as it moved and grew — the dishes from the old country, then the ones picked up along the way. It reads like a small family history told through food.

Start today: Decide on your order — by section or by generation — and list your section names.

Step 6

Bind it into one book

What to do: Bring the recipes, the scanned cards, the stories, and the photos together into a single printed book, with one dish per spread: the recipe and its scanned card on one side, the photo of the dish and the story on the other. Print enough copies so every household that helped gets one.

Why it works: A folder of files gets buried; a book on the kitchen shelf gets opened and splattered and used. With EverStory, you bring the photos and the recipe cards and it drafts the story behind each one — you add the details only you remember, like who always asked for seconds — and end up with a finished cookbook where the recipe, the photo of the dish, and the family story sit on one spread, without doing any design yourself.

Start today: Choose the one dish your family would miss most and make it the first spread.

When a recipe lands on the page next to a photo of the dish and the story of the Sunday it was made, it stops being instructions. It becomes a seat at the table — one your grandchildren can take, in any country, for as long as they keep cooking.

A Few Things That Make It Better

Don't wait until the collection is "complete." A family cookbook is never finished — there's always one more dish, one more story someone suddenly remembers. Start with the five recipes your family would be saddest to lose, build the book around those, and add more later. A book with five dishes and their stories beats a perfect list that never gets made.

Keep the imperfect versions. The recipe that says "bake until it looks done," the measurement nobody can explain, the step grandma always did by feel — leave them in, with a note. Those quirks are part of the voice. If you smooth everything into clean, exact instructions, you keep the dish but lose the cook. The same instinct that saves a handwritten card applies to the words themselves.

If you're building a wider family keepsake, a cookbook pairs naturally with the photos and stories around it. The same recipes, tables, and faces that fill these pages belong in a family memory book too, and the stories behind the dishes are part of how you tell your family story across generations. Food is just one of the threads — but it's the one everybody shows up for.

Turn your family's recipes into a book

Bring the recipe cards and the photos of the dishes. EverStory drafts the story behind each one — you add the details only you remember — and it becomes a printed cookbook your whole family can cook from.

Start your book

Takes a few minutes · No design skills needed