Your partner wants that pasta recipe you made last week. Your grandmother's stew should go to your niece. Your housemate wants to help cook but has no idea how you do it. Sharing recipes sounds simple, but in practice 90% of shared recipes end up as "I sent it on WhatsApp" — and then never found again. Here's how to tackle it properly.
Use cases: why people share recipes
Couples and cohabitators — both have their favorites, slowly merging into "our repertoire"
Families at a distance — parents passing down classics, adult children sharing new discoveries back
Housemates — a shared kitchen collection everyone cooks from and contributes to
Friend groups — after a dinner, everyone wants that recipe, one easy handoff instead of five WhatsApps
Each use case has a different solution. Not everything needs to be a shared collection.
Three levels of sharing
Level 1: Sharing individual recipes (one-off)
You send someone one recipe they want to try. Best approach:
- Short link — the recipe on Parsely has a shareable URL, send that via WhatsApp or iMessage
- Curated — add a sentence on why you like it: "super simple, 30 min"
- Receiver can save it — if they're on Parsely, one click to save; if not, they see a clean webpage
Level 2: Shared list (family / housemates)
For people who cook, live, or plan together:
- A shared "Dinners" list where everyone can add
- Scale portions per household size — useful when the group is sometimes 2, sometimes 5
- Notes per recipe — "this was everyone's favorite" or "less chili next time"
This level turns meal planning from "I decide, you cook" into really together.
Level 3: Family archive (generational)
Grandma's stew, grandpa's steak sauce, aunt's cake. These are recipes that disappear if you don't actively digitize them.
- Photograph handwritten recipes with Parsely's photo import
- Add family context in the notes ("grandma always made this for Christmas")
- Share with cousins — same collection, everyone has access
A family archive list is something you never regret. Within 10 years, handwritten recipes often become illegible or get lost.
What to avoid
- WhatsApp as a recipe archive — searching WhatsApp for "that recipe from March" is misery
- Screenshots that sink into your camera roll — you'll never find it again
- Email as a solution — same problem, just slower
If you're sending the same recipe three times to three people, it's time for a real approach.
Etiquette when sharing recipes
Small things that make a difference:
- Credit the source if you didn't invent it. Creators appreciate credit.
- Be honest about adjustments — "I did it with half the garlic" is useful for the recipient
- Ask before sharing someone else's recipe — some family recipes are seen as "ours"; check before forwarding
How Parsely supports this
Parsely has three sharing paths:
- Public sharing per recipe — send a link anyone can open, even without an account
- Private lists — shared list between selected people (for example, your family)
- Public collections — larger themed collections you publicly curate
Start where you are: first share individual recipes via link, then a shared list with your partner, then maybe a family archive. Start sharing recipes in Parsely and experiment with what level fits your situation.