Mealie vs Tandoor: Which Recipe Manager to Self-Host?

You want one app to store recipes, plan meals, and generate shopping lists — without handing your data to some ad-supported recipe site that wraps a 200-word ingredient list in 3,000 words of backstory. Mealie and Tandoor Recipes are the two strongest self-hosted options. Both run in Docker, both scrape recipes from URLs, and both have active communities. But they make very different trade-offs.

Quick Verdict

Mealie is the better choice for most households. Its recipe importer handles more sites reliably, the meal planner and shopping list are tightly integrated, and the UI is noticeably more polished. Tandoor is the pick if you need multi-language support across the interface, want more granular nutritional data tracking, or prefer a more traditional database-style approach to recipe management.

Overview

Mealie is a Python-based recipe manager built by hay-kot. It started as a simple recipe scraper and has grown into a full household management tool with meal planning, shopping lists, and a public API. The project has strong momentum — v2.x was a significant rewrite that modernized the stack and improved performance.

Tandoor Recipes is a Django-based recipe manager created by vabene1111. It leans more toward the “recipe database” model — powerful search, detailed nutritional information, flexible keyword and tag systems, and solid multi-user permissions. It has been around longer and has a mature feature set.

Both are actively maintained with regular releases.

Feature Comparison

Feature	Mealie v2.7.1	Tandoor v1.5.34
URL recipe import	Excellent — handles most major sites	Good — occasional failures on complex layouts
Manual recipe entry	Full editor with ingredient parsing	Full editor with structured fields
Meal planning	Built-in calendar with drag-and-drop	Built-in meal plan with weekly view
Shopping list	Auto-generated from meal plan	Auto-generated, but less integrated
Shopping list grouping	Groups by aisle/category	Groups by supermarket sections
Multi-user support	Household groups with roles	Multi-user with fine-grained permissions
Mobile experience	Responsive PWA, installable	Responsive web, installable PWA
Nutritional tracking	Basic — pulled from imported data	Detailed — integrates with FDC/OpenFoodFacts
Multi-language UI	English primary, community translations	Full i18n, 25+ languages
API	REST API with OpenAPI docs	REST API with OpenAPI docs
Ingredient parser	NLP-based, handles natural language well	Regex-based, more rigid
Recipe scaling	Yes	Yes
Cookbook/collection organization	Cookbooks (curated groups)	Books and keywords
Import from other apps	Supports Tandoor, Paprika, Chowdown, others	Supports Mealie, Paprika, Nextcloud Cookbook, others
OCR for handwritten recipes	No	Yes (experimental)
Database	SQLite (default) or PostgreSQL	PostgreSQL (required)
License	AGPL-3.0	AGPL-3.0

Recipe Import Quality

This is where Mealie pulls ahead meaningfully. Recipe scraping sounds simple — parse some structured data from a URL — but in practice, recipe sites are a mess of inconsistent markup, paywalls, and JavaScript-rendered content.

Mealie uses a combination of JSON-LD schema parsing and custom scrapers. In testing, it handles the major recipe sites (AllRecipes, Serious Eats, NYT Cooking, BBC Good Food, Budget Bytes) with high reliability. It extracts ingredients, instructions, prep time, and images cleanly.

Tandoor uses a similar approach but stumbles more often on sites with non-standard markup. When it works, the result is comparable. But you will hit more “import failed” or “partially imported” results. Tandoor compensates with its OCR feature for scanning physical cookbooks and handwritten recipes — something Mealie does not offer.

Winner: Mealie for URL imports. Tandoor if you have a stack of physical cookbooks to digitize.

Meal Planning and Shopping Lists

Mealie treats meal planning as a first-class feature. The calendar view lets you drag recipes onto days, and one click generates a consolidated shopping list from the entire week’s plan. The ingredient parser is NLP-based, so it handles entries like “2 large eggs” or “1/2 cup flour, sifted” correctly and deduplicates across recipes.

Tandoor has meal planning too, but it feels more like an add-on than a core workflow. The shopping list generation works, but the connection between “I planned these meals” and “here’s what I need to buy” requires more manual steps. Ingredient merging is less reliable with Tandoor’s regex-based parser.

For a household that plans weekly meals and shops from a list, Mealie’s workflow is noticeably smoother.

Winner: Mealie.

Mobile Experience

Neither app has a native mobile app. Both offer responsive progressive web apps (PWAs) that you can install to your home screen.

