How to Save Recipes From Anywhere: Cookbooks, Links, Social and AI

By Alex Fahey, founder of Chop it. Last updated 5 August 2026.

Good recipes now arrive from five directions: cookbooks, websites, social video, other people, and AI chats. Most saving systems handle one of those, which is how a household ends up with a shelf of cookbooks, a folder of screenshots, forty browser bookmarks and a ChatGPT history nobody can search. This guide covers how to capture each source properly, whatever tools you use.

The principle worth adopting first: a recipe is only saved when you can find it in March and cook from it. A screenshot is a photo of a recipe, not a recipe. A bookmark is a promise that a website will still exist. The test of any method is whether the ingredients and steps end up somewhere structured, searchable and yours.

From a website

The easiest source, because recipe sites publish structured data underneath the page. Any decent recipe manager can read a pasted link and extract the ingredients, steps and servings. Paprika built a business on doing this well; Chop it does it as one of five input routes.

Copying links into a notes app is the trap here. The link is not the recipe, and recipe sites reorganise, paywall and die. Extract the content while it is in front of you.

From a cookbook or a handwritten card

Photograph the page. Text recognition has become good enough to turn a photographed page, including handwriting, into structured ingredients and steps. In Chop it this is the "snap a page" route: one photo, then check the quantities it read, because recognition of a grandmother's handwriting is good but not infallible.

The alternative is typing the recipe out, which is why most people's cookbook recipes have never joined their digital collection at all.

From TikTok, Instagram or YouTube

The hardest source, and the one growing fastest. The recipe lives partly in the caption and partly in the video itself, and both vanish if the creator deletes or the platform changes.

Screenshots capture the caption and lose the method. Saving the video keeps it inside the platform's app, unsearchable next to your other recipes. The durable route is extraction: paste the link into a tool that parses the ingredients and steps themselves, so the structured recipe survives whatever happens to the source. Chop it's "paste a link" route handles the major platforms.

From another person

The text from a friend with "that curry you liked" deserves better than the messages app. Paste it into whatever holds your collection, or photograph it if it arrived on paper. The recipes with the most sentimental value are the ones stored most precariously.

From an AI chat

The newest source and the leakiest. A recipe ChatGPT wrote for you exists in a conversation that scrolls away, cannot be searched by ingredient, and is hard to find again three weeks later. We wrote about this failure mode in detail in ChatGPT meal planning: what works and what does not.

Two fixes. The manual one: copy anything worth keeping out of the chat immediately, into your recipe manager. The integrated one: use Chop it inside ChatGPT, where a recipe you create in conversation can be opened in the app as a structured recipe, no retyping.

Why one library matters

Scattering is not a storage problem, it is a cooking problem. A recipe you cannot find is a recipe you do not cook, and a collection split across five apps cannot be planned or shopped as one week. The point of capturing every source into one place is what becomes possible afterwards: the week's plan draws on everything you have ever saved, and one merged shopping list covers all of it, whatever direction each recipe arrived from.

Frequently asked questions