Skip to main content
If your brewing app can export BeerXML or BeerJSON, Brewgravity can read it. Below are the paths for the common ones.
Brewfather exports both BeerXML and BeerJSON. Either works — BeerJSON is the newer, richer format and is the better choice when offered.Export from the recipe list (for several at once) or from an individual recipe’s menu, then drop the files on Brewgravity’s import page.

​
BeerXML or BeerJSON?

BeerXML (.xml)

The older standard, and the one supported almost everywhere. Choose it when you want the export to work with any tool, including ones you have not picked yet.

BeerJSON (.json)

The modern successor. More precise about units and better at representing things BeerXML fudges. Choose it when your app offers it.
Brewgravity reads both, and decides which parser to use from the file extension — so keep the .xml or .json extension on the file when you save it.

​
Coming from a spreadsheet

If your recipes live in a spreadsheet rather than in brewing software, the API is the shorter route: create a recipe with POST /v1/recipes, then add its fermentables, hops, and yeast. A script that walks a CSV and posts each row is a couple of dozen lines.

​
Coming from paper

Type it in. The recipe editor is one screen and stats update as you go, so transcribing a notebook recipe is genuinely faster than converting it into a file first.