A family recipe book that people actually keep has three things in it: twenty to forty recipes rather than a hundred, a photograph of the original handwriting next to the typed version, and two or three sentences about where each one came from.
The typed recipe is what someone cooks from. The photograph and the sentences are why they keep the book on a shelf instead of in a drawer.
Two questions that change everything downstream.
Who sets the tone. A book for your mother can assume shared history and say "the one Nana made at Easter." A book for a sibling moving out needs the context filled in. A book for a wedding gets read by someone marrying into the family, who needs the most explanation and will appreciate it the most.
How many copies decides the printing. One or two is a photo-book order. Twelve, for every cousin, is worth laying out more carefully, because you only want to do the proofing once.
Decide both now. Gathering recipes without knowing either is how projects stall at the halfway point.
This is the part that fails, and it fails for a predictable reason: "send me any family recipes you have" gets answered by nobody.
Ask each person for the one dish you associate with them. "Can you send me how you make the apple cake?" gets a reply, usually the same day. The request is specific, flattering, and small enough to answer from a phone.
A few things that help:
Do this first, while the cards are in your hands and before anyone starts transcribing.
A recipe scanner reads the card into a structured recipe and keeps the photograph of the original attached, which is exactly the pair you need for the book: the typed version for the page, the photograph for beside it.
Both halves of what the book needs, from one photograph.
If a card is going back to its owner, photograph it before it leaves. Cards that go home in coat pockets have a way of not coming back out again.
Tradish is launching on iOS and Android soon. Scan the cards, keep the handwriting and the story with each recipe, and share the collection with everyone who should have it. Join the waitlist for early access and our best launch price.
This is the difference between a recipe book and a family recipe book, and it takes two or three sentences per dish.
For each one: who it came from, when it gets made, and one memory. That is the whole formula.
Nana's apple cake. Made every Easter and for no other reason, in the same tin, which she would not replace. She measured the sugar in a teacup and refused to say which teacup.
Collect these while you are talking to people about the recipe, not afterwards. The anecdote arrives attached to the dish, in the same message, and trying to reconstruct it later is how you end up with thirty recipes and no stories.
In Tradish every recipe has a From section for this — the photo of the original, who it came from, where it sits in the family's year — which means the stories are gathered as you go rather than assembled at the end.
Resist designing it. The books that work are plain.
Keep the quirks in the text where they are charming and fix them where they are confusing. "Bake until it smells right" stays. A missing oven temperature gets a sensible one added in brackets.
Whatever service you print with, order one copy first.
Things that only show up in print: card photographs that looked fine on screen and are muddy on paper, type that is smaller than you thought, a recipe that runs four lines onto a second page, and the spelling of a relative's name.
Fix those, then order the rest. The proof costs one book and saves you from twelve wrong ones.
Finally, keep the digital collection after the book is printed. The book is the gift; the collection is the backup, and it is the thing you add to next year when someone sends you one more recipe.
Twenty to forty is plenty, and fewer well-chosen ones beats a hundred filler recipes. The test is whether someone in the family would recognise the dish, not whether it fills a page.
Yes, as photographs alongside the typed version. The typed version is what people cook from; the photograph of the card is what makes it a keepsake rather than a cookbook.
Ask for one specific dish rather than "any recipes," because a specific request gets answered and an open one does not. A photo of the card texted back is a perfectly good submission.
Who it came from, when it gets made, and one memory. Two or three sentences is enough, and it is the part people read first and could never reconstruct later.
Any photo-book service will do it, and a simple layout of one recipe per page with the card photo beside it prints well. Order a proof copy before you order the rest.
Ask for specific dishes, photograph every card before it goes home, write three sentences about each one, and lay it out plainly with the handwriting next to the recipe.
Then order a proof, fix what print reveals, and give it to people who will cook from it.
Tradish is launching on iOS and Android soon. Join the waitlist to be first to know when we launch.
Related reading: