Self-Host Mealie: Recipe Manager and Meal Planner 2026

TL;DR

Mealie (AGPL 3.0, ~7K GitHub stars, Python/Vue) is a self-hosted recipe manager and meal planner. Paste any recipe URL and Mealie scrapes and saves it — no more browser bookmarks graveyard. Organize into categories and tags, plan weekly meals, generate grocery lists by combining planned meals, and share recipes with family. There's no paid alternative doing this better — AllRecipes and Paprika charge $4.99/year but put recipes behind ads. Mealie stores everything on your server.

Key Takeaways

• Mealie: AGPL 3.0, ~7K stars — recipe import from any URL, meal planning, grocery lists
• URL import: Paste any recipe website URL, Mealie extracts ingredients and instructions
• Meal planner: Weekly drag-and-drop calendar, generate shopping list from the plan
• API: Full REST API — integrate with Grocy, Home Assistant, or custom scripts
• iOS/Android: Mobile-optimized web app (PWA) — works great while cooking
• Multi-user: Households with per-user and shared recipe collections

---

Mealie vs Tandoor vs Paprika

Feature	Mealie	Tandoor	Paprika
License	AGPL 3.0	MIT	Proprietary
GitHub Stars	~7K	~5K	—
Cost	Free	Free	$4.99 once
URL scraping	Yes	Yes	Yes
Meal planner	Yes	Yes	Yes
Grocery list	Yes	Yes	Yes
Nutrition info	Yes	Yes	Limited
iOS/Android	PWA + API	PWA + API	Native
Multi-user	Yes	Yes	No (local)
Self-hosted	Yes	Yes	No

---

Part 1: Docker Setup

# docker-compose.yml
services:
  mealie:
    image: ghcr.io/mealie-recipes/mealie:latest
    container_name: mealie
    restart: unless-stopped
    ports:
      - "9000:9000"
    volumes:
      - mealie_data:/app/data
    environment:
      ALLOW_SIGNUP: "true"   # Disable after first user
      MAX_WORKERS: 1
      WEB_CONCURRENCY: 1
      BASE_URL: "https://recipes.yourdomain.com"
      # Default admin:
      DEFAULT_EMAIL: "${ADMIN_EMAIL}"
      DEFAULT_PASSWORD: "${ADMIN_PASSWORD}"
      # Email (optional for password reset):
      SMTP_HOST: "smtp.yourdomain.com"
      SMTP_PORT: 587
      SMTP_AUTH_STRATEGY: "TLS"
      SMTP_FROM_EMAIL: "mealie@yourdomain.com"
      SMTP_FROM_NAME: "Mealie"
      SMTP_USER: "${SMTP_USER}"
      SMTP_PASSWORD: "${SMTP_PASS}"
      # Language:
      DEFAULT_GROUP: "Home"
      TZ: "America/Los_Angeles"

volumes:
  mealie_data:

# .env
ADMIN_EMAIL=admin@yourdomain.com
ADMIN_PASSWORD=your-admin-password

docker compose up -d

Visit http://your-server:9000 — log in with your admin credentials.

---

Part 2: HTTPS with Caddy

recipes.yourdomain.com {
    reverse_proxy localhost:9000
}

---

Part 3: Importing Recipes

From a URL (any recipe website)

1. Click + New Recipe → Import Recipe
2. Paste any recipe URL from:
   • AllRecipes, Food Network, NYT Cooking, Serious Eats, Budget Bytes
   • Personal food blogs
   • Any page with recipe schema markup
3. Mealie scrapes: title, ingredients, instructions, nutrition, time, servings
4. Review and save

From a file

• Import .zip Mealie exports from another instance
• Import from Nextcloud Cookbook
• Import .json in schema.org Recipe format

Manual entry

1. + New Recipe → Create Recipe
2. Fill in title, ingredients (one per line), instructions
3. Add tags, categories, nutrition info

---

Part 4: Meal Planning

1. Meal Plan → Week View
2. Drag recipes onto days (or click + to add)
3. Plan breakfast, lunch, dinner, snacks separately
4. View the week's plan at a glance

