Runners who plan races in spreadsheets end up in one of two places. Either the spreadsheet is a personal masterpiece that took a year to build, or it is a broken formula they copied from a forum in 2019 that quietly rounds the wrong way. Free specialized calculators do the same math faster and with fewer subtle errors. Here are six that cover the full training cycle from base mileage through race day, and none of them require an account or a subscription.
Photo by RUN 4 FFWPU on Pexels
1. Riegel formula race predictor
The single most cited race prediction is the Riegel formula, which projects a longer race time from a shorter one using a power function. Any calculator that runs this formula honestly is useful. The version at EvvyTools exposes the exponent so you can adjust for a less trained aerobic base, which most default calculators do not do.
If your only tool is the default Riegel exponent, the marathon projection from a fast half PR will be optimistic by 8 to 15 minutes for a first-time marathoner. The ability to nudge the exponent from 1.06 to 1.08 or 1.10 is what makes the number honest.
2. Mile split table generator
A split table is a mile-by-mile plan for a race. Generating one by hand from an average pace works, but it does not handle the conservation of the first 5K, the maintenance of miles 4-16, or the honest miles 17-20. A tool that produces the full table for a specific goal time, in your chosen units, and lets you export it to a wristband-sized print is worth more than the 30 minutes of arithmetic it saves.
The EvvyTools split output is one option. Another is the built-in split table view on the Runner's World site, which has the advantage of years of iteration but the disadvantage of requiring a slightly slower workflow to print. Either works for a first marathon.
3. Pace conversion between units
If you train in kilometers and race in a mile-based country, or vice versa, you need a fast conversion tool. Not because the math is hard, but because eyeballing 5:00 per kilometer as 8:03 per mile at 6 AM on race day is where errors happen.
The Wikipedia entry on pace has the underlying formulas. Any calculator that does both directions cleanly is fine. The one at EvvyTools supports both units in the same interface and shows the split table in whichever unit you chose, which is what actually matters at the starting line.
4. Race pace by heart rate zone
For runners training with heart rate zones (the classic Zone 2 through Zone 5 model), a calculator that translates race distance into a target zone is useful for calibrating effort in training. The reference on the underlying model is in the Wikipedia entry on VO2 max and the derivative Karvonen heart rate reserve formula. A marathon is typically raced at the top of Zone 3 or the bottom of Zone 4 for most runners, which is significantly below the pace runners naturally drift toward when they feel fresh.
Any calculator that produces target HR ranges from a max HR input is useful for verifying that your goal race pace lines up with your aerobic ceiling. If the target HR for your goal pace is above your lactate threshold, the goal pace is not physiologically sustainable and needs to come down.
5. Cumulative training load and taper predictor
Not every training decision is about race day. The intermediate decisions in weeks 4 through 8 of a training block, when mileage should peak and taper should begin, benefit from a tool that shows the aggregate load curve. Free training load calculators, of which several exist in the community, help visualize when to back off and when to push.
The exact calculator matters less than the discipline of updating it weekly. A number that gets checked once produces the same insight as no calculator at all. A number that gets updated every Sunday produces the taper timing that most self-coached runners get wrong.
6. Race day pace band generator
The last calculator in this list is the smallest and most useful. A pace band is a paper wristband with target elapsed times printed for each mile marker. On race day, you glance at your watch at each mile, compare to the band, and know instantly whether you are on plan.
Most runners produce these ad-hoc from a spreadsheet. A calculator that outputs a print-ready pace band, sized for your goal time and adjusted for course profile if the tool supports it, is a small piece of paper that makes a large tactical difference. The tools directory at EvvyTools is worth browsing for the exact outputs you need for a specific race.
Photo by Jean Marc Bonnel on Pexels
The pattern across all six
The six tools have one thing in common. Each one replaces a spreadsheet formula with a purpose-built interface that handles the common edge cases (rounding, unit conversion, elevation adjustment) without asking the runner to think about them. The runner spends the training block on running, not on debugging their calculator.
None of these tools is complicated. The distinction is that they are set up correctly out of the box. A spreadsheet you built in 2019 has whatever assumptions you made in 2019, whether or not you remember them. A tool from a maintained source has current assumptions and gets corrected when the underlying formulas evolve.
The companion guide on marathon pacing explains how to translate these calculator outputs into an actual race plan, and the general EvvyTools blog covers the training-side questions that determine whether the race plan is defensible in the first place.
Why free calculators beat paid apps for most runners
The paid running apps that dominate the market bundle calculators with training plan generation, workout logging, and social features. For runners who want all of that in one place, they are worth the money. For runners who already have a training plan and just need pace math on race week, they are overkill.
A dedicated free calculator opens in 200 milliseconds, produces the output you need, and gets out of the way. It does not require an account, does not push notifications, and does not ask for your credit card. The tradeoff is that it does not know anything about your training history. If you have that history in a separate log (a paper training journal, a spreadsheet, or an app you already use for logging), the calculator on race week just needs to do the arithmetic.
For most self-coached runners, the split is: use whatever you already use for logging your training, and use a fast standalone calculator for race week pace math. Merging both into one paid tool is a preference, not a requirement.
What to test in the last two weeks
Two weeks before your marathon, run a final calibration of every tool you plan to use on race day. Cross-check the split table output against your goal time. Confirm the pace units match what your watch will report. Print the pace band if you plan to wear one, and verify the times are legible. This is a 15-minute exercise that catches misconfigured settings before race morning, which is not the time to discover them.
The final tactical rule is worth repeating: use two independent calculators and cross-check the results. If two tools produce the same split table, you have a plan. If they disagree by more than a few seconds a mile, one of them is misconfigured and it is worth finding out which before race day, not after.
Top comments (0)