A plain-language look at the most popular open-source recipe app, for anyone tired of losing recipes to tab hoarding, paywalled apps, or Apple-only lock-in.

TL;DR

What it is: Open-source (AGPL-3.0) self-hosted recipe manager and meal planner — a single place for every recipe in your household, accessible from any device [README].
Who it’s for: Families and individuals who want recipe storage, meal planning, and grocery lists without subscribing to another app or handing their cooking habits to a cloud service that may disappear or raise prices [3].
Cost savings: Paprika costs ~$4.99 on mobile plus $19.99 on desktop (one-time). Mela is iOS/macOS-only with an annual subscription. Mealie self-hosted runs on a Raspberry Pi or a $5/mo VPS — free forever once deployed [2].
Key strength: URL-based recipe importing that actually works. Paste a link, Mealie scrapes the recipe. Combined with shopping list generation and a meal planner, it replaces three or four separate tools [README][1][3].
Key weakness: No official mobile app. The iOS third-party option (MealieSwift) costs £10. Remote access requires setting up a reverse proxy. Not plug-and-play for non-technical users [2].

What is Mealie

Mealie is a self-hosted recipe manager built around a Vue.js frontend and a FastAPI backend. You run it on your own hardware or a cheap VPS, and it gives your household a shared recipe library with meal planning, shopping list generation, and a full REST API.

The project was started by a developer known as Hay Kot and grew quickly: from a Reddit announcement in January to a feature-complete release a few months later [1]. It now has 11,729 GitHub stars and support for 35+ languages [README]. The creator also runs Recipinned, a hosted version for people who want Mealie’s features without managing their own server [website].

The core pitch is in the GitHub description: “Easily add recipes into your database by providing the url and Mealie will automatically import the relevant data.” That URL-import feature is the reason most people first install it. The rest — meal planning, shopping lists, multi-user support — is what keeps them.

Why People Choose It

Three themes come up consistently across the reviews.

Escaping platform lock-in. Nextcloud Cookbook, Mela, and Paprika each have meaningful drawbacks: Nextcloud’s bundled apps tend to be mediocre compared to dedicated alternatives [1], Mela is Apple-only, and Paprika stores everything in a proprietary format on someone else’s server. Mealie stores your recipes in SQLite or PostgreSQL on infrastructure you control. One reviewer’s summary of the pattern: he’d already replaced Nextcloud News with FreshRSS and Nextcloud Photos with Photoprism — Mealie was the logical next step for recipes [1].

Privacy. The XDA Developers piece [3] is almost entirely about this angle: commercial recipe apps require accounts, harvest data about your cooking habits, and you can’t audit what they do with it. Mealie requires none of that. Your shopping lists, meal plans, and family recipes stay on your server.

The UI is actually good. This isn’t a given for self-hosted software. The recipe card layout with hover previews, the Cook Mode that turns a recipe into a distraction-free step-by-step view, the ability to check off individual steps while cooking — these are features that paid apps frequently don’t have [1][3]. The XDA reviewer specifically calls out Cook Mode and the ability to add comments to recipes as differentiators from competitors [3].

Features

Recipe importing:

Import from URL — Mealie scrapes the recipe automatically [README][1]
Import from images [2]
Manual entry via UI editor [README]
Bulk URL import via community guide [website docs]
Migration from Chowdown, Nextcloud Cookbook, Copy Me That, Paprika, Tandoor, and others [documentation]

Search and organization:

Smart search with keyword and literal string support [documentation]
Fuzzy search (“brocolli or broccoli?”) when using PostgreSQL [documentation]
Tag with categories and tags for flexible filtering [documentation]
Cookbooks — group recipes by your own criteria [README]

Meal planning and shopping:

Meal Planner — plan by week, month, or year [README][website]
Shopping list generation from planned meals [README][3]
Automatic ingredient consolidation across multiple recipes — select five meals, get one unified list with no duplicates [3]
Ingredient natural language processing that builds a searchable ingredient database over time [2]

Multi-user support:

Households — separate user groups that share recipes within a group [documentation]
New users via sign-up links or admin panel [website]
LDAP and OIDC (v2) authentication for organizations [website docs]
Permissions and public access controls [website docs]

Integration and automation:

Full REST API with interactive Swagger documentation [README][website]
Webhooks for sending today’s meal plan to third-party services [website]
Home Assistant integration [website docs][2]
n8n integration for backup automation [website docs]
iOS shortcut support [website docs]
Optional ChatGPT/AI model integration for ingredient analysis [2]

