Somewhere in most families there's a recipe box, or a folder of handwritten cards, or a Google Doc someone started that never got finished. And somewhere in the same family there's a person who knows things about those recipes that aren't written anywhere.
How you save a family recipe depends on what you're trying to preserve. And the answer turns out to be: the two formats preserve very different things. Understanding that difference helps you get the most out of both.
What a Written Recipe Does Well
A written recipe is precise, searchable, and practical.
You can pull it out when you need it. You can print it and prop it on the counter while you cook. You can send it to a cousin who wants to make it for Thanksgiving. You can search for it by name. It doesn't require any technology to access beyond paper or a screen.
A good written recipe tells you the ingredients in exact quantities, the steps in logical sequence, the temperature and time, and ideally some notes about technique or common mistakes. It's designed to be used, not just read.
For a cook who has never made the dish before, a written recipe is usually what they need. It gives them enough structure to attempt the dish without guidance. It can be modified — scaled up, scaled down, adapted for dietary restrictions — in a way that a voice recording cannot be.
Written recipes also have a kind of permanence that feels official. There's a reason families write them down and keep them. The act of writing creates an artifact. It says: this matters, this is worth recording, this belongs to our family.
Where written recipes fall short:
They can't capture the sound of the right sizzle. They can't tell you what the dough should feel like. They can't convey "cook it until it smells done" in a way that actually teaches you anything if you haven't smelled it.
They also can't capture the story. A recipe card can say "Grandma Rosa's Sauce" at the top. It cannot tell you that Grandma Rosa learned it in 1952 from a neighbor in the tenement building, or that she always made it on Sundays so the whole floor could smell it, or that she cried the first time she made it after her mother died and the smell brought her back to the kitchen in Italy.
That story is not in the ingredients. And it's what makes the recipe a family recipe rather than just a recipe.
What a Voice Recording Does Well
A voice recording captures everything that doesn't fit on a card.
It captures the technique in the cook's own words — their description of what to look for, what to listen for, what to feel. It captures the exceptions: "I always do this when I'm making it for company, but when it's just us I skip this step." It captures the variations: "My mother added raisins and I never did — you can do it either way."
It captures the sensory descriptions that no written recipe can convey: "You'll hear the oil stop bubbling when it's ready." "It should smell slightly nutty, not burnt." "When you press it with a finger and it springs back, it's done." These are the descriptions of an expert who has made this dish a hundred times, and they are invaluable to someone trying to learn it.
Most importantly, a voice recording captures the story. The conversation will surface things the cook has never thought to write down: where the recipe came from, who taught it to them, what it means to the family, how it's changed over generations, what occasions it belongs to. These stories are the living context that transforms a recipe from a set of instructions into a family artifact.
Where voice recordings fall short:
They're not practical to cook from. You can't easily scan a voice recording for the quantity of an ingredient. You can't prop it on the counter and follow along step by step without stopping and starting it repeatedly. And as with all digital media, they require some kind of device to access.
They also need to be organized to be useful. An unlabeled voice recording buried in your phone's audio files is far less useful than a labeled, organized recording in a dedicated archive.
The Case for Doing Both
The ideal approach is both formats, used together.
Start with a voice recording. Have the conversation — in the kitchen if possible, watching the cook make the dish, asking questions as they go. Let the recording capture everything: the ingredient descriptions, the technique, the shortcuts, the history, the story.
Then use the voice recording to create a written recipe. This is different from writing a recipe from memory or asking for measurements. You have a complete record of everything the cook said. You can listen back and catch the things you missed in the moment. You can translate "a handful" into "approximately a quarter cup" based on what you observed. You can write down the sensory descriptions as notes alongside the ingredients.
The result is a written recipe that's more complete than anything you could have gotten by just asking for measurements — because the voice recording surfaced all the details the cook knows but wouldn't have thought to mention.
And then you have both: a practical document for cooking from, and a living record of the cook speaking the recipe in their own voice.
The Voice Recording as the Primary Document
There's an argument for treating the voice recording as the primary document and the written recipe as the derivative.
The voice recording is the original. It's what the cook actually said, in their actual words, in the moment. It's complete and unedited. It will never be more accurate or more complete than it is right now.
The written recipe is an interpretation. You decided what measurements meant. You formatted and organized what was a natural conversation. You made choices about what to include and what to leave out.
For family history purposes — for preserving the recipe as a cultural and personal artifact — the voice recording is more valuable. If you lose the written recipe, you can reconstruct it from the voice recording. If you lose the voice recording, you cannot reconstruct it from anything.
Treat the voice recording accordingly. Back it up. Store it in multiple places. Don't let it live only on one device.
When You Already Have a Written Recipe
If your family already has a written recipe for an important dish — a recipe card in Grandma's handwriting, a typed recipe from a family cookbook — the voice recording is still worth doing.
The written recipe tells you what to make. The voice recording tells you what it means.
Use the written recipe as a starting point for the conversation. "I have your written recipe here — can you walk me through it and tell me things you'd add?" This prompts the cook to review something they know, which often surfaces memories and details that didn't make it into the written version.
Ask about what's not in the recipe: the little things they always do that they didn't think to write down, the variations they use for different occasions, the things they'd change if they were writing it today.
Ask about the recipe card itself, if it exists. Who wrote it? When? Is there a version of this dish that predates the card?
The written recipe and the voice recording together give the fullest picture.
A Practical Starting Point
If you want to preserve a family recipe this week, here's a simple path:
Ask the cook if you can record them explaining or making the dish. Set up your phone. Let the conversation be natural.
After the recording, listen back and make notes. Write down every measurement, every technique description, every step.
Draft a written recipe based on those notes. Make it practical — the kind you'd actually use.
Keep both files: the recording and the written recipe. Label them clearly with the cook's name and the date.
Then make the dish yourself and have the cook taste it. Record that session too — feedback on the first attempt almost always surfaces additional details.
LifeEcho is built for exactly this kind of preservation. Record a cooking session on your phone, upload it to LifeEcho, and use the transcription feature to turn it into text you can work from. Keep the recording and the transcript together, organized by person and dish. Start today — with one recipe, one conversation, one session.