How to Save Recipes from Pocket, Feedly & Read-Later Apps (Before They Pile Up Unread)
Read-later apps are built for articles. A recipe is not an article — it is structured data: ingredients with quantities, steps in order, a serving count. Pocket saves the text around the recipe. Feedly saves the post. Neither gives you something you can actually cook from.

The Read-Later App Is a Recipe Black Hole
Pocket has over 150 million registered users and has processed more than three billion saves since its launch in 2007. A substantial portion of those saves are recipe articles. Feedly, the leading RSS reader, has roughly 14 million active users, many of them following food blogs, recipe newsletters, and cooking publications. Both apps are very good at the thing they were built for: making long-form articles readable later, without the ads and distractions of the original webpage.
The problem is that a recipe is not a long-form article. When a food blogger publishes a new dish, the post typically runs to 800 or 1,500 words: an introduction, a personal story, photography notes, variations, substitutions, and then the actual recipe — a structured block of ingredients and steps tucked somewhere in the middle. Pocket saves all of that as a single block of text. Feedly displays the full post in its reader. In both cases, you end up with the article, not the recipe.
This distinction matters the moment you try to cook. You cannot scale a recipe saved as text. You cannot generate a shopping list from it. You cannot search your Pocket archive by ingredient. You cannot ask “what can I make with chicken and spinach” and have Pocket surface the five recipes you saved last winter that match. The article exists in your queue; the recipe inside it is not accessible as recipe data.
Why So Many Recipes End Up in Read-Later Apps
The flow is entirely natural. You follow Smitten Kitchen in Feedly. A new post arrives on a Tuesday morning. You are at work, you do not have time to read it properly, and you definitely do not have time to cook it right now. You mark it Read Later or save it to Pocket with one tap. The intention is genuine: you will come back to it at the weekend.
The weekend arrives, you are in the supermarket with no list, and the recipe is somewhere in Pocket under a hundred other things you also meant to read. The efficient path is to buy what you already know how to cook. The recipe stays unread. By the time you remember it, six months have passed and the ingredients are out of season.
The same pattern repeats across Instapaper, Safari Reading List, Chrome bookmarks with the Pocket extension, and any other save-for-later tool that treats web content uniformly. They are all optimised for reading, not for cooking. A recipe saved to Pocket is not a recipe in your kitchen — it is a reminder that you once intended to cook something.
What Feedly Does Well (and Where It Falls Short)
Feedly is genuinely useful as a recipe discovery tool. If you subscribe to the right food blogs — Serious Eats, NYT Cooking, Bon Appétit, Ottolenghi’s newsletter, a handful of independent food writers — Feedly puts every new recipe in one place the moment it is published. The signal-to-noise ratio is much better than social media, and the posts appear in full without algorithmic suppression.
Where Feedly falls short is at the moment of cooking. Feedly has no concept of a recipe as a data structure. A post saved to a Feedly board is stored as a blog post with a title, a publication date, and full text. There is no ingredients field, no step counter, no serving size metadata. When you open a Feedly board to decide what to cook this week, you are browsing articles, not browsing recipes — and the difference matters when you are standing in a supermarket with ten minutes to shop.

