> For the complete documentation index, see [llms.txt](https://docs.brewfather.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.brewfather.app/styles.md).

# Styles

View BJCP, Brewers Association, and custom beer style guidelines and add your own styles.

![Multiple style guidelines from BJCP, Brewers Association, Norbrygg, SHBF](https://771697612-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LEzhWP2LGeXaKgS2qr4-887967055%2Fuploads%2FEVlOzbqHAeIvb1PcLC3U%2Fstyles-list.png?alt=media\&token=9f042c14-5231-48c4-9331-d41b5acdc53d)

BJCP 2021 is enabled by default. Change active style guidelines by using the book icon in the top right.

Supports the following style guidelines:

* Custom Styles
* BJCP 2021
* BJCP 2015
* BJCP 2015 Cider
* BJCP 2015 Mead
* BJCP 2025 Cider
* Brewers Association 2025
* Norbrygg 2025 (Norwegian)
* SHBF 2020 (Swedish)
* DØLD 2022 (Danish)
* BJCP 2021 (Brazilian Portuguese)

### Adding Custom Styles

We are aware that some styles exist and that they are not included in a guideline. In these cases, you can add a Custom Style.

1. Go to the styles page
2. Click the "Edit Custom Styles" icon in the top right
3. Click on "+ Add Style" button
4. Fill the required fields
5. Make sure "Custom Style" guidelines are activated in the styles page with the book icon in the top right

After adding a new style, there are several actions you can take:

* Update information
* Duplicate an existing Custom Style (as basis to a new Custom Style)
* or Remove.

### Adding Custom style guidelines from XML

You can also add a whole new guideline if you want, using the XML import format.

1. Go to the styles page
2. Click the "Edit Custom Styles" icon in the top right
3. Click import button bottom left
4. Import a style BeerXML file - Example: BJCP 2008 file can be downloaded below
5. Make sure custom style guidelines are activated in the styles page with the book icon in the top right

{% file src="/files/-MVpMVHHJ5QH1apP-Tcd" %}

{% file src="/files/-MVpNop7bReYQuqgNK4I" %}

## Related docs

* [Custom Styles](/profiles/custom-styles.md)
* [Recipe Designer](/recipes/designer.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.brewfather.app/styles.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.