How PeakPacing works
Six steps that turn the GPX track of a race into a power plan, segment by segment — and then let you ride it at home, before race day.
1. The race type
You start by choosing the discipline: swim, bike, run, duathlon or triathlon. That choice decides which legs the wizard has to plan and which thresholds it asks for in the next step.
2. The thresholds
FTP, run threshold and swim pace are entered by hand or imported from a connected Intervals.icu profile. They are the basis every target is computed from: without current thresholds the plan is arithmetically correct and practically useless.
3. The course
You upload the GPX track of the race. From it PeakPacing derives the distance, elevation and gradient of every segment, and the GPS bearing that the next step needs in order to work out where the wind is in your face and where it is not.
4. The weather
Expected temperature, humidity, and wind direction and strength. Wind is not applied as an average penalty across the whole leg: it is resolved segment by segment by comparing its direction with the direction of travel, so an out-and-back course in a stiff wind produces different targets in the two directions.
5. The plan
The pacing engine combines gradient, frontal area (CdA), rolling resistance (Crr), drivetrain loss and the wind component, and returns the watts to hold and the expected split time for every segment. CdA and Crr are configurable, with presets for the aero time-trial position and for the road position.
The fuelling plan comes out alongside the power plan: fluid, sodium and carbohydrate per hour, computed from the estimated race duration and the environmental conditions rather than from a rough guess at sweat rate.
6. Riding it on the trainer
This is the part that separates PeakPacing from other pacing tools. The plan is not exported to Zwift or TrainerRoad to be ridden: PeakPacing connects to the smart trainer over Bluetooth FTMS and drives it in ERG mode from the same interface that generated the plan.
During the session you can switch to free ride in watts or speed without stopping, and change the target with a Zwift Click remote without touching the screen. When the session ends the virtual activity can be uploaded to Intervals.icu and Strava in TCX format.
What you need
- A Google account to sign in.
- A smart trainer or treadmill that supports Bluetooth FTMS, if you want to ride the plan and not just generate it.
- A browser with Web Bluetooth — Chrome, Edge or Opera, on desktop or Android — or the native iOS/Android build.
- Optional: an Intervals.icu account to import thresholds and workouts, and a Strava account to upload activities.