> 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/tools/color-conversion.md).

# Color Conversion

Convert beer color values between SRM, EBC, and Lovibond scales.

The Color Conversion tool converts beer color measurements between SRM, EBC, and Lovibond scales.

## How to Use

1. **Enter a value** in any color unit field
2. **View instant conversions** - All other units update automatically
3. **Visual color preview** shows approximate beer color
4. The tool remembers your last entered value

## Beer Color Scales

### SRM (Standard Reference Method)

* Used primarily in North America
* Range: 1-40+ for most beers
* Based on light absorbance at 430nm

### EBC (European Brewery Convention)

* Used in Europe and many other regions
* Range: 2-80+ for most beers
* EBC ≈ SRM × 1.97

### Lovibond

* Older system, still used for malt
* Visual comparison method
* Similar scale to SRM

## Color Ranges by Style

### Light Beers (2-6 SRM)

* **Pilsner**: 2-4 SRM
* **Light Lager**: 2-3 SRM
* **Wheat Beer**: 3-6 SRM
* **Blonde Ale**: 3-6 SRM

### Amber Beers (6-15 SRM)

* **Pale Ale**: 5-10 SRM
* **IPA**: 6-14 SRM
* **Amber Ale**: 10-17 SRM
* **Märzen**: 8-17 SRM

### Dark Beers (15-40+ SRM)

* **Brown Ale**: 18-35 SRM
* **Porter**: 20-30 SRM
* **Stout**: 30-40+ SRM
* **Imperial Stout**: 30-40+ SRM

## Factors Affecting Beer Color

### Ingredients

* **Base Malts**: 1.5-4 L
* **Crystal Malts**: 10-120 L
* **Roasted Malts**: 300-600 L
* **Specialty Malts**: Wide range

### Process Variables

* **Boil Time**: Longer = darker
* **pH**: Higher = darker
* **Oxidation**: Darkens over time
* **Caramelization**: From kettle heat

## Measuring Beer Color

### Laboratory Method

* Spectrophotometer at 430nm
* 1cm path length
* Dilute if needed
* Most accurate method

### Visual Comparison

* Compare to color charts
* Use proper lighting
* White background
* Less accurate but practical

### Digital Tools

* Phone apps available
* Photo analysis
* Reasonable estimates
* Convenient for homebrewers

## Practical Applications

### Recipe Design

* Target specific color
* Balance malt bill
* Predict final appearance
* Match style guidelines

### Quality Control

* Monitor batch consistency
* Track color changes
* Identify process issues
* Compare to standards

### Competition

* Meet style requirements
* Judge expectations
* Visual appeal
* Score optimization

## Color Perception

### Lighting Effects

* **Daylight**: Most accurate
* **Incandescent**: Appears redder
* **Fluorescent**: May shift hue
* **LED**: Varies by type

### Glass and Volume

* Appears lighter in thin layers
* Darker in full pint glass
* Sample in consistent vessel
* Standard is 1cm path

## Tips for Color Control

1. **Accurate Measurements**: Weigh malts precisely
2. **Fresh Ingredients**: Old malt may darken
3. **pH Control**: Monitor and adjust
4. **Consistent Process**: Same boil time/vigor
5. **Avoid Oxidation**: Minimize post-fermentation

## Troubleshooting

### Darker than Expected

* Check boil time and pH
* Avoid scorching

### Lighter than Expected

* Verify extraction efficiency
* Check malt specifications

## Using with Recipe Design

* Convert between scales when following recipes
* Check if your beer color matches style guidelines
* The tool remembers your last entered values
* Use for consistent color targeting across batches


---

# 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/tools/color-conversion.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.