Garmin PacePro (Pace Pro)

Home » Garmin Features » Performance » PacePro
Accuracy
Dependent on course file elevation quality
Best for
Hilly road races and trail events with a known course profile
Weakness
Fixed targets do not adapt to performance during the race
Plain English: PacePro tells a runner how fast to run each kilometre of a race, given the hills in that section, slower on steep climbs and faster on flat or downhill ground, so that the overall effort stays steady and the finish-time target is met.
In practice: the quality of the course file determines everything. A route can look correct on the map but contain a flawed elevation profile; Strava and other platforms have occasional inaccuracies over bridges, under tree cover, and near steep cliffs, all of which feed directly into wrong split targets. Road races are where PacePro earns its keep: in my experience, official course files tend to have clean elevation data, and the split targets hold up well across the distance. One behaviour worth knowing before race day: on courses with several short climbs and descents packed into each kilometre, switch to Elevation-Based splits, because kilometre-based averaging flattens out the terrain and the targets mislead on every split.

Quick answers

What does the Garmin PacePro screen show?
Garmin’s manual labels five fields on the PacePro screen: the target pace for the current split, the runner’s current split pace, a progress bar for the split, the distance remaining in the split, and the overall time ahead of or behind the target finish time. The overall figure is cumulative across every completed split, so a runner can be behind target pace on the current climb and still show ahead overall.


Which Garmin watches have PacePro?
Every current Garmin running watch, including the entry-level ones. The Forerunner 55, 165 and 170, Vivoactive 6, Venu 4 and Venu X1 and the Instinct 3 series all carry it in their owner’s manuals, alongside the Forerunner 265, 570, 965 and 970, Fenix, Enduro and Epix. The Venu 3 does not, and Edge cycling computers offer Power Guide instead. On-watch creation needs a course loaded first, but works on watches without maps, such as the Forerunner 165.


Does PacePro adjust the target pace during a run, or are the targets fixed?
Targets are fixed at strategy creation and remain static throughout the activity. Only the cumulative ahead/behind display updates in real time as the runner progresses through each split.


What is the difference between PacePro and Grade-Adjusted Pace?
PacePro sets a pre-calculated target pace for each split before the race begins, based on the segment’s average gradient. Grade-Adjusted Pace is a live data field that shows the flat-ground equivalent of the runner’s current effort in real time, using barometric altimeter data.


Can a PacePro plan be created from a previous activity?
Yes. Save the previous activity as a course in Garmin Connect, then use that course as the basis for a new PacePro strategy. The elevation profile from the original activity will be used to calculate the split targets.


What happens to PacePro guidance if the runner goes off course?
Route deviation corrupts the cumulative ahead/behind figure, but forward guidance recovers from the point the runner returns to the planned route. The time accumulated during the detour should be disregarded from that point onward.


PacePro – a deep dive

When PacePro Is Actually Useful

  • On a relatively flat half-marathon in 2024, PacePro handled my negative split planning perfectly: with a few taps, I had a set of split targets I could trust and actually execute on race day.
  • A trail race with a course diversion and a flawed elevation profile was a bad experience: the detour added roughly a minute I had not planned for (the plan recovered), and four kilometre-sections had targets that were materially wrong due to elevation data errors in the course file.
  • On hilly races, I now use Grade-Adjusted Pace (or power) as my real-time effort signal rather than following PacePro targets, because even with Elevation-Based splits enabled, numerous short climbs and descents within each segment are not properly accounted for.

Garmin PacePro (Pace Pro) is a race pacing tool that divides a course into individual splits and assigns a target pace to each one, adjusted for the average gradient of that segment, so that a runner expends roughly equal effort across varied terrain rather than equal time per kilometre on flat and hilly sections alike. Garmin’s own description is plainer: “The PacePro feature allows you to create a custom pace band based on distance and pace or distance and time. You can also create a pace band for a known course to optimize your pace effort based on elevation changes.” The runner provides a target finish time and a split preference, positive, negative or even, and the feature uses the elevation profile from a loaded course to derive a different target pace for each segment. The PacePro Plan is then displayed on the watch during the activity, showing the target pace for the current split, the runner’s actual pace, and the cumulative gap relative to the plan.

PacePro requires an accurate course file to function as intended. Where the course profile differs materially from the actual race route, whether through errors in the source file, course changes or route deviations, the split targets will be calculated against the wrong gradients, rendering guidance unreliable.

What the PacePro Metrics Actually Mean

Garmin PacePro strategy view showing split target pace, current pace, and ahead/behind gap during an outdoor run

