Marathon Pace Calculator Online — Free Marathon Pace Calculator Tool

CodexFuse Team · 2026-11-01T13:04:55.463Z · 10 min read min read

Work out the exact pace per km and per mile for your marathon goal time, with a worked 4-hour example, splits, and honest limits.

A marathon pace calculator turns one target — your goal finish time — into the steady pace you must hold for 42.195 kilometres. Enter the time, and it returns your pace per kilometre, your pace per mile, and your average speed, so training stops being guesswork.

That single number matters because marathons are rarely lost in the first 10 kilometres. They are lost when a runner starts 15 seconds per kilometre too fast, feels strong for an hour, and then pays for it from kilometre 30 onwards.

What does a marathon pace calculator actually tell you?

A marathon pace calculator divides your goal time by the marathon distance to give the average pace you need across the whole race. It returns pace per kilometre and per mile plus average speed, which you can then use to set training paces, plan drink-station splits, and judge whether a goal time is realistic.

It does not predict your finish time from fitness, weather, hills, or race-day nerves. It works backwards: you choose the time, and it shows what that time demands, kilometre by kilometre.

The maths behind the pace, in plain language

The calculation itself is simple division, and knowing it helps you sanity-check any result. A marathon is 42.195 kilometres, or 26.219 miles. Divide your goal time in minutes by 42.195 for pace per kilometre, and by 26.219 for pace per mile.

Check the 4-hour row: 240 minutes divided by 42.195 gives 5.69 minutes per kilometre, or 5:41; divided by 26.219 miles it gives 9.15 minutes per mile, or 9:09.

A worked example: Sara's 4-hour marathon plan

Sara is a fictional club runner, aged 34, who has finished two half marathons in 1 hour 52 minutes and 1 hour 49 minutes. She wants to finish her first marathon in under 4 hours, and she has 16 weeks to train.

Her first step is not a training plan. It is a reality check. A 4-hour marathon needs 5:41 per kilometre for the full distance, and her half-marathon pace is around 5:19 to 5:32 per kilometre over half the distance. That gap is plausible but not comfortable, which tells her the goal is ambitious rather than fantasy.

She enters 4:00:00 into the marathon pace calculator and gets 5:41 per kilometre, 9:09 per mile, and 10.55 km/h. She then builds her checkpoint table from that pace, rather than trying to remember a single number mid-race.

The 30-kilometre checkpoint is the one Sara watches most closely. If she reaches it in 2:50:35, she is on target. If she reaches it in 2:44:00, she has gone out too fast, and the honest move is to slow down now rather than hope the last 12 kilometres will be kind.

For training, Sara does not run every session at 5:41 per kilometre. Her easy runs sit well slower, her long runs touch race pace only late, and one weekly session practises short stretches at 5:41 so the pace feels familiar.

How to use the CodexFuse marathon pace calculator

The CodexFuse marathon pace calculator keeps the process to three steps, as shown on the tool page itself. There are no extra fields for age, weight, or course profile to fill in, which is also why its result should be treated as a pace target, not a prediction.

1. Enter your target time: type the marathon finish time you are aiming for, in hours, minutes, and seconds.
2. Click calculate: the tool works out the pace from that single input.
3. Read your pace: note the pace per kilometre, the pace per mile, and the average speed, then write down the checkpoint times that matter to you.

One practical note from the tool page: it asks you to log in to use the tool, and a free account is offered to get started. If you only want a one-off number, the table above covers the most common goal times, but for an exact time such as 4:07:30, running it through the tool avoids rounding errors.

What this calculator will not do for you

Honest limits matter here, because a pace number looks more certain than it is. The calculator assumes perfectly even pacing on a flat course in neutral conditions. Real marathons are rarely any of those things.

• No hills or heat adjustment: a hilly or hot course will slow the same runner down, so a flat-course pace is a starting point, not a promise.
• No fatigue curve: it does not model how pace typically fades after kilometre 30, which is why even pacing, or a slight negative split, is safer than banking time early.
• No fitness assessment: it cannot tell you whether 4 hours, 4:30, or 5 hours fits your current training, so cross-check the pace against a recent half marathon or a long run.
• No race-day tactics: drink stations, crowds, wind, and toilet stops all cost seconds, so experienced runners build a small buffer into their plan rather than aiming at the exact second.

