How to Export Your Recipes: A Complete Guide

7 min read

Once you have imported your recipes into MoveMyRecipes -- whether from a Paprika archive, a Cook'n database, a CopyMeThat export, a website URL, an OCR image, or any other supported source -- the next step is choosing an export format.

MoveMyRecipes offers seven export formats, each suited for different purposes. This guide explains what each format looks like, what it is good for, and when you should choose it.

1. JSON (Schema.org)

File extension: .json Best for: Importing into other recipe apps, programmatic use, long-term archival

JSON export produces a Schema.org-compliant array of Recipe objects. Each recipe includes standardized fields: name, description, recipeIngredient (as an array of strings), recipeInstructions (as an array of HowToStep objects), prepTime, cookTime, totalTime, recipeYield, recipeCategory, url, aggregateRating, nutrition, and image.

Custom fields that do not map to Schema.org -- like personal notes, difficulty ratings, or favorite status -- are preserved with an x- prefix (e.g., x-notes, x-difficulty).

When to choose JSON:

  • You are importing into a self-hosted recipe manager like Mealie or Tandoor Recipes, which accept Schema.org JSON.
  • You want a machine-readable backup that preserves the most data with the most structure.
  • You plan to write scripts or tools that process your recipe collection programmatically.
  • You want a format that will remain parseable and useful decades from now.

JSON is the most complete export format. If you are unsure which format to pick, JSON is a safe default.

2. CSV

File extension: .csv Best for: Spreadsheets, databases, bulk analysis

CSV export creates a spreadsheet-compatible file with one row per recipe. The columns are: Name, Description, Ingredients, Instructions, Prep Time, Cook Time, Total Time, Yield, Category, Source URL, Rating, and Notes.

Ingredients are joined into a single cell with newline separators. Instructions are numbered ("1. Preheat oven...") and similarly joined. ISO 8601 time durations are converted to readable strings like "1 hr 30 mins."

When to choose CSV:

  • You want to open your recipes in Excel, Google Sheets, or LibreOffice Calc.
  • You are doing bulk analysis -- sorting by cook time, filtering by category, counting ingredients.
  • You need to import into a database or another system that accepts CSV.
  • You want a quick, scannable overview of your entire collection in a flat table.

The tradeoff with CSV is that multi-line fields (ingredients and instructions) are crammed into single cells, which can be unwieldy for recipes with many steps. But for getting a bird's-eye view of a large collection, nothing beats a spreadsheet.

3. Markdown

File extension: .md Best for: Note-taking apps, plain-text archives, Obsidian vaults

Markdown export produces clean, readable text files. Each recipe gets a heading with the name, a metadata line showing prep/cook/total time, yield, category, and rating, followed by ingredient lists (as bullet points) and instructions (as numbered steps). Notes and source URLs are included at the bottom.

Multiple recipes in a single export are separated by horizontal rules (---).

When to choose Markdown:

  • You use Obsidian, Notion, Bear, or another note-taking app that works with Markdown.
  • You want recipes in a plain-text format that is human-readable without any special software.
  • You are building a personal knowledge base or digital cookbook in a file system.
  • You value simplicity and long-term readability over structure.

Markdown is arguably the most future-proof text format. A Markdown recipe file created today will be perfectly readable in 50 years with nothing more than a text editor.

4. CookLang

File extension: .cook Best for: CookLang ecosystem, plain-text recipe management

CookLang is an open-source recipe markup language (from cooklang.org) designed specifically for recipes. It uses a simple syntax where ingredients are marked with @, cookware with #, and timers with ~.

The MoveMyRecipes CookLang export includes metadata lines (using >> syntax) for the recipe name, description, servings, times, and source. Ingredients are listed as CookLang-formatted comments, and instructions are written as paragraphs. The exporter attempts to parse ingredient strings into CookLang's structured format (e.g., @flour{2%cups}) by identifying quantities and units.

When to choose CookLang:

  • You use CookLang-compatible tools like the CookLang CLI, CooklangApp, or a recipe viewer that supports .cook files.
  • You like the idea of a purpose-built, plain-text recipe format.
  • You want ingredients to be semantically tagged within the text rather than listed separately.

CookLang is a niche format, but it has a dedicated community and a clear design philosophy. If you are already in the CookLang ecosystem, this is your format.

5. PDF

File extension: .pdf Best for: Printing, sharing, recipe cards

PDF export generates formatted recipe cards using a styled template. Each recipe gets a clean layout with the title, description, a metadata bar (prep/cook time, servings, category), an ingredient list, numbered instructions, notes, and source attribution.

The styling uses a warm color palette with clear typography that looks good both on screen and printed on paper.

When to choose PDF:

  • You want to print recipe cards for a physical binder or recipe box.
  • You need to share a recipe with someone who is not technical -- just send them the PDF.
  • You want a polished, visual presentation of a recipe.
  • You are creating a printed family cookbook.

PDFs are not great for importing into other apps (the data is locked into the visual layout), but for human consumption -- reading, printing, sharing -- they are ideal.

6. HTML

File extension: .html Best for: Web viewing, email sharing, self-contained recipe pages

HTML export creates a self-contained web page for each recipe with embedded CSS styling. No external dependencies -- just open the file in any browser. The layout includes a styled header, a metadata bar with prep/cook time and servings, a two-column ingredient list, numbered instructions with step indicators, a notes section, and source attribution.

The pages are responsive, working well on both desktop and mobile screens, and include print-friendly styles.

When to choose HTML:

  • You want to host recipes on a personal website or share them via email.
  • You need a visual format that works in any browser without installing anything.
  • You want something that looks polished but remains a single, portable file.
  • You are building a simple recipe website from static files.

HTML gives you the visual presentation of PDF with the flexibility of a web format. You can open it, edit it, host it, or just keep it in a folder.

7. Open Recipe Format (ORF)

File extension: .yaml Best for: Structured data exchange, interoperability, recipe communities

Open Recipe Format is a YAML-based specification designed for storing and sharing recipes in a structured, human-readable format. Each recipe includes fields like recipe_name, recipe_uuid, ingredients (with structured name, amounts, and processing fields), steps, prep_time, cook_time, yields, notes, and source_url.

The MoveMyRecipes ORF exporter goes further than simply listing ingredients as strings. It parses ingredient text into structured components -- separating the quantity, unit, ingredient name, and processing instructions (like "diced" or "melted") into distinct fields. Units are normalized to full words ("tablespoon" instead of "tbsp").

When to choose ORF:

  • You want structured ingredient data, not just strings.
  • You are working with tools or communities that use the Open Recipe Format.
  • You want a YAML file that is both human-readable and machine-parseable.
  • You value an open standard designed specifically for recipe interchange.

ORF is the newest format MoveMyRecipes supports, and it represents a thoughtful approach to recipe data structure. If structured ingredients matter to you, ORF is worth considering.

Choosing the Right Format

If you are unsure, here is a quick decision guide:

  • Importing into another app? Start with JSON.
  • Opening in a spreadsheet? CSV.
  • Using Obsidian or a notes app? Markdown.
  • Printing? PDF.
  • Sharing via email or web? HTML.
  • Want structured ingredient data? Open Recipe Format.
  • Using CookLang tools? CookLang.

You are not limited to one. MoveMyRecipes lets you export the same recipe collection to multiple formats. Grab JSON for your long-term archive, Markdown for your Obsidian vault, and PDF for the recipes you want to print -- all from the same upload.

Every export is free, no account is required, and your files are automatically deleted after seven days. Head to movemyrecipes.com/convert to get started.

Ready to move your recipes?

Export and convert your recipe collection for free. No account required.

Convert My Recipes