How to save recipes from TikTok, including the slideshow posts most apps cannot read
TikTok is a harder place to save a recipe from than Instagram, for one structural reason: a much larger share of TikTok food posts put the recipe nowhere a computer can read it.
On Instagram the recipe is usually typed into the caption. On TikTok it is often spoken over the video, or burned into a photo carousel as a graphic, or sitting in a pinned comment. TikTok captions are short by convention.
So "how do I save recipes from TikTok" splits into two questions. Keeping the post, which is easy and free. And getting the actual ingredients out, which is where most tools quietly fail.
Keeping the post: Favourites, for free
TikTok has its own bookmark. Saving a video puts it in your Favourites, where you can sort things into folders, and it costs nothing.
If you only want to not lose a video, this is the answer and you can stop here.
Same caveat as every bookmark though: it is a pointer to somebody else's video, not a copy of the recipe. Creators delete posts and go private, and a favourite does not survive that. It also does not help you shop, because you cannot read a shopping list off a video while standing in an aisle.
Getting the recipe out: the share sheet
The route that works is Share, then pick a recipe app, and let it read the post and build a recipe card.
Before you judge any app on this, know about the link problem, because it makes apps look broken when they are not.
When you share from TikTok you do not usually get a clean address. You get a short link, something like vm.tiktok.com/... or vt.tiktok.com/..., which is a redirect rather than the real post. And if the recipe was a photo carousel rather than a video, the real address underneath is a /photo/ one.
That matters because TikTok's own free metadata service rejects both of those. A short link gets an error. A /photo/ address gets an error. An app that does not resolve the link first and rewrite it will fail on a large share of recipe posts, and the failure looks like "this app cannot read TikTok" when really it cannot read a redirect.
If an app fails on a shared link, try opening the post in a browser first, copying the full address from the address bar, and pasting that in. If it works that way, you have found a link resolution bug rather than a limit.
The slideshow problem
TikTok photo posts, the swipeable carousels, are everywhere in food content, and they are the hardest case.
The recipe is frequently a designed graphic: ingredients on slide two, method on slide three, as pixels rather than text. There is nothing in the caption to read. A tool that only reads captions returns nothing and tells you the post has no recipe in it, which is not true, it just cannot see it.
Getting those requires reading the images themselves. It works, it is not perfect, and it is worth knowing it is imperfect: text over a photograph of food at an angle, in a script font, is exactly the hard case for reading text off an image. Expect to check quantities on those.
The same goes for a recipe that is only ever spoken. If nobody typed it anywhere, in the caption, a comment, or a slide, then no app is extracting it, and anyone claiming otherwise is describing transcription of the audio, which is a different and less reliable thing.
Checking the comments
Worth doing by hand before you conclude a recipe is unavailable: look at the pinned comment and the creator's own replies.
A lot of TikTok creators put the full recipe in a comment, deliberately, because comments drive reach. Pinned is the usual place. An app that reads comments as well as the caption will pick these up. An app that does not will tell you there was no recipe.
One trap if you go looking yourself. The first comment is often not the creator's, it is a fan. The one you want is the one from the account that posted the video.
What none of this gives you
All of the above gets you words. It does not get you what is in the food.
That is the gap I build for, so read this knowing that. MyMealStream resolves the shared link first, including short links and photo posts, then reads the caption, the creator's own comment, or the slide images, and then works out the calories and macros from the ingredient lines rather than guessing from the dish name.
The limits, stated plainly:
- The numbers are a per ingredient database match, so a stated weight is accurate and "a handful" is not.
- Cooking loses fat, so adding raw ingredients up reads high unless it is corrected for. It is corrected for, using published retention figures, and it remains an estimate.
- Against recipes whose authors publish their own nutrition panels it comes out about 15 percent off on calories on average. That beats a guess and it is not a laboratory.
- A recipe read off slide images is held to a lower confidence bar than one read from text, and the app will decline rather than invent a recipe it could not read properly.
The detail of where this goes wrong is in how to calculate macros for a recipe. Five imports a month are free, which is enough to test it against the accounts you actually follow.
What I would actually do
Favourite things as you see them, because it is free and instant and you are on your phone anyway.
Then once a week, take the handful you actually intend to cook and run those through something that extracts the ingredients, so the shopping list exists before you need it. Trying to extract everything you favourite is how people give up.
And when you test an app, test it on a photo carousel and on a "recipe in comments" post specifically. Any of them can handle a creator who typed the recipe into the caption. Those two cases are the ones that separate them.