Running overlays: pace, splits, and elevation (without clutter)
Make runs easy to follow—whether it’s a race, a trail day, or a steady training loop.
Running videos are deceptively hard to “read.” A viewer can’t feel the gradient, and the difference between marathon pace and threshold pace isn’t obvious from a single camera angle. A good overlay solves that by adding just enough information to make the effort visible—without turning the screen into a dashboard.
For road runs, pace is the anchor metric. Most viewers understand min/km or min/mi immediately, and pace changes map naturally to the story of the run (warm-up, steady sections, surges, and cooldown). If you include only one widget, make it pace—clean, high-contrast, and stable.
Cadence is the best “second metric.” It’s a proxy for rhythm and form, and it helps explain why pace changed (shorter stride, fatigue, hill mechanics). If you have cadence data in your file, pairing pace + cadence creates a surprisingly complete picture without needing power-like complexity.
Heart rate is great for training context, but it’s also easy to misinterpret. HR lags behind effort, spikes on hills, and drifts late in long runs. If you show HR, consider presenting it as a zone indicator (or a calm line/number) rather than a rapidly updating graph. The overlay should explain the run, not distract from it.
On trails, elevation matters more than pace. Pace is still useful, but elevation profile + route map often tell the story better: the climb you earned, the descent that changed cadence, and the technical section where speed dropped. Keep the map small and legible, and let the elevation profile carry the narrative of terrain.
GPX files can also contain “gotchas” that break overlays: long pauses (coffee stops), GPS drift under trees, or missing cadence/HR when a platform stripped extensions. Before you render, sanity-check the start/end timestamps and trim the timeline to the part you filmed. Vectora’s Sync panel is built for that, and the Getting Started guide shows the full flow.
If you want a solid baseline, start from the running resource page and iterate: Running overlays.