How to Make a Family Recipe Book

There is one instruction that matters more than every design decision in a family recipe book, and most people skip it: photograph or scan the recipe in the original handwriting before you retype a word of it. A typed recipe preserves the food. The photograph preserves the person — the shaky capitals, the splash of fat on the corner, the crossing-out where she changed her mind about the sugar in 1974. Retyping is for cooking from; the image is the heirloom. Do that first, record who each recipe came from and when, and then worry about fonts. To be sure how the contributor of each recipe is related before you label the page, check with the cousin calculator.

Photograph the handwriting first

Before sorting, before typing, before any decision about the book, capture what already exists.

Photograph or scan every card, page and scrap as it is. Stains, corrections, splashes and all. A recipe card that has been used two hundred times looks used, and that is the point of it.

Do this before you sort. Sorting is when things get separated, lent out and lost. Ten minutes with a phone gives you an insurance copy of the entire tin.

Use flat, even light and shoot square on. Daylight near a window, no flash, the card on a plain sheet of paper. Scan at 600 dpi if you have a scanner; the detailed handling and resolution guidance is in the guide to digitising family documents.

Photograph the back as well. Backs of recipe cards carry dates, names, shopping lists and the occasional note about who the recipe came from originally.

Print the image into the book, not just the transcription. The strongest layout is a two-page spread: the photographed original on the left, the tested, readable version on the right.

Keep the paper originals safely. Recipe cards live in kitchens and take punishment. Once photographed, store them flat and away from heat, following the same rules as in preserving old family photographs.

The recipes that exist only in someone's head

This is the urgent part of the project, and the reason not to leave it until you have time.

Many family recipes have never been written down at all. They live in one person's hands and disappear the day that person stops cooking. No amount of later research recovers them.

Cook it with them and weigh as you go. Take digital scales into their kitchen. When they reach for the flour, catch the bowl and weigh it. When they say "until it looks right", photograph what "right" looks like.

Record the audio while you cook. A phone on the worktop catches the asides — "my mother always used dripping" — that are the most valuable part of the session and that nobody thinks to write down.

Ask the questions around the recipe, not just the method. Who taught you? When did you last make it? What was it made for? A set of prompts from the family history interview questions works just as well standing at a hob.

Write down the failures too. "Do not use the fan oven, it burns the bottom" is the kind of note that only exists in a family recipe and is worth more than any measurement.

Do the oldest cooks first. If you make one recording this year, make it the one with the person who is eighty-three, not the cousin who is forty.

Collecting recipes from relatives

An open request produces nothing. A short form produces a stack of replies.

Send a form with fields, not an invitation. Recipe name, who it came from, roughly when, ingredients, method, and one line on when the family eats it. Six fields on one side of a page.

Ask for one recipe each, with a deadline. "Your best one, by the end of March." People freeze when asked for "any recipes you have" and reply immediately when asked for exactly one.

Send paper to older relatives and a form to everyone else. A stamped, addressed envelope has a startlingly high return rate among people who ignore email entirely.

Ask for a photograph of the original. Add one line: "if you have it written down anywhere, please send a picture of that too, however messy". This is where the best material comes from.

Chase once, kindly, then move on. One reminder doubles your returns. A third makes the project feel like a chore for everyone.

Collect in person where you can. A table with blank cards at a gathering catches contributions from people who will never post anything back; it belongs on the list of family reunion activities for exactly that reason.

Vague measurements, and how to handle them

Old recipes assume knowledge the reader no longer has. The job is to translate without erasing.

Never delete the original wording. Print the original line and put the tested equivalent beneath it in a different weight or in brackets. "A teacup of flour (about 120 g)". The original is the record; the conversion is the service.

Test before you convert. Cook it once, weighing everything as you go, and write down what actually worked in your kitchen. A conversion taken from a chart without cooking the dish is a guess in a serious costume.

Note the equipment and the era. Old ovens ran differently, flour was softer, and many pre-war recipes assume a solid-fuel range. If your version needed twenty degrees lower for ten minutes longer, say so.

Treat these as starting points, not authorities. Cup and spoon sizes were never standardised across households or decades, and the surviving teacup in the family cabinet is better evidence than any table.

Flag anything unsafe rather than reproducing it silently. Old recipes sometimes assume raw eggs, long unrefrigerated standing or preserving methods that are no longer considered sound. Print the original and add a modern note beneath it.

What every recipe page should record

A recipe with no provenance is just food. Six extra lines turn it into family history.

Whose recipe it is, by full name. "Nan" is meaningless to a great-grandchild. "Elsie Rowe (my grandmother, 1919–2003)".

Where it came from before that. Many recipes are inherited twice over — from a mother, a neighbor, a workplace canteen, the back of a packet in 1968.