Generate a grocery list

1. Meal Plan → Shopping List
2. Select the date range
3. Mealie combines all ingredients from planned meals
4. Deduplicates and combines quantities (e.g., "2 cups + 1 cup flour = 3 cups flour")
5. Check off items as you shop

---

Part 5: Multi-User Households

Mealie supports households with shared and private recipes:

Create a household group

1. Admin → Groups → Create Group
2. Name: Smith Family
3. Members can share recipes within the group

User roles

• Admin: Manage users, all settings
• User: Create/edit own recipes, view shared
• Viewer: Read-only access to shared recipes

Invite household members

1. Settings → Users → Invite User
2. Share the invite link
3. Or create accounts: Admin → Users → Create User

---

Part 6: REST API

# Get API token:
# Profile → Security → API Tokens → Create

TOKEN="your-api-token"
BASE="https://recipes.yourdomain.com/api"

# Get all recipes:
curl "${BASE}/recipes?page=1&perPage=50" \
  -H "Authorization: Bearer $TOKEN" | jq '.[].name'

# Create a recipe:
curl -X POST "${BASE}/recipes" \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"name": "Simple Pasta", "recipeIngredient": ["200g pasta", "2 cloves garlic", "olive oil"]}'

# Get a recipe by slug:
curl "${BASE}/recipes/simple-pasta" \
  -H "Authorization: Bearer $TOKEN"

# Scrape from URL:
curl -X POST "${BASE}/recipes/create/url" \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"url": "https://www.budgetbytes.com/pasta-e-fagioli/"}'

# Add to meal plan:
curl -X POST "${BASE}/groups/mealplans" \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"date": "2026-03-10", "entryType": "dinner", "recipeId": "recipe-uuid"}'

---

Part 7: Organize with Tags and Categories

# Suggested category structure:
Categories:
  - Breakfast
  - Lunch
  - Dinner
  - Snacks
  - Desserts
  - Baking

# Suggested tags:
Tags:
  - 30-minutes
  - vegetarian
  - vegan
  - gluten-free
  - dairy-free
  - kid-friendly
  - meal-prep
  - one-pan
  - budget
  - holiday

Bulk tag via API:

# Apply tag to multiple recipes:
RECIPE_IDS=("uuid1" "uuid2" "uuid3")
for ID in "${RECIPE_IDS[@]}"; do
  curl -X PATCH "${BASE}/recipes/${ID}" \
    -H "Authorization: Bearer $TOKEN" \
    -H "Content-Type: application/json" \
    -d '{"tags": [{"name": "vegetarian"}]}'
done

---

Part 8: Home Assistant Integration

Integrate with Home Assistant for meal plan visibility:

# In Home Assistant configuration.yaml:
rest_command:
  get_mealie_plan:
    url: "https://recipes.yourdomain.com/api/groups/mealplans/today"
    method: GET
    headers:
      Authorization: "Bearer YOUR_MEALIE_TOKEN"

sensor:
  - platform: rest
    name: "Tonight's Dinner"
    resource: "https://recipes.yourdomain.com/api/groups/mealplans/today"
    headers:
      Authorization: "Bearer YOUR_MEALIE_TOKEN"
    value_template: "{{ value_json | selectattr('entryType','eq','dinner') | map(attribute='recipe.name') | first }}"

---

Maintenance

# Update Mealie:
docker compose pull
docker compose up -d

# Backup:
tar -czf mealie-backup-$(date +%Y%m%d).tar.gz \
  $(docker volume inspect mealie_mealie_data --format '{{.Mountpoint}}')

# Export all recipes (for migration):
curl "${BASE}/recipes/exports/download/recipes.zip" \
  -H "Authorization: Bearer $TOKEN" -O

# Logs:
docker compose logs -f mealie

Why Self-Host Mealie?

The case for self-hosting Mealie comes down to three practical factors: data ownership, cost at scale, and operational control.

