How to Manage SO2 in Winemaking: A Practical Guide for Small Wineries

Free sulfur dioxide (SO2) is winemaking's insurance policy. It protects your wine from oxidation, controls spoilage organisms, and keeps your fruit character intact through aging. But the margin between "protected" and "over-sulfited" is narrow — and most small wineries are managing it with a spreadsheet built in 2009.

Why SO2 Management Is Harder Than It Looks

The science is straightforward: you want to maintain enough molecular SO2 to be antimicrobial — typically 0.5–0.8 ppm for wines at table pH. The target free SO2 you need to hit that molecular level depends on your wine's pH. At pH 3.2, you might need 18 ppm free SO2. At pH 3.8, you might need 60+ ppm to get the same protection.

The problem isn't the math. It's the operational reality: multiple lots at different pH levels, barrels with different headspace, additions timed around rackings, bottling runs, harvest intake. Each decision compounds on the last. A missed addition in October shows up as a flaw in the glass two years later.

The Core Calculation You Need

To find your target free SO2, you first calculate the molecular SO2 you need (usually 0.5–0.8 ppm) and work backward using the formula:

Molecular SO2 = Free SO2 / (1 + 10^(pH − 1.81))

Rearranged: Target Free SO2 = Molecular SO2 × (1 + 10^(pH − 1.81))

Once you have your target, compare it to your current free SO2 reading (from an aeration-oxidation or Ripper titration), find the deficit, and calculate the addition in grams of potassium metabisulfite (KMS) or milliliters of liquid SO2 solution needed per volume of wine.

A common rule of thumb: 1 gram of KMS per 100 liters raises free SO2 by approximately 9 ppm, though this varies by wine chemistry and bound SO2 fractions.

Common Mistakes That Hurt Wines

• Dosing by habit instead of testing. "I always add 30 ppm at racking" is not a protocol — it's a guess. Wines bind SO2 differently depending on acetaldehyde levels, glucose oxidase activity, and residual yeast.
• Ignoring pH drift. A wine that falls from pH 3.4 to 3.6 during ML fermentation needs a different free SO2 target, even if nothing else changed.
• Late additions at bottling. Adding SO2 within 24–48 hours of bottling without letting it equilibrate leads to inconsistent free SO2 readings across the run.
• Using bound SO2 as a buffer. Bound SO2 provides minimal antimicrobial protection. Free SO2 is what matters. Track both, but act on free.

Building a Repeatable Cellar Protocol

The best small wineries treat SO2 management as a standing protocol, not an ad-hoc decision. That means:

1. Testing free SO2 on every lot at every racking, regardless of "how it looks."
2. Logging pH alongside free SO2 readings so your targets auto-adjust.
3. Setting calendar alerts for post-ML additions, pre-aging top-offs, and pre-bottling checks.
4. Keeping addition records by lot, date, amount, and method (dry vs. liquid solution).

When this data lives in a spreadsheet shared between two winemakers and a cellar hand, it breaks down fast. Versions diverge. Formulas get overwritten. The August intern accidentally deletes the pH column.

How WinemakerOS Handles This

WinemakerOS was built specifically to replace the ad-hoc SO2 spreadsheet. You enter your wine's current pH and free SO2 reading, and it calculates your target, deficit, and addition amount — for every lot, in real time. Protocol history is stored by lot, not by who sent the last email with the spreadsheet attached.

For wineries managing 10–50 lots across a vintage, this means fewer oversights, fewer spoilage events, and a cellar log that actually reflects what happened — not what someone remembers happening.