How to Name Recipes So You Can Actually Find Dinner
Lead with the dish you'd type next month, then one source or variant. Put weeknight and diet in tags — not in a paragraph-long title.

You typed "chicken" into the search bar and got fourteen results named some version of "Mom's," "good one," and Screenshot 2024-11-03. The recipe is in there. The title is not helping — and a photo or PDF with no real title field never will.
Short answer: Name every recipe with the dish you would type next month — lead with the food, then add one useful source or variant. Put cuisine, diet, and "weeknight" in tags, not in a paragraph-long title.
Titles find dinner; tags filter it
A title answers: what is this dish?
Tags answer: when do I cook it, and what rules apply?
If you bury "weeknight Thai chicken" only in a tag and leave the title as "Tuesday thing," search will fail when you remember the dish, not the day. If you stuff every attribute into the title, the list becomes unreadable and you still forget which words you used.
Opinion: Lead with the dish name you would say out loud to a friend. "Mom's famous" can live in the source field or a note — it should not be the only searchable words.
A naming pattern that survives a messy collection
Use one pattern for cards, PDFs, screenshots, and app titles:
Dish — Source or Person — Key variant
Examples that work:
- Chicken Piccata — Serious Eats — Capers heavy
- Chocolate Sheet Cake — Grandma Ruth
- Tomato Soup — Blender weeknight
- Stuffing — Thanksgiving — Uncle Dan
Rules that keep it short:
- Dish first. Use the common name you will search, not the magazine headline.
- One source label. "Grandma Ruth" or "NYT" is enough. Standardize spellings so you do not invent three versions of the same person.
- One variant max. Gluten-free, sheet-pan, or double-batch — pick the difference that matters when two recipes share a dish name.
- Skip the kitchen sink. Diet lists, cook times, and "uses leftover rice" belong in tags or notes.
Rename pass for the pile you already have
You do not need a perfect archive night. Do a 20-minute rename pass on the recipes you actually cook:
- Pull the last ten dinners you made from memory.
- Find each one in photos, email, binders, or apps.
- Rewrite the title with the pattern above before you touch anything else.
- Only then add two or three tags (protein, occasion, pace).
Screenshots named by the phone camera are invisible to future-you. Rename at intake: the moment you save a photo or PDF, give it a dish-first title. Waiting until "someday" is how IMG_ files multiply.
Handwritten cards can keep the original wording in a note field. The display title still needs a searchable dish name — "Aunt May's cookie recipe" becomes "Snickerdoodles — Aunt May" so December-you can type snickerdoodle.
Names that fight you (and what to use instead)
| Weak title | Better title |
|---|---|
| Mom's cake | Chocolate Sheet Cake — Mom |
| Good pasta | Cacio e Pepe — Weeknight skillet |
| IMG_4821 / Scan001 | Lemon Bars — Church cookbook |
| Healthy chicken thing | Sheet-Pan Chicken — Yogurt spice |
| Soup | Lentil Soup — Ham hock |
If two recipes would get the same title, add the variant that changes the cook: grill vs oven, red sauce vs white, kid-mild vs full chile.
Where Keepsake Cook fits
When the collection is photos, PDFs, and pasted text, searchable titles only help after the recipe is actual text — not a locked image. Keepsake Cook turns a photo or PDF into an AI-organized recipe with a real title field you can edit, so "chicken" stops meaning fourteen mystery screenshots.
Try it free on the worst-named keeper in your camera roll. Fix the title once, then find it on purpose next Tuesday.
Close: one rule for intake
Every new recipe gets a dish-first name before it joins the pile. Tags can wait five minutes. A blank or camera title cannot — that is how dinner gets lost in a collection you already own. If the keepers still live as photos and PDFs, try Keepsake Cook free and give the worst one a real title on the way in.
