Quick quiz: where is that roast chicken recipe you loved three weeks ago? Take a second. Is it a browser bookmark, a screenshot buried in your camera roll, a link your partner texted you, a tab you never closed, or a vague memory of "that one site with the good crispy skin"? If you had to check more than one place, you don't have a recipe collection. You have a recipe scatter.
This is the quiet problem underneath almost every "what's for dinner?" stall. It's not that you don't have good recipes — you've saved dozens. It's that they're spread across so many places that finding one is more effort than just ordering takeaway. The recipes exist. You just can't lay hands on them when it counts.
Here's how to fix that: what "in one place" should actually mean, why the scatter happens, and how to build a single recipe home you'll genuinely use — especially if there are two of you both saving things.
Where your recipes actually live right now
Most people's recipes are spread across five or six systems that don't talk to each other:
- Browser bookmarks — a folder called "Recipes" with 60 links, none of them titled usefully, half of them dead.
- Screenshots — the fastest way to "save" a recipe and the worst way to find one later. Your camera roll is not searchable by "the pasta thing."
- Instagram and TikTok saves — a growing pile of reels you'll rewatch never, because rewatching a 40-second video to get a quantity is nobody's idea of cooking.
- Texts and DMs — "send me that recipe" is where recipes go to be forgotten. It's in the chat somewhere, scrolled past weeks ago.
- Open browser tabs — the 19 tabs you're keeping open because they're recipes you mean to cook. They will die in a browser crash.
- Actual paper — the printout, the magazine tear-out, the card in your nan's handwriting. These are the ones worth keeping and the easiest to lose.
Each of these felt sensible in the moment. The problem is the sum: no single place holds everything, so "find a recipe" becomes "search six places, give up, cook the same three meals you always cook."
Why the scatter happens (and why it's not your fault)
The scatter isn't a discipline problem. It's a design problem. You find recipes in lots of different contexts — scrolling your phone on the couch, reading a blog on your laptop, standing in a friend's kitchen — and each context has its own easiest "save" button. On Instagram it's the bookmark. On a website it's the browser bookmark or a screenshot. In a chat it's just… leaving it in the chat.
Every one of those saves takes the path of least resistance in the moment, and every one drops the recipe into a different bucket. Nobody sits down and decides to fragment their recipe collection across six apps. It happens one convenient save at a time.
And it gets worse with two people. When you're cooking as a couple, you've now got two phones, two camera rolls, two Instagram accounts, and two sets of bookmarks — and the recipe your partner loved is saved in a place you can't even see. Half your shared collection is invisible to the other half. We wrote a whole piece on why the nightly "what's for dinner?" debate is really a decision-fatigue problem, and a scattered recipe collection is the fuel that keeps it burning.
What "in one place" should actually mean
"Keep all your recipes in one place" is easy advice and useless on its own — a folder of 60 dead bookmarks is technically "one place." The place has to actually work. A real recipe home passes five tests:
- It's searchable. You can type "salmon" and find every salmon recipe you've saved, in seconds. Screenshots and bookmarks fail this instantly.
- It's readable. When you open a saved recipe, you see the ingredients and method — not a 2,000-word essay, three pop-ups, and an autoplay video you have to scroll past to reach the actual food.
- It's shared. If two people cook together, both people can see and add to the same collection. One partner's saves shouldn't be locked inside their phone.
- It's usable. A saved recipe should lead somewhere — onto a meal plan, onto a grocery list — not just sit in a pile you admire occasionally.
- It's low-effort to add to. If saving a recipe takes more than a few seconds, you won't do it, and you'll be back to screenshots within a week.
Any system that fails these tests will slowly leak back into the scatter. A folder of bookmarks fails four of the five. That's why it never sticks.
How slrp keeps every recipe in one place
slrp is a recipe organiser built around exactly these tests. The core move is simple: you paste a recipe's web address and slrp pulls out just the good stuff — the title, ingredients, cook time, and method — and drops it into your library, minus the ads and the life story. We go deep on the mechanics in how to save recipes from any website, but the short version is: copy the link, paste it, done. No retyping ingredients, no screenshots you'll never find.
Because everything lands in the same library, it's all searchable in one box. That salmon recipe from three weeks ago is one search away, not a six-app treasure hunt. And because slrp strips each recipe down to the essentials, opening a saved recipe shows you the food — not the clutter it came wrapped in. Our recipe organiser is the whole feature, if you want the full tour.
The part that matters most for couples: the library is shared. slrp is built for two people who cook together, so both partners save into the same collection and both partners can see all of it. The recipe your partner loved isn't trapped on their phone anymore — it's right there in the library you both use. No more "send me that recipe" texts that vanish into the chat.
And crucially, the collection does something. A recipe in your slrp library isn't a dead bookmark — it's ready to drop onto a meal plan, which then builds you a grocery list automatically. The whole point of organising your recipes is so you can actually cook them, and slrp closes that loop.
Setting it up: a 20-minute recipe cleanup
You don't need to migrate five years of saved recipes in one sitting — in fact, please don't. Most of those bookmarks are dead or were saved on a whim you no longer remember. Do this instead, once, in about twenty minutes:
- Open your bookmarks folder and be ruthless. You're not saving all 60. You're saving the ten or so recipes you've actually cooked or genuinely still want to. Delete the rest without guilt — if you haven't cooked it in a year, you're not going to.
- Paste those ten links into slrp. A few seconds each. Now your keepers all live in one searchable place.
- Do a quick camera-roll pass. Find the recipe screenshots worth keeping, track down the original recipe online, and paste that link in. For the handful you can't find a source for, that's fine — screenshots that survive a cull are usually the ones you've memorised anyway.
- Add your partner. Get both of you saving into the shared library from day one, so the collection is complete instead of half-hidden on someone's phone.
That's the migration. Ten good recipes beat sixty dead bookmarks, and you'll add to the collection naturally from here.
Keeping it tidy without it becoming a chore
The reason recipe collections rot is that "organising" them sounds like admin, and admin is the thing you'll always postpone. The trick is to make saving the default action in the moment you find a recipe, so there's never a backlog to organise later.
- Save the second you find it, not later. "Later" is where recipes go to be forgotten. Saw something good on your phone at lunch? Paste the link into slrp before you close the tab. Ten seconds now beats never.
- Stop screenshotting. A screenshot is a save that fails every one of the five tests. Break the habit: when you're tempted to screenshot a recipe, save the link instead.
- Let the video recipes go through the source. Most reels and TikToks are re-plating a recipe that also lives on a website or in the caption. Find the written version and save that — you'll thank yourself when you need a quantity mid-cook and don't have to scrub a video.
- Trust the collection. The whole payoff is being able to stop hoarding "just in case." Once everything you'll actually cook is in one searchable place, you can let the rest go.
The real payoff isn't tidiness
Getting your recipes into one place feels good on its own — but tidiness isn't the point. The point is what a real collection lets you do next. When every recipe you'd actually cook lives in one searchable, shared library, meal planning stops being "stare at a blank week and Google for inspiration" and becomes "pick five things from the collection we already love." That's the difference between a plan that happens and a plan that doesn't.
From there, the rest of the system falls into place: a plan you both agree on, a grocery list that builds itself, and far fewer "what's for dinner?" stalemates. If you want the full workflow, our complete guide to meal planning for couples walks through it end to end, and once your library's sorted, how many meals to actually plan for the week is a good next read.
Start with the twenty-minute cleanup. Ten good recipes, one place, both of you. It's a small change that quietly fixes a surprising amount of dinner.