How to Get Recipes Out of Pocket
The key insight is that Pocket saves the original URL alongside the cached article text. That URL is the thing you need: it points to the original recipe page, which almost always contains machine-readable recipe metadata (structured data in Schema.org/Recipe format) that Pantree can read directly and accurately.
Step by step
- Open Pocket and find the saved recipe article.
- Tap the overflow menu (the three dots) and select “Open original” or “Share” → copy the link. Make sure you copy the original URL (e.g.
smittenkitchen.com/2026/...), not apocket.coshare link. - Open Pantree and tap + → Import from URL.
- Paste the URL. Pantree fetches the recipe’s structured data — ingredients, steps, serving count, cook time — and saves it as a proper recipe entry with auto-scaling and a shopping list.
For recipes on major food sites — NYT Cooking, AllRecipes, Serious Eats, BBC Good Food, Tasty, Bon Appétit, Epicurious, Food52 — this takes under ten seconds and is accurate. For personal food blogs using standard WordPress recipe plugins (WP Recipe Maker, Tasty Recipes, Mediavine Create), it works equally well because those plugins embed the same Schema.org structured data.
How to Get Recipes Out of Feedly
Feedly makes it slightly easier to get to the original URL because feed posts are displayed with a direct link to the source article at the top of every post. Tap the title or the external link icon to open the original page in your browser, then copy that URL and use it in Pantree exactly as above.
If you have saved recipes to Feedly boards over months or years, the systematic approach is to open each board, go through the saves, open the original link for each recipe you actually want to keep, and import it into Pantree. For an average queue of 30–50 saved recipe posts, this takes about an hour once and is not a task you repeat — it is a migration from an article graveyard into a recipe library.
What About Instapaper and Safari Reading List?
Both have the same structural issue as Pocket. Instapaper is an older, simpler read-later service with no recipe-specific functionality. It saves articles as text and has remained largely unchanged since Pinterest acquired and then divested it. Safari Reading List is Apple’s built-in equivalent — articles saved to it are accessible offline in Safari but have no search, no tags, and no recipe parsing.
The fix is identical for both: find the original URL behind the saved article (in Safari Reading List, long-press the item to see the URL; in Instapaper, tap the article title and use the external link icon), and import that URL into Pantree. The underlying recipe data on the original page is what matters, not the tool you used to save the article.
The Broader Pattern: Discovery Versus Use
Read-later apps solve a real problem — they let you pull interesting content out of a noisy feed and read it later in a cleaner format. For recipes, though, the journey from discovery to dinner requires a second step that general read-later tools never provide: converting the article into structured recipe data that you can actually cook from.
The practical workflow that works: use Feedly (or any RSS reader, or following food writers on Substack) for discovery — that is what these tools do well. When something looks genuinely worth cooking, skip the read-later queue entirely and import the URL directly into Pantree. The recipe is then in a library you can search by ingredient, scale for any number of people, and turn into a shopping list in two taps. It never enters the read-later graveyard at all.
For recipes already buried in Pocket or Feedly, the URL method above recovers them efficiently. A queue of a hundred saved recipe articles typically contains twenty or thirty worth actually keeping. Those twenty or thirty take under five minutes to migrate. The rest can be archived or deleted without guilt — if you have not cooked from them in six months, the moment has passed.
Related Guides
If food content fragmentation is a problem across multiple apps, there are guides for saving recipes from browser tabs, getting recipes out of Evernote, and migrating recipes from Notion. For recipes arriving via email newsletters and Substack, the email newsletters guide covers the same URL-import approach applied to inbox saves.
Frequently Asked Questions
Can Pocket save a recipe as a structured entry with ingredients and steps?
No. Pocket saves the full text of an article, stripping most formatting and ads so the reading experience is cleaner. What it cannot do is identify which part of that text is an ingredients list, parse quantities and units, separate prep steps from headnotes, or store the recipe in a form that can be scaled or used to generate a shopping list. The recipe is inside the saved article as running text, but Pocket treats it the same way it treats a news story or a think-piece: as a block of text to read, not a structured data object to act on.
Is Feedly better than Pocket for saving recipes?
Feedly is a feed reader built around following blogs and publications, so it is better at surfacing new recipes as food bloggers publish them — you subscribe to Smitten Kitchen or Serious Eats and see every new post in one place. For saving recipes, however, it has the same structural problem as Pocket: the recipe lives inside a blog post formatted as a long article, and Feedly stores that post as text, not as a recipe. You can mark posts as Read Later or save them to boards, but there is no ingredient extraction, no scaling, and no shopping list. Feedly is a discovery tool; it is not a recipe manager.
What happened to Pocket's recipe features?
Pocket has never offered structured recipe features. It was built as a general-purpose read-later tool for any web content, and its core offering — distraction-free reading of saved articles — is not a natural fit for recipe use. Mozilla acquired Pocket in 2017 and has maintained it as a general reading app. In 2023, Mozilla announced plans to wind down direct Pocket development and integrate its features into Firefox. As of 2026, Pocket continues to operate as a standalone app, but no recipe-specific functionality has ever been added. The gap between what Pocket saves (an article) and what a cook needs (structured recipe data) has remained constant since the service launched in 2007.
How do I find all the recipe articles I have saved in Pocket?
Pocket's search function searches the full text of saved articles, so searching for words like 'ingredients', 'tablespoon', 'preheat', or specific ingredient names will surface recipe articles. You can also tag saved articles — if you have tagged recipe saves as 'recipe' or 'food', you can filter by that tag. For Feedly, you can filter your saved posts by board or tag if you have been consistent about organising saves. In both cases, the search finds the article; what you do with the recipe inside it is a separate step.
Can I import a Pocket article's URL into Pantree?
Yes, and this is the recommended approach. Pocket saves the original URL of each article alongside the cached text. Open the article in Pocket, tap the overflow menu or share icon, and copy the original URL (not the pocket.co link). Paste that URL into Pantree's Import from URL feature and Pantree fetches the structured recipe data directly from the original recipe page. This is faster and more accurate than copying the Pocket article text by hand, because Pantree reads the page's machine-readable recipe metadata rather than trying to parse running text.
What is the best read-later app specifically for recipes?
General read-later apps — Pocket, Instapaper, Feedly's save feature, Safari Reading List, Chrome bookmarks — are all built for articles, not recipes. The best read-later tool specifically for recipes is a dedicated recipe app that treats ingredients, quantities, steps, and serving counts as first-class data rather than text. Pantree imports recipes from any URL (including the original URLs behind Pocket saves), from photos and screenshots, and from manual entry, and stores each recipe as structured data you can scale, search by ingredient, and use to generate a shopping list. The difference is not cosmetic — a recipe saved as text is something you read; a recipe saved as structured data is something you cook from.