Mealie Review: A Developer's Honest Look at the Self-Hosted Recipe Manager
Mealie keeps coming up whenever developers ask about self-hosted recipe management. It's got 11,000+ GitHub stars, an active community, and a genuinely polished web interface. If you're evaluating recipe management options and Mealie is on your list, here's what you actually need to know.
One disclosure up front: we make Cooklang, which is a different approach to recipe management. We'll get to the comparison at the end. But the bulk of this review is about Mealie on its own terms — what it does well, where it gets frustrating, and who it's built for. Take our perspective on alternatives with that context in mind.
What Mealie Is
Mealie is a free, open source, self-hosted web application for managing recipes. The stack is Python (FastAPI backend) and Vue.js frontend. Deployment is Docker-based — the standard install is a docker-compose.yml that spins up the app alongside a database. You get a polished, mobile-friendly web UI that works from any browser on your network.
The project lives at github.com/mealie-recipes/mealie. There's a live demo at demo.mealie.io if you want to click around before committing to a self-hosted install.
Core features:
- Recipe import from URLs (web scraping)
- Meal planning with a calendar view
- Shopping lists generated from meal plans
- Multi-user support with household groups
- A full REST API
- Supports SQLite or PostgreSQL as the backend database
It is free software. The cost is your time and your hosting infrastructure.
What Mealie Does Well
Web Scraping
The most-praised feature, and it earns the praise. Point Mealie at a recipe URL and it pulls out the title, ingredients, instructions, and often the photo. This works reliably on most major food sites because those sites use Schema.org structured data, which Mealie parses directly.
This isn't magic — any tool that reads application/ld+json gets most of the work for free. But Mealie handles the cases that structured data misses, and the import workflow is smooth enough that you'll actually use it.
The UI
Mealie's interface is polished. The recipe cards look good, the cooking mode is readable on a phone propped against your kitchen backsplash, and the meal planner has a proper calendar with drag-and-drop. It feels like a real consumer product, not a project someone put on GitHub and hoped for the best.
For non-technical household members, this matters a lot. You can hand someone a URL to your Mealie instance and they'll figure it out without a tutorial.
Multi-User Households
Mealie has a genuine household model. Multiple users, permission levels, shared meal plans, shared shopping lists. This is the use case it's built for: a family where multiple people contribute recipes, plan meals together, and need a shared shopping list that updates in real time.
If you live alone or are the only cook, most of this goes unused. But if "multiple people in my house need to use this" is a hard requirement, Mealie has a real solution.
The API
Mealie exposes a documented REST API over everything — recipes, meal plans, shopping lists, tags, categories. If you want to automate around your recipe data, the API is there. Some people use it to pull meal plan data into Home Assistant, push recipes from other tools, or build custom shopping list integrations.
Where Mealie Can Be Frustrating
Docker Is Required
This is not a criticism of Docker. But "requires Docker" is not trivial for everyone. If you're a developer who runs containers routinely, the docker-compose up -d install takes ten minutes. If you're a home cook who knows their way around a terminal but hasn't worked with containers, it's a steeper ramp.
Mealie doesn't have a native desktop app. There's no "download and run" installer for macOS or Windows. The only path is a server — whether that's a VPS, a Raspberry Pi on your home network, or a NAS that supports Docker. That's a real prerequisite.
Your Data Lives in a Database
Recipes in Mealie are stored in SQLite or PostgreSQL. That's fine for the app. It's frustrating when you want to access your recipes outside of Mealie.
You can't just open a recipe in a text editor. You can't grep your recipe collection. You can't put it in Git. The data is there, but it's in a database, and the database is inside a Docker volume, and getting a single recipe out in a readable form requires going through the web interface or the API.
Mealie does have export functionality — you can export your data in various formats. But the exports are for backup, not for working with recipes as files. The recipe format is opaque by design.
Updates Sometimes Break Things
Mealie moves fast, which is mostly a good thing. Frequent updates mean bugs get fixed and features get added. The downside is that database schema migrations are a real part of the update process. Most of the time they work automatically. Occasionally they don't, and you're in a situation where your app won't start and you're debugging Docker logs to figure out what migrated incorrectly.
If you're running a self-hosted service that your household depends on, you need a backup strategy and some tolerance for occasional maintenance windows. That's not unique to Mealie — it's true of any self-hosted web app — but it's worth being clear about.
No Offline Mode
Mealie is a web application. If your server is down, unreachable, or you're somewhere without a network connection, you have no access to your recipes. There's no offline mode, no local cache, no client-side storage.
For most home use cases — cooking in your kitchen where your home server is running — this is fine. But it's a real limitation if you want to cook from a recipe while camping, traveling, or anywhere your Mealie instance isn't reachable.
Scraping Quality Varies
The URL import works well on mainstream food sites. It works inconsistently on smaller sites, personal food blogs, and anything that doesn't follow structured data conventions. You'll sometimes get a recipe with instructions merged into a single block, or ingredient quantities parsed incorrectly, or a photo that didn't come through.
This isn't a Mealie-specific problem — it's inherent to web scraping. But it means imports require occasional cleanup, and some sources just don't work.
Who Mealie Is For
Mealie is the right choice if you want a turnkey web application for your household's recipe collection and you're comfortable with Docker.
Specifically, it fits if:
- Multiple people in your household need to access and contribute recipes
- You import recipes from the web frequently and want that to be low-friction
- You want a polished interface that looks good and works on phones
- You're comfortable maintaining a Docker-based service
- You want a shared meal plan and shopping list
It's not a great fit if you want something you can run without a server, need offline access, want to version-control your recipes, or prefer to keep your data in a format you can access without the app.
A Different Approach
Cooklang takes the opposite philosophical position from Mealie. Instead of a web application backed by a database, Cooklang recipes are plain text files. They look like this:
No server required. No database. Any text editor opens it. You can sync it with iCloud, Dropbox, or Git. The CookCLI generates shopping lists, runs a local recipe server, and handles imports. There are native mobile apps for iOS and Android.
The trade-offs are real. No built-in web scraping with a GUI. No multi-user dashboard. No drag-and-drop meal planner. If those features matter to you, Mealie has them and Cooklang doesn't.
But if your priority is data ownership, long-term portability, and a system that works without running infrastructure — plain text files that you control forever — that's the trade-off Cooklang makes.
These are different philosophies, not a ranking. Mealie is excellent at what it does. So is Cooklang. The question is what you're actually trying to build.
For a side-by-side comparison of Mealie, Paprika, KitchenOwl, and Cooklang across more criteria, see this full comparison.
If you want to try Cooklang, the getting started guide takes about five minutes.
-Alex