How to preserve family recipes — with video, not just cards

What a recipe card cannot hold

Most family recipes were never written down as instructions. They were written down as reminders — a list of ingredients, a temperature, a time. The person writing them already knew how the dough should feel, so they never wrote it.

That is why a recipe you inherit so often tastes almost right. The measurements survived. The judgment did not. "Cook until done" meant something precise to the person who wrote it, and nothing at all to you.

The parts that go missing are consistent, and they are all visual or physical: how thick the batter runs off a spoon, how dark the onions go before the next step, how much salt a hand actually holds, how long a thing rests before it is cut.

Record the cooking, not the recipe

The instinct is to sit someone down and interview them. It rarely works. People cannot describe motions they have stopped thinking about, and being questioned makes them self-conscious.

What works better is to film them doing what they were going to do anyway. Cooking occupies the hands and the attention, so the explaining becomes incidental — and incidental explaining is where the real instructions live.

• Prop the phone against something on the counter. A stack of books works. Do not hold it.
• Frame the hands and the pan, not the face. You are recording technique, and it makes people less self-conscious.
• Do not stop them to re-do a step. The mistakes and corrections are the most useful footage you will get.
• Ask one question when they add something: "how do you know when it is enough?" Then stay quiet.
• Record the messy middle. The beginning and the plating are the least informative parts.

Short clips beat one long film

A forty-minute unbroken video is a recording nobody will ever watch again, including you. It is also fragile: one corrupted file and the whole dish is gone.

Break it by step instead. One clip for the sauce, one for the fold, one for the sear. Short clips are easier to shoot, easier to find later, and they map onto how the dish is actually cooked.

If you only manage one clip per dish, make it the step that is hardest to describe in words. That is the step the written recipe already failed to carry.

Write down only what the video misses

Video is bad at quantities and shopping. Text is bad at motion and judgment. Use each for what it is good at instead of duplicating both.

A workable minimum is: the ingredient list with amounts, the name whoever taught you called it, and roughly when they used to make it. Everything else can live in the footage.

One line of context is worth more than a paragraph of instructions later on. "My mother made this every Chuseok, and she always doubled the garlic" tells a grandchild more than a perfectly formatted method.

Store it where someone will find it

Most family recipe videos die on a phone. The phone fills up, gets replaced, or gets lost, and nobody knew the videos were there in the first place.

Wherever you keep them, two things matter more than the platform: someone other than you must be able to find them, and the file must survive your next phone. A shared cloud folder with a clear name does both, and it costs nothing.

Disclosure: we build Lumiere Dish, a free app made for exactly this — short recipe videos kept together with the people they came from. It is one option among several, and a shared folder you actually maintain beats any app you abandon.

Start with the dish you would miss most

Do not build a plan to archive everything. Plans like that produce nothing. Pick the single dish whose loss would hurt most, and record that one the next time it gets made.

The occasions when these dishes get cooked are limited and predictable — holidays, birthdays, the visit home. There are only a handful of chances per year, which is the real reason these recipes get lost. Not carelessness. Arithmetic.