Tutorial

Instagram recipes to website: how to move your captions over without retyping everything

A caption is a fine place to post a recipe and a bad place to keep one. Here's how to move your Instagram recipes to a website: what captions leave out, a worked before-and-after, and exactly which parts software can do for you.

By Crumb EditorsUpdated 8 min read

Someone comments "recipe?" under your Reel. You reply "it's in the caption!" An hour later they're back: "how long in the oven though?" Multiply that by a few hundred posts and you have the real reason to move your Instagram recipes to a website.

The move itself is less work than it looks, and more work than any "one click" promise suggests. Some of it a machine can do in seconds. Some of it only you can do, because the answer was never written down. This guide shows you which is which, with one real-looking caption taken all the way through.

Crumb is our product, and it comes up below because it was built for this move. The rest of the guide works on any recipe website. If you haven't picked a platform yet, start with how to create a recipe website.

What a caption leaves out

Captions are written for people who can watch you cook. The video quietly answers half the questions. Once the recipe has to stand on its own, these are the gaps that show up again and again:

  • Amounts said out loud, or not at all. "Gochujang, honey, soy." How much of each?
  • Oven and pan details. The temperature was on screen for two seconds. The tray size never was.
  • "Till it looks right" cues. Fine when you can see it. Useless when you can't.
  • No yield. Serves two? Four? A snack for one very hungry person?
  • Fixes hiding in the comments. "Oops, that should be 1 tsp salt, not 1 tbsp!" lives in a reply, not the caption.
  • Two versions of the same dish. You posted it in January and again in October with "even better now!"
  • Room. Instagram caps a caption at 2,200 characters, hashtags and story included. A full recipe with notes often doesn't fit, so something gets cut.

A worked example: what an import can and can't do

Here's a typical caption for a snack that does well on Instagram:

crispy gochujang chickpeas 🔥🔥 the snack I make every single week!!

what you need: 2 tins chickpeas, gochujang, honey, soy, oil, sesame seeds

dry the chickpeas really well (this is the secret!!), toss in oil, roast till crunchy, then toss in the sauce and back in for a few mins 🙌

save this for later + follow for more easy snacks #snackideas #chickpeas #gochujang #easyrecipes

Stage one: split into fields. This is the part software is good at. Whether you do it by hand or an import does it, sorting gets you this:

Ingredients: 2 tins chickpeas · gochujang · honey · soy · oil · sesame seeds

Steps: 1. Dry the chickpeas really well. 2. Toss in oil and roast till crunchy. 3. Toss in the sauce and return to the oven for a few minutes.

Serves: ? · Oven: ? · Times: ?

Tidier, but nobody can cook it yet. Every question mark is still a question mark, because the caption never answered it.

Stage two: fill the gaps from what you know. Here's the same dish after you've checked your notes and footage, or made it once more with a notebook open:

Crispy gochujang chickpeas

Serves 4 as a snack · Prep 10 min · Cook 35 min

  • 2 cans (400 g each) chickpeas, drained and rinsed

  • 1 tbsp neutral oil

  • 1½ tbsp gochujang

  • 1 tbsp honey

  • 1 tsp soy sauce

  • 1 tsp sesame seeds

  1. Heat the oven to 200°C (400°F). Rub the chickpeas dry in a clean tea towel, letting loose skins fall away.
  2. Toss with the oil on a large baking sheet so they sit in a single layer. Roast for 25 to 30 minutes, shaking once, until they rattle when you shake the tray.
  3. Stir the gochujang, honey and soy together. Toss the hot chickpeas in it, spread them out again and roast for 5 more minutes, until sticky and dark at the edges. Scatter over the sesame seeds. They crisp up more as they cool.

Here's where each change came from:

What changedWhere the answer came fromCould software do it?
Ingredients and steps in separate listsThe captionYes
Hashtags and "save this" removedThe captionYes
Sauce amountsYour notes, or the videoNo
Oven temperature and roasting timeYour notes, or a test cookNo
"Till crunchy" became "they rattle"You, at the stoveNo
Serves 4, tray size, single layerYouNo

