Import Brewfather recipes
There is no account link and no API between the two apps. You export a file from Brewfather and import it here, and that works for one recipe or a hundred.


Getting the file out
Section titled “Getting the file out”Open the recipe in Brewfather and use its export option. Brewfather offers BeerXML and BeerJSON, and either works. BeerJSON is the newer format and carries units explicitly, so pick it where the choice is offered. Brewfather can also export its whole recipe library as a batch of files, which is the way to move everything at once.
Then in Beerwright, press Import on the recipes page, choose the file, and check the preview before you accept it. The importing page explains what the preview shows and how we decide each field. We keep every number in the file, and the catalog only fills in what the file leaves out.
What to expect
Section titled “What to expect”Ingredients match by name. Brewfather’s names are close to the makers’ own, so most malts and hops match a catalog entry and pick up the mash-pH chemistry that a file can’t include. An ingredient that doesn’t match is normal. We build it from the file’s own figures, it calculates the same way, and the import notes list it as custom.
Whirlpool additions come across. BeerXML is older than whirlpool
hopping, so Brewfather writes a hop stand as USE=Aroma with the stand
duration. We read that as a whirlpool addition with the stated time as the
stand. Treating it as a zero-minute boil addition would lose all the
bitterness a modern hoppy recipe gets from its whirlpool.
Dry-hop times are days. Brewfather writes dry-hop time in days, where BeerSmith writes minutes. We read a time of sixty or less as days, so a four-day dry hop comes in as four days.
Equipment does not come across. BeerJSON has no equipment section, and Brewfather’s BeerXML equipment section doesn’t fit a Beerwright profile, so imported recipes use your default equipment profile. Set up your rig under Profiles first and switch the recipe to it after import.
Batches and the fermentation log stay behind. The export only contains recipes. Brewfather’s batch records and device readings aren’t part of a recipe export, so we can’t bring them across. Your stock comes across separately; see below.
The vitals in the file are not used. The preview shows Brewfather’s OG and IBU next to ours, and then we keep ours. Small differences come from the two apps using different models, and the FAQ lists the ones we use.
A device already posting to Brewfather
Section titled “A device already posting to Brewfather”If a controller or a relay posts your fermenter’s readings to Brewfather’s custom stream, it can post to us without changing what it sends. Paste a device URL where the Brewfather one goes. The devices page has the field list.
Your stock
Section titled “Your stock”Brewfather can export your inventory too. Use its inventory export and choose Brewfather JSON, then Import on the Inventory page. The inventory page explains what comes across and what doesn’t.
Related
Section titled “Related”- Switching from Brewfather, for the whole move in order, and the months you already paid for.
- Importing recipes, for the rules every import follows.
- Importing from BeerSmith, Importing from Brewer’s Friend.
- Plans, for importing more recipes than the free plan holds.
Something wrong on this page? Tell us.