How to save a recipe from an Instagram reel (properly)

You found a recipe in a reel. You want to cook it on Thursday. Between those two sentences sits a surprising amount of friction, and it is why the average saved folder has two hundred videos in it and produces roughly none of the week's dinners.

Here are all the ways to close that gap, compared honestly — including the ones that have nothing to do with us, and the one that is genuinely the best free option.

The short version

1. Screenshot it

Works: instantly. No apps, no accounts, no thought.

Doesn't: your camera roll is now the pile the saved folder used to be. Screenshots aren't searchable, don't scale to four servings, and cannot be ticked off one-handed in a shop while you're holding a basket. Six months from now you will be scrolling past 400 photos of a beach to find a photo of some noodles.

Fine for one recipe you are cooking tonight. Useless as a system.

2. Save it in Instagram, into collections

Works: it is already there, it is one tap, and collections give you a little structure — "weeknight", "baking", "things to try".

Doesn't: the recipe still is not extracted. You are saving a pointer to a recipe, not the recipe. On Thursday you still have to reopen the app, rewatch the video, pause on the right frame and squint at an ingredient list that was on screen for one and a half seconds.

And there is a failure mode people discover too late: creators delete posts, and accounts go private. A saved post that no longer exists shows you a grey box. The recipe you were relying on for Thursday is simply gone, and there is nothing you can do about it, because you never actually had it.

3. Copy the caption into your notes app

Works: genuinely well, and it is free. The text is yours. It is searchable. It survives the post being deleted, the creator quitting, and Instagram rearranging its interface again.

Doesn't: it is manual, every single time, which means you will do it for about one recipe in ten and it will be the wrong one in ten. Captions are also a mess — emoji, hashtags, three lines of preamble, "full recipe below 👇", and quantities in a different order from the steps that use them. And when you have forty of them, your notes app still cannot plan a week or write you a shopping list.

This is the best free method, and it is the one worth beating. Any app that cannot clearly beat "paste it into notes" is not worth installing.

4. Message it to yourself

Works: the lowest-effort save there is.

Doesn't: everything else. It is the same pointer problem as the bookmark, with worse organisation, in a thread that also contains links to trousers.

5. Share it into something that extracts it

Share the post into an app that reads the caption and turns it into a structured recipe — separate ingredients, separate quantities, numbered steps.

Works: one tap, and once a recipe is structured rather than stored you can do real things with it. Scale it from two servings to five and have the quantities follow. Search it four months later by an ingredient rather than by remembering the thumbnail. Put it in a week. Turn a week into a shopping list.

Doesn't: it depends on the recipe being written down somewhere the app can read. Plenty of creators put theirs in a pinned comment. Some say it aloud and never type it. Some post a photo of handwriting.

Any app claiming it works every time is not being straight with you. The honest version is: a good extraction most of the time, an honest failure the rest of the time, and a fast way to paste the text in yourself when there is nothing to extract.

What if the recipe is in the comments?

This is the most common failure, and it is worth knowing the workaround regardless of which app you use.

If the caption says "recipe in comments", open the comments, find the creator's own pinned comment, and long-press to copy it. Then paste that into whatever you are using. It takes about five seconds and it works every time, because you are doing the reading yourself.

What you should expect from an app here is not magic — it is honesty. It should tell you it could not find a recipe, rather than inventing a plausible one. An app that guesses at quantities it never saw is worse than an app that admits it failed, because you will not find out until you are standing in the kitchen.

What to check before you commit your collection to an app

Three questions, and they take about five minutes to answer:

1. Does it credit the creator? Every imported recipe should carry the handle

and a link back to the original post. If an app quietly strips where a recipe came from, it is building a business on other people's work and hoping you do not look. It also means you can never go back and watch the technique again.

1. Does the shopping list actually merge? This is the real test. Import three

recipes that all use garlic. If you get three lines, the list will irritate you within a fortnight and you will stop opening it. We wrote about why that is so hard to get right — it is a better test of an app's care than any feature list.

1. Can you get your recipes back out? Anything holding your collection

hostage is a bad long-term home for it. Ask before you have 200 recipes in there, not after.

A fourth, if you are the sort to plan: does it fill the week for you, or hand you an empty calendar? Most hand you the calendar. That is a whole problem of its own.

What we're building

FasterChef is option five, built by people who got tired of option three.

Share a reel, get a recipe with the creator credited and linked. It plans your week from what you have saved — not from a stock database of recipes you never chose — and writes one shopping list that merges duplicates, converts units and sorts by aisle. When the recipe genuinely is not in the caption, it says so and gives you a box to paste into, and reads that instead.

It's coming to iPhone. The waitlist is below, and everyone on it gets in before it opens to the public.