Telemetry overlays for your ride videos. RideMetri reads the speed, cadence, heart rate and elevation off a Garmin track, draws them over your footage, and exports a clean PNG sequence, frame for frame in sync with the ride. It runs entirely in the browser.
A ride leaves two files behind: a Garmin track full of numbers and a clip full of motion. Putting the numbers on the clip usually means a paid desktop app or a plugin, an export queue, and a lot of manual keyframing. That is enough friction that most amateur cyclists posting a Reel just don’t bother.
The product bet: the thing standing between the ride and the post isn’t features, it’s setup. So RideMetri does it in a browser tab, with no account, no upload, and exactly one export target: the 9:16 frame every short-form platform wants. Drop in a GPX or TCX track and your footage; it parses every point, draws the route on a map, and lets you nudge the offset and playback rate until the gauges move with the ride. Lay out the widgets, mark the stretch you want, export a numbered PNG sequence zipped for your editor.
The core UX insight is that syncing a GPS clock to a camera clock can’t be automated reliably across arbitrary footage. So instead of hiding a fragile auto-align, I made syncing by eye fast and legible: one offset field, one rate slider, a live readout of what each is doing.
Everything (parsing, compositing, encoding the frames) runs on the client. The files never leave the machine, which is a positioning choice as much as a technical one.
The desktop tools already win on power. The only opening is the gap between finishing a ride and posting it, so every scoping decision was made to shrink that gap.
How I judge it. One test: someone who has never seen it should get a synced, exported overlay of a real ride inside ten minutes, on a laptop, without asking me anything. If a step needs explaining, that step is the bug.
The existing options are clear: desktop apps like the ones from the action-camera makers, a few paid plugins, and DIY After Effects. All of them are capable and all of them are heavy. The gap for a lightweight, browser-based overlay was obvious; the open question was whether the hard part could be made pleasant.
That hard part is sync. I built a throwaway prototype that tried to auto-align GPS speed to motion in the footage. It worked on a clean test clip and broke on everything real: shaky mounts, stop-start riding, tunnels with no signal. That result killed auto-sync as the primary path and made “sync by eye, done well” the core design problem rather than a fallback.
Watching a few riders use early builds settled the rest: they scrubbed to an obvious landmark (a sprint, a stop) and matched the dial there. So the sync UI is built around a big scrubbable preview and a live readout, not a settings form.
Every one of these traded something real away. They’re the reason the tool is a browser tab and not a desktop app.
RideMetri reads the speed, cadence, heart rate and elevation off your Garmin track and draws them over your footage.
The mockups on this page are rebuilt from the real front end; figures are illustrative, not exported from a specific ride.
What I’d change. The sync step is the whole product and it’s still the part first-time users stall on. It needs a guided first-run, not just a live readout. And a long export at 25fps can walk a browser tab into a memory wall; the honest fix is a smaller default range with a clear “render in chunks” path, which I’d rather ship than pretend the ceiling isn’t there.