Data ownership is the fundamental argument. When you use a SaaS version of any tool, your data lives on someone else's infrastructure subject to their terms of service, their security practices, and their business continuity. If the vendor raises prices, gets acquired, changes API limits, or shuts down, you're left scrambling. Self-hosting Mealie means your data and configuration stay on infrastructure you control — whether that's a VPS, a bare metal server, or a home lab.

Cost at scale matters once you move beyond individual use. Most SaaS equivalents charge per user or per data volume. A self-hosted instance on a $10-20/month VPS typically costs less than per-user SaaS pricing for teams of five or more — and the cost doesn't scale linearly with usage. One well-configured server handles dozens of users for a flat monthly fee.

Operational control is the third factor. The Docker Compose configuration above exposes every setting that commercial equivalents often hide behind enterprise plans: custom networking, environment variables, storage backends, and authentication integrations. You decide when to update, how to configure backups, and what access controls to apply.

The honest tradeoff: you're responsible for updates, backups, and availability. For teams running any production workloads, this is familiar territory. For individuals, the learning curve is real but the tooling (Docker, Caddy, automated backups) is well-documented and widely supported.

Server Requirements and Sizing

Before deploying Mealie, assess your server capacity against expected workload.

Minimum viable setup: A 1 vCPU, 1GB RAM VPS with 20GB SSD is sufficient for personal use or small teams. Most consumer VPS providers — Hetzner, DigitalOcean, Linode, Vultr — offer machines in this range for $5-10/month. Hetzner offers excellent price-to-performance for European and US regions.

Recommended production setup: 2 vCPUs with 4GB RAM and 40GB SSD handles most medium deployments without resource contention. This gives Mealie headroom for background tasks, caching, and concurrent users while leaving capacity for other services on the same host.

Storage planning: The Docker volumes in this docker-compose.yml store all persistent Mealie data. Estimate your storage growth rate early — for data-intensive tools, budget for 3-5x your initial estimate. Hetzner Cloud and Vultr both support online volume resizing without stopping your instance.

Operating system: Any modern 64-bit Linux distribution works. Ubuntu 22.04 LTS and Debian 12 are the most commonly tested configurations. Ensure Docker Engine 24.0+ and Docker Compose v2 are installed — verify with docker --version and docker compose version. Avoid Docker Desktop on production Linux servers; it adds virtualization overhead and behaves differently from Docker Engine in ways that cause subtle networking issues.

Network: Only ports 80 and 443 need to be publicly accessible when running behind a reverse proxy. Internal service ports should be bound to localhost only. A minimal UFW firewall that blocks all inbound traffic except SSH, HTTP, and HTTPS is the single most effective security measure for a self-hosted server.

Backup and Disaster Recovery

Running Mealie without a tested backup strategy is an unacceptable availability risk. Docker volumes are not automatically backed up — if you delete a volume or the host fails, data is gone with no recovery path.

What to back up: The named Docker volumes containing Mealie's data (database files, user uploads, application state), your docker-compose.yml and any customized configuration files, and .env files containing secrets.

Backup approach: For simple setups, stop the container, archive the volume contents, then restart. For production environments where stopping causes disruption, use filesystem snapshots or database dump commands (PostgreSQL pg_dump, SQLite .backup, MySQL mysqldump) that produce consistent backups without downtime.

For a complete automated backup workflow that ships snapshots to S3-compatible object storage, see the Restic + Rclone backup guide. Restic handles deduplication and encryption; Rclone handles multi-destination uploads. The same setup works for any Docker volume.

Backup cadence: Daily backups to remote storage are a reasonable baseline for actively used tools. Use a 30-day retention window minimum — long enough to recover from mistakes discovered weeks later. For critical data, extend to 90 days and use a secondary destination.

Restore testing: A backup that has never been restored is a backup you cannot trust. Once a month, restore your Mealie backup to a separate Docker Compose stack on different ports and verify the data is intact. This catches silent backup failures, script errors, and volume permission issues before they matter in a real recovery.

Security Hardening

