A family cookbook sounds like a retirement project — something you start when you have *time*. It isn't. With a little structure, you can collect the recipes, arrange them, and hold the finished book after a single Sunday. Here's the method we use ourselves.
The mistake most people make is treating it like an archive: every recipe, perfectly transcribed, in chronological order. That's a multi-year project, and multi-year projects don't get finished. A family cookbook is not an archive. It's the forty dishes your family would actually grieve, arranged so people cook from them. That fits in a weekend — and here's how the weekend goes.
Start with the recipes that matter
Before you touch a scanner or open an app, decide the size of the book. We like the ten-to-forty rule: fewer than ten recipes and it feels like a pamphlet; more than forty and you'll still be typing at Christmas. Twenty-five is the sweet spot — a real book, achievable in one sitting.
Then ask the family. Not "what recipes should we include?" — that question gets you a shrug. Ask instead: if this dish disappeared forever, would you miss it? The soup that means someone's home. The cake that shows up at every birthday. The thing your uncle burns slightly, every time, and everyone loves anyway. Write down the answers as a simple list. That list is your table of contents.
One warning: this conversation is the best part of the whole project, and it will tempt you to keep going. Someone will remember a forty-first dish. Someone else will want to relitigate the dumpling filling. Write it all down and keep moving — a second edition is a wonderful problem to have, and it's only possible if the first one exists.
- Aim for ten to forty recipes; twenty-five is ideal.
- Ask each family member for the three dishes they'd grieve.
- Include at least one recipe from the oldest cook in the family.
Gather everything in one afternoon
Set a timer for two hours and collect, don't organize. Photograph the index cards, the stained cookbook pages, the back-of-the-envelope versions. Don't retype anything yet — a photo of the original is worth more than a clean transcription, because it keeps the handwriting.
For the recipes that live in someone's head, dictate while cooking. Call your grandmother, put her on speaker, and cook the dish with her. Write down what actually happens — "a little more until it smells right" is the instruction. The tidy version can come later; the true version can't.
And use the laziest capture tool you have. We built the forever.recipes Telegram bot for exactly this: forward a photo of a recipe card or a voice note from the family group chat, and it lands in your book draft. No app to open, no folder to maintain — the pile builds itself while you cook.
Two small habits make the pile useful later. First, photograph the whole card, not just the ingredient list — the stains and the handwriting are part of the recipe, and they deserve a place next to the typed version. Second, record the source in one line: who it came from, and when. "Rosa's card, photographed at Easter" is exactly the kind of detail the next generation will read twice.
Measure the pinches with real spoons as you go. "Until it smells right" deserves a number.
Arrange chapters people will actually use
Resist alphabetical order — nobody cooks alphabetically. Choose a structure that matches how your family thinks about food, and commit to it. Three structures work almost every time:
- By person — Grandma Rosa's chapter, Uncle Marco's chapter. Best when the cooks are the story.
- By meal — breakfasts, Sunday lunches, the holiday table. Best when the book will actually live in the kitchen.
- By occasion — birthdays, the first cold day, the recipe for when someone's sick. Best as a gift book.
If you're stuck, look at ready-made structures and steal one — our templates exist for this. The arrangement matters more than the typography: a chapter called "the birthday table" gets cooked from; a chapter called "D–G" does not.
Add the notes that make it yours
Here's the secret of every beloved family cookbook: the recipes are not the point. The margin notes are. "Room-temperature tomatoes, never from the fridge." "Dad always burns the first one — that's the cook's portion." "Make double; your cousin will appear." A recipe stripped to bullet points could be anyone's. The notes are what make it yours.
So transcribe them verbatim, in the voice they were said. Don't polish away the warnings or the little jokes. Give each note room on the page — next to the recipe it belongs to, in a handwriting-style face if you can. Future cooks will thank you for the quantities, but they'll love you for the notes.
Print it, share it, gift it
A folder on a phone disappears when the phone breaks. So make the book physical: forever.recipes gives you an editorial print view — recipes on clean pages, notes in the margin, photos where they belong — and a PDF you can take to any printer or keep as a backup. For the family abroad, share the book as a link with a QR code on the last page, so the cousin in another country gets the same book without a parcel.
Ten recipes are free to start, and the printed options are on the pricing page. Order at least two copies: one for the kitchen, and one that mysteriously stays wrapped for the next birthday.
Think about who the book is for and print for that table: one copy for the kitchen that does the cooking, one for each household that scattered, and one that stays pristine. A bound book with your family's name on the spine is the rare gift that gets more valuable every year — and the one thing nobody will ever regift.
The one-Sunday plan
Here's the whole thing as a timed checklist. Coffee is assumed throughout. The plan works for one person driving with the family on call — and if two of you split it, one typing and one gathering, you'll be done by mid-afternoon with time left to argue about the dumplings.
- 9:00 — Make the list: ten to forty recipes, asking the family by text while the kettle boils.
- 10:00 — Gather: photograph every card, page, and screenshot; forward strays to the Telegram bot.
- 12:00 — Cook one recipe with the person who knows it, and dictate the real version.
- 14:00 — Type the recipes into forever.recipes, notes and all.
- 16:00 — Arrange the chapters: by person, by meal, or by occasion.
- 17:00 — Check the print view, order the PDF or the bound copies, and pour something nice.
That's the whole method: collect, arrange, hold. The recipes were already yours — now they're on a shelf, splattered and handed down, instead of scattered across four phones. When you're ready, make your own cookbook and start with the dish you'd miss most.
The forever.recipes team