The complete marathon pace chart below shows projected finish times for the marathon, half marathon, 10K, and 5K at every pace from 5:00/mi to 15:00/mi (with kilometer equivalents). Use the calculator tools to plan your race strategy, set realistic goals, and build a pacing plan you can trust on race day.
Every 15-second pace increment from 5:00/mi to 15:00/mi. Scroll to find your target pace or use the highlight feature to mark a specific row.
| Pace/mi | Pace/km | Marathon | Half Marathon | 10K | 5K |
|---|
Enter your target marathon finish time to calculate the required pace, or enter a pace to see your projected finish time across all distances.
Enter your target pace to generate projected elapsed times at each mile marker and 5K checkpoint. Print this page to carry your split sheet on race day.
Plan a negative split strategy where you run the second half faster than the first. Most marathon world records have been set with negative splits. Enter your target finish time and desired split percentage.
Enter your maximum heart rate to see your training and racing zones. If you don't know your max HR, a common estimate is 220 minus your age, though individual variation can be significant.
Based on your marathon goal pace, here are the recommended training paces for different workout types. Enter your target marathon pace to personalize these recommendations.
Compare your marathon performance against others in your age group using age-grading factors. This lets you see what your time would be equivalent to for an open-age runner, making cross-age-group comparisons fair.
The Boston Marathon requires runners to meet qualifying standards based on age and gender. Below are the official qualifying times along with the required pace per mile. Note that in recent years, a qualifying time alone hasn't guaranteed entry; cutoff times have been several minutes faster than the published standards.
| Age Group | Men | Men Pace/mi | Women | Women Pace/mi |
|---|
Source: Boston Athletic Association. Standards may require additional buffer (typically 5-7 minutes faster) due to field limits. Last verified March 2026.
Marathon pacing is simultaneously the simplest and most misunderstood aspect of distance running. The math is straightforward: pick a pace, multiply by 26.2 miles, and that's your finish time. But actually executing a consistent pace over 26.2 miles, while managing fatigue, weather, terrain, fueling, and the psychological demands of the distance, is where the real challenge lies. I've been running and tracking race pacing data for years, and the patterns I've observed in my own training and in watching thousands of race results are remarkably consistent.
A pace chart isn't just a reference table. It's a planning tool. When I this one, I wanted it to do more than what the laminated card from your local running store does. Those cards show you a grid of paces and finish times. That's fine. But what they don't show you is the context around each pace: what training zones correspond to it, what kind of weekly mileage typically supports it, or how a negative split strategy would change your mile-by-mile plan.
The difference between a 9:00/mile pace and a 9:15/mile pace is only 15 seconds per mile, but across a full marathon it adds up to about 6 minutes and 33 seconds. That's the difference between a 3:55 finish and a 4:02. For someone chasing a sub-4-hour marathon, understanding this granularity matters. It's why the chart above goes in 15-second increments rather than full-minute jumps.
The most common mistake in marathon running is starting too fast. Race-day adrenaline, crowd energy, and the feeling of fresh legs conspire to pull runners ahead of their planned pace in the first few miles. I tested this by analyzing finish-time data from several large marathons, and the pattern is stark: runners who go out 30+ seconds per mile faster than their average finishing pace are significantly more likely to experience dramatic slowdowns after mile 18.
The physiological reason is straightforward. Running above your aerobic threshold burns glycogen faster. Glycogen stores are finite, typically supporting about 90-120 minutes of hard running. Once glycogen is depleted, the body shifts to fat metabolism, which can't sustain the same pace. This is the infamous "wall" or "bonk" that marathon runners dread. Starting conservatively preserves glycogen for when you need it most, which is miles 20-26.
Sports science and race data both favor either even pacing or slight negative splits (running the second half slightly faster than the first). The argument for negative splits is practical: if you're running at a sustainable effort in the first half, slight fatigue in the later miles is offset by the motivation of knowing you have energy in reserve. The calculator on this page lets you plan a negative split of 1-5%, which translates to running the second half 10-30 seconds per mile faster than the first.
Most marathon world records have been set with roughly even splits or modest negative splits. Eliud Kipchoge's record-setting performances have consistently featured disciplined first halves followed by slightly faster second halves. That said, most recreational runners end up with positive splits (slower second half) due to starting too aggressively. If your goal is simply to run a smart race, even splits should be the target. Negative splits are the aspiration.
Pace per mile is an imperfect measure of effort because it doesn't account for heat, humidity, wind, elevation, or how you're feeling on race day. Heart rate offers a more physiologically honest signal. Most experienced marathoners race in Zone 3 (roughly 70-80% of max heart rate), starting in the lower portion and allowing heart rate to drift upward in the second half as fatigue accumulates.
I've found that combining pace targets with heart rate ceilings produces the best results. For example, if your target pace is 9:00/mi and your Zone 3 ceiling is 155 bpm, you would hold 9:00/mi as long as your heart rate stays below 155. If it creeps above 155 early in the race, that's a signal to slow down regardless of what your watch says about pace. This approach prevents the common scenario where a runner hits their pace target but is secretly overextending in the first half.
One of the most well-supported principles in distance running is that roughly 80% of training volume should be at easy effort (Zone 1-2), with only 20% at moderate-to-hard effort (Zone 3-5). This doesn't mean 80% of your runs are easy, it means 80% of total weekly mileage. Many runners make the mistake of running too hard on easy days and too easy on hard days, which leads to chronic fatigue and underwhelming race performances.
The training pace calculator on this page generates recommended paces for five workout types based on your marathon goal pace. Easy runs should feel genuinely comfortable, and you should be able to hold a conversation. Tempo runs should feel "comfortably hard," sustainable for about 30-40 minutes. Intervals are hard but not all-out. Marathon pace runs are the most race-specific workout, typically done as 8-14 miles at your target race pace.
After years of pacing my own marathons and helping others plan theirs, the single most impactful piece of advice I can offer is this: don't race the first half. Run the first half. Race the second half. The discipline required to hold back when you feel great at mile 3 is what separates a good marathon from a miserable one.
Practically, this means arriving at the start with a concrete plan. Know your target pace. Know your mile splits. Know what heart rate ceiling you won't exceed in the first 13 miles. Write it on your arm if you have to. The race environment is make you go faster than planned, with pacers, crowds, and downhill sections in the early miles. Your job is to resist that pull.
Fueling is inseparable from pacing. Most runners need 30-60 grams of carbohydrate per hour during a marathon. Practice this in training. Taking a gel or chews every 4-5 miles, starting at mile 4-5, is a common strategy. Don't wait until you're hungry or bonking to fuel, because by that point it's too late for the carbohydrates to be absorbed in time to help.
Weather adjustments are also critical. For every 10 degrees above 55 degrees Fahrenheit, expect to add about 1-3% to your finish time. On a hot day, a 4:00 marathon runner should adjust expectations to 4:05-4:12. It's better to slow down proactively in heat than to blow up at mile 20 trying to hold a pace your body can't sustain in those conditions.
Finish time increases linearly with pace. Each 1-minute increase adds approximately 26 minutes to finish time.
Tested and verified on Chrome, Firefox, Safari, and Edge. All calculations run entirely client-side.
| Browser | Desktop | Mobile |
|---|---|---|
| Chrome | 90+ | 90+ |
| Firefox | 88+ | 88+ |
| Safari | 15+ | 15+ |
| Edge | 90+ | 90+ |
| Opera | 76+ | 64+ |
Tested March 2026. Data sourced from caniuse.com.
Source: Wikipedia - Marathon · Wikipedia - Boston Marathon · Verified March 25, 2026
Source: Hacker News
I've spent a lot of time refining this marathon pace chart and the calculators that go with it. I it because the pace charts I found online were either incomplete, hard to read on mobile, or didn't include the split and negative-split planning tools that I actually needed when preparing for races. I tested every calculator against manual computations and verified the Boston qualifying times against the BAA's official standards. It doesn't require any account or app download, and it won't ever need one. Everything runs in your browser, and nothing leaves your device.
The Marathon Pace Chart is a free browser-based tool for runners of all levels. planning your first 5K, targeting a Boston qualifier, or coaching a team, it provides accurate pace projections, split tables, and training zone recommendations without downloads, signups, or ads.
by Michael Lip. All Marathon Pace Chart features run via client-side JavaScript. There is no server, no account system, and no way for your data to leave your device.
March 19, 2026
March 19, 2026 by Michael Lip
Update History
March 19, 2026 - First deployment with validated logic March 22, 2026 - Enhanced with FAQ content and meta tags March 24, 2026 - Improved color contrast and reduced DOM size
March 19, 2026
March 19, 2026 by Michael Lip
March 19, 2026
March 19, 2026 by Michael Lip
Last updated: March 19, 2026