Save recipes from the internet — and find them again three weeks later

When you open your smartphone and tap «Bookmarks» in the browser, you probably see a list of 80–200 addresses. Of those, it feels like 30 are recipes. You don't recognise them by the title, because the title is usually called «The world's best tomato sauce — my story from Tuscany» and not «Tomato sauce». You don't recognise them by the thumbnail, because the browser shows none. You simply don't recognise them again.

The same goes for screenshots — the photo library fills up with images from Instagram, you scroll through 800 photos two weeks later and can't find the one recipe. It's there. But without order, saving is almost worthless.

This isn't a personal failure. Browser bookmarks were made for websites, not for recipes — they have no fields for ingredients, prep time, category. Photo apps were made for memories, not for recipes. You can force them to play recipe archive — but they play it badly.

What you actually need is an app with three properties:

1. Fast saving — paste an address, done. No manual typing.
2. Its own fields for ingredients, steps, time, category — searchable.
3. Find again in under 10 seconds — filters (vegetarian, <30 minutes, with aubergine), search, image preview.

The rest of this article shows four ways that deliver this — three with their weaknesses, one as a recommendation.

The obvious attempt: you create one note per recipe. Copy in title + ingredients + steps, take a photo, add the URL as the source. With a bit of discipline, a searchable recipe archive emerges.

Strengths:

• You have full control. Format, tags, structure are up to you.
• Works offline, runs on all devices.
• If you use Notion/Evernote/Apple Notes anyway, no extra tool.

Weaknesses:

• A lot of manual work. You have to copy, format, sometimes insert images. 3–5 minutes per recipe.
• No dedicated fields for ingredients and steps. «Ingredients» is a text block in the note body. You can't ask «show me all recipes with aubergine».
• No shopping list. You can't derive a list from a note — you'd have to retype it.
• Becomes cluttered with many recipes. Up to 30 recipes it's fine, at 200+ the note list itself becomes a bookmark graveyard.

Conclusion: note apps are good for a few recipes with high personal context (family recipes with memories). For a growing everyday archive, they're the wrong tool.

There's a whole class of apps that solve exactly this problem — recipe managers. Best-known representatives: Paprika, Pestle, Mela, Crouton (each ~5–25 CHF one-off or subscription). They have a built-in browser into which you enter the recipe URL, and the app automatically pulls out the title, ingredients, and steps.

Strengths:

• Fast import via URL. You paste the address, the app fetches the recipe itself.
• Clean fields. Ingredients, steps, time, category — each on its own line, searchable.
• Shopping lists and weekly-plan features (depending on the app).

Weaknesses:

• Built for a single person. Most classic recipe managers were built as solo apps. Family sharing is often awkward (no real-time sync, every adult needs their own account).
• Pricing model. Paprika costs separately per platform (~5 CHF iOS + ~5 CHF Android + ~25 CHF macOS — if you use it across several devices).
• Proprietary format. Export is possible, but the file format belongs to the app. Moving to another tool is possible, but takes time.
• No continuous weekly-plan mode in most of these apps — you can collect recipes, but the path «collect → plan → shop → cook» isn't all of a piece.

Conclusion: recipe managers are a clear step forward from note apps, but they remain recipe archives. If you want to collect and collecting is an end in itself, they're good. If you want to think further into weekly plan + shopping, you need an app that does that as well.

If your recipe inspiration comes mainly from Instagram, TikTok, or YouTube, the temptation is great to use the platform-native bookmark features — Saved Collections on Instagram, playlists on YouTube, favourites on TikTok.

Strengths:

• Zero effort. One tap, the recipe is «saved».
• Original format. You keep video, language, style. If the recipe is a 60-second reel, you've got the reel.
• Visual. You remember by the image — not always the case with food blogs.

Weaknesses:

• You lose it if you leave the platform. Delete Instagram, your recipes are gone. Account gets blocked → gone. Platform retires the feature → gone.
• No access to the ingredients as a list. You have a 60-sec reel in which the person says the ingredients. While cooking you have to find the spot where they said «two tablespoons of olive oil».
• Search is bad. Instagram Saved has no useful search. You scroll.
• Useless in the supermarket. You want a shopping list; what you have is a reel.

Conclusion: Instagram/YouTube collecting is the «I'll deal with it later» solution. In reality, nobody deals with it later. What you really want: to move the recipe from the reel into a proper recipe card you can actually use in the supermarket. That's the transition to Way 4.

mangia is built differently from the classic recipe managers. Instead of «collect recipes» as an isolated function, collecting is part of a continuous path: collect → into the weekly plan → from there a shopping list → cook → the family can follow along.

Concrete import ways in mangia:

• URL import. You paste the address of a food blog / recipe page. mangia reads the page's structured recipe data and creates a clean recipe. Works with all pages that supply such data (80–90 % of food blogs do today). For the remaining 10 %, mangia automatically reads the recipe from the text.
• PDF import. Got a PDF of a cookbook excerpt, a meal-box insert, an old magazine? Drop the PDF in, mangia reads it.
• Photo import. Photo of a recipe card, a book excerpt, a board in a restaurant? Photo in, mangia automatically fetches title + ingredients + steps.
• Paprika import. Got a collection in Paprika? In Paprika you export a `.paprikarecipes` file (all recipes in one archive), drop it into mangia, and mangia creates each recipe individually in your library. Works for the whole collection in one step — a very popular migration path.
• Share-to-mangia (Android, iOS to follow). You're in the browser, in Instagram or YouTube, you tap «Share» → «mangia», the recipe lands in the archive. One tap.

What then happens with the imported recipe:

• It lands in your personal recipe collection.
• You can drag it by drag-and-drop into your weekly plan.
• From the weekly plan, a shopping list emerges automatically, in which identical ingredients from several recipes are merged (3 × «1 onion» = «3 onions»).
• While cooking, the cooking mode guides you through the recipe step by step in order.

That's the point where collecting is no longer an end in itself — but only the beginning. Classic recipe managers leave you standing at a collection. mangia takes you from there all the way to the meal on the table.

There isn't the right way, but the right way for your everyday life. Three typical profiles:

Profile 1 — the occasional collector («5 recipes a month»). You don't need a specialised app. Apple Notes with a single note «Recipes» and category tags is enough. If you ever reach 50+ recipes, you can switch. Until then: keep the effort minimal.

Profile 2 — the ambitious collector («20-50 recipes a month, watches a lot of Instagram/YouTube»). You need fast import + clean fields. Here mangia is a good fit, because Share-to-mangia and the automatic photo import bring the effort per recipe close to zero. Paprika & co. also work, but are less convenient when the recipe happens to be on your phone.

Profile 3 — the weekly planner («I want to plan, shop, cook, all from one app»). Here classic recipe managers usually aren't enough — they're recipe archives, but not a continuous path from collecting to shopping. mangia walks the path plan → list → cook in one app. If you cook in a family (shared list, child profiles), mangia is the easiest way today.

The honest cross-comparison table:

For «I want a meal on the table and no stress getting there», mangia is a very good choice today. For «I just need notes», it's over-engineered.