Self-hosting means you are responsible for Mealie's security posture. The Docker Compose setup provides a functional base; production deployments need additional hardening.

Always use a reverse proxy: Never expose Mealie's internal port directly to the internet. The docker-compose.yml binds to localhost; Caddy or Nginx provides HTTPS termination. Direct HTTP access transmits credentials in plaintext. A reverse proxy also centralizes TLS management, rate limiting, and access logging.

Strong credentials: Change default passwords immediately after first login. For secrets in docker-compose environment variables, generate random values with openssl rand -base64 32 rather than reusing existing passwords.

Firewall configuration:

ufw default deny incoming
ufw allow 22/tcp
ufw allow 80/tcp
ufw allow 443/tcp
ufw enable

Internal service ports (databases, admin panels, internal APIs) should only be reachable from localhost or the Docker network, never directly from the internet.

Network isolation: Docker Compose named networks keep Mealie's services isolated from other containers on the same host. Database containers should not share networks with containers that don't need direct database access.

VPN access for sensitive services: For internal-only tools, restricting access to a VPN adds a strong second layer. Headscale is an open source Tailscale control server that puts your self-hosted stack behind a WireGuard mesh, eliminating public internet exposure for internal tools.

Update discipline: Subscribe to Mealie's GitHub releases page to receive security advisory notifications. Schedule a monthly maintenance window to pull updated images. Running outdated container images is the most common cause of self-hosted service compromises.

Troubleshooting Common Issues

Container exits immediately or won't start

Check logs first — they almost always explain the failure:

docker compose logs -f mealie

Common causes: a missing required environment variable, a port already in use, or a volume permission error. Port conflicts appear as bind: address already in use. Find the conflicting process with ss -tlpn | grep PORT and either stop it or change Mealie's port mapping in docker-compose.yml.

Cannot reach the web interface

Work through this checklist:

1. Confirm the container is running: docker compose ps
2. Test locally on the server: curl -I http://localhost:PORT
3. If local access works but external doesn't, check your firewall: ufw status
4. If using a reverse proxy, verify it's running and the config is valid: caddy validate --config /etc/caddy/Caddyfile

Permission errors on volume mounts

Some containers run as a non-root user. If the Docker volume is owned by root, the container process cannot write to it. Find the volume's host path with docker volume inspect VOLUME_NAME, check the tool's documentation for its expected UID, and apply correct ownership:

chown -R 1000:1000 /var/lib/docker/volumes/your_volume/_data

High resource usage over time

Memory or CPU growing continuously usually indicates unconfigured log rotation, an unbound cache, or accumulated data needing pruning. Check current usage with docker stats mealie. Add resource limits in docker-compose.yml to prevent one container from starving others. For ongoing visibility into resource trends, deploy Prometheus + Grafana or Netdata.

Data disappears after container restart

Data stored in the container's writable layer — rather than a named volume — is lost when the container is removed or recreated. This happens when the volume mount path in docker-compose.yml doesn't match where the application writes data. Verify mount paths against the tool's documentation and correct the mapping. Named volumes persist across container removal; only docker compose down -v deletes them.

Keeping Mealie Updated

Mealie follows a regular release cadence. Staying current matters for security patches and compatibility. The update process with Docker Compose is straightforward:

docker compose pull          # Download updated images
docker compose up -d         # Restart with new images
docker image prune -f        # Remove old image layers (optional)

Read the changelog before major version updates. Some releases include database migrations or breaking configuration changes. For major version bumps, test in a staging environment first — run a copy of the service on different ports with the same volume data to validate the migration before touching production.

Version pinning: For stability, pin to a specific image tag in docker-compose.yml instead of latest. Update deliberately after reviewing the changelog. This trades automatic patch delivery for predictable behavior — the right call for business-critical services.

Post-update verification: After updating, confirm Mealie is functioning correctly. Most services expose a /health endpoint that returns HTTP 200 — curl it from the server or monitor it with your uptime tool.

---

See all open source lifestyle and home tools at OSSAlt.com/categories/home.