Each split target represents the pace at which the runner should complete that segment in order to stay on track for the goal finish time. The pace varies between splits because equal physical effort produces different speeds across different gradients. The cumulative ahead/behind figure shown during the activity is a running total of time gained or lost across all completed splits plus the current split to date, not a snapshot of current versus target pace. The split-level target pace is the more actionable figure for moment-to-moment execution.

When PacePro is created without a specific course, using only a target race distance and goal time, all splits receive the same flat target pace because gradient data is absent. The uphill effort slider is absent in this mode.

How Garmin calculates PacePro

A PacePro Plan is built in Garmin Connect, or on the watch from a loaded course, and synced before the activity begins. Stated: Garmin says the plan is a pace band built from distance and pace or distance and time, and that for a known course it optimises pace effort for the elevation changes, with the splits and elevation plot available to preview. Inferred: Garmin Connect reads the course’s elevation profile, calculates the average gradient of each split, and converts the flat-equivalent target pace into a gradient-adjusted target using a running-economy-at-gradient relationship of the kind Minetti and colleagues measured, because that is the only published basis for such a conversion and the targets behave as that relationship predicts. Unknown: the exact cost-of-gradient curve Garmin uses, how the uphill effort slider reweights it, and how the positive or negative split preference is distributed across the course; Garmin publishes none of these.

Three split options are available: Every Kilometre, Every Mile, and Elevation-Based. The first two use fixed distances and average the gradient across each full segment; Elevation-Based instead creates splits at hill-start points, avoiding gradient averaging but producing uneven split distances. Two further sliders control uphill effort weighting and the preference for an overall positive or negative split. On the watch the plan can be started only from an outdoor running activity.

What affects the PacePro reading

Course file accuracy is the primary variable. Where the elevation profile is incorrect, gradient adjustments will be wrong, and targets will misrepresent the terrain’s actual demand. Fixed-distance splits average the gradient over each full kilometre or mile, so a climb and descent within the same split produce a target that understates the required effort on the climb; Elevation-Based splits avoid this at the cost of uneven split distances. Route deviation corrupts the cumulative ahead/behind figure, but forward guidance recovers from the point the runner returns to the planned route.

How accurate is Garmin PacePro

The relevant accuracy question is whether, when followed, split targets produce an evenly distributed effort across the course. This depends on the accuracy of the elevation data in the course file and the validity of the grade-adjusted calculation. The grade-adjusted effort model draws on research by Minetti et al. (2002), who measured the metabolic cost of running on gradients from minus 45 to plus 45 per cent and established the non-linear relationship between gradient and energy expenditure that grade-correction models use. The model is well validated for the moderate gradients of road and trail races; above roughly 25 to 30 per cent, runners typically transition to hiking, and the model’s predictions become less reliable because it assumes continuous running mechanics. Whether Garmin’s targets follow Minetti’s curve exactly is unknown, as noted above.

Competitor equivalents

  • Polar Race Pace sets a flat, even-pace target for a given distance and goal time with no grade adjustment; it is functionally closer to a pace band than a course-based strategy.
  • Suunto Race Pacer, available as a third-party SuuntoPlus app, supports flat, even-pace and negative-split targets by distance or time but has no grade adjustment.
  • Apple Pacer, introduced in watchOS 9, sets a flat target pace for a distance and goal time with no grade adjustment; Apple’s Race Route feature allows racing a previous effort on a repeated course, but is a ghost function rather than a pre-planned strategy.
  • Coros has no pre-planned grade-adjusted pacing strategy; its Effort Pace is a live grade-adjusted pace, the counterpart of Garmin’s Grade-Adjusted Pace rather than of PacePro. The COROS Pace Pro is a watch model name, not a pacing function.
  • Wahoo has no equivalent grade-adjusted course pacing feature.

Which Garmin devices support PacePro

Garmin introduced PacePro in August 2019 on the Fenix 6 series, and it has since spread to every current Garmin running watch. The owner’s manuals for the Fenix 8 and 9 series, Enduro 3 and 4, Epix Gen 2, Forerunner 970, 965, 570, 265, 170, 165, 70 and 55, Venu 4 and Venu X1, Vivoactive 6 and the Instinct 3 series all include it; the Venu 3 does not, and Edge cycling computers carry Power Guide, a power-based equivalent, instead of PacePro. The elevation profile always comes from the course: a course drawn in Garmin Connect takes its elevation from Garmin’s map data, and an imported GPX file carries whatever elevation its source recorded, which is where most bad targets begin. Plans can be created in Garmin Connect for any supported watch, or on the watch itself from a loaded course, and the manuals show that on-watch creation does not require maps; the Forerunner 165 procedure is identical to the Forerunner 965’s.