When it was written down, and by whom. Add your own name and the date you transcribed it. Two generations on, that line answers most of the questions a reader will have.

When the family eats it. Christmas Eve, after funerals, the first cold Sunday of autumn. This is what makes a recipe book readable by people who do not cook.

One line of story. Not a paragraph. "Made every birthday until she moved to the bungalow" does more than half a page of description.

Any warnings or family arguments about it. Whether it should have raisins in. Families are consistent about these disputes and future generations find them delightful.

Layout and structure

The structure decides how the book is used, and whether anyone opens it after the first month.

Order by course or by person, not alphabetically. Alphabetical order is for reference books. A recipe book grouped by contributor reads like a family; grouped by course, it works in a kitchen.

One recipe per page, or one per spread. Recipes split across a page turn get abandoned mid-cook. If a recipe is long, shrink the type rather than running it over.

Left original, right transcription. The most satisfying spread in any family recipe book, and it needs no design skill at all.

Leave a notes box on each page. Room for the next cook to write what they changed. A recipe book that gets annotated is a recipe book that stays alive.

Add photographs of the food and the cook. A picture of the finished dish is useful; a picture of the person who made it, in her own kitchen, is the reason the book gets kept.

Include a contents page and an index. Two extra pages, and the difference between a book that gets used and a book that gets admired.

Printing and binding

Match the binding to how the book will be used, which is in a kitchen, with wet hands.

Spiral or wire binding lies flat. This is the single most practical choice for a book anyone will actually cook from. Perfect-bound books snap shut over the mixing bowl.

Ring binders with plastic pockets are the most forgiving. Wipeable, reorderable, and new recipes can be added for the next forty years. Less beautiful, considerably more useful.

Printed photo books look best and cost most. Excellent as a gift, and the file can be reordered whenever a new branch of the family wants copies. Consider it alongside the other options in the list of family tree gift ideas.

Laminate the pages you cook from most. Or print two copies — one to keep clean, one to ruin.

Print more copies than you need. The marginal cost of the fifth copy is small; setting the whole book up again in three years is not. Six copies across six households is also the best backup strategy there is.

Keep the source files and the scans in two places. The layout file, the original photographs and a flat PDF, backed up somewhere that is not the same laptop.

Sharing it and keeping it going

Give copies out rather than making one perfect object. A single beautiful book in one house is fragile. Six ordinary ones are effectively permanent.

Ask for corrections and additions in writing. Every recipient will spot something. Collect the corrections for a second edition rather than defending the first.

Add a page for the next generation. A blank template page with the fields already printed, so somebody's grandchild has an obvious way to contribute.

Keep the digital originals accessible. The photographs of the handwriting are the archive; the printed book is one expression of it. Store them the way you would any other family document.

Fold it into a wider project if you have one. A recipe section sits naturally inside a broader family memory book, and a researched narrative can borrow from it — the process for that is set out in creating a family history book.

FAQ

How many recipes do I need for a family recipe book?

Twenty to forty is a realistic and finishable book. Fewer than fifteen feels thin as a gift; more than sixty and the project usually stalls. Finish a small one, hand copies out, and let the corrections and additions build the second edition.

Should I retype recipes or keep the handwriting?

Both, on facing pages. The photographed original preserves the handwriting, the stains and the corrections. The typed version is what someone can actually cook from at eight o'clock on a weekday. Neither one replaces the other.

What do I do about a recipe nobody can make work?

Print it anyway, with a note saying it has not been successfully tested and what went wrong. An honest, flagged failure is part of the record. Silently rewriting it into something that works loses the original recipe entirely.

How do I handle recipes with no measurements at all?

Cook alongside the person who makes it and weigh every ingredient as it goes in. If that is impossible, make a tested attempt, record it as your version, and keep the original vague wording above it so nobody mistakes your guess for the source.

Is it worth making a digital-only recipe book?

As a backup, yes. As the only copy, no. Kitchens destroy devices, accounts close and file formats change. Print physical copies and treat the digital files as insurance rather than the finished thing.

Can children help make one?

Very effectively. Give them the job of interviewing one relative about one dish and writing it up in their own handwriting. Children ask the direct questions adults are too polite to ask, and their pages are usually the ones people read first.

Cook from it, and let it get dirty

Photograph the handwriting before anything else, then record who each recipe came from, who taught them, and when you wrote it down. Test the vague measurements, print the conversion beside the original rather than replacing it, and flag honestly anything you could not make work. Bind it so it lies flat, leave a notes box on every page, and print enough copies that the book survives a house move and a flood. Most importantly, cook the recipes that currently exist only in somebody's memory while that person is still standing at the stovetop to show you. Before you write a contributor's name onto a page, confirm exactly how they connect using the cousin calculator.