5K pace chart: what each pace actually gets you.

What a 5K pace chart is actually for

Most runners look up a 5K pace chart hoping the number will answer a question the number cannot answer. The chart tells you what pace produces what finish time. It does not tell you which finish time your fitness can produce. Those are two different problems, and mixing them up is how race day gets ugly.

A good pace chart does two things well. It converts a target finish time into a per-mile and per-kilometer pace so you know exactly what to hold from the start line. And it gives you the pace you need to hit during workouts if you want that finish time to be realistic on race day. That is it. It is a lookup table, not a training plan and not a fitness test.

Quick math for anyone who wants it. A 5K is 5 kilometers, which is 3.10686 miles. To convert a finish time to a per-mile pace, divide by 3.10686. To convert to a per-kilometer pace, divide by 5. Bookmark the chart below anyway, because nobody wants to do decimals in a warmup.

The 5K pace chart

Finish times from 15:00 (a sub-elite range) down to 40:00 (a strong first-timer), with the pace you need to hold per mile and per kilometer. The right column notes which broader training pace that speed corresponds to, so a runner using VDOT-based pacing can see the training context at a glance.

One more useful reference. The 5K covers exactly 12.5 laps of a standard 400-meter track. If you train by lap splits, multiply the per-kilometer pace by 0.4 to get a 400-meter split. A 20:00 5K (4:00 per km) is 96 seconds per lap. A 25:00 5K (5:00 per km) is 120 seconds per lap. That is your track-workout target when goal race pace is the prescribed intensity.

How to pick your goal pace, not your fantasy pace

In 15 years of coaching, this is the section that separates the runners who PR from the runners who blow up at mile two. About 6 out of 10 first-time 5K racers I work with pick a goal pace that is roughly 15 to 25 seconds per mile faster than their fitness supports. They do not do it because they are arrogant. They do it because a chart makes 21:00 look as reachable as 22:00, when in fact only one of the two is honest.

The rule I use with athletes is this. Your goal 5K pace is the pace you can hold for one continuous mile in a workout with about 30 seconds of pain still in reserve at the end. Not the pace you can hit for 400 meters and call good. A mile at goal race pace with a little left over is the closest single indicator that the pace is real.

Two better inputs if you have them. A recent race, ideally within the last eight weeks, run into a chart like the VDOT tables gives you a full set of equivalent paces. Or a hard workout of 5 x 1000 meters at threshold effort with 90 seconds jog rest, averaged, sits about 15 to 20 seconds per mile slower than your current 5K pace. Add those numbers back and you have a defensible goal.

What the chart cannot do is judge your week. Fitness on Tuesday and fitness on race Saturday are related but not identical. If you slept 5 hours the two nights before, the 21:00 pace becomes a 21:45 pace no matter what the paper says.

The mile-by-mile plan on race day

Once the goal pace is honest, the race is an execution problem. The distribution of effort across three miles is what most amateurs get wrong. Even splits are the target, not negative splits. On a course this short, the runners who try to bank time in mile one almost always give it back plus interest in mile three.

Here is how the miles actually shake out for a well-executed 5K.

First 800 meters: five seconds slower than goal pace

Adrenaline will pull you 10 to 20 seconds per mile too fast for the first half kilometer. Fight it. Aim for 3 to 5 seconds per mile slower than goal pace for the first 800 meters, then settle in. This costs you almost nothing on the clock, because a controlled opening lets you actually hold pace when it hurts later.

Mile one to mile two: the honesty mile

By 1 kilometer in, you should be locked on goal pace. Breathing should be at about a 7 out of 10. If you are already at 9 out of 10 here, the pace is wrong. Back off 5 seconds per mile and race the version of you that actually turned up today. Adjusting early beats hanging on and cracking at 4K.

Mile two to mile three: the dark stretch

Somewhere around the 3-kilometer mark, the brain starts negotiating. Breathing is at 9 out of 10. Legs feel heavy. This is the section that decides your finish time. Do not check the watch every ten seconds. Pick a runner 30 meters ahead and slowly close the gap. Every fixed target beats every abstract negotiation with the pace number.

The last 400 meters: empty the tank

With 400 meters left, the goal shifts from "hold pace" to "spend everything left." A well-paced 5K should let you close the last quarter mile 5 to 10 seconds per mile faster than goal. If you can dead-sprint the last 200 meters, you paced it right. If you cannot lift the pace at all, you went out too fast, and the split at mile one is where that call was made.

