# Forktastic Blog > Recipes, meal planning, and food technology — by the team behind the Forktastic AI recipe scanner. ## Personal Access Tokens for Forktastic: Setup & Best Practices Source: https://forktastic.com/blog/en/forktastic-personal-access-tokens Published: 2026-09-09T16:00:01.121+00:00 > Full PAT walkthrough for Forktastic — issuance, scope, revocation, why per-client tokens, and what to do if a token leaks. Personal Access Tokens (PATs) are how the Forktastic MCP server authenticates requests. They're short-string credentials you issue from your account, scoped to read-only access, revocable at any time. This post is the full PAT walkthrough — issuance, scope, revocation, security best practices. What a PAT is A long random string (think 40+ characters) that uniquely identifies one token associated with your account. When you authenticate to the Forktastic MCP server, you pass the PAT in the Authorization header. The server matches it to your account and grants read-only access to your recipe library. How to issue one Open Forktastic. Settings → Personal Access Tokens. Tap "New Token." Give it a label — "Claude Desktop," "Cursor," "my-agent-server," whatever describes its use. Tap "Create." Copy the token immediately — it's shown once. After this screen, the full token isn't viewable again (only the last few characters, for identification). Why issue separate tokens for separate uses One PAT per client is the right pattern. If you use Claude Desktop on your laptop and Cursor at the office and a separate agent on a server, issue three PATs labeled accordingly. Three reasons: Revocation is granular. If your laptop's PAT leaks, you revoke just that one without disrupting your office work. Rate limits don't pool. Each PAT has its own 60/min and 5,000/day buckets, so a runaway agent on one machine doesn't throttle the others. Audit trail. You can see which PAT is making which requests in usage logs. What a PAT grants Read-only access to your account's data — your recipes, your cookbooks, your family group, trending recipes (public data). Nothing else. The MCP server's tools are all read; there is no write endpoint, no create-recipe API, no delete-anything API. The PAT also can't see other users' data. Even within a family group, the PAT only reads what your account is entitled to see (your own recipes plus the family-shared content the family owner has shared). How to revoke a PAT Settings → Personal Access Tokens → tap a token → Revoke. Immediate; the token stops working within a few seconds. Re-issue if you need a new one. Always revoke when: A device with the PAT is lost or stolen. You uninstall a client that had the PAT. A teammate left and had access to the PAT. You suspect the PAT may have been exposed (committed to git, leaked in logs). Security best practices Never commit a PAT to git — treat them like passwords. Use environment variables in your config. Never share a PAT in chat , even with a teammate. They should issue their own. Don't reuse a PAT across machines. Issue one per machine. Rotate tokens periodically. Every 6-12 months, revoke and re-issue active PATs. What to do if a PAT leaks Revoke it immediately. Issue a new one. Update wherever the old PAT was used. The damage from a leaked Forktastic PAT is bounded — read access to your recipes only — but the principle of fast revocation matters. Where to go next For Claude setup, Claude walkthrough . For Cursor, Cursor walkthrough . For rate limits, rate limits reference . For the MCP pillar, MCP pillar guide . --- ## Forktastic MCP in Cursor: Recipes in Your IDE Source: https://forktastic.com/blog/en/forktastic-mcp-cursor-setup Published: 2026-09-07T16:00:00.941+00:00 > Step-by-step Forktastic MCP setup for Cursor — issue a PAT, add the server config, build agents against your recipe library inside your dev environment. Cursor's MCP integration is the same shape as Claude Desktop's — you add a server, you authenticate with a Personal Access Token, and the tools become available to whichever agentic mode you're using. This is the Forktastic-specific Cursor setup. Why connect Forktastic to Cursor If you build software with Cursor and you keep recipes on the side as a hobby, having your recipe library available in your IDE is more useful than it sounds. Quick agent prompts like "format my X recipe as a Markdown table for a Slack message" or "generate a shopping list from the recipes I have planned this week" become one prompt away while you're already in your dev environment. It's also useful for developers building integrations against Forktastic — you can introspect the API responses interactively while you're writing code that calls them. Step 1 — Issue a Personal Access Token In Forktastic: Settings → Personal Access Tokens → New Token. Label it "Cursor" so you know which client it's for. Copy the token immediately — it's shown once. Full PAT walkthrough. Step 2 — Add the server to Cursor's MCP config In Cursor, open Settings → MCP → Add Server. The config follows the standard MCP server schema: { "name": "forktastic", "command": "npx", "args": ["-y", "@modelcontextprotocol/server-fetch"], "env": { "MCP_URL": "https://mcp.forktastic.com/rpc", "MCP_TOKEN": "your-PAT-here" } } (Exact UI may vary by Cursor version — the principle is: add a server, paste the URL, paste the token, save.) Step 3 — Verify Open a new chat in Cursor. Type: "Using the Forktastic MCP server, list my cookbooks." Cursor should call the list_cookbooks tool and return your actual cookbook list. If the tool doesn't show up, restart Cursor and re-check the server config. What this enables in your dev flow Generate Markdown recipe exports for documentation or Slack messages. Test integrations against your actual library data while building. Use your recipe library as test data for code that processes structured content. Build agents that work with recipes (planners, finders, formatters). What's the same as Claude The seven tools — search_recipes, get_recipe, list_cookbooks, search_cookbooks, get_cookbook, get_trending, get_family — work identically in Cursor and Claude. Full tool reference. The rate limits — 60/min, 5,000/day per token — apply per token regardless of client. If you use the same PAT for Cursor and Claude, they share the bucket. Issue separate PATs if you want separate buckets. Rate limits reference. Where to go next For the tool reference, 7 MCP tools . For Claude instead, Claude setup . For PAT management, PAT walkthrough . For the MCP pillar, MCP pillar guide . --- ## Build a Recipe Agent: The 7 Tools in Forktastic's MCP Server Source: https://forktastic.com/blog/en/recipe-agent-mcp-tools Published: 2026-09-04T16:00:01.502+00:00 > Reference for the 7 tools in Forktastic's MCP server — plus three example agent designs: weekly planner, pantry-aware finder, Markdown export formatter. Once your Forktastic library is connected to Claude or Cursor via MCP, the next question is what to build with it. This post is the reference for the seven tools the Forktastic MCP server exposes, with example queries and example agent designs. The seven tools search_recipes Purpose: Full-text search across your recipe library. Inputs: query (string, required), limit (int, optional, default 20), offset (int, optional, default 0). Output: Array of recipe summaries (id, title, photo URL, source URL, dietary tags). Use case: "Find my Italian recipes" — Claude calls search_recipes with query="italian". get_recipe Purpose: Fetch full recipe by ID, including ingredients, steps, notes, nutrition. Inputs: recipe_id (UUID, required). Output: Full recipe object. Use case: "Read me the steps for that pasta recipe" — Claude calls get_recipe with the ID from a prior search. list_cookbooks Purpose: List your cookbooks. Inputs: limit , offset (optional). Output: Array of cookbook summaries (id, name, recipe count, last updated). Use case: "What cookbooks do I have?" search_cookbooks Purpose: Search cookbooks by name. Inputs: query (string). Output: Array of cookbook summaries. get_cookbook Purpose: Fetch a cookbook with its recipes. Inputs: cookbook_id (UUID). Output: Cookbook with array of recipe summaries. Use case: "Show me everything in my 'Grandma's Kitchen' cookbook." get_trending Purpose: Get currently-trending recipes across the platform (not just yours). Inputs: limit (optional). Output: Array of trending recipe summaries. Use case: "What's popular right now?" — useful for discovery. get_family Purpose: Get your family group info (members, shared cookbooks). Inputs: None (uses the PAT's account). Output: Family group with members and shared cookbook list. Use case: "Who's in my Forktastic family group?" Three example agent designs 1. The weekly meal-planner agent Prompt: "Each Sunday, query Forktastic for recipes I've cooked in the last quarter. Pick 3 based on: variety of cuisines, recipes I haven't repeated recently, and what's in season. Output as Markdown for my notes app." Tools used: search_recipes, get_recipe, list_cookbooks. 2. The pantry-aware finder Prompt: "I have chicken, broccoli, rice, garlic, and soy sauce in my fridge. Find recipes from my Forktastic library that use 3+ of those ingredients." Tools used: search_recipes (for ingredient match), get_recipe (to verify ingredient list). 3. The export-to-Markdown formatter Prompt: "Pull the recipe with ID X from Forktastic and format it as Markdown suitable for pasting into a Slack message. Include source URL, ingredients as a checklist, and steps as a numbered list." Tools used: get_recipe. Rate limits to know about 60 requests per minute and 5,000 per day per token. For most agent workloads this is plenty; for high-frequency operations, batch your queries. Rate limits and pagination reference. Pagination List endpoints (search_recipes, list_cookbooks, get_trending) use offset-based pagination with limit/offset parameters. Default limit 20, max 100. Offset overshoots return empty arrays (not errors). Where to go next For setup, Claude connection walkthrough or Cursor setup . For rate limits, rate limits reference . For the MCP pillar, MCP pillar guide . --- ## How to Connect Forktastic to Claude with MCP Source: https://forktastic.com/blog/en/connect-forktastic-claude-mcp Published: 2026-09-02T16:00:00.998+00:00 > Step-by-step Claude MCP setup for Forktastic — issue a PAT, add the server to your Claude config, build a recipe agent. This walkthrough connects your Forktastic recipe library to Claude — Claude Desktop, Claude Code, or anywhere that supports MCP. Once connected, every Claude session has read access to your recipes, cookbooks, and family-shared content. You can ask Claude to plan your week, find recipes by ingredient, generate shopping lists in any format you want, or build agents that work with your library. The prerequisites Forktastic Pro (MCP access is gated behind the Pro entitlement). A Claude client that supports MCP — Claude Desktop, Claude Code, or any compatible client. Five minutes for setup. Step 1 — Issue a Personal Access Token In Forktastic, go to Settings → Personal Access Tokens → New Token. Give it a label ("Claude Desktop", "Claude Code", etc) so you know which client it's for. The token is shown once — copy it immediately. Full PAT walkthrough. Step 2 — Add the server to your Claude client For Claude Desktop, open the config file at ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or the equivalent path on your platform. Add a server entry: { "mcpServers": { "forktastic": { "command": "npx", "args": ["-y", "@modelcontextprotocol/server-fetch"], "env": { "MCP_URL": "https://mcp.forktastic.com/rpc", "MCP_TOKEN": "your-PAT-here" } } } } (Exact config syntax may evolve with Claude Desktop updates — check the current Claude Desktop MCP docs if this snippet doesn't load. The principle is the same: add Forktastic's MCP server with your PAT.) Step 3 — Restart Claude Quit Claude entirely and reopen. The Forktastic tools should now appear in your tool palette. Test with a simple question: "List my Forktastic cookbooks." Claude should respond with your actual cookbook list. The seven tools you now have search_recipes — full-text search across your library get_recipe — fetch a specific recipe by ID list_cookbooks — your cookbooks search_cookbooks — search cookbooks by name get_cookbook — fetch a cookbook with its recipes get_trending — popular recipes (across the platform, not just yours) get_family — your family group info (members, shared cookbooks) Full tool reference and example queries. What you can do once it's connected Ask Claude: "Plan a week of dinners from my library using what's in my fridge. I have chicken, broccoli, and rice." "Find the three slow-cooker recipes I've used the most in the last quarter." "Generate a Markdown shopping list for the recipes I have planned this week." "Find recipes in my library that don't have any allergen warnings for my niece's nut allergy." Each of these uses the MCP tools to read from your actual library, not from Claude's training data. What it can't do The MCP server is read-only. Claude can't create, edit, or delete recipes through it. This is a deliberate scope decision — write access through agentic tooling has a much higher risk surface, and the trust model isn't ready yet. Troubleshooting If the tools don't appear after restart, check: The PAT is valid (re-issue if you're not sure). You're on Forktastic Pro (PATs require Pro). The Claude config file is syntactically valid JSON. Restart Claude completely, not just close the window. Where to go next For the tool reference, 7 MCP tools walkthrough . For Cursor instead of Claude, Cursor setup . For the MCP pillar overview, MCP pillar guide . --- ## Forktastic for Power Users: MCP, AI Tools and Developer Workflows Source: https://forktastic.com/blog/en/forktastic-power-users-mcp-guide Published: 2026-08-31T16:00:01.23+00:00 > Forktastic ships a production MCP server at mcp.forktastic.com/rpc — seven tools, PAT auth, 60 req/min. A developer's take on what a recipe agent looks like. This post is for the developer reading the rest of the Forktastic blog and wondering whether the app does anything interesting under the hood. The answer is yes, and the most interesting thing is the MCP server. If you're not a developer, you can skip this one. Nothing here improves how your recipes are organized. But if you build with Claude, Cursor, or any other Model Context Protocol-aware tooling — Forktastic ships a production MCP server at mcp.forktastic.com/rpc that lets you read your recipe library directly from inside your agent. This is unique to Forktastic in the 2026 recipe-app space. No other recipe app has anything close. Why a recipe app has an MCP server The honest answer: because the people building agents now keep wanting to do useful things with the recipes they already own. "Plan a week of meals from my Forktastic library that uses what's in my fridge." "Generate a shopping list as a Markdown table for a Slack message." "Find the recipes I've cooked the most in the last quarter and summarize the cuisine trends." All of those are agent-shaped tasks, and they all need read access to the recipe library. The Forktastic MCP server exposes seven read-only tools that map directly to the things an agent would want to know: search recipes, get a specific recipe, list cookbooks, search cookbooks, get a specific cookbook, get trending recipes, get family info. The full tool reference is here. Connecting Claude If you use Claude (Claude Desktop, Claude Code, or anywhere that supports MCP), add Forktastic as an MCP server in your config. Authenticate with a Personal Access Token issued from your account. After that, every Claude session has your recipe library as context. The Claude connection walkthrough, end to end. Connecting Cursor Cursor's MCP integration follows the same shape. Add the Forktastic server to your Cursor config, drop in a PAT, and you have agentic access to your recipe library from your IDE. The Cursor setup walkthrough. Personal Access Tokens Authentication for the MCP server is Personal Access Tokens — short-string credentials you issue from your Forktastic account that grant agentic read access to your library. Tokens are scoped to the account that created them, can be revoked at any time, and never grant write access. PAT issuance, revocation, and best-practice guide. Rate limits The MCP server enforces 60 requests per minute and 5,000 requests per day per token, with pagination on list endpoints. The pagination model is offset-based with PGRST103 handling for offset overshoot — if you've never built against a PostgREST-backed API before, the rate-limit + pagination guide covers the details that matter. Rate limits and pagination reference. What you can build with it Three real examples, all of which work today: A weekly meal-plan agent that scans your library, your cooked-history, and the season, and proposes a Pick 3 for the week. Runs as a Claude subagent on a cron. A pantry-aware recipe finder that takes a free-form list of ingredients you have on hand and returns recipes from your library that use them — better-targeted than the standard ingredient filter because Claude can reason about substitutions. A recipe-export-to-Markdown tool for blog posts or shared docs: a Claude session can pull any recipe by ID and format it however you want — Markdown, plain text, HTML, even a Notion-friendly block structure. The recipe agent build walkthrough covers all three with copy-paste code. What it doesn't do (yet) The MCP server is read-only in 2026. You can't create or edit recipes through it. This is a deliberate scope decision — writes through agentic tooling have a much higher risk surface, and the trust model needs to be carefully designed before opening write access. We expect to add scoped write capabilities (with explicit user confirmation per write) in a later release. It also doesn't expose any other user's data. Your PAT only sees your account and (if you're in a family group) the recipes your family has chosen to share with the group. There is no global recipe index, no public discovery layer, no cross-user read. Why this matters for the future of recipe apps The interesting thing about MCP isn't the protocol itself — it's that recipe data becomes available to whatever AI workflow you happen to be running. A recipe app that ships an MCP server is a recipe app that admits your data should compose with everything else you use. A longer essay on this idea is here. Where to go next If you want to actually start: connect Claude , issue a PAT , and read the tool reference . If you came to this post by accident and you're not a developer, the honest 2026 comparison post is the right place to start. --- ## Recipe Safari Extension for iOS: Save Recipes While You Browse Source: https://forktastic.com/blog/en/recipe-safari-extension-ios Published: 2026-08-28T16:00:01.014+00:00 > One-tap recipe saving from Safari on iOS — install the Forktastic Safari extension and stop switching apps every time you find a recipe. The Forktastic Safari extension on iOS adds a single button to your browser that saves any recipe page directly into your Forktastic library. Once installed, the friction between "I see a recipe I like" and "it's in my library" is one tap. Why this matters more than it sounds Most recipe-import friction happens because you have to switch apps. You see a recipe in Safari, copy the URL, switch to Forktastic, paste, save. The four steps don't feel like much in isolation, but multiplied by every recipe you ever want to save, it's the difference between a library that grows and a library that doesn't. The Safari extension cuts this to one tap inside Safari. You stop switching apps. You stop losing track of which URL belonged to which tab. Installing the extension Install Forktastic from the App Store. The extension is bundled with the main app. Settings → Safari → Extensions. Find Forktastic in the list, toggle it on. Grant the extension permission to read pages — required so it can parse recipe data from the page you're on. Open Safari, visit any recipe page. The Forktastic icon appears in the share sheet. Using it On any recipe page in Safari: Tap the share icon (bottom of Safari). Tap Forktastic. Confirm Save. The recipe imports in 2-3 seconds. You don't leave Safari. If you want to keep reading after saving, you can. What the extension does differently from manual URL import Same parser, same result. The extension just removes the app-switch step. If you only save a couple of recipes a month, the difference is small. If you save a few per week, the time saved compounds. iPadOS The extension works identically on iPadOS — Safari → share → Forktastic. Useful when you're reading recipes on the iPad in the kitchen. What about Chrome on iOS? Chrome on iOS uses WebKit under the hood like Safari but doesn't expose extension APIs in the same way. The Forktastic extension is Safari-only. From Chrome, copy the URL and paste into Forktastic's URL import — same end result, one extra tap. Android equivalent? Android doesn't have the same browser-extension model. The Forktastic Android app registers as a share target — so from any browser, tap share → Forktastic → save. Functionally equivalent to the iOS Safari extension. Where to go next For the full URL import flow, URL import walkthrough . For broader import methods, the import pillar . --- ## Best Recipe App for iPhone in 2026 (HealthKit + Safari Extension Integration) Source: https://forktastic.com/blog/en/best-recipe-app-iphone-2026 Published: 2026-08-26T16:00:03.3+00:00 > iPhone-specific recipe app picker for 2026 — HealthKit, Safari extension, Apple Watch, and family Pro. Forktastic, Paprika, Recime, AnyList compared. Picking a recipe app on iPhone in 2026 is a different question than picking one in general, because iOS has integrations that don't exist on other platforms. HealthKit, Apple Watch, Siri, the Safari extension model, and Apple Sign-In all change the calculus. This post is the iPhone-specific take on the best recipe apps right now. What "best for iPhone" really means The honest baseline: any recipe app that ships on iOS can be "good on iPhone." What differentiates the best is whether the app actually uses what iOS gives it — HealthKit logging, Apple Watch glances, Siri integration, the Safari share-sheet, dark mode, dynamic type for accessibility, widgets, Live Activities for timers. Most recipe apps treat iOS as a build target. The best treat it as a platform. The leaders for iPhone in 2026 Forktastic Uses HealthKit for meal logging (cook a recipe, log the macros to Apple Health), Safari extension for one-tap saving, voice cook mode that respects iOS dark mode and dynamic type, family Pro that mirrors Apple Family Sharing's "one sub covers everyone" model. The iPhone build is treated as the primary platform; the Android and web builds follow. Apple Health logging walkthrough. Paprika iOS-first historically. Mature, stable, offline-first. Doesn't ship HealthKit integration or modern voice features but the core iOS experience has been refined for over a decade. Paprika vs Forktastic. Recime Strong iOS presence; their AI Instagram / TikTok extraction is the headline feature. Good iOS UX, less platform-specific integration depth than Forktastic or Paprika. Recime vs Forktastic. AnyList Excellent iOS app — particularly strong for grocery list workflow, Siri integration, Apple Watch list. Recipe management is workable but secondary. Apple Notes / Reminders + Apple Recipes (new) For users who want absolutely zero subscription cost and don't need much, the built-in apps now do enough. The trade-off is that you give up structured recipe handling, voice cook mode, and family sharing parity. HealthKit integration matters more than you think If you use Apple Health for any nutrition tracking, the recipe app that logs your cooked meals directly to Health saves you from running a separate food tracker. Forktastic does this. Most competitors don't. Setup walkthrough. Apple Watch For active cooking, Apple Watch glances are useful — see the current step at a glance while your phone is on the counter. Forktastic ships a Watch companion for Cook Mode; check the iOS app's feature list for each contender. Where to go next For the Android-specific version of this comparison, best recipe app Android 2026 . For the broader 2026 comparison, honest 2026 comparison . For Apple Health setup specifically, Apple Health walkthrough . --- ## How to Save Recipes from Any Website to Your Phone Source: https://forktastic.com/blog/en/save-recipes-from-any-website Published: 2026-08-24T16:00:01.359+00:00 > URL import in Forktastic — how it works on every major food blog, plus the 5% of edge cases and how to handle them. The single most common way you'll add recipes to your library is by importing them from food blogs. This walkthrough covers exactly how that works in Forktastic, what edge cases to expect, and how to handle them. The fast path — paste a URL Open Forktastic → tap the + → Import from URL → paste the recipe URL → tap Save. Forktastic fetches the page, parses the structured recipe data (the JSON-LD or microdata most food blogs already publish for Google's rich recipe cards), and imports title, ingredients, steps, photo, total time, servings, and any nutrition data the site published. On most major food blogs — Serious Eats, NYT Cooking, Bon Appetit, Food52, Smitten Kitchen, Half Baked Harvest, all the recipe sites you've heard of — this works on the first try in under three seconds. Even faster — Safari extension (iOS) On iPhone and iPad, install the Forktastic Safari extension. Now any time you're reading a recipe in Safari, tap the share icon → Forktastic → Save. The recipe imports without leaving Safari. Full Safari extension walkthrough. When URL import doesn't work cleanly About 95% of the time URL import is clean. The 5% where it gets messy: Sites with a long lifestyle preamble. Some food blogs put 2,000 words of story before the actual recipe. Forktastic's parser pulls from the structured recipe data, not the prose, so the story stays on the original site — but if the site forgot to mark up the recipe with structured data, the importer may grab the wrong content. The fix is paste-text: copy the actual ingredients and steps from the article, paste into Forktastic, AI parses it into a structured recipe. Paywalled sites. If the recipe lives behind a paywall and you don't have a subscription, the importer can only see what's public. Subscribe to the site or copy-paste the visible portion after logging in. Non-recipe pages. If you accidentally paste a category page, an author page, or a roundup post, the importer reports "no recipe found." Pick the specific recipe URL from the page and re-try. Recipes embedded in YouTube descriptions. URL import doesn't watch videos. For recipes that live in a video, take a screenshot of the description and use photo OCR (see method 3). What gets imported Title — exact text Photo — the recipe's hero image (re-uploaded to Forktastic's image storage so the recipe still works if the original site goes down) Ingredients — structured list with quantities Steps — in order Times — prep, cook, total when published Servings — when published Nutrition — when published Source URL — preserved, so you can always return to the original What doesn't get imported The lifestyle preamble — the author's story about their grandmother's kitchen — does not get imported. That stays on the source site. The "Why this works" paragraphs from sites like Serious Eats also stay on the source site. You can always click the source URL in Forktastic to read them. This is intentional. The blog is the long-form home for the story; Forktastic is the home for the recipe. Bulk URL import? Forktastic doesn't currently support pasting a list of URLs at once. Each URL imports individually. For users moving from another recipe app, the right path is the dedicated bulk importers — Paprika ZIP import or paste-text bulk via the AI parser. Where to go next For the full set of import methods, the import pillar guide . For Instagram or TikTok captures, Instagram walkthrough and TikTok walkthrough . For handwritten or printed sources, the photo OCR guide . --- ## How to Migrate Your Entire Paprika Library to Forktastic in 5 Minutes Source: https://forktastic.com/blog/en/migrate-paprika-to-forktastic Published: 2026-08-21T16:00:01.948+00:00 > Five-minute Paprika-to-Forktastic migration via .paprikarecipes ZIP import — the only modern recipe app that supports this. If you've been using Paprika for a few years, you have a problem when you go to try anything else: your entire recipe library is locked inside one app's data format, and no competing app has a way to read it. Most "Paprika alternative" lists you'll find on the web acknowledge this and then handwave it. "Just re-import your recipes" — which is technically true if you have an evening for every 20 recipes you own. Forktastic is the only modern recipe app in 2026 that supports direct bulk import of a Paprika export file. This post is the five-minute migration walkthrough. What you need before you start Paprika 3 installed on your Mac, PC, iPad, or iPhone. Forktastic installed on the device you're going to migrate to. About five minutes. Step 1 — Export your Paprika library to a ZIP Open Paprika on Mac or PC (the desktop apps make this easier than the mobile apps for a one-shot migration). Go to File → Export → Export Recipes. Select all recipes — Cmd-A on Mac or Ctrl-A on Windows — and choose Paprika Recipe Format . Save the file. It will have a .paprikarecipes extension and contain every recipe in your library as a single archive. If you only have Paprika on iOS, you can email the export to yourself from inside the app and pick up the .paprikarecipes attachment on your computer. Don't try to open the file on iOS — it'll try to import back into Paprika. Step 2 — Open Forktastic and start the import In Forktastic, go to Settings → Import → From Paprika . The importer asks for the .paprikarecipes file. Drop it in, or pick it from your Files / Finder. Forktastic parses the ZIP, extracts every recipe with its ingredients, steps, cook times, photos, and notes preserved. The progress indicator shows recipe count as it goes. For a library of 200 recipes, the import takes roughly 30 seconds end-to-end. Step 3 — Pick where the recipes land Before you commit the import, Forktastic asks where to place the recipes. You have three options: Single new cookbook called "From Paprika" (the default) — keeps everything together so you can review the import before merging into your main library. Preserve Paprika categories as separate cookbooks — if your Paprika library was organized into categories like "Dinners", "Baking", "Family Favorites", each one becomes a Forktastic cookbook. Drop everything into Unorganized — for when you'd rather re-organize from scratch. Pick the option that matches how you organized in Paprika. The "preserve categories" path is the closest to a one-to-one migration. Step 4 — Verify a few recipes Open three recipes you remember well and verify they came in cleanly. Ingredients, steps, photo, notes. If something looks wrong on a specific recipe, the import log (Settings → Import → Recent imports) shows per-recipe success and any parse warnings. In our testing, the import preserves about 99% of recipes losslessly. The ~1% that lose anything are recipes with non-standard ingredient formats — for example, ingredients written as full sentences instead of "amount + item." Forktastic still imports them, just with the original text in the notes field instead of the structured ingredient list. What about photos? Paprika stores recipe photos inside the ZIP. Forktastic re-uploads each photo to its own image storage during import — no broken images, no Paprika-cloud dependency. Once the import is done you can delete the original .paprikarecipes file; the recipes are fully Forktastic-native. What about Paprika's meal plans and grocery lists? The current import handles recipes and recipe metadata. Paprika's meal-plan and grocery-list data are not part of the migration in this release — you set those up fresh in Forktastic. For most users this is fine because the planning workflow is the part you wanted to leave behind anyway. What if I have hundreds of recipes? The biggest Paprika library we've migrated for testing was around 1,400 recipes. The import took 3 minutes 10 seconds. There is no per-import cap, but if your library is large enough that the import takes 5+ minutes, the importer chunks the work so the app stays responsive. Don't close the screen mid-import. What does this cost? The Paprika import works on every Forktastic plan, including the free tier. If you have a library larger than 10 recipes (the free-tier cap) the import will still ingest everything — you'll just see the recipes locked behind the Pro upgrade once you exceed 10. Most Paprika migrators upgrade right after importing because the whole point of moving is to keep using the library. After the import — the rest of the migration Set up Family Sharing if you cook with others. Two-minute walkthrough. Try a single meal plan with the Pick 3 method. Pick 3 method intro. Try voice cook mode for the first recipe you cook from the migrated library. Voice cook mode guide. If anything goes wrong during the import — wrong file format, partial parse, missing photos — every recipe is stored in a re-runnable import log so you can re-attempt without losing anything. Where to go next The honest Paprika vs Forktastic comparison post covers what Paprika still does better — offline-first sync is its lasting advantage — so the migration decision is informed, not just a sales pitch. And the honest 2026 comparison covers the full field of alternatives if you're still deciding. --- ## Save Recipes from Anywhere: Every Import Method Forktastic Supports Source: https://forktastic.com/blog/en/save-recipes-from-anywhere-guide Published: 2026-08-19T16:00:02.352+00:00 > Five recipe import methods compared — and a practical migration workflow for moving 200 recipes in over a weekend evening. The first time you stop using a recipe app, it's almost always because importing recipes into it became friction. The single biggest predictor of whether someone's recipe library will keep growing is whether saving the next recipe takes two taps or twenty. This guide covers every import method Forktastic supports — five of them — and which one fits which kind of source. Method 1 — URL import (the most common case) If the recipe lives on a website, paste the URL. Forktastic's URL importer pulls the title, ingredients, steps, photo, and metadata from the structured data the recipe site already publishes (the same data Google uses to render rich recipe cards). Works on essentially every major food blog. The full URL-import guide covers the edge cases — paywalled sites, sites that bury the recipe in a long lifestyle preamble, and sites with non-standard markup. Method 2 — Paste-text capture (when there's no URL) For text you've already copied — from an email, a messaging app, a screenshot's OCR result, a TikTok caption — paste the raw text into Forktastic and the AI parser turns it into a structured recipe. This is the fastest way to capture something a friend texted you. Step-by-step. Method 3 — Photo / OCR (for handwritten and printed sources) The most underrated import method is the one for things that don't live on the web at all. Take a photo of a recipe card, a page from a cookbook, a printout taped to your grandmother's fridge — Forktastic OCRs the text and AI-parses it into a structured recipe. The full walkthrough for digitizing handwritten family recipes goes deep on the practical workflow (lighting, multi-page recipes, capturing the stories alongside the recipe). Photo capture is also the right answer for screenshots of Instagram Reels or TikTok videos with on-screen text. Instagram-specific workflow ; TikTok-specific workflow. Method 4 — Paprika bulk ZIP migration (for people moving in) Forktastic is the only modern recipe app that supports direct bulk import from a .paprikarecipes export ZIP file. Export your entire Paprika library, drop the ZIP into Forktastic, and the importer ingests every recipe at once with ingredients, steps, photos, and notes preserved. The five-minute migration guide walks through it end to end. If you've been on Paprika for years and have hundreds of recipes, this is the only realistic way to move without losing everything. Method 5 — Safari extension on iOS (save while browsing) On iPhone and iPad, the Forktastic Safari extension adds a "Save to Forktastic" button to any recipe page. You see a recipe you like while you're browsing, tap save, and it's in your library without leaving Safari. No copying URLs, no switching apps. Extension setup and usage. What about Pinterest? Pinterest is a recipe-discovery layer over the same recipe websites you'd import from directly. The right workflow is: find recipe on Pinterest → click through to the source website → use URL import. Importing the Pinterest pin itself isn't useful because the pin doesn't carry the recipe data — it just links to the source. The full Pinterest workflow. What about photo-based ingredient detection? Photo Match — Forktastic's Pro feature for AI ingredient detection — is technically not an import method, it's a search method. Take a photo of what's in your fridge, and Photo Match identifies the ingredients and surfaces recipes from your library that use them. It's the answer to "what can I make tonight" rather than "save this recipe for later." How Photo Match works. Picking the right method for a source Recipe on a food blog → URL import Friend texted you the recipe → Paste-text Recipe written on a card or in a cookbook → Photo OCR Recipe is an Instagram Reel or TikTok video → Screenshot + Photo OCR Migrating from Paprika → Bulk ZIP import You're browsing in Safari and saw something → Safari extension What this looks like for a real migration If you're starting from a sizable existing library — say 200 recipes across a Paprika app, a few Instagram saves, and a stack of family recipe cards — here's the realistic order: Run the Paprika ZIP import first. That handles the bulk of the library in one shot. Spend an evening photographing the family recipe cards and OCRing them in. Group them into a "Family" cookbook so they're separate from web-sourced recipes. Open Instagram and Forktastic side by side, screenshot the dozen recipes you've been saving, OCR them in. Going forward, use the Safari extension for everything you discover while browsing. The whole migration takes a weekend evening. After that, the library compounds because saving the next recipe takes seconds instead of minutes. Where to go from here The other 49 posts in the Forktastic launch run cover specific workflows in depth. If you cook with other people, jump to family recipe management . If you want to know what the cooking experience looks like once recipes are in, jump to voice cook mode . And if you're still comparing apps, the honest 2026 comparison is here. --- ## Index - [The 12 Best Free Recipe Organizer Apps in 2026 (Honest Comparison)](https://forktastic.com/blog/en/best-free-recipe-organizer-apps-2026) - [Best Shared Grocery List App for Families in 2026](https://forktastic.com/blog/en/best-shared-grocery-list-app-2026) - [Plan to Eat vs Forktastic: Dedicated Planner vs Household Workflow](https://forktastic.com/blog/en/plan-to-eat-vs-forktastic) - [BigOven vs Forktastic: Legacy Stalwart vs Modern Tool](https://forktastic.com/blog/en/bigoven-vs-forktastic) - [Mealime vs Forktastic: Curated Plans vs Your Own Library](https://forktastic.com/blog/en/mealime-vs-forktastic) - [AnyList vs Forktastic: Which Family Recipe App Wins in 2026](https://forktastic.com/blog/en/anylist-vs-forktastic) - [Paprika vs Forktastic: A 2026 Comparison](https://forktastic.com/blog/en/paprika-vs-forktastic) - [Recime vs Forktastic: Social-First vs Family-First Recipe Management](https://forktastic.com/blog/en/recime-vs-forktastic) - [Read Recipe Steps Aloud: TTS for Hands-Free Cooking](https://forktastic.com/blog/en/read-recipes-aloud-tts) - [Voice Cook Mode vs Alexa Recipe Skill: Which Actually Helps?](https://forktastic.com/blog/en/voice-cook-mode-vs-alexa) - [Cooking with Vision Impairment: How Voice Mode Helps](https://forktastic.com/blog/en/accessible-cooking-voice-app) - [Voice Timers While Cooking: Set Timers Without Touching Your Phone](https://forktastic.com/blog/en/voice-timer-recipe-cooking) - [Voice Recipes in 6 Languages: Spanish, French, German, Portuguese, Arabic & English](https://forktastic.com/blog/en/voice-recipes-multilingual) - [All 14 Voice Commands in Forktastic Cook Mode (Complete Reference)](https://forktastic.com/blog/en/voice-commands-cook-mode) - [Hands-Free Cooking: The Complete Voice Cook Mode Guide](https://forktastic.com/blog/en/hands-free-cooking-voice-cook-mode) - [How to Add a Recipe by Pasting Text (Quick Capture Method)](https://forktastic.com/blog/en/add-recipe-from-text) - [Photo Match: Use AI to Find Recipes from a Picture of Your Fridge](https://forktastic.com/blog/en/photo-to-recipe-ai) - [Pinterest to Cookbook: How to Save Pinterest Recipes Properly](https://forktastic.com/blog/en/save-pinterest-recipes) - [How to Save Recipes from TikTok Videos](https://forktastic.com/blog/en/save-recipes-from-tiktok) - [Import Recipes from Instagram Reels: Step-by-Step Guide](https://forktastic.com/blog/en/import-recipes-from-instagram) - [Best Recipe App for Android in 2026 (Health Connect + Material You)](https://forktastic.com/blog/en/best-recipe-app-android-2026) - [Batch Cooking: A Prep-Day Workflow for Busy Families](https://forktastic.com/blog/en/batch-cooking-prep-day-workflow) - [Meal Planning with Dietary Restrictions (GF, Vegan, Allergies)](https://forktastic.com/blog/en/meal-planning-dietary-restrictions) - [Meal Planning for Picky Eaters: Dietary Tags + Family Sharing](https://forktastic.com/blog/en/meal-planning-picky-eaters) - [Meal Planning That Actually Works for Real Families](https://forktastic.com/blog/en/meal-planning-that-works) - [How to Order Your Weekly Groceries via Instacart in Forktastic](https://forktastic.com/blog/en/instacart-grocery-checkout-forktastic) - [One-Click Grocery Lists: From Meal Plan to Shopping List](https://forktastic.com/blog/en/meal-plan-to-grocery-list) - [Family Recipe Backup: Never Lose a Recipe Again](https://forktastic.com/blog/en/family-recipe-backup) - [How to Pass Down a Family Cookbook (PDF Export Guide)](https://forktastic.com/blog/en/family-cookbook-pdf-gift) - [How to Digitize Grandma's Handwritten Recipes (Without Losing the Stories)](https://forktastic.com/blog/en/digitize-grandma-handwritten-recipes) - [Cooking Together: Real-Time Recipe Sharing in Households](https://forktastic.com/blog/en/cooking-together-real-time-recipe-sharing) - [One Subscription, Whole Family Pro: How Forktastic's Family Plan Works](https://forktastic.com/blog/en/one-subscription-whole-family-pro) - [How to Share Your Cookbook with Your Whole Family in 2 Minutes](https://forktastic.com/blog/en/share-cookbook-with-family) - [Family Recipe Management: The Complete 2026 Guide](https://forktastic.com/blog/en/family-recipe-management-guide) - [Best Recipe App 2026: An Honest, Feature-by-Feature Comparison](https://forktastic.com/blog/en/best-recipe-app-2026) - [The Pick 3 Method: A Weekly Meal Plan That Doesn't Burn You Out](https://forktastic.com/blog/en/pick-3-weekly-meal-plan) - [Log Meals to Health Connect on Android (Recipe → Macros)](https://forktastic.com/blog/en/log-meals-health-connect-android) - [Forktastic: The AI Recipe App That Imports From Anywhere](https://forktastic.com/blog/en/forktastic-the-ai-recipe-app-that-imports-from-anywhere)