Two rows out of six. That's the deal with any import: software can pull captions from your account, split them into fields and skip posts that aren't recipes. It can't hear amounts you only said in the video, pick which of two versions you'd stand behind, or know a pan size nobody wrote down. If a tool fills those in anyway, that's a guess, and it lands in a reader's kitchen. Even the sorting needs checking: Crumb's own help says automated formatting makes mistakes, like a tablespoon turning into a teaspoon.

For more on the rewriting itself, see how to turn a caption into a complete recipe.

Getting your captions in, platform by platform

On WordPress, you'll mostly paste by hand. WP Recipe Maker, the plugin most guides recommend, imports from other recipe plugins, and Instagram isn't on that list. Copy each caption into a post, then fill the recipe card fields.

On Crumb, there are three ways in, described in the recipe help and the Instagram help:

  1. Paste one recipe. In Recipes, choose New recipe → Import written recipe, paste the caption text and choose Format recipe. Crumb sorts it into ingredient, step, timing and serving fields and saves a draft. Paste the text itself: a link to the post won't work.
  2. Connect Instagram. This needs a public Instagram Creator or Business account. Choose whether new recipes arrive as drafts or publish automatically (start with drafts), approve the connection on Instagram's own screen, then choose Import earlier posts. Crumb reads up to your 500 most recent posts and adds every complete recipe as a draft. After that it checks for new posts about every 30 minutes.
  3. We prepared them for you. Some creators start with recipes Crumb prepared from their public posts. Some dishes won't be there, and a first import may cover only part of a long archive.

Whichever way, the rule from the example holds. Crumb only turns a post into a recipe when the ingredients and steps are written in the caption. "Recipe in my bio!" or a method you only said out loud won't come through. Those you write up yourself.

Pick a first batch and track it

Your grid is a mix of full recipes, half recipes and beautiful plates with no words at all. Don't try to move it all. Pick 10 to 20 dishes: the ones with the most "recipe?" comments, that you still cook, and that hang together (weeknight dinners, say, or your baking).

Track them in one sheet, one row per dish, not per post:

DishSource postsWhat's missingStatusPublic link
Gochujang chickpeasOne ReelSauce amounts, ovenNeeds a test cook
Chickpea stewJan post, Oct repostWhich version?Comparing
Banana oat muffinsOne post, plus notesNothingReady to review

After an import, check the sheet against your drafts. Which dishes arrived? Which are missing? Add those by hand.

For the stew posted twice: a straight repost is one page. A correction ("I doubled the cumin") means the page gets the corrected amount. A genuinely different version, like a slow-cooker take, can have its own page with a name that says so. Never take the spices from one caption and the liquid from the other. That's a stew you've never cooked.

Read every draft like someone making dinner

Read each draft top to bottom as if you've never seen the video, and check:

  • Every ingredient has an amount and any prep it needs.
  • Every ingredient is used in the method, and the method uses nothing that isn't listed.
  • Oven temperatures, pan sizes and times are there, with a cue for doneness.
  • The yield says how much it makes.
  • Quantities match your original, especially teaspoons versus tablespoons.
  • The main photo shows this dish, in this version.

If a gap can't be filled from your notes, keep it as a draft and test the recipe first. The muffins don't have to wait for the chickpeas, though. Publish each recipe the day it's ready.

Go public and send the recipe, not the homepage

Publishing a recipe and making your website public are separate steps on Crumb. A published recipe on a private website is still invisible to readers. Building and previewing are free. New direct signups get 30 days public free, then Crumb Pro is $15 a month.

When someone asks for the chickpeas, send the chickpeas page. Open it in a private browser window, signed out, check it's the public page with no preview in the address, and paste that link into the last column of your sheet. That's your link for DMs and Story stickers.

On Crumb you can also let Instagram do the replying. Comment recipe links sends a private reply with the recipe link when someone comments a keyword, like "Comment CHICKPEAS for the recipe." It only works once the website is public and that recipe is published and free, so publish first, then post.

Your bio still gets one link, so point it somewhere people can browse.

Your next batch

Once the first fifteen are live, pick five more from the sheet. Group them as you go so readers can find their way around; building a useful recipe archive covers categories that grow with you. A few batches in, "recipe?" stops being a paragraph you type and becomes a link you paste, which is where growing a recipe audience really starts.

Instagramrecipe websitesrecipe imports
← Back to the blog