How to Save a Recipe You Saw, Tasted or Tweaked (Without Another Recipe Box)
A recipe you saw, a dish a friend made, a tweak you swore you'd remember: here's how to catch each one in the moment with a photo, a voice note or a single line, so it's there the next time you cook.
The best way to remember a recipe you saw is to catch it before you walk away. Save the link and take a screenshot of the ingredients. For a dish at a friend's house, photograph the card or record them telling you how they made it. For your own changes, say them out loud into your phone while you cook, or write one line once you've eaten.
You don't need a new recipe box or an elaborate system. You need something that takes five seconds, done while the details are still fresh. The rest of this guide covers how to remember a recipe you saw on a screen, how to get one out of a relative who never measures, and how to keep track of "less salt, 10 more minutes" so you aren't guessing again next time.
Why recipes slip away so fast
Recipes slip away for two reasons.
First, memory for new details fades quickly. Hermann Ebbinghaus's forgetting curve, replicated in a 2015 PLOS ONE study, describes how forgetting is steepest soon after we learn something. You may remember the dish was great. A few days later you won't remember it had two tablespoons of fish sauce, not one.
Second, recipes reach you at bad moments. You scroll past a video on the bus. Your aunt explains her stew while clearing plates. You change the oven time with flour on your hands. None of these are moments when you'd sit down and type out a tidy recipe card.
So the trick is to capture something rough right away and tidy it later, or never. A blurry photo you can find beats a perfect card you never wrote.
How to remember a recipe you saw on a screen
Recipes on screens look easy to keep. They're already written down, after all. In practice they can vanish. Videos scroll away, posts get deleted, and blog pages get rewritten. Some never had a written recipe at all.
Save the link and the important part
Do two things together:
- Save the link. It's your way back to the original, with the photos, the method and the comments.
- Screenshot the ingredients and key steps. This is your backup if the page changes or the video disappears. For a video with no written recipe, pause on the frames where quantities appear, or jot them down as you watch.
A screenshot alone is fragile. It sinks into your camera roll among hundreds of others, with nothing to tell you what it was. If your photos are already full of these, see how to stop using screenshots as notes.
Add the words you'll search for later
When you save it, add a few words about how you'll think of it later. Not just "chicken recipe," but "the crispy chicken thighs with lemon from that Saturday video." Think of the words you'd type when you're hungry in three weeks: the main ingredient, the cuisine, where you saw it, and why it caught your eye ("one pan," "15 minutes," "kids might eat this").
That single sentence matters more than the folder you put it in. It's often easier to remember a detail of a recipe than where you filed it.
How to save a recipe from a friend or relative
A recipe someone tells you out loud is easy to lose and hard to get back. Many family recipes exist only in one person's hands. If you want to save a recipe from a friend, or from a grandparent, treat it as a short interview.
Photograph the card, both sides
If there's a written card, take a recipe photo: save it on the spot, front and back. Old cards often have notes in the margins or on the back ("double for Easter," "use the small pan"). Shoot in good light, flat on a table, so the handwriting is readable. Then add a line saying whose recipe it is and when you got it. A photo of handwriting is also worth keeping for its own sake.
Record them talking you through it
If there's no card, ask whether you can record them on your phone while they explain, or better, while they cook. People who cook by feel describe things they'd never think to write down: what the dough should feel like, what smell means it's ready.
Later you can turn the recording into text if you want a written version. The guide to turning a voice memo into text on iPhone covers the free built-in ways.
Pin down the vague parts
Home cooks often use measures that only make sense in their own kitchen. Ask a follow-up for each one, right then, while they can show you.
| They say | Ask this | What to write down |
|---|---|---|
| "A handful" | "Can you grab it so I can see?" | Measure their handful in a cup or on a scale |
| "Until it looks right" | "What does right look like?" | The colour, thickness or texture they mean |
| "A glass of milk" | "Which glass?" | The volume of that glass |
| "Bake it a while" | "About how long, at what heat?" | A time range and the oven setting |
| "My usual pan" | "What size is it?" | The pan size, or a photo of it |
| "Some spice mix" | "What's in it, or what brand?" | The brand name, or a photo of the jar |
If you can, watch them make it once and write down what they actually do, not what they say they do. The two often differ. For more on catching spoken instructions, see how to remember instructions someone gives you out loud.
Write down the dish, even if you didn't get the recipe
Sometimes asking for the recipe would be awkward, or the host is busy. Still note the dish: who made it, what was in it as far as you could tell, and what you liked. "Mia's lentil soup, smoky, maybe paprika and a lemon squeeze at the end." That's enough to ask her later or to find something similar. The same habit works for remembering wines or restaurant dishes you loved.
How to remember recipe tweaks while you cook
Your own changes are some of the most valuable notes in your kitchen, and the ones least likely to be written down. You think "next time, less salt" while eating. By next time, months later, it's gone. Then you make the same mistake again.
Talk it while your hands are messy
You won't wipe your hands and type mid-recipe. You can talk. Use your phone's voice assistant or a voice recorder and say what you just changed: "Used one onion not two. Added a splash of vinegar. Simmered 40 minutes, not 30." More ideas for capturing things with busy hands are in how to capture an idea when you can't type.
Say the recipe's name at the start of each note so you know what it belongs to later. "Lentil soup: ..." is enough.
Write one line after you eat
The best tweaks often come at the table, once you've tasted the finished dish. Before the plates are cleared, write one line. Use the same short shape each time so it's quick to write and easy to read later:
- What dish and when: "Banana bread, Nov 2026"
- What you changed: "Cut sugar to 3/4 cup, added walnuts"
- How it turned out: "Not too sweet, a bit dry"
- What to do next time: "Pull it 5 min earlier"
The fourth part is the most useful. "A bit dry" tells you what went wrong. "Pull it 5 minutes earlier" tells you what to do about it.
Note your kitchen, not just the recipe
Some tweaks aren't about the recipe at all. They're about your setup, and they'll apply to many dishes:
- Your oven. If things always need longer than the recipe says, write that down once with a rough figure.
- How you measured. A cup of flour can weigh quite different amounts depending on how you fill it. King Arthur Baking's ingredient weight chart lists a cup of all-purpose flour at about 120 grams, and weighing is the more consistent way to measure. If a bake worked, note whether you scooped or weighed.
- Your altitude. The USDA notes that above 3,000 feet, recipes may need changes in time, temperature or ingredients, partly because water boils at a lower temperature. If you've moved, your old notes may need updating.
- Swaps you made because of what you had. "Used Greek yogurt instead of sour cream, fine" saves you wondering next time.
Write down recipe changes where you'll actually see them
A tweak is only useful if it's in front of you the next time you make the dish. Here are the usual places people write down recipe changes, with their trade-offs.
| Where | Good for | Watch out for |
|---|---|---|
| Pencil in the cookbook margin | Recipes from a book you always use | Only helps when the book's open; can't search it |
| Sticky note on the printed recipe | Printed favourites in a binder | Falls off, gets splashed |
| A recipe app's notes field | Recipes you've already saved in that app | Only covers recipes that live in the app |
| Your phone's notes or a notes app | Everything, including verbal recipes and tweaks | Needs clear words so you can find it later |
Whatever you use, two habits make the difference:
- Use the dish's name every time. If your tweak says "banana bread" and your saved recipe says "banana bread," a search finds both.
- Keep it in one place. Notes spread across screenshots, texts to yourself and paper scraps are hard to piece together when you're standing at the stove.
If you mostly capture by photo and voice, it helps to use somewhere that holds photos, recordings and typed lines together and lets you search them. Your phone's built-in notes app can do a lot of this, and EyeNotes is another option that lets you search in plain words, such as "Mia's lentil soup." If you already struggle to find old notes, how to find a note when you only remember part of it has practical tips.
What you can skip
Many recipe systems fail because they ask too much at the start. You can safely skip:
- Retyping every recipe into a neat format. A photo or link plus one line of your own words is enough for most dishes.
- Sorting into categories up front. "Soups," "weeknight," "holiday" sound useful, but deciding where something goes can be the step that stops you saving anything at all.
- Saving everything you see. Save what you'd actually cook. A hundred recipes you'll never make bury the five you will.
- Perfect measurements from people who cook by feel. Get close, cook it once, and record what you changed. Your version will improve each time.
Tidy up only the recipes that earn it. If you've made a dish three times and your notes are getting messy, that's the moment to write one clean version with your tweaks folded in. Until then, a rough note you can find is all you need.
A quick routine for each case
- Saw it on a screen: save the link, screenshot the ingredients, add one sentence about what it is and where you saw it.
- Ate it at a friend's: photograph the card or record them explaining it, and ask about every vague measure. At the very least, note the dish and who made it.
- Changed it yourself: say the change out loud while you cook, then write one line after you eat: what changed, how it went, and what to do next time.
Each takes less than a minute. Next time you're standing in the kitchen wondering how much garlic it was, you'll have the answer.
Frequently asked questions
How do I save a recipe from a video that has no written recipe?
Pause the video on the frames where ingredients and amounts appear and take screenshots, or jot the quantities down as you watch. Save the video link too so you can rewatch the method. Then add a short note in your own words naming the dish and where you saw it, because a screenshot on its own is easy to lose among the rest of your photos.
How do I get a recipe from someone who doesn't measure anything?
Watch them cook it once and measure as they go. Ask them to grab their usual handful, then put it in a measuring cup or on a scale. Ask what the dish should look, smell or feel like at each stage, and record them explaining. Your first attempt won't be exact, so note what you'd change and adjust the next time you cook it.
Is it okay to write notes in a cookbook?
Yes, if it's your own book. Pencil in the margins is a long-standing way to keep recipe tweaks, and plenty of people value inherited books for those notes. The drawback is that notes only help when the book is open in front of you. If you cook from many sources, keep a copy of your key changes somewhere you can search as well.
Can I share a recipe I copied with friends?
Sharing for personal use is common and generally fine. In the US, a plain list of ingredients is usually not protected by copyright, but a writer's descriptions, stories and photos can be, and rules differ by country. This isn't legal advice. When you pass on a recipe from a blog or book, the courteous approach is to rewrite the steps in your own words and say where it came from, or simply share the link.
What should I write down after changing a recipe?
Keep it to one line with four parts: the dish and date, what you changed, how it turned out, and what to do next time. For example: 'Banana bread, Nov: less sugar, added walnuts, a bit dry, bake 5 minutes less.' The 'next time' part matters most, because it turns a vague memory into a clear instruction.