A marathon pace chart translates your goal finish time into the per-mile or per-kilometer pace you need to sustain across 26.2 miles. For example, a 4:00:00 marathon demands an average of 9:09 per mile (5:41 per km), while a 3:30:00 requires 8:00 per mile (4:58 per km). But these are average paces—real-world execution requires starting conservatively, adjusting for course and conditions, and shifting to perceived effort in the final miles when physiology, not your watch, dictates pace.

Marathon Pace Chart: Finish Time to Per-Mile and Per-Kilometer Splits

Below is a comprehensive pace reference spanning the most common marathon finish times. Use these splits as your baseline target, then apply the race-day adjustments covered in the sections that follow.

| Finish Time | Pace per Mile | Pace per Kilometer | |—————–|——————-|————————| | 3:00:00 | 6:52 | 4:16 | | 3:15:00 | 7:26 | 4:37 | | 3:30:00 | 8:00 | 4:58 | | 3:45:00 | 8:34 | 5:19 | | 4:00:00 | 9:09 | 5:41 | | 4:15:00 | 9:43 | 6:02 | | 4:30:00 | 10:17 | 6:23 | | 4:45:00 | 10:51 | 6:44 | | 5:00:00 | 11:26 | 7:06 | | 5:15:00 | 12:00 | 7:27 | | 5:30:00 | 12:34 | 7:49 |

These numbers represent even-pace averages. If you’re targeting a 4:00 marathon, holding 9:09 from gun to tape is mathematically correct—but physiologically suboptimal for most recreational and competitive runners. The next section explains why.

How to Use This Pace Chart on Race Day (Without Blowing Up)

Starting at your goal pace from mile one is the single most common pacing error in marathon racing. Research by Hanley (2016) and Santos-Lozano (2014) shows that sub-elite runners who run slight negative splits—finishing the second half 1–3 minutes faster than the first—record better overall times and lower perceived suffering than those who attempt even or positive splits. The reason is glycogen management: your body stores roughly 90–120 minutes of high-intensity fuel, and aggressive early pacing depletes those reserves before mile 18.

Recommended race-day execution for a 4:00:00 goal:

• Miles 1–6: 9:20–9:25 per mile (10–15 seconds slower than chart pace). This window allows your heart rate to stabilize, your fueling plan to take effect, and your GPS to calibrate in the crowded start.
• Miles 7–20: 9:09 per mile (goal pace). Settle into rhythm, check splits every 5K, and prioritize consistent fueling—30–60 grams of carbohydrate per hour.
• Miles 21–26.2: By perceived effort, aiming for 9:00–9:15 per mile if properly fueled. Your watch becomes less reliable here; focus on maintaining turnover and posture rather than hitting exact splits.

Perceived exertion is your primary governor. Goal pace should feel “comfortably hard” through mile 18—a 6 or 7 out of 10 on the effort scale—then escalate to “hard” (8 out of 10) in the final 10K. GPS watches lag by 3–5 seconds in crowded starts and often misread tangents around sharp turns, so trust effort over digits in the first two miles.

Why Even Splits Are Not the Goal for Most Runners

Elite marathoners often run slightly positive splits—finishing the second half 30–90 seconds slower—because they operate at VO₂ max percentages that require immediate glycogen access from the gun. Recreational runners finishing between 3:30 and 5:00, however, race at lower intensities and benefit from banking physiological reserves early. A 2023 meta-analysis of 50,000+ marathon finishers found that runners who complete the first half 2–3% slower than the second half minimize time loss in the final 10K, where pace deterioration typically costs 20–60 seconds per mile for evenly paced athletes.

The practical takeaway: treat the chart pace as your second-half target, not your starting gun pace. Conservative early miles aren’t “giving up time”—they’re insurance against the exponential slowdown that begins once muscle glycogen drops below 30% of capacity, typically around mile 20 for runners holding aggressive paces from the start.

Adjusting Your Target Pace for Heat, Hills, and Humidity

Environmental and topographical variables can shift your effective pace by 30–90 seconds per mile, even when effort remains constant. Ignoring these factors leads to under-fueling, premature fatigue, and missed time goals despite proper training.

