Import BeerSmith recipes
BeerXML started as BeerSmith’s format, and in practice it still means “what BeerSmith writes, plus what other programs write so BeerSmith can read it”. Most of the quirks we handle on import are BeerSmith’s.


Getting the file out
Section titled “Getting the file out”Select the recipes in BeerSmith and use its export to BeerXML. One file can hold many recipes, and we read all of them. Then press Import on the recipes page in Beerwright, choose the file, and check the preview. The importing page explains the preview and how we decide each field: your numbers come first, and the catalog only fills in what the file couldn’t state.
Or export the BeerSmith file itself
Section titled “Or export the BeerSmith file itself”BeerSmith has a format of its own, and you can import that instead. In
BeerSmith, check the recipes you want and choose File, then Export
Selected. You get a .bsmx file, which you can import directly with the same
Import button, and the preview marks it BeerSmith. You get every recipe you
checked in one file.
The native file is a little more accurate than BeerXML in four places:
- Your strike temperature. In BeerXML, BeerSmith writes the infusion
temperature as display text, so we can’t tell which unit it’s in. The
.bsmxgives the unit, so a mash that strikes at 162 °F comes in at 72 °C instead of being capped at the top of the range. - Your rig. The recipe includes the whole equipment profile it was written for: batch and boil volumes, the boil-off as an hourly rate, trub and chiller loss, tun deadspace, top-ups, tun volume and the brewhouse efficiency your numbers were calculated at. We read all of it, and the batch size and boil length go onto the recipe itself.
- Your fermentation schedule. BeerSmith fills in all three stages whether
or not your profile uses them. The
.bsmxrecords how many you actually use, so a two-stage profile comes in with two stages and its conditioning, without a tertiary you never planned. - How you carbonate, and when you pitched. The carbonation profile tells us bottle or keg, and the yeast’s package date comes across in a form we can read.
Apart from those four, a .bsmx brings the same things BeerXML does. It can
also include your brew sessions, which are the gravities and volumes you
measured, stored on the recipe itself. We show those in the preview wherever
you recorded one and leave the fields you never filled in alone. They don’t
become batches, because none of our imports create batches.
One thing to watch for: BeerSmith can also export a .bsmx of just grains,
hops or equipment, from those views instead of the recipe view. That file is a
list of ingredients, not recipes, so we tell you and point you to Import on
the Inventory page.
BeerSmith quirks we handle
Section titled “BeerSmith quirks we handle”The encoding. BeerSmith saves files as ISO-8859-1 by default instead of UTF-8, and it sometimes writes Windows character codes into pasted notes. We read the file in the encoding it declares and convert those codes, so a recipe named after a Kölsch keeps its umlaut.
Display fields. Next to every real field, BeerSmith writes a DISPLAY_*
field, rounded and in your unit. We ignore those and use the numeric field.
Figures with units in them. BeerSmith writes an estimated OG as
"1.056 SG" and color as "7.0 SRM". We take the number. We show the file’s
own vitals in the preview and then throw them away, because we calculate our
own.
Potential. BeerSmith gives a malt’s yield as a gravity per pound per gallon, such as 1.036 for 36 PPG. We convert it, and it becomes the row’s yield, using your number instead of the catalog’s.
Recommend mash. BeerSmith’s database writes RECOMMEND_MASH=FALSE on
base malts, Maris Otter among them. Following it would steep a base malt and
cost an all-grain recipe a third of its gravity, so we ignore it and let the
ingredient’s own type decide mash or steep.
Adjuncts. Flaked maize and torrified wheat come in as grain, because in a mash that’s how they behave.
Whirlpool additions. BeerXML is older than whirlpool hopping, so BeerSmith
writes a hop stand as USE=Aroma with its duration. We read it as a whirlpool
addition with that stand time.
Dry-hop time in minutes. BeerXML says every time is in minutes, and
BeerSmith follows that, so a four-day dry hop is 5760. We read any time over
sixty as minutes, and it comes in as four days.
Dates. BeerSmith writes a yeast’s manufacture date in your locale’s order, and we can’t tell day-first from month-first. If a date could be either, we leave it blank. It’s only used for the viability estimate, and you can retype it on the row.
Corn sugar by another name. BeerSmith writes “Corn Sugar” where others write “corn sugar (dextrose)”. Both match the same catalog entry.
What does not come across
Section titled “What does not come across”We don’t create Beerwright profiles from BeerSmith’s equipment profiles, mash profiles or carbonation settings. The recipe uses your default equipment profile and the schedule in the file, so set up your rig under Profiles and switch the recipe to it. We also leave out tasting notes, ratings, per-ingredient notes and the file’s own style ranges, and the importing page lists the rest.
Your stock
Section titled “Your stock”BeerSmith can export ingredients as a BeerXML list, and if the file includes the amounts you have, that brings your stock across. Choose it with Import on the Inventory page. The inventory page explains what comes across and what doesn’t.
Related
Section titled “Related”Something wrong on this page? Tell us.