How to save a recipe from any website

Every recipe website has the same shape. Twelve hundred words about a trip to Sicily, four ads, a video that starts playing on its own, a newsletter popup, and then somewhere near the bottom, the thing you came for.

You don't want the page. You want the list.

The short answer

Copy the URL, open Fork & Spoon, paste it into import. You get back the ingredients with amounts as separate rows, the steps in order, and nothing else. On a phone you can share the page from your browser straight to the app instead.

What happens behind the scenes

Worth knowing, because it explains why some pages come through perfectly and others come through rough.

Structured data first. Most modern recipe sites embed a machine-readable version of the recipe in the page, the same data that lets Google show cooking times and star ratings in search results. It follows a shared standard and contains exactly the fields you want: ingredients, steps, servings, timings. When Fork & Spoon finds it, that's what gets used instead of reading the visible page, and the result is close to perfect because the site did the structuring itself.

Page text as the fallback. Plenty of sites don't publish that data, especially older blogs and anything hand-built. Then the visible page gets read and the recipe is worked out from it. This is where the ads and the Sicily story get stripped out, and it's slightly less exact: a stray "Jump to Recipe" or a related-posts heading occasionally sneaks in. That's a quick edit rather than a problem.

Identifying as a browser. A surprising number of recipe sites return a 403 or a cookie wall to anything that doesn't look like a person with a browser, so Fork & Spoon sends normal browser headers. It's the most common cause of "import just does nothing" in tools that skip that step.

Sites that won't import

Honestly:

• Paywalled recipes. If you need a subscription to see the recipe in your own browser, it can't be read from outside either. Open it while logged in, screenshot it, and use photo import.
• Hard cookie walls. Some sites show nothing at all until you accept tracking, and there's no page to read behind that.
• Recipes that only exist as an image. A scanned page or a graphic with the recipe drawn on it has no text to extract. Photo import handles those.
• Pages assembled by JavaScript after loading. Less common on recipe sites than it used to be, but it happens.

What you get back

• Ingredients as separate rows with amounts and units, so you can scale servings and send the lot to a shopping list
• Steps in order, without the ads or the anecdote
• The source link, kept with the recipe so you can go back to the original
• Servings, timings and cuisine where the page states them

You review it before saving. Import the same URL twice and Fork & Spoon notices and warns you first, so you don't end up with the same lasagne four times.

Where you do this, and who with

On the computer where you found the link. The same account opens in a browser at app.forkandspoon.app with nothing to install, and it works on a Windows machine or a shared family desktop. Since recipe links are usually found while sitting at a computer, that's where importing actually happens for most people, with the results waiting on your phone by dinnertime.

With someone on a different kind of phone. A shared cookbook works between an iPhone and an Android phone at once, along with the week menu and the shopping list. Whoever gets to the shop first ticks things off and the other one sees it.

And with people who've got nothing installed. Any recipe can be sent as a link that opens as an ordinary web page, which is what the original site did, minus the anecdote about Sicily.

Doing it by hand

1. Many recipe sites have a "Jump to Recipe" button at the top. Use it.
2. Select the ingredient list and the steps, copy.
3. Paste into a notes app and strip the leftovers, since the "Print" and "Pin" buttons often come along with the selection.
4. Paste the URL at the top so you can find the original.

Or use your browser's reader mode first, which removes most of the noise before you copy. Neither approach gives you separated amounts you can scale or tick off in a shop, but both beat a bookmark.

Why a bookmark isn't enough

Bookmarks rot. Blogs get abandoned, domains lapse, and recipes get rewritten or quietly deleted when a site redesigns. A recipe you've actually saved doesn't depend on someone else keeping their hosting bill paid.

And once it's saved properly it does things a bookmark can't: land on a Thursday in the week menu, break itself into a shopping list ordered by supermarket aisle, and go to whoever's cooking as a link that opens in any browser without an app.