How to organize your recipes

Almost everyone who cooks has a pile: bookmarks, screenshots, a note app, three cookbooks with sticky tabs, and a link someone sent on WhatsApp in 2019. The pile is not a filing problem. It's a format problem, and that's why filing it never works.

Saving a recipe takes one second. Finding one takes minutes, and cooking from it takes a scroll through 1,400 words about a trip to Sicily. Because saving is free and retrieving is expensive, the pile only ever grows in one direction.

The second thing that makes it worse: every recipe you save is in somebody else's format. Different order, different units, different level of detail, different idea of what “until done” means. Fifty recipes is fifty small acts of translation you have to perform again every time you cook.

Bookmarks and links. The fastest to add and the fastest to rot. Sites get redesigned, go behind a paywall, or vanish; a bookmark is a pointer to someone else's server and you don't control it. Worse for daily use: you can't scan a bookmark. A folder of forty blue links tells you nothing about what's for dinner.

Screenshots. Solves the rot — you own the pixels. But the text isn't searchable in any way you'd trust, screenshots are always cropped at the wrong point, and they land in a camera roll with 6,000 photos of other things. A screenshot is a recipe you can only find by remembering roughly when you saved it.

The notebook or binder. This one actually works, and it's worth asking why, because the answer is not “paper”. It works because copying a recipe out by hand forces it into your format. Same order, same units, same shorthand, every time. You can find things in it because everything looks the same.

The binder's only real flaw is the work. Typing up a hundred recipes is a project people start and abandon — and it's the single most common reason a good system dies.

When I asked people who had genuinely got on top of their recipe collection how they did it, the answers were almost identical, and none of them involved an app. They picked one format and retyped everything into it. One person prints and laminates them and keeps them in a lever arch file in the kitchen.

What they had all worked out is the thing the software usually misses: the standardisation is the feature. Storage was never the hard part — every note app on earth will store a recipe. The hard part is that all fifty look different, and the only fix anyone had found was to do the translation once, up front, by hand.

So the goal isn't a folder structure. It's that every recipe in your collection should look the same as every other one. Get that and the organising mostly solves itself; skip it and no amount of tagging will save you.

Four properties. In rough order of how much they matter:

• One shape, every time. Ingredients in the same place, steps in the same order, units you use. This is the one that does the work.
• Survives the source. If the blog dies, you still have the recipe. Keep the link for credit, but don't depend on it.
• Findable in seconds. Searchable text beats tags, and tags beat folders. Most people need far fewer categories than they think — you cook a rotation of about thirty things.
• Works where you cook. On a phone, with one hand, possibly wet, on a screen that keeps going to sleep. A system that only works at a desk is a system for collecting recipes rather than cooking them.

If you're starting from a pile, the order matters more than the tool:

• Start with what you actually cook, not with the backlog. The thirty recipes in your rotation are 90% of the value and they'll take an evening. The other two hundred can wait, possibly forever.
• Convert, don't collect. Do the format work at save time. A recipe filed in its original form is a recipe you'll have to decipher later, and later is when you're hungry.
• Keep the source link on the recipe. Credit is right, and it's occasionally useful when you want the headnote or the photo.
• Don't build a taxonomy on day one. Add categories when the search stops finding things, which is later than you expect.

RecipeTables exists because of the paragraph above about retyping. You paste a link, the text, or a photo of a cookbook page, and you get the recipe back in one fixed format — ingredients as rows, steps as columns that merge — the same shape every time, whatever the source looked like. Sign in and they're saved to a box you can search.

It is, honestly, the binder-and-laminator system with the typing removed. That's the whole idea. Try it on a recipe you already cook, or look through the library to see what the format does to a normal recipe blog.