Infrastructure:

Docker deployment (SQLite or PostgreSQL) [README]
Automatic backups in any Jinja2-supported format [website]
Progressive Web App — no app store required [documentation]
Recipe quantity scaling [2]
Markdown support in recipe editor [website]

The ingredient NLP deserves a specific callout. As Mealie processes more recipes, it gets better at recognizing ingredients. Users occasionally have to manually correct misidentified items, but the system improves with use — it’s not static [2]. This matters because shopping list consolidation only works well when the ingredient database is accurate.

Pricing: SaaS vs Self-Hosted Math

There’s no clean subscription pricing to compare against here — this isn’t the Zapier vs. Activepieces situation where both sides charge monthly per-use fees. Recipe apps mostly charge one-time or via annual subscription.

Common paid alternatives:

Paprika: ~$4.99 on iOS/Android, $19.99 on Mac, $9.99 on Windows. No cloud sync without paying for the cloud add-on. Data is in Paprika’s format.
Mela: iOS and macOS only. Annual subscription pricing (data not available at time of writing). No Android, no web.
AnyList: Family plan around $12/year. US-centric. No self-hosting.

Mealie self-hosted:

Software: $0 (AGPL-3.0)
Raspberry Pi you already have: $0 incremental
Hetzner CAX11 (ARM, 4GB RAM): ~$5/mo
Your time to set it up: 30–90 minutes if you know Docker

Recipinned (hosted, from Mealie’s creator):

Pricing data not available at time of writing — check the Recipinned website for current plans [website]

The self-hosting math isn’t primarily about monthly savings here — it’s about format independence and permanence. Paprika has had format compatibility issues across major versions. Mela is Apple-ecosystem-only. Both can sunset or pivot. Your Mealie data lives in a standard database you control. If you have 300 family recipes in there, you’re not losing them because a startup raised Series B and changed its pricing.

Deployment Reality Check

The install story is genuinely good. Neil Turner’s review [2] describes running it on personal hardware via Docker. The thecrow.uk reviewer [1] got it running in approximately five minutes. Neither of those is a lie, but they’re also both technical users comfortable with Docker.

What you actually need:

A machine running Docker (Raspberry Pi 3B+ or better, a home server, or a $5 cloud VPS)
1–2GB RAM minimum; 2–4GB comfortable
A domain name and reverse proxy (Nginx Proxy Manager, Caddy, Traefik) if you want HTTPS and remote access
SQLite for personal use; PostgreSQL if you have more than ~20 simultaneous users [2]

What you choose at install: The docs offer two paths — SQLite (simpler, good for individuals and small families) and PostgreSQL (better for larger instances with concurrent access) [documentation]. For a household of 2–5 people, SQLite is fine.

What can go sideways:

No official mobile app. Mealie is a PWA, which means you add it to your home screen from a browser. It works, but it’s not a native app. The iOS-native alternative, MealieSwift, costs £10 one-time [2]. Android options exist but the selection is smaller.
Remote access requires a reverse proxy. If you want to pull up a recipe from the grocery store, you need your instance exposed via a reverse proxy with HTTPS. This is a 30-minute setup task for someone who’s done it before and a 3-hour task for someone who hasn’t [2].
Ingredient NLP needs training. The ingredient parser starts rough and improves as you add more recipes. Users occasionally need to manually correct misidentified items [2]. This is a real friction point if you import 200 recipes on day one.
Migration from Mela is manual. If you’re coming from Mela specifically, there’s no automated importer. You’re re-entering recipes by hand [2]. The supported migration sources are Chowdown, Nextcloud Cookbook, Copy Me That, Paprika, Tandoor, DVO Cook’n, and X3 [documentation].
Some features were rough at launch. The thecrow.uk reviewer noted that meal planner ingredient aggregation wasn’t working at the time of his install [1]. The project moves fast enough that these issues typically get fixed, but it’s worth checking the current issue tracker if a specific feature is critical to your workflow.

Realistic time to a working instance for a technical user: 30–60 minutes. For someone new to Docker following a guide: 2–4 hours, including domain setup and reverse proxy configuration. If you’ve never touched a Linux command line, budget a full day or find someone to deploy it for you.

Pros and Cons

Pros

