Import recipes from other brewing software
Press Import on the Recipes page. We accept four kinds of file, and we work out which one you have from what’s inside it, whatever its extension says:
- BeerXML — what BeerSmith, Brewfather and Brewer’s Friend all export
- BeerJSON — the newer format, from anywhere
- BSMX — BeerSmith’s own file, the one already sitting in your library
- A Beerwright data export — your own workspace export
Your file stays in your browser. We read it, match its ingredients against the catalog and cost every recipe in it on your device, so even a two-hundred-recipe file is never uploaded anywhere.


What happens, in order
Section titled “What happens, in order”- Choose a file. You pick it from a file picker; you can’t drag it in.
- Preview. You see every recipe in the file, each checked and each one
something you can uncheck. Next to each one we show the vitals we calculated
and the ones the file claimed, like
1.062next to(file: 1.060). A small difference is normal. It usually means the two programs use a different IBU model or efficiency, and we always show you our own numbers rather than repeating the file’s. - Confirm. Each recipe you selected comes in as its own step, so ⌘Z undoes one recipe at a time. The first one opens.
Next to each recipe in the preview we show how its ingredients matched, such as “8 matched” and “2 custom”, and a collapsed panel lists any notes and warnings.
If the file is malformed, we show you the error with its line and column, and nothing is imported.
How we fill in each field
Section titled “How we fill in each field”We keep every number the file gives us. The catalog fills in what the file leaves out, and we use it to work out which ingredient each row is.
So if your BeerXML says Maris Otter at 37 PPG and 3 °L, you get Maris Otter at 37 PPG and 3 °L, even if the catalog’s figures are different.
The one thing neither format can carry is mash-pH chemistry: an ingredient’s distilled-water pH, its buffering capacity and its malt class. A catalog match is the only way your recipe gets them, which is why matching matters. If an ingredient doesn’t match, we leave those values empty.
Ingredient matching
Section titled “Ingredient matching”We compare each name in the file against the catalog, and we’re forgiving about
how it’s written. Accents and plurals don’t matter, words like malt, pellet
and hops are ignored, and so are region names. Spellings the trade uses
interchangeably count as the same word, so Pils, Pilsen and Pilsner match,
and so do Caramel and Crystal. Yeast product codes (US-05, WLP001) match
directly.
If a maltster’s name is part of the product name, we treat it as the maltster. BeerSmith and Brewfather put it either at the front, as in “CNC Pils”, or in parentheses at the end, as in “Honey Malt (Gambrinus)”, and either way we only match that maker’s products. That’s why “Rahr Vienna” comes in as a custom ingredient instead of matching someone else’s Vienna. Rahr doesn’t make a Vienna malt, and we’d rather leave it unmatched than match it to the wrong one.
Two things prevent a match entirely:
- A different kind or form. A sugar never matches a grain, and a dry yeast never matches a liquid strain.
- A different number.
Crystal Malt - 20Lwon’t matchCrystal 60. Names that differ only in a number are different ingredients, and getting the color wrong by 40 °L would give you a visibly wrong beer.
An ingredient that doesn’t match is perfectly normal. We build it from the file’s own values, it calculates the same way, and we mark it as custom and mention it in the import notes.
What is inferred, and why
Section titled “What is inferred, and why”BeerXML is a 2008 format, and the programs that write it don’t agree on what some fields mean. Where we have to make a call, we tell you about it in the import notes.
| The file has | We read it as | Why |
|---|---|---|
USE=Aroma |
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 |
RECOMMEND_MASH=FALSE on a base malt |
Ignored; the recipe’s own type decides mash or steep | BeerSmith writes this on base malts. Following it would cost an all-grain recipe a third of its gravity |
| A dry-hop time over 60 | Minutes | BeerSmith writes minutes |
| A dry-hop time of 60 or less | Days | Brewfather writes days |
| A yeast amount by weight | 11.5 g sachets | |
| A yeast amount of 0.5–10 L | Packs | |
| Any other yeast volume | 35 mL vials | |
| A style category number | Used only if the file names the 2021 guidelines | 8B was Special Bitter in 2008 and is Schwarzbier in 2021, so a number from the wrong edition would give you the wrong style |
Where the file leaves something out entirely, we use a default and tell you: 66 °C for 60 minutes if there is no mash step, 20 °C for 14 days if there is no fermentation schedule, 18.927 L (5 US gal) if there is no batch size, 60 minutes of boil, 75 % attenuation, and 2.4 volumes of CO₂.
If a value is just out of range, we bring it back to the nearest sensible value and tell you. If it’s impossible, like 250 % attenuation or pH 14, we ignore it.
What is dropped
Section titled “What is dropped”- Every
DISPLAY_*field. We use the numeric field next to it instead. - Tasting notes and ratings, the file’s own style ranges, priming and keg fields, and tags from other programs we don’t recognize.
- Per-ingredient notes. The recipe’s own notes come across, starting with the brewer’s name if the file gave one.
- BeerJSON’s equipment block.
- Any unit we don’t recognize. If we can’t read the unit, we treat the amount as missing, because using the bare number with the wrong unit would be worse. For the same reason we don’t accept a gravity in Plato or Brix.
There is also a limit per recipe of 64 fermentables, 64 hops, 64 miscellaneous items, 16 yeasts, 16 mash steps and 16 fermentation steps.
Brewfather, BeerSmith and Brewer’s Friend
Section titled “Brewfather, BeerSmith and Brewer’s Friend”There is no Brewfather integration, no account linking and no API. We support those programs through the files they export, and the quirks in the table above are the ones their exports have. Each one has its own page on where to find the export and what to expect from it: Brewfather, BeerSmith and Brewer’s Friend.
What gets frozen at import
Section titled “What gets frozen at import”Your recipes shouldn’t change when we update the ingredient catalog. So when an ingredient matches, we copy the figures we calculate with (yield, color, moisture, alpha acid, attenuation and the mash-pH chemistry) into the recipe itself.
We also note which catalog entry each ingredient matched and which version of the catalog it came from. That’s only a note about where it came from, and we never use it to look a value up again. A recipe you import today will calculate the same way in a year, however the catalog has changed since.
We don’t keep the original file. Once you’ve imported it, the recipe in Beerwright is all there is, and there’s no “view original” anywhere.
We show you the vitals the file claimed in the preview and then throw them away. We never use them in a calculation or save them with the recipe.
Exporting
Section titled “Exporting”You can export in three ways:
- A single recipe: from the recipe’s overflow menu, choose Export as BeerJSON. We write the calculated vitals into the file.
- A selection: check the recipes on the list, then press Export in the
bar along the bottom. You get one file,
beerwright-N-recipes-YYYY-MM-DD.beerjson.json, with each recipe’s own vitals. If you only check one, it’s the same as exporting a single recipe. - Everything: in Settings, choose Export all data to get
beerwright-workspace-YYYY-MM-DD.jsonwith your recipes, equipment profiles, water profiles and settings.
There is no BeerXML export. We read BeerXML but don’t write it. BeerJSON is the format we export.
A BeerJSON file from Beerwright also includes the ingredient figures we froze, where each one came from, and the recipe’s water settings. So if you import your own export, you get the recipe back as it was. Other programs skip that extra section and read the standard BeerJSON.
Importing a workspace export brings in recipes only. Your equipment profiles, water profiles and settings are in the file, but this import doesn’t read them, and the import notes mention it.
Importing more than your plan allows
Section titled “Importing more than your plan allows”Before you start, we check how many recipes you have and warn you:
Your plan has room for 3 more recipes. Importing more than that will import the first 3 and leave the rest — deselect some, or upgrade first.
We don’t stop you, though. We import recipes one at a time until you reach your plan’s limit, then skip the rest. See Plans, billing and trial codes.
Related
Section titled “Related”- From Brewfather, from BeerSmith and from Brewer’s Friend.
- Ingredients, for how an imported ingredient is matched to the catalog.
- Profiles, for the equipment an imported recipe lands on.
Something wrong on this page? Tell us.