Cooking content has moved to video. TikToks, Reels, YouTube Shorts: that's where people find what to cook tonight. But cooking from a video is painful. You pause, rewind, squint at the captions, and try to catch "a little bit of paprika" before the clip loops.
This is a concise overview. The full source-backed guide, tested workflows, and current limitations are published on CookbookSocial: How to turn cooking videos into structured recipes.
So I built CookbookSocial. You paste a link to a cooking video or a recipe website and get back a normal recipe you can edit: title, ingredients, steps, and a link to the original source. It goes into your personal cookbook, next to your own recipes.
What it does
- Imports supported public sources: recipe websites and selected public YouTube, TikTok, Instagram, Facebook, X, and Threads posts. Available source signals vary by post type.
- Speaks your language: the app works in 20 languages, and a recipe from a Japanese video can be translated into Polish or Ukrainian. The original stays untouched.
- Does the boring parts: nutrition and allergen info, shopping lists, metric or imperial units.
- Lets you share: make a recipe public and send a clean page instead of a 3-minute video.
- Runs where you cook: on the web, on iPhone and on Android.
What surprised me while building it
Videos often don't contain the recipe. A surprising number say "full recipe at the link in the description". So the app has to follow that link and check that it leads to the same dish. Recipe websites have the same problem. One steak page only teased the recipe and linked to the full post. The app once followed the wrong link, from a "popular posts" block, and came back with German Lebkuchen Bars. 🥩 → 🍪
One video can hold five recipes. "TOP 3 zucchini recipes" used to either turn into one confusing mega-recipe or get rejected. Now the app asks which dish you want. The tricky part is the opposite case: a cake with its dough and cream is one recipe with parts, not three separate ones.
AI is very good at sounding right. Give a model a one-line caption and it will happily invent a few reasonable-looking steps. For a cooking app that's the worst outcome: you only find out the steps were made up when dinner fails. So the app is built to stick to the source. It checks results for steps the source doesn't support. It would rather tell you what's missing, or that it couldn't find a recipe, than make one up.
Credit the creator. Every imported recipe keeps a link to the original video or post. The people who film these recipes do the real work, and the app should send people back to them, not replace them.
What I learned
- The AI part is the easy part. Most of the work is making sure what it produces is actually true.
- Real-world content is messier than any test case you can imagine.
- An honest "couldn't find it" builds more trust than a polished wrong answer.
Try it
You can start for free. Free accounts can store up to 50 recipes and save or add up to 5 recipes per calendar month. AI imports and new translations use separate credits and do not count toward that monthly limit; additional credits can be purchased without Premium. See the current details on the pricing page. Web: cookbooksocial.app, iPhone: App Store, Android: Google Play.
I'd love feedback: what's the most annoying thing about cooking from videos for you?
Top comments (0)