Temperature adjustment: For every 5°F above 60°F, add approximately 2% to your pace. A 4:00 marathoner (9:09/mile) racing in 70°F conditions should expect to slow by roughly 10–11 seconds per mile—equivalent to a 4:05 finish—if maintaining the same cardiovascular effort. At 80°F, that penalty doubles to 20–22 seconds per mile. Below 50°F, most runners see minimal benefit; cold primarily affects warm-up quality, not sustained pace.

Elevation gain: Subtract 15–20 seconds per mile for every 100 feet of net elevation gain per mile. A course with 2,000 feet of total climbing spread across 26.2 miles (76 feet per mile average) costs roughly 12–15 seconds per mile compared to a flat course. On steep climbs, shift entirely to effort-based pacing—hold a conversational effort going up, then recover (don’t attack) on descents.

Humidity above 70%: Add 5–10 seconds per mile. High humidity impairs evaporative cooling, raising core temperature and heart rate even when air temperature feels moderate. If dew point exceeds 65°F, treat the race as a hot-weather event regardless of thermometer reading.

Quick reference for a 4:00 marathoner (9:09 baseline pace):

• 70°F, flat, dry: 9:20/mile
• 75°F, 1,000 ft gain, 60% humidity: 9:35/mile
• 80°F, flat, 80% humidity: 9:45/mile

Adjust your chart pace downward during taper week using local race-day forecast data. Under-promising your finish time by 3–5 minutes based on conditions is smarter than clinging to a pace that ignores physiology.

Common Pacing Mistakes and How to Avoid Them in Training

Even with a perfect pace chart, race-day execution fails when training hasn’t rehearsed the specific demands of goal pace under fatigue. Here are the four most common errors and their corrections.

1. Never practicing goal pace beyond 10 miles in training. Running 6–8 miles at marathon pace feels controlled; holding it for 18–20 miles reveals the true physiological cost. Schedule at least two long runs of 18–20 miles where you complete the final 6–8 miles at goal pace, with the earlier miles 20–30 seconds slower. This trains your body to access fat as fuel while preserving glycogen for the late-race pace push.

2. Ignoring fueling rehearsal. Pace collapses at mile 18–22 are rarely muscular—they’re glycogen depletion. Practice consuming 30–60 grams of carbohydrate per hour during every run longer than 90 minutes, using the same gels, chews, or sports drink you’ll use on race day. Gastrointestinal tolerance must be trained just like pace tolerance.

3. Racing every long run. Running 20 miles at goal pace might feel like productive preparation, but it builds fatigue rather than aerobic capacity and significantly raises injury risk. Reserve goal-pace segments for the final third of long runs, and run the bulk of weekly mileage 60–90 seconds per mile slower than marathon pace. Expert running guides emphasize that aerobic development happens in the easy-pace volume, not in repeated hard efforts.

4. Trusting watch pace in the first mile of a crowded start. GPS accuracy drops to ±15 seconds per mile in the opening kilometers due to satellite interference and course tangents. For the first 5K, run by perceived effort—it should feel almost too easy, a 4 or 5 out of 10—then check your average pace at the 5K mat. If you’re 10–15 seconds fast, ease back immediately; if you’re 10 seconds slow and feel controlled, hold steady.

Add one weekly tempo run of 6–8 miles at goal marathon pace to build pace-specific conditioning. These sessions teach your body to clear lactate efficiently at race intensity and give you a reliable “feel” for goal pace that becomes your primary reference when the watch reads erratically.

From Chart to Course: Translating Pace Into Race-Day Execution

Race-day execution is the bridge between your chart pace and your finish-line time. Here’s a step-by-step plan using a 4:00:00 marathon as the template, adaptable to any goal time by scaling paces proportionally.

Miles 1–6 (9:20–9:25 per mile): The start will feel slow. You’ll be passed by dozens of runners. Ignore them. Your only job is to settle into a rhythm 10–15 seconds slower than goal pace while your cardiovascular system ramps up and your fueling plan begins. Take your first gel or chew at mile 5, paired with water. Check your watch at mile 3 and mile 6; if average pace is faster than 9:20, actively slow down.