If the pace the calculator returns feels impossibly fast compared with your recent long runs, believe the long runs. Adjust the goal time until the pace matches what you can actually sustain, then train from there.

Turning a pace number into a training week

A pace target only helps if it changes how you train. The simplest structure is to keep most running easy, use one session a week to practise race pace in short blocks, and let the long run grow gradually.

For Sara, that means easy runs at a talking pace, well slower than 5:41 per kilometre, plus a midweek session such as 4 × 2 kilometres at 5:41 with easy jogging between efforts.

Two supporting tools make that week easier to manage. A heart-rate zone calculator helps keep easy runs genuinely easy, and an interval timer handles the work-and-rest blocks without staring at a watch. Fuel and recovery matter just as much: a macro calculator can give a starting point for daily nutrition, and a calories-burned calculator puts long-run energy needs in perspective.

Common pace mistakes that cost runners minutes

• Starting with the crowd: the first kilometres feel easy because of adrenaline and other runners, so check your watch at 1 km and 5 km, not just at halfway.
• Banking time early: running the first half faster than goal pace rarely survives the second half, and the time lost late is typically larger than the time gained early.
• Confusing miles and kilometres: 9:09 per mile and 5:41 per kilometre describe the same 4-hour marathon, but mixing them up mid-race is a costly error — pick one unit and stick to it.
• Ignoring the course profile: a pace that works on a flat course needs adjusting on hills, so study the elevation before race day and plan slower uphill kilometres.
• Chasing the exact second: aiming for 3:59:59 instead of “under 4 hours” changes nothing in training, but it can push a runner into an unsustainable early pace.

The fix for all five is the same: write down three checkpoints before the race, check them calmly, and adjust early.

Frequently Asked Questions

What pace do I need for a 4-hour marathon?

You need 5:41 per kilometre, or 9:09 per mile, at an average speed of 10.55 km/h. That means reaching halfway in 2:00:00 and 30 kilometres in about 2:50:35, assuming perfectly even pacing on a flat course.

Is a marathon exactly 42 kilometres?

No, it is 42.195 kilometres, or 26.219 miles. The extra 195 metres matter: at 5:41 per kilometre, that final stretch alone takes around 1 minute 6 seconds, which is why rounding the distance down gives a slightly optimistic pace.

Should I run even splits or a negative split?

Even pacing is the safest default for most runners, and a slight negative split — a second half a little faster than the first — is a sound ambition. Starting fast to “bank time” usually backfires, because fatigue in the final 12 kilometres costs more time than an early surplus saves.

Can a pace calculator predict my finish time?

Not on its own. A basic pace calculator works backwards from a goal time you choose; it does not measure your fitness. For a prediction, combine it with a recent half marathon or a long training run, and treat the result as an estimate, not a guarantee.

How do I convert pace per kilometre to pace per mile?

Multiply your pace per kilometre by 1.609 to get pace per mile, or divide pace per mile by 1.609 to go the other way. For example, 5:41 per kilometre multiplied by 1.609 gives 9:09 per mile, which is the same effort over a longer unit.

Is the CodexFuse marathon pace calculator free?

Yes, the tool page describes it as free with unlimited use, returning pace per kilometre, pace per mile, and speed. It does ask you to log in, with a free account offered to get started.

Your next step: run the number, then train to it

Do not leave your marathon goal as a vague hope. Open the marathon pace calculator, enter your goal time, and write down your pace per kilometre, your pace per mile, and your 10 km, halfway, and 30 km checkpoints today. Then build your next training week around that pace — easy runs easy, one race-pace session, and a long run that grows steadily.

If you run a coaching business or running club alongside your training, move your hosting, business email, and backups to CodexFuse — fully managed on pay-as-you-go credits, no subscriptions, no lock-ins. Get started today, run your pace number now, and train to a target you can actually hold.