Velometry fills in your Strava activity description on every ride — headwind and tailwind split, year-to-date totals and this week's numbers, written the moment your ride uploads.
Connect with StravaBuild one description template, go ride, and let Velometry drop in the real numbers from your activity — every single time. Short of ideas? Start from our Strava description templates.
Connect once with OAuth. Velometry reads your activities and never asks for a password — your Strava token stays locked inside the app.
Write a template with {token} placeholders for your outdoor rides, and a second one for Zwift and other virtual rides. Clickable metric chips are grouped by family, so building them takes seconds.
Head / side / tail wind split, wind speed & direction, and a compass arrow — computed from your GPS by the wind-factor engine. How wind on Strava works →
Distance, elevation, average speed and power for the year and the current week, plus how much this ride moved each average — and, for virtual rides, your winter in the pain cave from 1 November to 31 March.
Strava webhooks notify Velometry the moment a new ride lands, so the description is written seconds after upload — without lifting a finger.
Metrics are computed on demand. Nothing derived from Strava data is persisted — fully in line with the Strava API Agreement.
Authorize through Strava's official OAuth flow — that single action is your login and drops you straight into the admin panel. No separate account, no password.
In the admin panel, compose your description and drop in metric tokens from the wind, year-to-date and weekly families — with a second template for virtual rides built on indoor-season tokens — or load one of the ready-made templates.
Record as usual. When your activity syncs to Strava, a webhook tells Velometry it's time to work.
Velometry resolves every token to a real value and fills in the description — your ride, told with your numbers.
You design the left. Velometry produces the right — automatically, on every activity.
Every token belongs to a family: wind, year, week — and, for virtual rides, the indoor season. Velometry only computes the families your template actually uses — no wasted calls. The full token reference lists every one.
The signature metric: how much the wind was working with — or against — you, derived from your GPS track. Strava never shows this — here's why, and how to get it.
{wind_factor}overall head/side/tail balance — minus fought you, plus helped{wind_direction_indicator}compass arrow showing where the wind blows{average_wind_speed}average wind speed over the ride (km/h){average_wind_direction}average wind direction in degrees{head_wind_factor}factor for the headwind component{side_wind_factor}factor for the crosswind component{side_crosswind}crosswind speed across your direction of travel{tail_wind_factor}factor for the tailwind component{head_wind_percent}headwind share (%){side_wind_percent}crosswind share (%){tail_wind_percent}tailwind share (%)Season totals as of this activity — a retro snapshot from the moment you rode, not "up to today".
{distance_ytd}total distance this year (km){elevation_gain_ytd}total climbing this year (m){avg_speed_ytd}time-weighted average speed (km/h){avg_speed_ytd_impact}how much this ride shifted the average speed (±){avg_power_ytd}time-weighted average power, rides with a meter{avg_power_ytd_impact}how much this ride shifted the average power (±){ride_count_ytd}rides so far this year{moving_time_ytd}time in the saddle this year (143h 20min){avg_distance_ytd}your average ride length (km){climb_rate_ytd}metres climbed per kilometre ridden{active_days_ytd}how many separate days you rode{distance_rank_ytd}where this ride ranks by distance this year{avg_hr_ytd}time-weighted average heart rate, rides with a strap{energy_ytd}energy burned this year (kJ){moving_time_ratio_ytd}share of your time out actually spent movingThe same fifteen measurements over a shorter window: Monday 00:00 up to this ride. Resets every Monday.
{distance_week}distance so far this week (km){elevation_gain_week}climbing so far this week (m){avg_speed_week}time-weighted average speed this week (km/h){avg_speed_week_impact}how much this ride shifted the week's average speed (±){avg_power_week}time-weighted average power, rides with a meter{avg_power_week_impact}how much this ride shifted the week's average power (±){ride_count_week}rides this week{moving_time_week}time in the saddle this week (6h 12min){avg_distance_week}average ride length this week (km){climb_rate_week}metres climbed per kilometre ridden this week{active_days_week}how many of the seven days you rode{distance_rank_week}where this ride ranks by distance this week{avg_hr_week}time-weighted average heart rate, rides with a strap{energy_week}energy burned this week (kJ){moving_time_ratio_week}share of your time out actually spent moving_week twin — same measurement, Monday-to-Sunday window.
Zwift, MyWhoosh, Rouvy and every other virtual ride from 1 November to 31 March — used in your separate virtual ride template.
{sessions_season}sessions this season, this one included — rides under an hour apart count once{session_number_season}this ride's session number — #5, then #5[2] for the race after the warm-up{pain_cave_time_season}time on the trainer this season (31h 40min){pain_cave_minutes_season}the same time as a plain minute count{virtual_distance_season}virtual kilometres this season{virtual_elevation_season}virtual metres climbed this season{everests_season}that climbing in Everests (8 849 m each){pain_cave_days_season}how many separate days you rode indoors{avg_session_time_season}your typical session length{longest_session_season}your longest session this season{sessions_per_week_season}how often you get on the trainer{season_week}which week of the season this is{avg_power_season}time-weighted average power this season{avg_power_season_impact}how much this session shifted it (±){energy_season}energy burned this season (kJ){avg_hr_season}time-weighted average heart rate this season{elevation_rank_season}where this session ranks by climbing{season_label}the season's name, e.g. 2026/27The questions riders ask before connecting.
Strava itself has no auto-description feature — every ride starts with an empty description box. Velometry fills it for you: you write one template with metric tokens, and each time a new ride uploads Strava notifies Velometry, which resolves the tokens to real numbers and writes the finished text to that activity.
No. Strava records your GPS track, speed, power and heart rate, but it does not show wind. Velometry sends the GPS streams to the wind-factor engine at windfactor.cc, which returns how much of the ride was headwind, sidewind and tailwind, plus wind speed and direction — and puts that straight into the description. More on wind data for Strava rides →
Your own words plus metric tokens from four families: Wind Factor (head/side/tail split, wind speed, wind direction), Year to date (distance, elevation, average speed, average power, heart rate, energy, ride count, distance rank and more), This week (the same measurements over a Monday-to-Sunday window) and, for virtual rides, Indoor season (sessions, virtual kilometres and climbing, time in the pain cave). See 20 ready-made description templates.
Yes. Every metric family, including the wind-factor one, is free with no paywall, no trial and no card. Connecting with Strava is also your login, so there is no separate account to create.
No — Velometry writes descriptions for bike rides only: outdoor rides including gravel and MTB, and virtual rides during the indoor season. Runs, swims, walks and e-bike rides are left completely alone, because a season average built from cycling would be misleading on them.
Yes. Virtual rides from Zwift, MyWhoosh, Rouvy and any other platform Strava files as a virtual ride get their own template, separate from your outdoor one — there is no wind on a trainer, so it is built around your indoor season instead: sessions, virtual kilometres and climbing, and time in the pain cave, counted from 1 November to 31 March. Virtual rides outside that window are left alone.
Yes. The Recent rides tab in the admin panel lists your last 10 rides with a Regenerate button that re-renders the matching template (ride or virtual) for that ride and replaces the description on Strava. Year-to-date values are computed as of the ride itself, so a regenerated old ride still shows the season as it stood back then.
No. Metrics are computed on demand and nothing derived from your Strava activities is persisted, in line with the Strava API Agreement. Velometry keeps only your Strava identity, the access tokens and your template — and erases all of it automatically when you revoke access.
Seconds. Strava sends a webhook the moment the activity is created, Velometry renders your template in the background and writes the description back — typically before you have finished looking at the map.
One click signs you in with Strava and opens your admin panel — build a template and you're done.
Connect with Strava