Altitude Correction for Candy Thermometers: Why Fudge Fails at 2,000 Meters

A cook at 2,000 meters follows a fudge recipe exactly — same ingredients, same technique, same 237°F target on a properly calibrated thermometer — and the batch comes out soft and won't set. Nothing was done wrong. The recipe's target temperature simply wasn't corrected for elevation, and at 2,000m that correction is large enough to change the outcome completely.

A quick safety note before the math

Whatever elevation you're cooking at, the syrup itself is exactly as hot and exactly as hazardous. Sugar syrup anywhere near soft crack or above sits at 150°C/300°F and up, sticks to skin instead of running off, and causes serious burns. Keep children and pets out of the kitchen while the pot is on, never leave it unattended, cook in a deep heavy pan, and never touch or taste hot syrup to check it — use a thermometer or the cold-water test with the pan off the heat. Cool any burn under running water immediately and seek medical care for anything beyond a minor one. Altitude changes the target number the thermometer should read; it doesn't change any of that hazard, at any elevation.

Why altitude changes the target at all

Every sugar stage is really a measurement of how much water is left in a boiling syrup, and temperature is just a convenient proxy for it. But that proxy is calibrated against the boiling point of water, and the boiling point of water isn't a universal constant — it drops as atmospheric pressure drops, which is exactly what happens as elevation increases. At sea level, water boils at 212°F (100°C); climb high enough and the same water boils at a noticeably lower temperature, because there's less air pressure pushing down on it, resisting the transition to vapor. Sugar syrup, being mostly water for most of its cook, follows the same pattern — it reaches any given water content, and therefore any given sugar stage, at a lower thermometer reading the higher you go.

The standard correction

The widely used kitchen approximation is straightforward: subtract roughly 1°F from every sugar-stage target for every 500ft of elevation above sea level, or about 1°C for every 300m. It's not a precise atmospheric-physics calculation — actual pressure varies with weather too, not just elevation — but it's accurate enough to be the standard adjustment most confectionery references recommend, and it's the same correction this site's sugar stage calculator FAQ and the sugar stage reference both use.

Working the correction for 2,000 meters

2,000 meters converts to just under 6,562 feet (2,000 ÷ 0.3048). Applying the 1°F-per-500ft rule: 6,562 ÷ 500 ≈ 13.1°F of correction. That means every sea-level target on the chart needs to come down by roughly 13°F (about 7.3°C) at this elevation. Soft Ball, normally 235–239°F at sea level, becomes roughly 221.9–225.9°F (105.5–107.7°C) once corrected for 2,000m — a genuinely large shift, not a rounding adjustment. A cook at this elevation aiming for the sea-level number is, in effect, aiming at a target that's simply wrong for their kitchen.

What that gap actually does to a batch

Here's the part that explains the failed fudge directly. Running the site's stage classifier on a 237°F reading — a perfectly reasonable sea-level Soft Ball target — correctly returns Soft Ball. But that classification only holds at sea level. Reinterpreting that same 237°F reading as what it's equivalent to once the 13.1°F elevation correction is reversed puts the syrup's true concentration at roughly 250°F sea-level-equivalent — which lands in Hard Ball territory (246–265°F), a full stage past Soft Ball. In other words: a cook at 2,000m stopping at the sea-level Soft Ball number hasn't actually reached anywhere near enough water loss for true Soft Ball at their elevation — they've pulled the syrup while it's still holding meaningfully more water than the recipe's texture depends on, which is exactly why it comes out soft, sticky, and won't set the way it's supposed to.

It's not just Soft Ball — every stage shifts the same way