Three paces most 5K runners misuse

The chart above shows one number: goal 5K pace. A training week uses at least three different paces, and blurring them together is the most common training error I see across the intermediate runners I coach.

1. Easy pace, run too fast

The most expensive mistake in 5K training is running easy days at moderate pace. It feels productive. It is not. Easy days too fast leave the legs flat for the two sessions that actually build 5K speed, and about 7 out of 10 stalled 5K runners I audit are guilty of it. The full argument on easy pace goes into the physiology; the short version is that easy pace is 90 to 120 seconds per mile slower than 5K pace for most runners, not 30.

2. Threshold pace, confused with 5K pace

Threshold pace is roughly 15 to 20 seconds per mile slower than 5K pace, and it is where a huge portion of your 5K fitness actually gets built. Running your tempo repeats at 5K pace by accident turns them into VO2 max intervals that break down after two reps. Slow them 15 seconds per mile and you can hold the effort long enough to raise your lactate threshold, which is what pushes your 5K time down for the next block.

3. Race pace as a fantasy, not a rehearsal

Goal 5K pace should show up in workouts three to five times in the four weeks before the race. Not once. If your first repeat at goal pace is race day itself, you have no evidence you can hold it. A workout of 5 x 1000 meters at goal 5K pace with 2 minutes jog rest, four weeks out, tells you the truth about whether the number on the chart is your number.

Deriving your training paces from goal 5K pace

A pace chart earns its value in training, not just on race morning. Say your goal 5K is 22:00, which the chart puts at 7:05 per mile. Your other training paces derive from that: easy at 8:35 to 9:00, long-run at 8:10 to 8:35, threshold at 7:20 to 7:25, and mile-pace strides at 6:45. Those are the numbers a coach would set from a recent race. The chart cannot rewrite them as your fitness shifts, which is where the actual work of getting faster lives.

Three patterns to watch for on race day

Across the athletes I have coached through 5Ks, a few patterns show up over and over. They are natural overcorrections of a runner trying to do the right thing on a course too short to forgive an error.

1. The first-mile surge. Fresh legs plus adrenaline plus other runners flying past equals a first mile 15 seconds too fast. The rest of the race is a tax on that decision. Cap the first 800 meters at 3 to 5 seconds slower than goal, no matter what the field does.
2. The dead-legs excuse. If your legs feel heavy 90 seconds into a 5K, it is rarely fatigue. It is a warm-up that ended too early. Add 3 to 5 minutes of easy jogging with two or three 20-second pickups before the start.
3. Waiting for the last 200 meters to race. A well-run 5K is decided between kilometers 3 and 4, not in the finish chute. That section is where you commit. The finish sprint is the finish, not the race.

What to do tomorrow

If you have a 5K on the calendar and you want the pace chart to actually help, here is the five-step protocol:

1. Run a benchmark this week. A hard mile time trial, or a workout of 5 x 1000 meters at threshold with 90 seconds jog rest. This is your fitness on paper.
2. Look up your goal pace. Take your benchmark, add or subtract from the chart above using the VDOT logic (a benchmark mile of 6:40 is roughly a 22:00 5K pace of 7:05). Write that pace down.
3. Rehearse the pace twice. Two workouts at goal 5K pace in the next four weeks. First one: 5 x 1000 meters at goal pace, 2 minutes jog rest. Second one: 3 x 1600 meters at goal pace, 2:30 rest. If both feel repeatable, the pace is honest.
4. Sharpen the last two weeks. Drop total volume by 20 to 30% in the final 10 to 14 days. Keep intensity. Sleep more. This is where a bad taper undoes a good block.
5. Race the plan. First 800 meters at goal pace minus 3 to 5 seconds per mile. Miles one and two locked on. Mile three, close the gap on the runner ahead. Last 400, empty the tank.

A chart cannot know your training block, your last race, or the two hours of sleep you lost this week. Those are the inputs a coach reads before setting your paces and rewriting them across a season. If you want that layer, that is what I do at RunFitCoach. Apply here or book a free intro call and we will build the week around the race that matters.

Pick a pace. Rehearse it. Run it.

Written by

Coach Johnny Crain

2:12 marathoner. 4× US Olympic Marathon Trials qualifier. 4× NCAA national champion and 4× NCAA runner-up. Spoke at the RRCA National Convention. Founder and head coach at RunFitCoach, where he coaches every athlete personally.