What Features Does Mealie Offer for Managing Recipes?

Mealie is a self-hosted recipe manager. It is aimed at people who want to keep their own recipe collection on their own server, organize and search it, import recipes they already have in other apps, and control who can see what. The core feature set covers recipe storage and retrieval, importing from other apps, permissions and public access, and backup and restore. It also documents authentication options and AI providers, so it can fit into a home server setup rather than being a closed hosted service.

Storing, organizing, and finding recipes

Mealie's documentation lists a feature overview as a top-level section, which is the place to check the current, authoritative list of what the app does. In practice, the recipe-management value comes from three things:

• A single place for your recipes. Instead of scattered bookmarks, screenshots, and notes, recipes live in one collection you host yourself.
• Organization you control. Because it is self-hosted, your categories, tags, and structure are yours to define rather than dictated by a third-party service.
• Retrieval. The documentation includes a dedicated guide on improving the ingredient parser, which matters because search and filtering depend on ingredients being parsed into usable units and names. If your recipes import with messy ingredient lines, that guide is the fix.

If your main need is "find any recipe by an ingredient I have on hand," the ingredient parser quality is the feature to evaluate first. If your need is simply "keep my recipes in one searchable library," the storage and organization features are the core.

Importing recipes from other apps

Mealie documents an "Import from other apps" section, so migration is a first-class concern rather than an afterthought. The documentation also includes several concrete import paths under Community Guides:

• Bulk URL import — for bringing in recipes you have as links.
• Bookmarklet — for capturing a recipe from a page while you browse.
• iOS Shortcut — for importing from an iPhone or iPad.
• Home Assistant import — for pulling recipes in from a Home Assistant setup.
• Bring API without internet exposure — for integrating with the Bring shopping-list app while keeping your instance off the public internet.

This matters if you already have recipes in another app or in a pile of saved links. The existence of a bulk URL importer and a bookmarklet means you are not limited to entering recipes one at a time by hand. Check the "Import from other apps" documentation for the exact formats and steps, since supported sources and behavior can change between versions.

Permissions, public access, and authentication

Mealie separates permissions and public access from authentication, which tells you these are two distinct controls:

• Permissions and public access govern what anonymous or logged-in visitors can see and do.
• Authentication covers how users prove who they are, with documented support for LDAP and OpenID Connect.

That combination is useful if you want to share a recipe with family or the public without giving them an account, while still requiring login for editing. It also means Mealie can plug into an existing identity provider instead of maintaining separate passwords. If you run other self-hosted services with LDAP or OIDC, this is the feature that lets Mealie join that setup.

Backup, restore, and data management

The documentation includes a Backup and Restoring section and a community guide on automating backups with n8n. For a self-hosted recipe collection, this is the difference between a hobby project and something you can trust with years of recipes. Two practical points follow from the documentation:

• Backups are a documented, supported operation, not something you have to improvise.
• Automation is possible via n8n, so you can schedule backups rather than remembering to run them.

If you are choosing between self-hosted options, weigh how well each one documents backup and restore. Mealie documents both.

Installation and technology choices

The documentation's Installation section includes an installation checklist and two database options:

The checklist is the right starting point before you install, because it lists what to decide and prepare first. The database choice is the main architectural decision: SQLite is marked recommended, while PostgreSQL is available if you prefer it or already run it. The documentation also covers backend configuration, security, and logs, which are the areas you will touch when tuning or troubleshooting a deployment.

AI providers and extensibility

Mealie documents AI providers as a configuration area. This indicates the app can be connected to an AI provider for some functionality, and the documentation is where the supported providers and setup are described. Treat this as an optional capability to check against your needs rather than a core requirement — the recipe storage, import, permissions, and backup features stand on their own without it.

How to decide

• Choose Mealie if you want a self-hosted recipe manager with documented import paths from other apps, granular public-access and authentication controls (including LDAP and OIDC), and documented backup and restore.
• Look elsewhere if you want a fully hosted service with no server to run, or if you need a feature that is not in the current feature overview.
• Before committing, read the installation checklist, confirm whether SQLite (recommended) or PostgreSQL fits your setup, and test the importer against a sample of your existing recipes — the ingredient parser guide is there because import quality varies by source.

The authoritative, current list of features is the Feature overview in the Mealie documentation; use it to confirm anything version-specific before you migrate a large collection.