On December 20, 2024, Yummly went dark. The app stopped working. The website went offline. Twenty-six million registered users opened their recipe collections and found nothing there.
They had received about six weeks’ warning. No bulk export option was ever offered. The official guidance — save your recipes one at a time, as PDFs — was technically possible for someone with an afternoon to spare and a few dozen saved recipes. For anyone with a real collection, it was not a solution.
The shutdown raised a question that more people are asking now than they were a year ago: when you “save” a recipe to an app, what do you actually own?
What Yummly was
Yummly launched in 2009 as a semantic recipe search engine. It didn’t host recipes — it indexed them from across the web and let users save favorites to a personal collection. At its peak, the platform had more than 26 million registered users and a database of over two million recipes. It was, by most measures, the dominant recipe discovery app of its era.
In 2017, Whirlpool Corporation acquired Yummly for a reported $100 million. The strategic pitch was appliance integration — personalized recipe recommendations tied to smart ovens and connected kitchen devices. Whirlpool introduced Guided Cooking features and the Yummly Smart Thermometer, a hardware product that retailed for around $100.
In April 2024, Whirlpool laid off Yummly’s entire team of 75 employees, citing a pivot toward generative AI. Eight months later, the app and website shut down permanently. As of December 18, 2024 — two days before the app closed — the Smart Thermometer also stopped functioning. Users who had paid for hardware received partial reimbursements of $30–$87.
The export problem
The data loss wasn’t just a side effect of the shutdown. It was a structural problem that had been there all along.
Yummly stored links to recipes, not the recipes themselves. When a user “saved” a dish, what Yummly recorded was essentially a bookmark — a pointer to a page on someone else’s website, plus some metadata like the ingredient list. The full instructions lived on external servers that Yummly had no control over.
This meant that even before the shutdown, many saved recipes were already partially broken. Food bloggers had deleted posts, moved domains, or restructured their sites. The recipe you saved in 2019 might have been pointing to a page that no longer existed by 2022.
When Yummly closed, users didn’t just lose access to a convenient interface. They lost years of curation — and in many cases, lost the underlying content too, because it was never stored anywhere they controlled.
The Chrome extension workaround that circulated in the final weeks exported a JSON file of collection metadata: recipe names, tags, and external URLs. Not the recipe text. Not the instructions. Just the links — many of which were already dead.
What this reveals about recipe apps
Yummly’s collapse is an unusually clear example of a problem that’s easy to overlook until it’s too late.
Most cloud-based apps create a feeling of ownership without the reality of it. You build a collection, you curate it, you return to it regularly — and so it feels like yours. But if the company changes direction, gets acquired, or shuts down, what happens to that collection depends entirely on decisions you had no part in making.
Yummly isn’t the only case. PlateJoy, a meal planning service, was acquired by a healthcare company in 2021 and shut down by 2025. Whisk, a well-regarded grocery and meal planning app, was acquired by Samsung and gradually drifted away from its original audience as Samsung Food. The pattern isn’t rare — it’s the default trajectory for independent consumer apps that get absorbed by larger organizations.
The users who got burned weren’t naive. They were home cooks who reasonably assumed that a well-funded, widely used app would continue to exist. That assumption turned out to be wrong, and the cost was real.
What to look for in a replacement
If you’re moving your recipes somewhere new, a few questions are worth asking before you commit to another platform.
Does the app store the full recipe, or just a link? A recipe manager that extracts and stores the actual text — ingredients, instructions, servings — is fundamentally more durable than one that bookmarks an external URL. If the original website disappears, your recipe should still be there.
Can you export your collection? This is the clearest signal of whether a product respects data ownership. An app that makes it easy to export your recipes in a standard format is one that isn’t holding your data hostage. If export is buried, limited, or absent, that’s worth noting before you invest years of curation.
Is the company independent? Independent products aren’t immune to shutdowns, but they tend to have simpler incentive structures. An independent recipe app is built to serve its users. An app owned by a hardware manufacturer, a media company, or a consumer health conglomerate is serving a broader strategy — and that strategy may not include your recipe collection indefinitely.
None of these questions guarantee a product’s longevity. But they’re reasonable filters for identifying apps that treat recipe data as something worth protecting.
Moving your recipes
If you have recipes scattered across Yummly exports, saved PDFs, or a browser full of bookmarks, migrating them is more manageable than it sounds.
Start with what you actually cook. Most people find they rotate through a core set of 30–50 recipes. Those are the ones worth migrating first. The aspirational saves — the elaborate weekend projects you bookmarked three years ago and never made — can wait, or be reconsidered entirely.
For recipes you still have as URLs, try importing them directly into a recipe manager that extracts recipe content from websites. If a link still works, this takes seconds. For recipes that exist as PDFs or printed copies, photographing or scanning them is the most reliable path. Apps like Sharp Cooking can extract structured recipes from photos, including handwritten recipe cards.
Once your recipes are stored as full text in a system you control, the underlying website no longer matters. The recipe is yours regardless of what happens to any external service.
Conclusion
Yummly’s shutdown was disruptive. It was also predictable — not because Whirlpool was unusually careless, but because the conditions for this kind of outcome are common in the consumer app market. Products get acquired. Priorities change. Users absorb the cost.
The lesson isn’t to avoid digital recipe management. It’s to choose it carefully. A recipe collection built over years is a personal archive — a record of what your household cooks, how your tastes have evolved, and which dishes matter enough to make again. That archive is worth keeping in a place where you control what happens to it.
For context on how to build a recipe collection that lasts, or why storing a recipe is fundamentally different from bookmarking it, the related guides go deeper on both.
FAQ
What happened to Yummly?
Yummly was acquired by Whirlpool Corporation in 2017 and shut down permanently on December 20, 2024. Whirlpool laid off the entire Yummly team in April 2024, citing a strategic shift toward generative AI. Users received approximately six weeks’ advance notice. No bulk recipe export option was ever provided.
How do I get my recipes out of Yummly?
Yummly is no longer accessible, so direct export is no longer possible. If you used a third-party export tool before the shutdown, you may have a JSON file with recipe metadata and external URLs — though many of those links may no longer work. For recipes saved as PDFs, you can re-import them into a new recipe manager using photo or document extraction tools.
What is the best Yummly alternative?
The most important feature to look for in a replacement is full recipe storage — apps that save the actual recipe text rather than a link to an external website. This protects your collection if a source site goes offline. You should also check that the app supports data export, so you can move your recipes again if you ever need to. Recipe managers with transparent data ownership policies are better long-term choices than large-platform apps with complex ownership structures.
Why couldn’t I export my Yummly recipes?
Yummly was fundamentally a recipe aggregator — it indexed recipes from other websites rather than storing the full content itself. What Yummly saved was primarily metadata and links, not the recipe instructions. This architectural choice made bulk export difficult in practice, and Yummly never built an official export feature. The community-created Chrome extension that existed before the shutdown could export collection metadata but not the recipe text itself.
How do I choose a recipe app that won’t shut down on me?
No app can guarantee permanent operation, but some signals are worth checking. Look for apps that store the full recipe text locally, offer straightforward data export, and have a clear, simple business model — ideally one where users are paying customers rather than an audience being monetized. Independent apps without corporate parent companies tend to have simpler incentive structures than products embedded in larger platform strategies.