How to read a marathon pace chart
A marathon pace chart answers one simple question: for the finish time I want, what pace must I average? Find your goal time in the left column, then read across to the average pace per mile and per kilometer. That pace is the speed you need to hold — on average — for all 26.2 miles (42.195 km) of the marathon.
Three things the raw chart does not tell you, and why this page exists as a tool rather than a dead table:
- No goal time is exactly on the chart. A static table lists round numbers (3:30, 3:35, …). If your goal is 3:32:17, you need the exact pace — the generator above computes it to the second.
- The chart assumes perfectly even pacing. Almost nobody runs a perfect even split. The generator lets you model a negative split (second half faster than the first), which is how most personal bests are actually run, and shows what each mile marker should read on your watch.
- Courses are not flat and watches are not perfect. The hill adjustment converts your goal pace into an effort pace for rolling courses, and the race-day tips below explain why you should target a few seconds per mile faster than the chart says (tangents and GPS error add real distance).
Worked example 1 — marathon goal 3:30:00, even pacing
Goal: finish a marathon in 3:30:00 (12,600 seconds) at an even pace.
- Pace per mile. 12,600 ÷ 26.2 = 480.9 seconds per mile =
8:01/mi. - Pace per kilometer. 12,600 ÷ 42.195 = 298.6 seconds per kilometer =
4:59/km. - Speed. 26.2 ÷ 3.5 =
7.49 mph(42.195 ÷ 3.5 =12.06 km/h). - Checkpoints. 5K: 5 × 298.6 = 1,493 s =
24:53. 10K:49:46. Halfway (13.1 mi): exactly half of 3:30:00 =1:45:00. 30K:2:29:18. - Pace band. At mile 10 your watch should read 10 × 480.9 = 4,809 s =
1:20:09. Print the band, tape it to your wrist, and glance at each mile marker instead of doing math mid-race.
Try it: select Marathon → Miles → goal time 3:30:00 → Even split, and the generator reproduces every number above.
Worked example 2 — half marathon goal 1:45:00, negative split + hills
Goal: finish a half marathon in 1:45:00 (6,300 seconds) with a 10 s/mile negative split, on a course with rolling hills (+3% effort).
- Average pace. 6,300 ÷ 13.1 = 480.9 s/mi =
8:01/mi(6,300 ÷ 21.0975 = 298.6 s/km =4:59/km). - Negative split. Second half 10 s/mi faster than the first: first-half pace = 480.9 + 5 =
8:06/mi, second-half pace = 480.9 − 5 =7:56/mi. Check: (6.55 × 485.9) + (6.55 × 475.9) = 6,300 s ✓. - What the watch reads. Mile 7 (first mile of the second half): 6 × 485.9 + 475.9 = 3,391 s =
56:31. Mile 10:1:20:19— ten seconds slower than the1:20:09an even split would show (you ran the first half conservatively; you make it up in the second half). - Hill adjustment. On a hilly course, hold the effort of your goal pace, not the number: 480.9 × 1.03 = 495.3 s/mi =
8:15/mieffort on the climbs, and let gravity pay you back on the descents.
Try it: select Half marathon → Miles → 1:45:00 → Negative split 10 → Hill +3%.
Even split vs negative split
An even split means every mile at the same pace. It is the simplest plan and the mathematically fastest if you can execute it — but it demands perfect discipline in the exciting first miles, when adrenaline makes goal pace feel easy.
A negative split means running the second half faster than the first (typically 5–15 seconds per mile faster in the second half for recreational runners). It is how the large majority of personal bests are run: you bank no time early, avoid the classic blow-up at mile 20, and pass hundreds of fading runners late. The trade-off is that you must be willing to feel "too slow" for the first half of the race.
Practical rule of thumb: if this is your first marathon at a goal time, plan a slight negative split (5–10 s/mi). If you are an experienced racer chasing a PR on a flat course, an even split executed with discipline is theoretically optimal.
Adjusting for hills and course difficulty
Pace charts assume a flat course. On a hilly course, the same finish time costs more effort. The hill adjustment in the generator converts your goal pace into an effort pace: a +3% setting means "run the uphills at the effort of a pace 3% slower than goal, recover on the downhills." This keeps your physiological output constant instead of your watch pace — which is what actually determines whether you blow up.
As a rough guide: gently rolling courses ≈ +1–2%, distinctly hilly courses (e.g. Boston's Newton hills) ≈ +3–5%. Beyond that, pick a flatter race or a more conservative goal time.
Race-day pacing tips
- Run the tangents. 26.2 miles is measured on the shortest legal route. Weaving around other runners and taking wide corners routinely adds 0.2–0.4 miles — at 8:01 pace that is 2–3 extra minutes. Target each mile 3–5 seconds faster than chart pace as insurance.
- Start 10–15 seconds per mile slower than goal pace for the first 2–3 miles. Crowds, adrenaline, and cold legs make the start the easiest place to ruin a race.
- Trust the band, not the crowd. When a pack surges past you at mile 8, check your wristband split. If you are on your numbers, let them go — you will likely see them again at mile 22.
- Practice goal pace in training. A chart tells you the number; only rehearsal teaches your legs what it feels like. Include miles at goal pace inside your long runs.
- Recompute if conditions change. Heat, wind, and illness all raise the cost of a given pace. It is smarter to adjust the goal time in the generator the night before than to chase an unrealistic band.
Looking for something else?
Boundary — this tool vs our other running tools (each serves a different intent):
- Predicting your finish time from a recent race? That is a race time predictor, not a pace chart — use our running pace predictor (Riegel / Cameron / VDOT models, predicts marathon time from a 5K or 10K).
- 5K-specific pacing? See our 5K pace chart — goal times and splits tuned for the 5K distance.
- Converting treadmill speed to pace? See our treadmill pace chart — mph/km/h to min/mi and min/km, incline adjustments, and belt calibration.
- Swim pacing? See our swim pace lab (CSS-based swim pacing).
Frequently asked questions
What is a marathon pace chart?
A marathon pace chart maps goal finish times to the average pace per mile and per kilometer required to achieve them. For example, a 3:30:00 marathon requires averaging 8:01 per mile (4:59 per kilometer) across all 26.2 miles. Use the generator above for any exact goal time, or browse the static marathon and half marathon charts for common targets.
How do I find my goal pace for a target finish time?
Divide your goal time in seconds by the race distance. For a 3:30:00 marathon: 12,600 seconds divided by 26.2 miles equals 480.9 seconds per mile, which is 8:01/mi; divided by 42.195 km equals 298.6 seconds per kilometer, which is 4:59/km. The generator on this page does this instantly and also builds the full per-mile split table for your race.
Does this page include a half marathon pace chart?
Yes. The Half Marathon Chart tab covers 13.1 miles (21.0975 km) for goal times from 1:00:00 to 3:00:00, and the pace band generator handles both distances. For example, a sub-2:00 half marathon requires 9:10 per mile (5:41 per kilometer).
What pace do I need for a sub-3:00 marathon? What about sub-4:00?
A sub-3:00 marathon requires 6:52 per mile (4:16 per kilometer): 10,800 seconds divided by 26.2 miles. A sub-4:00 marathon requires 9:10 per mile (5:41 per kilometer). Both rows are highlighted in the static marathon chart above.
What is a pace band, and how do I print one?
A pace band is a small table of cumulative split times showing what your watch should read at each mile or kilometer marker. Enter your goal in the generator, click Calculate pace band, then Print wristband. The print stylesheet produces a clean black-on-white band you can cut out and tape to your wrist or forearm.
Should I run even splits or negative splits?
A negative split, running the second half faster than the first, is how most personal bests are run, because it avoids the classic late-race blow-up. Example: a 1:45:00 half marathon with a 10 s/mile negative split means 8:06/mi for the first half and 7:56/mi for the second, still averaging 8:01/mi. For a first marathon at a goal time, a slight negative split of 5 to 10 s/mi is the safest plan.
How do I adjust my pace for a hilly course?
Convert goal pace into effort pace: multiply by (1 + hill percent / 100). At +3% on an 8:01/mi goal, run the climbs at 8:15/mi effort and let gravity pay you back on the descents, keeping your physiological output constant instead of your watch pace.
Why does my GPS show more than 26.2 miles on race day?
The 26.2-mile distance is measured on the shortest legal route, the tangents. Weaving around runners, taking wide corners, and GPS error routinely add 0.2 to 0.4 miles, which is 2 to 3 extra minutes at 8:01 pace. Target each mile 3 to 5 seconds faster than chart pace as insurance.
How is this different from a running pace predictor?
A pace predictor estimates what you can run based on a recent race, for example predicting your marathon time from a 10K. This chart does the reverse: given the finish time you want, it tells you the exact pace you must hold, split by split. For predictions, use our running pace predictor tool.
Can I use this chart on a treadmill or for a 5K?
This page covers road racing at the marathon and half marathon distances. For treadmill speed-to-pace conversion with mph, km/h, and incline adjustments, use our treadmill pace chart. For 5K-specific goal times and splits, see our 5K pace chart.
How accurate are the split times?
Splits are exact averages, goal seconds divided by distance, rounded to the nearest second for display. Rounding can make a displayed marker differ by one second from the exact value; the underlying math is exact.
Is this medical advice?
No. This tool provides general fitness and pacing information for recreational runners only. It is not medical advice, not a training plan, and not a substitute for a qualified coach or healthcare professional. Consult your doctor before beginning marathon training, especially if you have a heart condition.