How to Save Recipes From Instagram (and Actually Cook From Them)

Instagram is where recipes go to be admired, not cooked. You tap the little bookmark, the reel joins the other two hundred you've saved, and then a Tuesday comes around when you actually want to make the thing — and you're scrubbing back and forth through a 30-second video trying to catch how much flour went in.

The recipe is there. It's just trapped — in a caption, a pinned comment, or spoken once over background music. You can't scale it, can't turn it into a shopping list, can't search "that lemon pasta" three weeks later.

Here's how to get it out once, into a file you can actually use.

The idea: get the text out, then keep it

A saved Reel depends on the post staying up, the creator staying around, and Instagram staying open. None of that is yours. A plain-text recipe file is — it's searchable, scalable, and still readable in ten years.

Cookify does the extraction. You give it the recipe in whatever form Instagram left it in, and it returns a clean Cooklang .cook file. There are three cases depending on where the recipe actually lives.

1. The recipe is in the caption

Most "full recipe below 👇" posts put it in the caption. Tap to expand the caption, copy the whole thing — quantities, steps, the lot — and paste it into Cookify as text. It ignores the emoji, the hashtags, and the "save this for later!!", and pulls out the actual recipe.

Lots of accounts post the recipe as an image — a tidy card, or a swipe-through carousel. Screenshot it (or save the image) and upload it to Cookify. It reads the picture and structures what it finds.

3. The recipe is only spoken in the Reel

Be warned: if the quantities are only said out loud in the video and never written down, no importer can reliably read them — check the caption and the pinned comment first, because that's usually where they hide. If it really is video-only, jot the steps down roughly as you watch, then paste that into Cookify. It's happy to structure messy text; it just can't invent what was never written.

What you get back

Not a screenshot, not another bookmark — a real recipe file:

---
title: Lemon Garlic Butter Pasta
servings: 2
source: https://instagram.com/p/example
---

Cook @spaghetti{200%g} in salted #pot{} until al dente, reserving @pasta water{1%cup}.

Melt @butter{2%tbsp} and soften @garlic{3%cloves} for ~{2%minutes}.

Add the pasta, @lemon{1} (juice and zest), and a splash of the pasta water. Toss.

Finish with @parmesan{30%g} and @black pepper{}.

Once it's a .cook file, the tools take over: Cook Editor and the mobile apps let you scale it from 2 servings to 6, merge its ingredients into a shopping list with the rest of the week's cooking, run the timers, and find it later by searching for an ingredient.

If you want the longer version — URLs, cookbook photos, exports from other apps — see Cookify: turn any recipe into clean Cooklang. And for the bigger picture on why saving social-media recipes as plain text beats hoarding bookmarks, our sister site has a good piece on keeping social-media recipes forever.

Try it on the next one you save

  1. Open Cookify.
  2. Paste the caption, or upload a screenshot of the post.
  3. Review the .cook file and save it to your collection.

That's the difference between a recipe you've seen and one you can cook.

Unlimited recipe import is part of Cookbot Pro, €10/month. The files you get out are open Cooklang, yours to keep with or without a subscription.