Convert Cooklang recipes
Cooklang is a plain-text recipe markup. We parse the spec — frontmatter or >> key: value, @ingredient{qty%unit}, #cookware{}, ~timer{} — and emit PDF, JSON, CSV, Markdown.
100% free. Open-source parsing. No account required.
What we parse
Both metadata styles and every inline marker the spec defines.
A single Cooklang recipe. We extract ingredients, cookware, timers, and metadata from either YAML frontmatter or canonical >> lines.
A zip archive of many .cook files — for example, a CookCLI cookbook/ directory zipped up. Every .cook file inside is parsed independently.
How to export from a Cooklang tool
CookCLI: zip your cookbook directory
CookCLI stores recipes as plain .cook files in a directory you choose. Zip the directory and upload the .zip here.
Cooklang Mac/iOS app: share a recipe
Open a recipe and use the share sheet to export the underlying .cook file.
Tandoor: export as Cooklang
Tandoor can export individual recipes as .cook. For batches, export each recipe and zip them, then upload the .zip.
Hand-written .cook files
Cooklang is plain text — any editor works. Drag the .cook file in here and convert.
Why convert Cooklang?
Cooklang is a brilliant format for cooks who like plain text — your recipes are diffable, scriptable, and work with any editor. But not every kitchen wants to read a markup file. Sometimes you want a printable PDF card, a CSV for a spreadsheet, or schema.org JSON to drop into a website.
We export your .cook files to all of those — and we are also one of the few converters that output .cook for round-tripping in the other direction.
Export to any format
Get your recipes in formats that work for you
Schema.org compliant
Print-ready cards
Excel-friendly
Plain text
For developers
Portable database
YAML format
Convert your Cooklang collection
Drop a .cook file or zip above and pick the output format you want.