URL import that actually works. The recipe scraper handles the major food sites reliably. This alone replaces weeks of manual data entry if you’re coming from a browser bookmark folder [README][1].
Shopping list generation with ingredient deduplication. Select multiple meals, get one consolidated list. Mealie understands that “2 cups flour” in recipe A and “1 cup flour” in recipe B means “3 cups flour” on the shopping list [3].
Cook Mode. A distraction-free, step-by-step cooking interface. Small feature, real value when your hands are covered in dough and you need to tap through instructions [3].
Household multi-user support. Recipe sharing within groups, with proper permission controls and separate households [documentation].
Real REST API. Interact with Mealie programmatically — Home Assistant integrations, n8n workflows, custom scripts [README][2].
Actively developed. 11,729 stars, regular releases, a Discord with a real community. Not an abandoned project [README].
35+ language translations. Unusually good internationalization for a self-hosted tool [README].
Migrates from popular recipe apps. Tandoor, Paprika, Nextcloud Cookbook and more — you don’t start from zero [documentation].

Cons

AGPL-3.0, not MIT. If you embed Mealie in a commercial product, the AGPL requires you to release your modifications. Not a problem for personal use; a problem if you’re building a SaaS on top of it.
No official mobile app. The PWA works but it’s not the same as a native app. Third-party apps exist and cost money [2].
Remote access requires extra setup. Reverse proxy is not bundled and not optional if you want mobile access outside your home network [2].
Ingredient NLP takes time to calibrate. The ingredient parser is smart but not perfect on day one. Expect some manual correction early on [2].
Meal planner edge cases. At least one reviewer hit a bug with meal plan ingredient aggregation at the time of install [1]. Feature maturity varies; core recipe management is rock solid, edge features less so.
No migration from Mela. If you’re Apple-ecosystem locked right now, the exit is manual [2].
Hosted option (Recipinned) pricing unclear. If you want someone else to run it for you, the pricing isn’t prominently published [website].

Who Should Use This / Who Shouldn’t

Use Mealie if:

You have recipes scattered across browser bookmarks, Pinterest boards, screenshots, and your grandmother’s handwritten cards, and you want one place for all of them.
You’re a family or household that plans meals weekly and wants grocery lists generated automatically.
You’re escaping Apple ecosystem lock-in (Mela) or format lock-in (Paprika) and want your recipe data in a standard database you control.
You already run Docker on a home server or VPS and adding another container is no big deal.
Privacy matters to you and you’d rather your shopping and cooking data stay off third-party servers [3].

Skip it if:

You’ve never touched Docker or a command line and have nobody to help. The setup ceiling is real [2].
You need a polished native mobile app right now. The PWA is fine; it’s not the same as Paprika on iOS.
You’re migrating from Mela — there’s no automated importer and manual re-entry is painful [2].
You only have 20 recipes and a browser bookmark folder is genuinely sufficient. The overhead isn’t worth it at that scale.

Alternatives Worth Considering

Tandoor Recipes — The other major self-hosted recipe manager. More mature in some areas (recipe scaling, shopping list features were available earlier), different UI philosophy. Worth comparing side-by-side if Mealie’s UI doesn’t click for you [1].
Nextcloud Cookbook — Works if you’re already deep in Nextcloud. Generally considered a step down from dedicated alternatives in interface and feature depth [1].
Paprika — Best-in-class native apps, especially on iOS. Closed source, proprietary format, one-time purchase pricing. The right choice if you’re Apple-only and okay with a single vendor.
Mela — Elegant iOS/macOS app with a subscription model. Apple ecosystem only — not usable on Android or the web without workarounds.
Recipinned — Managed hosting of Mealie features from the original creator. For people who want Mealie’s capabilities without running their own server. Check current pricing before committing [website].

Bottom Line

Mealie is the self-hosted recipe manager for people who are done losing recipes to browser tabs and don’t want to pay a monthly subscription for something that should just work. The URL import alone justifies the install for anyone sitting on a folder of bookmarked recipes they’ve been meaning to organize. Add shopping list generation, meal planning, and a full REST API, and it’s covering ground that no single commercial app does at the same price.

The honest caveat is the deployment overhead. It’s not plug-and-play. Getting to a working, remotely-accessible instance with HTTPS takes a couple of hours and requires Docker familiarity. That’s the real barrier — not the feature set, not the license, just the initial setup. If that afternoon of work is the blocker, it’s exactly the kind of one-time deployment that upready.dev handles for clients. Pay once, own the infrastructure forever.