- Blog
- Comparisons
- Mealie Review 2026: Honest Pros, Cons & Who It's For
Mealie Review 2026: Honest Pros, Cons & Who It's For
Mealie keeps coming up whenever developers ask about self-hosted recipe management. It has almost 14,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 (AGPL-3.0), self-hosted web application for managing recipes. This review is about the 3.x line; the latest release as I write is 3.31. The stack is Python (FastAPI backend) and a Vue.js frontend. Deployment is Docker-based: the standard install is one container from a docker-compose.yml, with SQLite inside it by default. 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: groups, with households inside them
- A full REST API
- SQLite by default, PostgreSQL if you want it, and a documented way to move between the two
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, and Mealie uses the same open source recipe-scrapers library many others do. For pages without that data it can fall back to an AI provider, if you configure one. 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. Users belong to a household, households belong to a group, and each user gets individual permissions (administrator, invite, manage the household, and so on). Meal plans and shopping lists are shared within a household. 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. Changes other people make show up within a few seconds while the list is open.
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. Every instance serves its own interactive API docs at /docs. Home Assistant ships a Mealie integration in its core, with meal plans as calendars and shopping lists as to-do lists.
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. Its FAQ says a non-Docker install is possible but recommends against it. So the path is a server — whether that's a VPS, a Raspberry Pi on your home network (64-bit; there are no 32-bit ARM images), or a NAS that supports Docker. That's a real prerequisite.
If you like Mealie but don't want to run it, its documentation points to Recipinned, a separate paid hosted product from Mealie's creator.
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. A single recipe exports as JSON, as a ZIP with its images, or as a PDF. You can export many recipes at once as a ZIP, and an admin can take a full backup of the site. But these are for backup and for moving between Mealie instances. JSON is a format for programs, not something you open and cook from.
Updates Need Your Attention
Mealie moves fast, which is mostly a good thing. A release comes out roughly every ten days. The downside is that some of them change behaviour. Two examples from 2026: since 3.26 the server only makes outgoing requests to public internet addresses, so webhooks and recipe actions aimed at something on your own network (a Home Assistant box, say) stop working until you add it to an allow-list. And since 3.22, single sign-on logins fail unless your identity provider sends a verified email. Several releases this year were security fixes. Mealie's docs tell you to read the release notes before upgrading, and they mean it.
Backups are also your job: Mealie no longer makes them automatically. If you're running a self-hosted service that your household depends on, you need a backup routine and some tolerance for maintenance. That's not unique to Mealie — it's true of any self-hosted web app — but it's worth being clear about.
Offline Is Limited
Mealie is a web application. It can be installed on a phone as a progressive web app, and the shopping list keeps working without a connection and syncs when you are back online. Recipes are a different matter: I found nothing in the docs or the app's configuration that keeps them on the device, so if your server is down or unreachable, plan on not having them.
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 your recipes offline, 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 (self-hostable with Docker if you want it always-on), and handles imports. There are native mobile apps for iOS and Android.
The trade-offs are real. Web import runs through a hosted converter (Cookify) or the CLI, not a scraper inside your own server. 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.
If you already have a library in Mealie and want it as text files, batch import on cook.md converts Mealie's ZIP export into .cook files in one go. It is a paid feature, part of Cook Basic.
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 of Mealie vs Paprika vs Cooklang across more criteria, see the full comparison.
If you want to try Cooklang, the getting started guide takes about five minutes.
-Alex