Strava description ideas

20 ready-made templates · last updated 14 November 2026

The description box is the one part of a Strava activity that stays empty unless you fill it. Below are twenty descriptions worth writing — each one built from live ride data, so the same template reads differently on every ride. Copy any of them, or load it into Velometry with one click and have it written for you the moment your ride uploads.

On this page What makes a good description Wind templates KOM and segment templates Season templates Weekly templates Zwift and virtual ride templates Make it automatic FAQ

What makes a good Strava description

A ride page already shows distance, elevation, time and power. Repeating those adds nothing. A description earns its place when it carries something the activity page cannot show:

Keep it to one to three lines. Strava truncates long descriptions in the feed, so whatever matters most belongs on line one.

In every example, {token} is a placeholder Velometry replaces with the real value for that ride. The second block shows how the description actually lands on Strava.

Wind description templates

Wind is the biggest thing missing from a Strava activity page, which makes it the most interesting thing to put in a description. See wind data on Strava for how the numbers are worked out.

1. Full wind breakdown

The complete picture — overall factor, wind speed and direction, then the head / side / tail split.

🌬️ WindFactor {wind_factor} · {average_wind_speed} {wind_direction_indicator}
🧭 Head {head_wind_percent} ({head_wind_factor}) · Side {side_wind_percent} ({side_crosswind}) · Tail {tail_wind_percent} ({tail_wind_factor})
🌬️ WindFactor -0.86 · 18.4km/h ↗
🧭 Head 48% (-1.24) · Side 33% (12.7km/h) · Tail 19% (0.46)
//velometry.cc

2. Wind one-liner

Minimal, and the one that survives feed truncation: the headline number, speed, direction.

🌬️ Wind {wind_factor} · {average_wind_speed} from {wind_direction_indicator}
🌬️ Wind -0.86 · 18.4km/h from ↗
//velometry.cc

3. Headwind hero

Narrative flavour — frames the ride as a fight rather than a data dump. Good on the days the average speed looks worse than the effort felt.

💪 Fought {head_wind_percent} headwind ({head_wind_factor})
🌬️ {average_wind_speed} from {wind_direction_indicator} · overall {wind_factor}
💪 Fought 48% headwind (-1.24)
🌬️ 18.4km/h from ↗ · overall -0.86
//velometry.cc

4. Wind plus season combo

One wind line, one season line — the everyday all-rounder, and the template most riders end up keeping.

🌬️ {wind_factor} wind · {average_wind_speed} {wind_direction_indicator}
📊 YTD {distance_ytd} · {elevation_gain_ytd} · {avg_speed_ytd}
🌬️ -0.86 wind · 18.4km/h ↗
📊 YTD 4 210km · 51 300m · 29.4km/h
//velometry.cc

KOM and top-10 segment templates

A KOM is worth writing down; a KOM taken into a headwind is worth bragging about. These templates list the segments themselves, each with the wind that was blowing while you rode it.

Strava fills segment ranks in a few minutes after the upload, so Velometry writes these lines a little later — and if a ride produced no top-10 effort at all, the lines are left out completely rather than published as a zero.

5. KOM hunter

Every crown you took, and the wind that was on it. On a ride without a KOM, both lines simply do not appear.

👑 KOMs: {ride_koms} · wind on them {ride_koms_wind_factor}
{ride_koms_list}
👑 KOMs: 2 · wind on them 1.79
👑 Dół (siodło) Kopytówka | WF: 1.88
👑 Paszkówka - Kopytówka | WF: 1.71
//velometry.cc

6. Top-10 scoreboard

The full leaderboard haul, ranked — crown for a KOM, keycap digits for the rest.

🏆 Top-10 efforts: {ride_top10s} · wind on them {ride_top10s_wind_factor}
{ride_top10s_list}
🏆 Top-10 efforts: 4 · wind on them 1.13
👑 Dół (siodło) Kopytówka | WF: 1.88
👑 Paszkówka - Kopytówka | WF: 1.71
2️⃣ Leńcze od Podolan | WF: 0.21
2️⃣ Leńcze pod Kościół-Grabie | WF: 0.73
//velometry.cc

7. Wind plus segments

The ride's wind on top, the segments it was blowing on underneath — and the two often disagree, which is the interesting part: a ride that fought the wind overall can still hand you crowns on the leg where it was behind you. Note the count sitting in the header line: that is deliberate, so on a ride with no top-10 the header disappears together with the list instead of dangling over nothing.