The Soft Ball example above isn't a special case; the same 13.1°F correction applies uniformly across the entire chart at 2,000m, because the underlying cause — water boiling at a lower temperature — affects every stage equally, not just the one a particular recipe happens to target. Hard Crack, normally 290–309°F at sea level, becomes roughly 277–296°F at 2,000m; Caramelization's 310°F floor drops to roughly 297°F. A brittle or toffee recipe cooked to the sea-level Hard Crack number at this elevation is actually overshooting into caramelization territory, which explains a different but equally common altitude complaint: brittle that tastes scorched or unexpectedly dark even though the cook followed the recipe's stated temperature exactly, with no obvious mistake anywhere else in the process.

Why some recipes already account for this

Recipes written specifically for high-altitude baking sometimes state their temperatures already corrected, which can create confusion if you're combining a recipe from an altitude-aware source with general guidance from a sea-level chart. If a recipe explicitly says it's already adjusted for a stated elevation, applying the standard correction on top of that double-corrects it, undershooting the target. Always check whether a recipe's stated numbers are sea-level defaults (the overwhelming majority are, since most recipes are written and tested at or near sea level) or already elevation-adjusted before applying any correction yourself, and when a recipe doesn't say either way, assume sea level.

Why this is easy to miss

This failure mode is especially frustrating because everything else about the cook can be done perfectly — correct ingredients, a properly calibrated thermometer, careful technique — and the batch still fails, because the recipe's stated number was simply never meant for this elevation. It's also easy to misdiagnose as a different problem entirely: undercooked syrup, humidity, or a bad thermometer all produce a similar "soft, sticky, won't set" symptom, and altitude doesn't announce itself the way a visibly scorched pot does. If a recipe consistently underperforms despite careful execution, and you live anywhere with meaningful elevation, altitude correction is worth checking before anything else.

Applying the correction in practice

The arithmetic is simple once you know your elevation: divide your elevation in feet by 500, and subtract that many degrees Fahrenheit from every stage target in a recipe (or divide meters by roughly 300 for the Celsius version). Rather than doing this by hand for every recipe, the sugar stage reference lays out the full corrected chart at several common elevations — sea level, 2,000ft, 5,000ft, 7,500ft, and 10,000ft — so you can read the adjusted band directly instead of recalculating it each time. For an elevation that falls between the listed bands, interpolating roughly between the two nearest ones is close enough for kitchen purposes, and erring toward the lower (more cautious) end of the interpolated range is safer than overshooting toward the higher one.

A more precise alternative: calibrate against your own boiling water

The 1°F-per-500ft rule is a generic approximation, and if you want a correction specific to your exact location and the day's weather rather than a rounded elevation figure, there's a more direct method: boil plain water and read your thermometer once it's at a steady, rolling boil. Whatever temperature it reads instead of the sea-level 212°F (100°C) is your actual correction for that day, at that spot — apply that same gap to every sugar-stage target instead of the generic elevation-based number. This accounts for local barometric pressure on top of elevation, which the generic rule doesn't capture, and it's worth doing at least once if a recipe keeps turning out wrong despite applying the standard correction, especially on a day with unusually high or low barometric pressure for your area.

Altitude affects more than the target temperature

The stage correction is the biggest and most important effect, but elevation touches a couple of other things worth knowing about. Water itself evaporates a little faster at lower atmospheric pressure, which can make a syrup's total cook time at high altitude run somewhat shorter than a sea-level recipe's stated time even after accounting for the temperature correction — another reason to cook to the (corrected) temperature rather than the clock. Lower air pressure can also mean a slightly faster, more vigorous boil at a given heat setting, so a pot that behaved predictably at sea level may need a touch less heat at altitude to avoid boiling over, particularly in the deep, heavy pan any hot-sugar work already calls for.

The takeaway

A candy recipe's stated temperatures are sea-level numbers by convention, not universal truth, and at any meaningful elevation — 2,000 meters very much included — that convention needs correcting before the number means anything useful in your kitchen. Get the correction right once for your elevation, apply it consistently across every stage a recipe calls for, and a recipe that's "just never worked" at altitude often turns out to have been correct all along — it was simply never given a number that made sense for where it was actually being cooked.