Cold Crash & Conditioning Automation for Fermentation (2026)

Cold crash by dropping a finished ferment to 32–38°F (0–3°C) once the gravity has been stable for a couple of days — the cold makes yeast and haze particles flocculate and settle, leaving brilliantly clear beer or wine in a day or two. The two things that matter are timing it off gravity (not the calendar) and avoiding suckback as the vessel cools. Here's how to run the crash and conditioning ramp automatically.

What cold crashing does

Near-freezing temperatures cause suspended yeast, proteins, and tannin-polyphenol haze to clump and drop to the bottom. The result is a clearer product without filtering or finings — and for hop-forward beer, cold conditioning also drops hop debris. It's the cheapest clarity you'll ever get; it just needs the cold and a little patience.

Timing: crash on gravity, not the calendar

Crash only after fermentation is actually complete — gravity has reached terminal and held steady for ~2–3 days. Crash too early and you halt active yeast before they finish attenuating and clean up byproducts (diacetyl, acetaldehyde), locking in off-flavors and leaving the beer under-attenuated. This is why an inline gravity reading (an iSpindel or float hydrometer) is so useful: "gravity flat for 48 hours" is the real trigger, and you usually want a diacetyl rest (a few warm days near terminal gravity) before you drop the temperature.

Setpoints for the crash and conditioning

• Diacetyl rest (before crashing): let the beer free-rise to ~68–72°F (ale) for 2–3 days at terminal gravity so the yeast cleans up.
• Cold crash: ramp down to 32–38°F (0–3°C). Closer to 32°F drops yeast hardest; many crash at ~34–36°F to stay safely above freezing the beer.
• Ramp rate: drop gradually (over hours, not instantly) where you can — a controlled ramp is gentler and reduces thermal shock and pressure swings.
• Hold: 24–48 hours is usually enough; longer compacts the sediment further.

The suckback trap

Here's the one that catches people: as a sealed fermenter cools, the gas inside contracts and creates a vacuum that sucks airlock liquid (or worse, air and oxygen) back into the beer — "suckback." Oxygen pickup at this stage stales the beer. The fixes are mechanical (a spunding valve, a CO₂ source, a blow-off into sanitizer rather than star-san-and-vodka, or a balloon/mylar capture) — but the control lesson is to ramp the temperature down gradually rather than slamming it cold, which makes the pressure change slower and more manageable.

Automating the ramp

Cold crash is a scheduled temperature transition, which is exactly what an edge controller does well:

• Trigger: gravity stable → (optional) diacetyl rest → cold crash, as a sequence of setpoints.
• Control: the same cooling source (glycol chiller, fridge, or freezer) and controller you fermented with, now targeting 32–38°F with a minimum run time.
• Ramp: step the setpoint down over a few hours rather than in one jump.
• Alerting + logging: warn if the vessel approaches freezing, and log the whole curve.

In LoopString, this is a recipe/schedule on top of the same fermentation flow: per-stage setpoints walk the beer from primary through the diacetyl rest into the cold crash automatically, edge control on the Raspberry Pi holds each stage, and alerts fire if it drifts toward freezing — with gravity and temperature logged so you can see clarity develop against the curve. You set the sequence once and the batch conditions itself overnight.

Quick reference

1. Crash only after gravity is terminal and stable for 2–3 days — not on a fixed date.
2. Do a diacetyl rest before dropping the temperature.
3. Ramp down to 32–38°F gradually; ~34–36°F is a safe target above freezing.
4. Manage suckback — ramp gently and use a spunding valve or CO₂/blow-off so you don't pull in oxygen.
5. Automate the whole primary → rest → crash sequence as scheduled setpoints and log the curve.