Where to find PacePro on Garmin

  • Garmin Connect mobile: More, then Training & Planning, then PacePro Pacing Strategies, then Create PacePro Strategy.
  • Garmin Connect web: Training & Planning, then PacePro Pacing Strategies, then Create PacePro Strategy; this view shows the course map, altitude profile, colour-coded pace curve and per-split table, and adjusting any variable updates all of them immediately.
  • On the watch, to start a downloaded plan: open an outdoor running activity, hold the menu button, then Training, then PacePro Plans, select the plan and press Start.
  • On the watch, to create a plan: open an outdoor running activity, hold the menu button, then Navigation, then Courses, select a course, then PacePro, then Create New, and enter a goal pace or goal time. This works on watches without maps.
  • During the activity a dedicated screen shows the five fields described in Quick answers; no data field setup is required.
  • After the activity, the planned-versus-actual pace comparison sits in the activity detail view in both app and web. No Connect Plus subscription is required.

Common problems and misreadings

Identical targets for every kilometre mean the strategy was created based solely on distance and time. A course file with elevation data is required for differentiated splits. See Quick answers above.

Targets that feel wrong on climbs almost always indicate a course file elevation error; the altitude profile in Garmin Connect should be checked against a mapping source before race day.

Brief GPS loss does not corrupt the ahead/behind figure, because tracking is position-based and resumes from the reacquired point. Time accumulated during a deliberate route deviation should be disregarded on return to the planned route. See Quick answers above.

How to improve PacePro

PacePro targets are fixed at strategy creation against a goal time. Improving the goal time requires improving the underlying fitness, primarily aerobic capacity and the ability to sustain a high fraction of maximal aerobic speed over the race distance. For undulating races, uphill-specific training, meaning hill repetitions at a controlled effort and threshold runs on rolling terrain, improves climbing efficiency and recovery speed from climbs.

Before setting a goal time for an important race, verify the altitude profile in the Garmin Connect strategy view against the actual race route.

Scientific basis

Minetti, A.E., Moia, C., Roi, G.S., Susta, D., Ferretti, G. (2002). Energy cost of walking and running on extreme uphill and downhill slopes. Journal of Applied Physiology, 93(3), 1039 to 1046. Measured the metabolic cost of running on gradients from minus 45 to plus 45 per cent, establishing the non-linear relationship between gradient and energy expenditure that underpins every published grade-adjusted pace model; Garmin has not confirmed that its own calculation uses it.

Abbiss, C.R., Laursen, P.B. (2008). Describing and understanding pacing strategies during athletic competition. Sports Medicine, 38(3), 239 to 252. Found that during prolonged efforts lasting more than two minutes, even or slightly negative pacing yields better outcomes than positive splits, the scientific rationale for grade-adjusted even-effort pacing on undulating courses.

How PacePro connects to other Garmin features

PacePro is most directly related to Grade-Adjusted Pace, the live data field that recalculates current running pace as its flat equivalent in real time: PacePro defines the per-split target before the race, and Grade-Adjusted Pace provides the real-time effort signal during it. ClimbPro operates on the same loaded course file but shows remaining distance and elevation for the current climb rather than pace targets. Course Planner also works on the loaded course, adding cut-offs, aid stations and planned rest stops to it. Race Predictor provides estimated finish times based on current VO2 max and is the natural starting point for setting the PacePro goal time, and since September 2024 its course-specific prediction adjusts that time for the same elevation profile PacePro paces against.


Small things I always use

Health, recovery and sleep

  • Kineon MOVE+: Red and infrared light for sore knees, Achilles and other joints after hard training. I use it.
  • FreeStyle Libre 3 Plus: Shows how my blood sugar responds to diet. Occasional use.
  • hDrop: Measures my sweat loss in summer and indoors. I use it.
  • Fourth Frontier Zone: Checks my heart under load in hard sessions.
  • Oura Ring 5: My partner’s recovery tracker of choice.
  • Eight Sleep: A cooling mattress cover my partner and I use nightly.

Watches and sensors

On the bike

Home and indoor training

  • NPE Runn: Makes my basic treadmill smart, sending more accurate speed and distance to my watch and Zwift. I use it.
  • Google Wifi: Keeps Zwift connected in my pain cave. I use it.
  • Apple TV 4K: Zwift on the big screen. I use two.
  • Google Nest Doorbell (wired, 2nd gen): My video doorbell, running in both Google Home and Apple Home via Starling. I use it.


Reader-Powered Content

Buy me a coffee

This content is not sponsored. It’s mostly me behind the labour of love, which is this site, and I appreciate everyone who supports it.

Support the site: Follow (free, fewer ads) · Subscribe (paid, ad-free) · Buy Me A Coffee

Written by real people, with AI assistance. Fact-checked and verified for originality. See the Editorial Policy. FTC: Affiliate Disclosure — some links pay commission. As an Amazon Associate, I earn from qualifying purchases.