🌬️ Wind {wind_factor} · {average_wind_speed} {wind_direction_indicator}
🏆 {ride_top10s} top-10 efforts today:
{ride_top10s_list}
🌬️ Wind -0.86 · 18.4km/h ↗
🏆 2 top-10 efforts today:
👑 Dół (siodło) Kopytówka | WF: 1.88
2️⃣ Leńcze od Podolan | WF: 0.21
//velometry.cc

Season and year-to-date templates

Year-to-date values are computed as of the ride, not as of today — so a description written in March still reads like March, even if you regenerate it in November.

8. Season progress

Cumulative totals plus how much this single ride moved your season averages.

📊 Season: {distance_ytd} · {elevation_gain_ytd} climbed
⚡ Avg {avg_speed_ytd} ({avg_speed_ytd_impact}) · {avg_power_ytd} ({avg_power_ytd_impact})
📊 Season: 4 210km · 51 300m climbed
⚡ Avg 29.4km/h (+0.2km/h) · 212W (-3W)
//velometry.cc

9. Climber's log

For riders who count metres rather than kilometres. Climb rate is metres gained per kilometre ridden, so a hilly season reads high even when the distance does not.

⛰️ {elevation_gain_ytd} climbed this year over {distance_ytd}
📈 That is {climb_rate_ytd} average · {ride_count_ytd} rides · {active_days_ytd} days out
⛰️ 51 300m climbed this year over 4 210km
📈 That is 12.2m/km average · 112 rides · 96 days out
//velometry.cc

10. Engine room

Power, heart rate and energy for the season. Needs a power meter and a strap — anything you did not record renders as n/a instead of a wrong number.

🫀 Season engine: {avg_power_ytd} · {avg_hr_ytd} · {energy_ytd} burned
⚡ This ride moved it by {avg_power_ytd_impact}
🫀 Season engine: 212W · 142bpm · 109 400kJ burned
⚡ This ride moved it by -3W
//velometry.cc

11. Ride of the year?

Ranks the ride you just did against every other ride this year by distance — the description that makes a big day feel big.

🏅 Ride #{distance_rank_ytd} by distance this year
📊 {distance_ytd} across {ride_count_ytd} rides · avg {avg_distance_ytd} each
🏅 Ride #3 by distance this year
📊 4 210km across 112 rides · avg 37.6km each
//velometry.cc

Weekly templates

The week runs Monday 00:00 to Sunday, and every year-to-date token has a _week twin. Weekly numbers are the ones that actually change training behaviour — they are small enough to chase.

12. Week so far

Where the current week stands after this ride. Resets every Monday, so it never becomes background noise.

📅 Week so far: {distance_week} over {ride_count_week} rides ({active_days_week} days)
⏱️ {moving_time_week} in the saddle · {elevation_gain_week} climbed · avg {avg_speed_week}
📅 Week so far: 186km over 4 rides (3 days)
⏱️ 6h 12min in the saddle · 2 140m climbed · avg 30.1km/h
//velometry.cc

13. Week vs season

The week set against the whole year — the quickest way to see whether you are ahead of your own pace.

📅 This week: {distance_week} · {elevation_gain_week} · {moving_time_week}
📊 This year: {distance_ytd} · {elevation_gain_ytd} · {moving_time_ytd}
📅 This week: 186km · 2 140m · 6h 12min
📊 This year: 4 210km · 51 300m · 143h 20min
//velometry.cc

14. Coffee-stop audit

Moving-time share is how much of your total time out was actually spent pedalling. Below 85% and the café is winning.

☕ {moving_time_week} moving this week — {moving_time_ratio_week} of the time out
📅 {ride_count_week} rides · {distance_week} · avg {avg_distance_week}
☕ 6h 12min moving this week — 91% of the time out
📅 4 rides · 186km · avg 46.5km
//velometry.cc

15. Everything, everywhere

The maximalist option: wind, week and season in three lines. Best kept for long rides, where a wall of numbers feels earned.

🌬️ Wind {wind_factor} · {average_wind_speed} {wind_direction_indicator}
📅 Week: {distance_week} · {elevation_gain_week} · {moving_time_week}
📊 Year: {distance_ytd} · {elevation_gain_ytd} · avg {avg_speed_ytd} ({avg_speed_ytd_impact})
🌬️ Wind -0.86 · 18.4km/h ↗
📅 Week: 186km · 2 140m · 6h 12min
📊 Year: 4 210km · 51 300m · avg 29.4km/h (+0.2km/h)
//velometry.cc

