Marathon Pace KM
Menu
← Back to pace chart hub

Race-Day Pace Adjuster (Heat / Wind / Hills)

Compare how the model changes a marathon target for heat, humidity, wind and hills. Its estimates are unvalidated, so use effort and actual conditions to guide your run.

Adjuster Results How to use Execution FAQ
Use case
Heat, wind, hills
Output
Illustrative pace range
Best for
Marathon planning
Mindset
Even effort, not ego

Allow for the conditions

Heat, humidity, headwinds and hills can make your usual target too demanding. Allow for them before the start.

Plain-English takeaway: on tough race days, the best pacing move is often accepting a smarter early slowdown so you do not create a much bigger late slowdown.

For a recorded example of pace changing while heart rate stays in a narrow range, inspect the Sydney selected watch laps in the Running Lab. Those observations alone cannot identify heat, fueling or another cause.

Conditions pace adjuster

Start with your “ideal conditions” marathon target pace or finish time, then adjust for heat, humidity, wind, and hills. The tool gives you an illustrative pace range rather than false precision from a single number.

h m s

Use the time you would target on a cool, flat, low-wind day.

Compare forecasts across the hours you expect to be running, including warmer later sections.

Used to estimate dew point if you do not know it.

If you know dew point, use it. It is often more useful than humidity alone.

A rough average is fine. You do not need perfect weather data.

Use your best judgment for the overall course profile.

This model applies a smaller multiplier for reported acclimatisation; it does not measure your heat tolerance.

These choices scale the model by 110%, 100% or 90%. None is a safety assessment.

Important: this is a planning tool, not a guarantee. In tough conditions, pace by effort and accept slower early splits. If you try to “bank time” in bad conditions, the conditions often take it back with interest.

What to do with your adjusted pace

Use the button to carry the central estimate into your split plan. You can edit it there. The range shows model assumptions, not a confidence interval or a safety assessment.

Best practice: do not just take the mid-point and lock it in as gospel. Ask whether the day is drifting harder, calmer, or more exposed than forecast, and be willing to race the first 10–15 km by feel.

Using the estimate

  1. Start with your ideal-condition goal, not a desperate stretch target.
  2. Use dew point if possible. If not, temperature plus humidity is still useful.
  3. Treat the output as a range, not as one magic pace.
  4. Run the first 10–15 km by effort, especially in heat or headwind.
  5. Generate checkpoints in the Marathon Pace Calculator.
  6. Execute with restraint, using tools like splits and negative split pacing.
Good question to ask before the gun: “Am I trying to run my ideal race, or the race this day actually allows?”

Common mistakes in bad conditions

Running in heat, wind and hills

Heat / humidity

Bias conservative early. Cardiac strain often rises before your pace or ego admits it.

Wind

Focus on effort, posture, and rhythm. Headwinds punish surging more than patient pacing.

Hills

Let pace float uphill, stay smooth on the crest, and use the downhills without overstriding.

In all three cases, even effort usually beats even pace. That is also why pages like how to use a marathon pace chart and even vs negative splits matter so much on tougher days.

These adjustments are unvalidated planning heuristics, not physiological predictions or a guarantee of safe exercise. See coefficients and limitations; revise the plan by effort and actual conditions.

Race conditions pacing FAQ

How much should I slow down for heat in a marathon?

Conditions do not produce one universally correct adjustment. Heat and humidity increase cardiovascular strain, so pace by effort and plan a conservative slowdown. This tool provides an illustrative range, while your appropriate effort still depends on acclimation, fueling, and the exact conditions.

Is dew point better than humidity for pacing?

Dew point is often a better single indicator because it reflects absolute moisture. If you know dew point, use it. If not, this tool estimates it from temperature and humidity.

Should I still aim for even splits in tough conditions?

In heat, wind, or hills, aim for even effort rather than even pace. Accept slightly slower early splits to avoid late-race collapse. A small negative split can still happen if you stay controlled early.

Should I bank time on a tough marathon day?

Usually no. Banking time early in bad conditions often increases the risk of a much bigger slowdown later.

Apply the plan to a course

These 2026 race guides put pacing decisions in a course context. Use the current organiser information for your event alongside them.