FREE MAGIC MILE CALCULATOR: PREDICT YOUR 5K TO MARATHON RACE PACE

The Magic Mile calculator is a race pace prediction tool developed by Jeff Galloway — a 1972 US Olympic marathon runner and one of the world’s most widely-followed distance running coaches. You run exactly one mile at your hardest sustainable effort (a time trial), then enter your time. The calculator applies Galloway’s proven multipliers to instantly predict your predicted race pace and finish time for 5K, 10K, 10 miles, half marathon, and marathon. Galloway developed the formula after working with over 300,000 runners across more than 40 years of coaching, analysing actual race finish times vs training pace data.

The Magic Mile is highly accurate for runners who: (1) run the time trial at a genuinely hard, sustained effort, (2) have been training consistently for at least 4–6 weeks, (3) run on a measured, flat course, (4) run in temperatures below 60°F / 15°C. Accuracy decreases significantly if the trial is run on a hot day, on a hilly course, after insufficient warm-up, at an inconsistent effort (starting too fast or too slow), or without adequate training base. For marathon prediction specifically, runners with higher weekly mileage (40+ miles/week) tend to perform closer to their predicted time than lower-volume runners, for whom the prediction may be slightly optimistic.

All formulas use the Magic Mile pace in minutes per mile (MM) as the base:

• 5K pace = MM + 33 seconds per mile
• 10K pace = MM × 1.15
• 10-mile pace = MM × 1.175
• Half marathon pace = MM × 1.2
• Marathon pace = MM × 1.3

To convert any per-mile pace to per-kilometre pace, divide the per-mile seconds value by 1.60934. For the half-mile conversion: multiply half-mile time by 2 and add 18 seconds.

The larger jump from half marathon (1.2×) to marathon (1.3×) reflects the dramatic physiological difference between the two distances. The marathon requires a substantially higher aerobic base and significantly greater glycogen management. At approximately miles 18–22, most runners experience glycogen depletion (“hitting the wall”), which forces pace to slow substantially. The marathon multiplier accounts for this natural fade — it is not a pessimistic estimate, but a realistic reflection of what recreational-to-intermediate runners experience when glycogen stores run low. Elite marathon runners, who are fat-adapted and glycogen-efficient from extremely high training volumes, often exceed the Magic Mile marathon prediction.

Jeff Galloway recommends running a Magic Mile every 2–3 weeks during a training cycle. Each new result reflects your current fitness level and allows you to update your training paces accordingly. Running it more frequently (weekly) is unnecessary and counterproductive — the effort required for an accurate Magic Mile is significant and needs recovery time. Always run the Magic Mile under comparable conditions: same time of day, similar temperature range, same course if possible, to make comparisons meaningful. Track your results over the training cycle to monitor fitness progress.

Yes — and this is one of the most useful Magic Mile applications. For the 5K, Galloway’s formula adds only 33 seconds per mile to the Magic Mile time, making it the most accurate distance prediction because the pace difference between a 1-mile effort and a 5K effort is relatively small. The 5K pace prediction assumes you are running a proper 5K race with appropriate warm-up and race conditions. For a solo 5K time trial on a training run, add an additional 5–10 seconds per mile to the predicted pace as a conservative starting point, since solo efforts without race-day adrenaline and crowd support tend to run 1–3% slower than race predictions.

The best location is a standard 400-metre athletics track — 4 laps equals exactly 1 mile (technically 1609.3m). A track eliminates GPS drift, is completely flat, has no traffic or turn delays, and provides the most reproducible results for tracking progress over time. If a track is unavailable, a flat, straight measured road segment or a running path with confirmed GPS distance is the next best option. Avoid hilly routes — even modest elevation affects pace enough to skew the prediction. Avoid routes with sharp turns, traffic stops, or surface changes (pavement to gravel mid-run).

No — the Magic Mile is not an all-out sprint. The correct effort is the fastest pace you can sustain for the entire mile without significant slowdown in the second half. On a perceived effort scale of 1–10, aim for approximately 8.5–9. You should be breathing hard and unable to speak in sentences, but not gasping or feeling like you will collapse. The most common error is starting too fast (first 400m at sprint pace) and dramatically slowing the final 400m — this produces a slower overall time and less accurate prediction. Aim for even splits or a slight negative split (second half marginally faster than first half).

Yes — significantly. Jeff Galloway states that the formula’s accuracy decreases when run in temperatures above 60°F (15°C). Heat increases cardiovascular strain, reduces the pace achievable at a given effort level, and affects heat dissipation. As a rule of thumb, for every 5°F (2.8°C) above 60°F, a runner’s sustainable pace slows approximately 20–30 seconds per mile. If you must run your Magic Mile in warm conditions, use the half-mile conversion option instead (shorter duration = less heat impact) or wait for cooler weather for the most accurate full-mile reading.

