How to Organize Recipes Without Losing Them to the Next App Shutdown

There's a graveyard of recipe apps. MacGourmet, Panna, Yummly, Evernote Food, ChefTap — each one shut down, got acquired, or quietly stopped syncing, and each transition forced people to export, migrate, or lose their recipes entirely.

Meanwhile, a printed index card from 1962 still works fine.

If you've spent years building a recipe collection, the most important question isn't "which app has the nicest interface?" It's "what happens to my recipes when this app disappears?" Here's how to organize recipes so the answer is nothing — they're still mine.

The problem isn't organization. It's ownership.

Most recipe apps store your collection in a private database. You can browse it, search it, tag it — but you can't really hold it. When you ask for an export, you get a CSV with mangled fractions, or a proprietary backup file only that app can read. Your recipes live in someone else's format, on someone else's terms.

So the first rule of durable recipe organization: keep your recipes in a format you can open with anything.

That format is plain text.

What a plain-text recipe looks like

A Cooklang recipe is just a .cook text file. It reads like a normal recipe, with a few annotations that let a computer understand it too:

---
title: Weeknight Dal
servings: 4
tags: [vegetarian, quick, indian]
---

Rinse @red lentils{200%g} until the water runs clear.

Simmer the lentils in @water{750%ml} with @turmeric{1/2%tsp}
and @salt{1%tsp} for ~{20%minutes}.

Meanwhile, fry @cumin seeds{1%tsp} in @ghee{1%tbsp} in a #small pan
until fragrant, then stir into the dal.

You can read it. A computer can read it. And because it's text, you can open it in 2026 or 2056, in any editor, on any device — no app required.

How to actually organize a plain-text collection

Plain text gives you durability. A little structure gives you sanity. Here's a setup that scales from 10 recipes to 1,000:

1. One recipe per file. Name files after the dish: Weeknight Dal.cook, Sunday Roast.cook. Your file browser becomes your recipe index.

2. Folders for broad categories. Mains/, Baking/, Sauces/. Don't over-think it — folders are cheap and you can move files anytime.

3. Tags in the frontmatter for everything else. A dish can be [vegetarian, quick, freezer-friendly] at once. Tags cut across folders, so you can pull up "everything quick and vegetarian" without duplicating files.

4. Let tools do the cross-referencing. Because the format is structured, software can build shopping lists, scale servings, and search by ingredient for you. You organize once; the tooling handles the rest.

Where Cook.md fits

Plain text on your own disk is the foundation. [Cook.md](/) is the layer that makes a plain-text collection pleasant to live with day to day:

  • Cook Editor — a free, open-source desktop app for writing .cook files with syntax highlighting, live preview, scaling, and shopping lists by aisle.
  • [Cook Cloud](/) — optional sync and backup, so the same collection is on your laptop, phone, and tablet.
  • Mobile apps — cooking mode, timers, and shopping lists for when you're actually at the stove.

The key difference from a typical recipe app: everything reads and writes the same .cook files. Cook.md doesn't lock your recipes inside a database. They sit on your disk as text. If you ever stop using Cook.md, your collection keeps working — in any editor, checked into git, sent by email. That's the point.

Already locked into another app?

Most people reading this have a collection trapped somewhere already. Good news: you can get it out. Cook.md's [Cookify](/) importer reads exports from Paprika, Mela, Mealie, Tandoor, Recipe Keeper, Crouton, Plan to Eat, and more — converting each recipe into a clean .cook file you own.

Migrating once, into a format that can't strand you again, beats migrating every time an app changes hands.

The test for any recipe system

Before you commit your collection to anything, ask one question:

If this company shut down tomorrow, could I still read every recipe?

With a database app, the honest answer is "maybe, if their export works." With plain-text Cooklang files, the answer is "yes — they're text files on my disk."

Organize for that, and you'll never have to migrate in a panic again.

Ready to start? Download Cook Editor — it's free and open source — and write your first .cook file in a couple of minutes.