The fastest way to save a recipe from any website into a planner you and your partner both use is to paste its URL into slrp — we read the recipe’s structured data (JSON-LD, microdata, or RDFa, which most recipe sites publish for Google), pull out the title, ingredients, cook time, and instructions, and drop the clean recipe straight into your shared library. No retyping, no screenshotting, no scrolling past 2,000 words about someone’s trip to Tuscany.
Want the full step-by-step guide? Read our complete guide to meal planning for couples.
You found the perfect pasta recipe. But first, you have to scroll past a 2,000-word essay about someone’s trip to Tuscany, dodge three pop-ups, and close an autoplay video. By the time you reach the ingredients, you’ve lost the will to cook.
Sound familiar? This is the reality of recipe websites in 2026. The recipes are great — the experience around them is not.
What if you could just... save the recipe?
That’s exactly what slrp does. Paste any recipe URL into slrp and it extracts just the good stuff — the title, ingredients, cook time, and instructions. No ads, no life stories, no clutter.
It works with thousands of recipe sites including Bon Appetit, BBC Good Food, Taste, RecipeTin Eats, Delicious, and more. If the site has a recipe, slrp can grab it.
How it works
- Copy the URL of any recipe you find online
- Paste it into slrp — we extract the recipe automatically
- It’s saved to your shared recipe library, ready for meal planning
No manual entry. No typing out ingredients. No screenshots you’ll never find again. Just paste and go.
What happens under the hood
The extraction isn’t magic — it’s pulling on the same structured data that recipe sites already publish for Google’s rich results. Most food sites embed a JSON-LD block on every recipe page that lists ingredients, cook time, yield, instructions and an image URL. slrp reads that block, normalises the fields, and parses each raw ingredient string (“2 cloves of garlic, finely chopped”) into structured pieces (quantity: 2, unit: cloves, name: garlic, preparation: finely chopped). That structure is what lets your meal plan and grocery list do their job afterwards.
For sites without JSON-LD, slrp tries microdata and RDFa — older standards but still used. If none of those exist (rare on modern recipe sites), we save the link gracefully so you can come back to it via your library. The recipe doesn’t arrive fully structured, but it doesn’t disappear either.
The ingredient parser is the bit we keep refining. “1/2 cup” and “½ cup” need to land as the same quantity. “Yellow onion” and “brown onion” should collapse to one row when both appear in your meal plan. “A handful of parsley” stays a string — we don’t pretend to know the gram-weight of a handful. Most of the gain in the grocery list comes from getting these small parsing decisions right.
Built for couples who cook together
slrp isn’t just a recipe saver — it’s a meal planning app designed for two. When you save a recipe, your partner sees it too. You can both browse the library, toss recipes into a meal plan, and auto-generate a grocery list from everything you’re cooking that week.
It’s the whole workflow: find a recipe → save it → plan your meals → get your grocery list. All from a simple URL paste.
Where the extraction falls short
The honest list of cases that don’t work cleanly today:
- Sites without structured data. A handful of independent food blogs still publish recipes as plain prose without any JSON-LD markup. slrp saves the URL so you don’t lose the find, but the ingredients and steps don’t land structured.
- Recipe data hidden in the instructions. “A splash of milk” tucked into step 4 won’t make it into the ingredient list unless the site declared it up top. We extract what the page declares.
- Video-first platforms. Instagram Reels, TikTok, and YouTube recipe videos don’t emit Recipe schema yet. slrp saves the link so you can rewatch it; we’re watching for when those platforms start structuring recipe metadata.
- Paywalled recipes. If a recipe lives behind a subscription (NYT Cooking premium content, for example), slrp can only read what the public preview exposes. If you have a subscription and a logged-in browser already saved the page locally, that’s a different story — but the extraction itself runs server-side, so it sees what an anonymous browser would.
Stop bookmarking, start cooking
Browser bookmarks, screenshot folders, recipe apps that make you type everything in — none of it works long-term. slrp is the recipe saver that actually sticks, because it takes less than 5 seconds to save a recipe and it’s immediately useful for your next meal plan.
Want to take it further? Read our complete guide to meal planning for couples, learn how to plan meals together, or auto-generate your grocery list.
Ready to ditch the recipe clutter?
Common questions about saving recipes
How do I save a recipe from any website?
In slrp, paste the URL into the add-recipe field. We fetch the page, pull the recipe data out of its structured markup (JSON-LD, microdata, or RDFa), and store the ingredients and steps in your library — no manual retyping, no scrolling past life stories. For sites that don't publish structured data, we fall back to saving the link itself so you can come back to it.
Why can't I just bookmark recipes in my browser?
You can — but bookmarks don't help when you want a grocery list from five recipes, or when the original page goes down, or when you're standing at the stove and don't want to scroll past three ads and a story about the author's grandmother. Saving the recipe (not just the URL) lets the app turn it into a plan, a grocery list, and a cooking view.
Does slrp save recipes from Instagram, TikTok, or YouTube?
Not yet — those platforms don't publish recipe data in the structured format Google and slrp read. We do save the link so you can come back to the video, and you can manually re-create the recipe in your slrp library. We're watching how the platforms handle recipe metadata; when Instagram and TikTok start emitting Recipe schema, slrp will read it.
Can I save a recipe from my phone's share sheet?
Yes — slrp's iOS share extension lets you share any URL from Safari, Mail, or Messages directly into your slrp library. The extension uses the same extraction pipeline as the web app, so the ingredients and steps land structured the same way. After saving you can keep browsing, then open slrp later to plan the recipe in.