Mealie’s PWA is well-optimized for mobile. Recipe views are clean, the shopping list works well as a checklist while you are in the store, and the meal plan calendar is usable on a phone screen. The UI was clearly designed with mobile as a priority.

Tandoor’s mobile experience is functional but feels more like a shrunk desktop site. It works, but you will do more scrolling and pinching. The shopping list is usable but not as refined.

Winner: Mealie.

Multi-User and Household Support

Tandoor takes this one. It has a proper permissions model — you can create multiple users with different access levels (admin, user, guest). Users can have private recipes while sharing others. The permission system is granular enough for shared households, cooking clubs, or family groups where not everyone should be able to edit everything.

Mealie has a “household groups” concept where users belong to a group and share recipes within it. It is simpler and works fine for a typical family. But if you need per-recipe permissions or want to run a single instance for multiple independent households, Tandoor’s model is more flexible.

Winner: Tandoor for complex multi-user setups. Mealie is fine for a single household.

Resource Usage

Resource	Mealie v2.7.1	Tandoor v1.5.34
RAM (idle)	~150 MB	~250 MB (app + PostgreSQL)
RAM (active use)	~250 MB	~400 MB
CPU	Low	Low-Medium
Disk (application)	~500 MB	~800 MB (includes PostgreSQL)
Disk (data)	Depends on recipe count and images	Depends on recipe count and images

Mealie is lighter, especially because it can run on SQLite without a separate database container. Tandoor requires PostgreSQL, which adds baseline memory overhead. On a Raspberry Pi 4 or a small VPS, the difference matters. On a proper home server, neither will stress your hardware.

Winner: Mealie — lighter footprint, especially with SQLite.

UI Polish

Mealie’s interface is modern, clean, and fast. The v2 rewrite brought a consistent design language, smooth transitions, and good information density. Recipes display well with large images, clear ingredient lists, and step-by-step instructions. The overall feel is closer to a commercial app than a self-hosted project.

Tandoor’s UI is functional and well-organized but a generation behind in polish. It is built on Django templates with Bootstrap, which gives it a capable but somewhat dated look. It gets the job done — you will not struggle to find anything — but it does not have the visual refinement that makes Mealie feel premium.

Winner: Mealie.

Where Tandoor Wins

Tandoor is not just a fallback option. It is genuinely better in specific areas:

• Nutritional tracking. Tandoor integrates with the USDA FoodData Central and OpenFoodFacts databases for detailed nutritional information per ingredient. If you track macros or have dietary requirements that need precise data, Tandoor is significantly more capable.
• Multi-language support. Tandoor’s UI is translated into 25+ languages with strong community maintenance. Mealie has translations but English is clearly the primary focus.
• OCR import. Tandoor can scan images of recipes (handwritten or printed) using OCR. Experimental, but useful for digitizing old family recipes.
• Keyword and tag flexibility. Tandoor’s tagging system is more powerful for building complex organizational hierarchies.

Use Cases

Choose Mealie If…

• You want the smoothest experience for weekly meal planning and grocery shopping
• Recipe URL importing is your primary way to add recipes
• You are running on limited hardware (Pi, small VPS)
• You want a polished, modern UI out of the box
• Your household has one group of users who share everything
• You want the easiest setup process (SQLite, single container)

Choose Tandoor If…

• You need detailed nutritional tracking per recipe and per meal
• You run a multi-language household or want a non-English interface
• You need granular per-user permissions or multiple independent user groups
• You have physical cookbooks or handwritten recipes to digitize via OCR
• You prefer a more database-oriented approach to recipe organization

Final Verdict

Mealie is the better recipe manager for most self-hosting households. The recipe import is more reliable, the meal plan to shopping list pipeline is tighter, the mobile experience is better, and the UI is a generation ahead in polish. It is also lighter on resources and simpler to deploy.

Tandoor is a strong app with legitimate advantages in nutritional tracking, multi-language support, and user permissions. If those specific features matter to you, Tandoor delivers. But for the common use case — a household that wants to save recipes from the web, plan meals for the week, and generate a shopping list — Mealie does it better.

Set up whichever fits your needs: How to Self-Host Mealie or How to Self-Host Tandoor.

Related

• How to Self-Host Mealie
• How to Self-Host Tandoor
• Best Self-Hosted Recipe Managers
• Docker Compose Guide
• Reverse Proxy Explained
• Backup Strategy