Miles 7–13 (9:09 per mile): This is your goal pace window. You should feel strong, controlled, and conversational if you had to speak. Fuel every 45 minutes (typically miles 5, 10, 15, 20), taking water at every aid station. Check splits every 5K rather than every mile—micro-managing pace causes over-correction and rhythm disruption. By mile 13, your first-half time should be 2:01–2:02 for a 4:00 goal.

Miles 14–20 (9:09 per mile, holding effort steady): The middle miles test mental discipline more than physical capacity. Pace will feel slightly harder even though your watch reads the same. This is normal—your glycogen stores are declining, and perceived effort naturally rises. Continue fueling on schedule. Resist the urge to push; mile 18–20 is where most marathons are lost, not won.

Miles 21–26.2 (9:00–9:15 per mile, by perceived effort): Throw out the pace chart. Your legs, breathing, and mental state now govern pace, not your watch. If you’ve fueled properly and paced conservatively early, you’ll have the reserves to hold 9:00–9:10 per mile and possibly push under 9:00 in the final 5K. If you bonked, survival pacing (9:30–10:00) is the goal. Focus on turnover—quick, light steps—and upright posture rather than stride length.

Taper’s role in execution: Your ability to hold these paces depends entirely on arriving at the start line rested. A proper 2–3 week taper reduces training volume by 40–60% while maintaining intensity (a few goal-pace intervals), allowing muscle glycogen to super-compensate and microtrauma to heal. Runners who skip or under-taper frequently report that goal pace “feels harder than in training”—because it is, on fatigued legs.

Mile-marker checks beat continuous pace monitoring. Note your time at miles 5, 10, 13.1, 20, and 25, compare to your plan, and adjust effort for the next segment. This prevents the cognitive load of interpreting every split and reduces the temptation to speed up when you see a “fast” mile or panic when you see a “slow” one caused by an aid station stop or tangent deviation.

Frequently Asked Questions

What pace per mile do I need to run a 4-hour marathon?

To finish a marathon in 4:00:00, you need to average 9 minutes and 9 seconds per mile, or 5:41 per kilometer. In practice, most runners should start slightly slower—around 9:20 per mile—for the first 10K to conserve glycogen, then settle into 9:09 pace through mile 20 before pushing the final 10K by perceived effort.

Should I run even splits for my goal marathon time?

Even splits are ideal in theory, but research shows recreational runners perform better with a slight negative split—running the second half 1–2 minutes faster than the first. Starting 10–15 seconds per mile slower than your chart pace for the first 6 miles reduces glycogen depletion and improves your ability to sustain pace after mile 18.

How do I adjust my marathon pace for heat or hills?

For every 5°F above 60°F, add roughly 2% to your pace (about 10–20 seconds per mile for a 4:00 marathoner). For hills, subtract 15–20 seconds per mile for every 100 feet of elevation gain per mile. Humidity above 70% typically adds another 5–10 seconds per mile. Use these adjustments during your taper to set realistic race-day expectations.

How often should I practice my goal marathon pace in training?

Incorporate goal pace into one tempo run per week—6 to 8 miles at target pace—and run the final 6 to 8 miles of at least two long runs (18–20 miles) at goal pace. Avoid running entire long runs at marathon pace; it builds fatigue without additional aerobic benefit and increases injury risk.

What if my watch shows different paces in the first mile of the race?

GPS watches often read inaccurately in crowded starts due to satellite interference and course tangents. For the first mile, rely on perceived effort—it should feel easy, almost too slow—and trust the tangents you’re running. Check your watch at mile 3 or 5 for a more reliable average, then adjust effort accordingly.

Can I use a pace chart for trail or hilly road marathons?

Pace charts are calibrated for flat, fast courses. For trail or hilly marathons, use the chart as a baseline but shift to effort-based pacing. Aim to hold steady effort (not pace) on climbs, then recover on descents rather than pushing hard. Consider using a heart-rate monitor or perceived exertion scale instead of pace targets.