How to Build a Recipe Collection You'll Actually Cook From

Most people's recipe collection isn't a collection at all — it's a pile. Bookmarks in one browser, screenshots in the camera roll, a few cards in a drawer, several emails to yourself. Each piece is fine; together they're unusable, because there's no single place to look.

What turns a pile into a collection

• One home. Not the best home — just one. Recipes split across five apps behave like recipes you don't have.
• A consistent shape. Every recipe with its ingredients, steps, and source in the same structure, so any of them can be scaled, searched, or shopped from.
• Findability over filing. A collection you have to navigate stays unused. One you can question — “which of these are vegetarian?” — gets cooked from.
• Room to grow untidily. You'll add recipes faster than you'll organize them. The system has to stay useful when it's messy, which means search has to carry the weight, not folders.

Start with what you already cook

The instinct is to begin with a grand import of everything. Don't. Start with the ten or fifteen dishes you genuinely make — the weeknight rotation. That's the collection you'll open every week, and it's small enough to finish in an evening. Everything else can trickle in as you rediscover it.

Organizing without over-organizing

• Tags beat folders for food, because a recipe is legitimately “quick” and “vegetarian” and “mum's” at once.
• Collections for occasions — Christmas, camping, the baby's food — are worth making explicitly, because that's how you actually reach for them.
• Don't tag everything on the way in. Capture first. Tag the ones you keep returning to.

Keeping it alive

A collection is a living thing: variants accumulate, notes get added in the margins, some recipes quietly stop being cooked. Keep the notes with the recipe rather than in your head, and let the ones you never make sink to the bottom rather than deleting them — storage is free, and one of them will come back into fashion.

Where iwant2eat fits

iwant2eat gathers a scattered pile into one private collection: capture by link, photo, email, or video; tag and group into collections; then ask it plain-language questions across everything you've saved. It learns which recipes you actually cook and floats them to the top, keeps the original source text next to the parsed version, and exports the whole collection to plain files whenever you want it back.