Zwift and virtual ride templates

A trainer session needs a different story. There is no wind indoors, and the GPS track of a virtual world says nothing about the weather — so Velometry describes virtual rides (Zwift, MyWhoosh, Rouvy and anything else Strava files as a virtual ride) with a template of their own, built around the indoor season: every virtual ride from 1 November to 31 March, up to and including the one being described. Every token ends in _season. Rides less than an hour apart count as one session — Zwift often saves a warm-up and the race after it as two activities — so #{session_number_season} reads #5 on the warm-up and #5[2] on the race, while a morning and an evening ride are sessions #5 and #6. Virtual rides between April and October are left without a description.

16. Pain cave log

Session number, virtual kilometres, climbing and time on the trainer — the whole indoor season in four lines.

🏠 Pain cave session #{session_number_season} · season {season_label}
🛣️ Virtual km: {virtual_distance_season}
⛰️ Virtual climbing: {virtual_elevation_season} ({everests_season} Everest)
⏱️ Time in the pain cave: {pain_cave_time_season}
🏠 Pain cave session #23 · season 2026/27
🛣️ Virtual km: 812km
⛰️ Virtual climbing: 9 640m (1.1× Everest)
⏱️ Time in the pain cave: 31h 40min
//velometry.cc

Zwift saved your warm-up on its own and the race started ten minutes later? Rides less than an hour apart are one session, so the race keeps the number and adds its place in the session — and the season totals include both rides:

🏠 Pain cave session #23[2] · season 2026/27
🛣️ Virtual km: 842km
⛰️ Virtual climbing: 10 040m (1.1× Everest)
⏱️ Time in the pain cave: 32h 30min
//velometry.cc

17. Pain cave one-liner

The season on a single line, for riders who like their numbers short.

🏠 #{session_number_season} · {virtual_distance_season} · {virtual_elevation_season} · {pain_cave_time_season} in the cave
🏠 #23 · 812km · 9 640m · 31h 40min in the cave
//velometry.cc

18. Watts & suffering

Season power and how this session moved it, with heart rate and energy. On a smart trainer the power is always there.

⚡ Session #{session_number_season}: season avg {avg_power_season} ({avg_power_season_impact})
🫀 {avg_hr_season} · {energy_season} burned since November
⚡ Session #23: season avg 214W (+2W)
🫀 138bpm · 24 300kJ burned since November
//velometry.cc

19. Virtual climber

For riders who live on the virtual mountains: climbing in Everests, and where this session ranks.

⛰️ {virtual_elevation_season} climbed indoors — {everests_season} Everest
🏔️ This session ranks #{elevation_rank_season} for climbing this season
⛰️ 9 640m climbed indoors — 1.1× Everest
🏔️ This session ranks #2 for climbing this season
//velometry.cc

20. Season tracker

Consistency over volume: the week of the season, how often you ride and for how long.

📆 Week {season_week} of {season_label}: {sessions_season} sessions ({sessions_per_week_season}/week)
⏱️ Avg session {avg_session_time_season} · longest {longest_session_season} · {pain_cave_days_season} days in the cave
📆 Week 10 of 2026/27: 23 sessions (2.3/week)
⏱️ Avg session 1h 22min · longest 3h 5min · 21 days in the cave
//velometry.cc

Make it automatic

Typing any of this by hand after every ride lasts about a fortnight. Velometry does it for you:

Changed your wording later? The Recent rides tab regenerates the description of any of your last 10 rides with the new template. Every token available is listed in the full token reference.

FAQ

What should I write in a Strava description?

Anything the ride data alone does not tell: how it felt, what the conditions were, and the numbers Strava does not show on the activity page — the headwind share, your season totals, or where the week stands. One or two lines is plenty; a wall of numbers reads as noise.

Can I reuse the same description on every ride?

Yes, as long as the numbers inside it change. Velometry keeps one template for outdoor rides and one for virtual rides, and re-renders the matching one for each activity, so identical wording carries different values every time.

How long can a Strava activity description be?

Strava accepts a long description, but the feed shows only the first couple of lines before truncating. Put the line you actually want read first.

Connect with Strava