Send recipes from the web directly to your Mealie instance.
Send2Mealie is a browser extension for Chrome and Firefox that adds a “Send to Mealie” button to Mealie supported recipe websites, allowing you to import recipes into your own Mealie server with minimal friction.
Built for self-hosters who want explicit control, minimal permissions, and predictable behavior.
Note: NOT ASSOCIATED WITH MEALIE.
-
15+ pre-configured recipe sites Works out of the box on popular recipe sites including AllRecipes, Food Network, BBC Good Food, NYT Cooking, and more.
-
User-added custom sites Add additional recipe websites using the browser’s optional host permissions. Access is granted only after explicit user approval, and custom permissions are restricted to HTTPS origins for parity across stores.
-
Recipe state detection Automatically indicates when a recipe has already been saved to your Mealie instance (“Mealied!”).
-
Duplicate detection Optional warning before importing recipes that already exist in Mealie.
-
Right-click Send2Mealie menu Send the current page to Mealie directly from the browser context menu, with optional duplicate checks.
-
Secure configuration storage Mealie server URL and API token are stored using the browser’s encrypted sync storage.
-
Immediate settings persistence Configuration changes are saved automatically.
-
Action-scoped notifications Browser notifications are displayed only after you explicitly send a recipe, providing success or failure confirmation without background alerts.
-
Security-focused design Strict URL validation, redacted error messages, minimal permissions, and no background scraping outside approved sites.
git clone https://github.com/gargolito/send2mealie.git
cd send2mealie
npm install
npm run build # Chrome build → build/chrome
npm run build:firefox # Firefox build → build/firefox/
# Distribution packages
npm run dist:chrome # Chrome zip → dist/chrome/
npm run dist:firefox # Firefox xpi → dist/firefox/
npm run dist:cowboy:chrome # Cowboy Chrome zip → dist/cowboy/chrome/
npm run dist:cowboy:firefox # Cowboy Firefox xpi → dist/cowboy/firefox/
npm run dist:cowboy:all # Both cowboy packagesThe cowboy version is intended for development installations with:
- HTTP protocol (not just HTTPS)
- IP addresses (e.g.,
192.168.1.100:8000) - Self-signed SSL certificates
- Non-standard domain names (e.g.,
mealie.local)
npm run build:cowboy:chrome # Chrome → build/cowboy/chrome/
npm run build:cowboy:firefox # Firefox → build/cowboy/firefox/
npm run build:cowboy:all # Both- Open
chrome://extensions/ - Enable Developer mode
- Click Load unpacked
- Select the
build/chromedirectory
- Open
about:debugging#/runtime/this-firefox - Click Load Temporary Add-on
- Select
build/firefox/manifest.json
- Open your Mealie server:
http://mealie.example.com(or your server URL) - Go to Profile → API Tokens (or
/user/profile/api-tokens) - Create a new token or copy an existing one
- Click the Send2Mealie extension icon
- Enter your Mealie server URL
- Standard:
https://mealie.example.com - Local/HTTP:
http://localhost:8000orhttp://192.168.1.100:8080(cowboy version only)
- Standard:
- (Optional) Paste your API token
- Only required for:
- The "Send to Mealie" page button
- Duplicate detection
- Not required for context menu or import settings
- Only required for:
- (Optional) Set Group Slug (defaults to
home)- Used in edit page URLs
- Click Test Connection to verify connectivity
- Works with or without API token
- Checks for valid Mealie server
- (Optional) Use Check Login (Browser Session) to verify cookie-based authentication
- Checks if you're logged into Mealie via browser cookies
- Useful when API token is not configured
- Enable Send2Mealie button on recipe pages - Show the button on recipe sites (requires API token)
- Check for duplicates before sending - Warn if recipe already exists (requires API token)
- Add recipe in edit mode - Automatically open the recipe editor after importing
- Enable parse mode - Tell Mealie to parse the recipe before editing
You can send recipes to Mealie using the right-click context menu:
- Visit any recipe page on a supported site (or any site globally)
- Right-click anywhere on the page
- Select "Send2Mealie" from the context menu
- The recipe imports into Mealie
- If "Add recipe in edit mode" is enabled in settings, the edit page opens automatically
- If "Check for duplicates before sending" is enabled and you have an API token, the extension verifies the recipe isn't already in Mealie
Notes:
- The context menu works with or without an API token (uses browser session if logged in)
- Duplicate checking requires an API token
- Works on any website globally (not limited to whitelisted recipe sites)
You can add recipe websites beyond the default 15+ sites:
- Visit a recipe page on any website
- Enter the full recipe URL in the "Add another site" field (e.g.,
https://example.com/recipe/pasta) - Click Add Site
- The extension validates that recipes can be scraped from the site
- If valid, your browser prompts for permission; grant it to enable the extension on that site
- The "Send to Mealie" button will now appear on that site's recipe pages
Notes:
- Only HTTPS sites are supported (browser security requirement) — use the Cowboy version for HTTP
- You must enter a full recipe page URL, not just the domain
- If scraping fails, the site cannot be added
Default mealie supported sites include:
-
AllRecipes
-
BBC Good Food
-
Budget Bytes
-
Eating Well
-
Food.com
-
Food Network
-
NYT Cooking
-
Sally’s Baking Addiction
-
Serious Eats
-
Simply Recipes
-
Skinny Taste
-
Tasty
-
Tasty Kitchen
-
The Pioneer Woman
-
The Spruce Eats
Additional sites can be added via the popup using explicit browser permission prompts.
Send2Mealie is designed to minimize data access:
-
No analytics, tracking, or telemetry
-
No third-party data sharing
-
Network requests are limited to:
-
User-approved recipe websites
-
The user’s configured Mealie server
-
-
Credentials are stored locally using the browser’s encrypted sync storage
See PRIVACY.md for full details.
See DEVELOPMENT.md for architecture notes, setup instructions, and contribution guidelines.
See the LICENSE file for details.

