How to Find Your Marathon Pace (Without Guessing)
A good marathon pace is not a wish. It is a number that comes from recent fitness, gets tested in long runs, and respects the conditions on the day.
The most common marathon mistake is picking a pace from hope rather than evidence, then watching it fall apart after 30 km. A realistic marathon pace is findable, but it has to come from current fitness and be tested in training, not chosen because it sounds good or matches a friend's time.
Disclosure: The Running Genie is the app behind this site. The method below is standard pacing practice. No calculator or app can guarantee a time; the marathon always has the final say.
1. Start from a recent race result
The most reliable starting point is a recent, well-run race at a shorter distance, ideally a half marathon, but a 10K or even a 5K works. Feeding that result into a calculator gives an estimated equivalent marathon time and pace. This is exactly what performance-based methods like VDOT do, explained in the VDOT explainer, and you can run the numbers with the VDOT calculator or the race time predictor.
2. Treat the prediction as a ceiling, not a promise
Here is the honest part most pace charts skip: race predictors assume the endurance to hold the effort for the full distance. They extrapolate from shorter races, where endurance is less of a limiter. If long-run training has been light, the real marathon will be slower than the prediction. The accuracy and limits of these tools are covered in race time predictor accuracy. For a first marathon especially, it is wise to aim a notch more conservative than the number.
3. Validate the pace in training
A predicted pace only becomes a real goal pace once long runs confirm it. The key tests are long runs that include segments at goal marathon pace, ideally feeling controlled rather than maximal. If marathon-pace segments late in a long run feel sustainable, the target is realistic. If they fall apart, the goal pace, the training, or both need adjusting. The training framework is in building a marathon plan.
4. Adjust for the day
- Heat and humidity: both slow sustainable pace; set a more conservative target and pace by effort early.
- Hills and wind: a hilly or windy course is not a flat-course pace; plan by effort, not just the watch.
- Altitude and fatigue: both reduce the pace the body can hold on the day.
A pace chosen in ideal conditions is a starting assumption, not a contract. Smart marathoners hold a little back early and let the second half decide, which is the surest defense against hitting the wall.
5. Put it together on race day
The finished plan is simple: a goal pace grounded in recent fitness, validated in long runs, and adjusted for conditions, then executed with even or slightly negative splits. The detailed execution side is in how to pace a marathon. The number is only as good as the honesty behind it.
6. Where The Running Genie fits
The Running Genie is built to take the guessing out of this. It sets pace targets from a runner's real data rather than a hopeful guess, and it builds the long-run endurance that decides whether a marathon pace actually holds. The aim is a goal pace that training has earned, not one borrowed from a chart.
The Running Genie sets marathon pace targets from your real running data and builds the long-run endurance to hold them. Free to download, with Strava, Garmin, Polar, Suunto, Apple Health, Health Connect, and file-upload paths depending on platform and device.
Find your marathon pace from fitness, prove it in long runs, and respect the conditions. A pace you have earned is one you can hold.
Predict the ceiling. Train the floor. Race the day in front of you.