To organize recipes from different sources, give every recipe the same cooking fields while keeping its origin explicit. A website, Reel, family card, and your own experiment can all use title, yield, ingredients, and steps—but they should not all claim the same level of authority or completeness.
Create a common recipe record
Use these fields across every source:
| Field | Why it matters |
|---|---|
| Title | Retrieval and identification |
| Source type | Website, public video, text, family, or original |
| Author or origin | Attribution and context |
| Original URL or physical reference | Verification and recovery |
| Yield | Meaningful quantities and serving changes |
| Ingredients | Shopping and preparation |
| Ordered method | Cooking without reconstructing sequence |
| Uncertainty | Missing or inferred information remains visible |
| Personal changes | Your tested edition stays separate |
Consistency belongs in the fields, not in pretending each source arrived equally complete.
Process each source according to its risks
Websites
Prefer the full recipe page and retain its URL. Watch for dynamically loaded sections, unusual layout, and updates after you captured it.
Social videos
Inspect caption, narration, on-screen text, and linked page separately. A visual demonstration may still omit yield or quantity.
Selected text and messages
Record who sent or wrote it. Rebuild line breaks carefully; copied text can detach quantities from ingredients.
Family cards and cookbooks
Transcribe the original wording before modernizing it. Ambiguous measures and assumed knowledge deserve notes, not invisible correction.
Your own recipes
Date meaningful iterations. “Original” does not mean fully tested.
Normalize in two passes
First make the source legible: preserve facts, repair obvious formatting, and expose omissions. Then make it usable for your kitchen: convert units if needed, add equipment context, and record substitutions as your edits.
Do not combine those passes. If you rewrite while transcribing, later readers cannot tell whether “180°C” came from the card or your experiment.
Use one inbox and one trusted library
Put incoming links, screenshots, and notes into a temporary queue. Only move an item to the main library after it has a minimum complete record or an explicit “idea only” status.
Mise can receive supported public videos, links, recipe pages, and selected text, then present editable ingredients and steps with the source retained. Manual review is what turns those heterogeneous drafts into a coherent personal collection.
Resolve duplicates deliberately
Two recipes with the same dish name are not necessarily duplicates. Compare source, yield, method, and your notes. Keep both when they represent meaningfully different techniques. Merge only when one is truly a copy and you can preserve the source and tested changes.
Name variants by their useful difference: “no-knead,” “grandmother’s,” “small pan,” or “weeknight.” Avoid “version 2” unless you also explain what changed.
Audit for source amnesia
Periodically filter for recipes with no source or authorship note. Fill what you can from evidence; label the rest “source not recorded” instead of making an attribution guess. A consistent system makes missing provenance easier to see, not easier to conceal.
Try the workflow
Keep the source. Review the recipe. Cook from your version.
Download Mise on the App StoreSources and further reading
Read how we research, draft, review, and correct guides in our editorial policy.