Yes, with two adjustments: (1) Set the treadmill to a 1% incline — research shows 1% gradient on a treadmill approximates the energy cost of outdoor running by compensating for the lack of air resistance. Running on 0% incline on a treadmill is measurably easier than outdoor running at the same speed. (2) Be aware that treadmill pace is mechanically controlled — it removes the natural variation of outdoor running and may produce a slightly faster time than an equivalent outdoor effort. For most runners, a treadmill Magic Mile (at 1% incline) is a valid and comparable measurement to an outdoor track result.

Absolutely not. Jeff Galloway himself uses run-walk intervals in his own ultra-distance running, and many experienced marathon runners — including Boston Qualifiers — use it strategically. Research published in various sports science journals shows that planned walk breaks: reduce blood lactate accumulation, lower core body temperature, allow muscle glycogen partial recovery, and result in faster marathon finish times for the majority of recreational runners (sub-4:30 marathon range) compared to continuous running. The psychological benefit is also significant — walk breaks reduce the mental weight of “running 26.2 miles” into a series of manageable run intervals.

Your Magic Mile pace per mile is the primary indicator: faster pace = longer run intervals, shorter walk breaks. Use the Run-Walk table in section 05 as your guide. Key principle: the run interval should feel comfortable — not hard. You should be able to maintain your run interval without breathing hard. If your run interval feels like a sustained effort, either shorten the run interval, extend the walk interval, or both. The goal is to arrive at mile 20 of a marathon still feeling controlled — not to maximise running time and blow up in the final 10K.

For most recreational runners — no. In fact, the opposite is often true. Runners who use planned walk breaks in a half marathon or marathon frequently finish faster than their continuous-running equivalent because they avoid the dramatic pace fade in the final miles caused by glycogen depletion and accumulated fatigue. The walk pace is slower than running pace, but the running pace during run intervals is maintainable at a higher level throughout the entire race. Studies and Galloway’s own data show that most runners attempting their first or second marathon finish faster using a run-walk strategy than attempting continuous running. The break-even point (where continuous running becomes faster than run-walk) is typically at a sub-3:30 marathon pace for most runners.

Running all or most training miles at or near race pace is one of the most common causes of running injury and overtraining. When you train at race pace repeatedly, you accumulate fatigue faster than you recover, glycogen stores are chronically depleted, and connective tissue (tendons, ligaments) does not get adequate recovery time. Galloway’s research shows that the majority of running adaptations — improved mitochondrial density, capillary development, fat oxidation efficiency — occur at easy, aerobic pace. Race pace is for racing. Training at 60–75% effort builds the aerobic engine that allows you to race at race pace on specific occasions without breaking down.

After calculating your Magic Mile result:

• Easy/daily run pace: Marathon predicted pace + 90 seconds to 2 minutes per mile
• Long run pace: Marathon predicted pace + 60–90 seconds per mile (use run-walk intervals)
• Magic Mile training pace: Magic Mile time + 2 minutes per mile (Galloway’s standard training pace)
• Tempo runs: 10K predicted pace (once per week, 20–40 min)
• Intervals: 5K predicted pace for 400–800m repeats (once per week, well-rested)

Never do more than 2 hard workouts (tempo + intervals) per week. All other running should be at easy pace or the Magic Mile +2 min training pace.

Several factors can cause underperformance vs the Magic Mile prediction: (1) Insufficient training mileage — the marathon multiplier (1.3×) assumes adequate long-run training; runners averaging under 30 miles/week typically run slower than predicted. (2) Hot race day — temperatures above 60°F (15°C) significantly slow marathon times. (3) Starting too fast — going out at 4-hour pace when your body is truly a 4:15 runner leads to a blow-up after mile 18. (4) Fuelling errors — inadequate glycogen loading or mid-race nutrition. (5) The Magic Mile was run on a favourable day (cool, rested, well-warmed-up) that did not reflect race day conditions. The prediction is a ceiling — race execution must match the training to achieve it.

No. All calculations run entirely in your browser using JavaScript. Your Magic Mile time, predicted paces, and all results are processed locally on your device — nothing is transmitted to any server, stored in any database, or shared with any third party. The calculator collects zero user data. You can use it entirely offline once the page has loaded.

Yes — toggle to min/km using the unit selector at the top of the calculator. All race paces and training paces are automatically converted and displayed in minutes per kilometre. The underlying formulas are calculated in miles (Galloway’s original system) and converted with full precision — there is no rounding error from the conversion. Finish times are the same regardless of unit selection; only the pace display format changes.

Jeff Galloway’s half-mile conversion formula allows runners who cannot complete a full-mile time trial to still get a Magic Mile equivalent result. Use it if: you are returning from injury, conditions are hot (above 60°F / 15°C), or you are a new runner building up distance. Run a hard half-mile time trial, enter your time, and tick the half-mile checkbox. The calculator automatically applies the Galloway conversion: (Half-Mile Time × 2) + 18 seconds = Magic Mile Equivalent. Example: a 5:05 half-mile converts to a 10:28 Magic Mile. The resulting predictions will be slightly less precise than a full-mile trial but are a valid starting estimate.