Build the shelf you use.
Drop saved recipes into Weeknights, Pasta, or Sunday lunch. A cookbook is edited for the way you actually cook.
Keep a weeknight shelf, a holiday binder, or the recipes one person taught you. Cookbooks give scattered saves a home, then make that home easy to share.
Drop saved recipes into Weeknights, Pasta, or Sunday lunch. A cookbook is edited for the way you actually cook.
Invite the people you feed to a cookbook, without turning every recipe in your library into a public post.
Shared cookbooks can carry updates, so a new sauce or a fixed instruction arrives where readers already cook.
Cookbooks are being tested with the rest of Sugo's kitchen: saved recipes, profiles, and shared tables.
A cookbook is a small, edited collection: weeknights, the things one person taught you, the six dishes that actually work for a dinner party. It is not a tag and it is not the whole library sorted differently.
The distinction matters because the thing that makes a saved-recipe collection useful over years is curation, not capacity. Everyone's library ends up with four hundred recipes and thirty they cook. Cookbooks are where the thirty live.
A recipe can sit on several shelves at once, and putting it on one does not move it out of your library.
Sharing in most recipe apps is all or nothing: either a recipe is private or it is a public post. Cookbooks sit in between. You invite specific people to a specific shelf, and nothing else you have saved becomes visible.
That is the shape of how recipes actually move between people. Someone asks for the roast potatoes, and what you want to send is the roast potatoes and the four other things from that Sunday, not an account.
Shared cookbooks can carry updates, so when you fix a step or add a note, the people cooking from it get the corrected version rather than the one they screenshotted in 2024.
It is not a social network. There are no followers, no feed, and no public profile you are building. Sharing is by invitation or by a link you choose to send.
Sharing a cookbook does not transfer ownership of what is in it. If you built a shelf out of recipes from a publisher's site, sending it onward is your call to make and your responsibility, which is worth remembering before sharing anything beyond the people you cook with.
One on the free plan, and unlimited on sugo+ and famiglia. Saved recipes themselves are unlimited on every plan, including free, so the limit is on how many shelves you organise them into, not on how much you keep.
Yes, that is the point of them. You invite specific people to a specific cookbook, or send a link you control. Nothing else in your library becomes visible, and there is no public profile or feed.
Yes. A shared cookbook carries updates, so fixing a step or adding a note reaches the people cooking from it rather than leaving them on an old copy.
No. A cookbook is a shared collection of recipes. A household, which is part of famiglia, is up to 20 people who also share a meal plan, grocery list, and pantry that everyone can edit.
Yes. A recipe can sit on as many shelves as make sense, and adding it to a cookbook does not remove it from your main library.
Import recipes from websites, TikTok, Instagram, YouTube, photos, Notes and other recipe apps: what works, how deep each one reads, and what doesn't yet.
An eighteen-minute cooking video contains about two minutes of actual recipe. Four ways to get those two minutes into a form you can cook from.
Cooking videos are where most recipes live now, and where they are hardest to keep. Four ways to get a recipe out of a video and into a form you can cook from.
Sugo is on the App Store for iPhone, iPad and Mac, on Google Play for Android, and in any browser at app.sugo.kitchen. It is free to start, so start saving the recipes you actually cook.