The Safa Brian Overlay Style: How to Recreate It on Your Own Rides

If you've spent any time watching cycling content on YouTube or Instagram, you've probably seen Safa Brian's videos — cinematic riding footage with a telemetry overlay that stays out of the way instead of covering the screen in numbers. It's become something close to a reference point for what a "good" cycling overlay looks like. This isn't an official guide (we're not affiliated with him), just a breakdown of what makes the style work and how to get close to it yourself.

What actually makes the style work

Watch a few of his videos back to back and the pattern is consistent:

• Few data points, not many. Speed is usually the anchor. Maybe heart rate or elevation alongside it. Never a dashboard of six metrics competing for attention.
• Speed placed prominently, usually bottom of frame, large enough to read at a glance without pausing.
• Smooth, continuous updates rather than numbers that visibly jump or stutter — the data feels like part of the footage, not a layer bolted on top of it.
• The footage does the work. The overlay supports the video; it doesn't try to be the video.

That last point matters most. A lot of the visual impact people attribute to "the overlay" is actually the footage underneath it — his videos typically involve multiple camera angles and production value most solo riders aren't working with. The overlay style is genuinely replicable on a phone-shot solo ride. The cinematography is a separate skill. This post is about the first one.

How to get close to it with your own footage

1. Pick two data points, maybe three. Speed, and one of elevation/heart rate/cadence. Resist the urge to show everything your GPS device recorded — a busy overlay is the fastest way to make footage look amateur, regardless of how good the video itself is.

2. Put speed where the eye already goes. Bottom-center or bottom-third of frame, sized to be legible without demanding attention. If you have to squint or pause the video, it's too small or too cluttered around it.

3. Smooth the updates. Raw GPS data updates once per second and looks robotic if you render it that way — numbers visibly stepping instead of flowing. Interpolating between points so values update several times a second (rather than once) is what removes that stutter. This is a rendering detail, not a filming one, but it's the difference between "clean" and "looks like a spreadsheet."

4. Keep color and typography minimal. One accent color, one typeface, consistent placement across the whole video. The overlay should look like it belongs to the video's own visual identity, not like a template dropped on top of it.

5. Don't fight your footage. If you're filming solo with a phone or action camera, you won't match a multi-angle production — and you don't need to. A clean overlay on honest, single-angle footage of your own ride looks better than a busy overlay trying to compensate for footage that doesn't have the production value to carry it.

Where SportsSync fits in

This minimal standard is the actual internal design target for SportsSync's default overlay template — the goal has always been "would this pass next to Safa Brian's overlays," not just "does it show the numbers." Upload a solo-ride video, sync it with your GPS data (via Strava or a GPX file), and the generated overlay follows the same principles above by default: a couple of data points, speed prominent, smooth updates, no dashboard clutter — built for exactly the "you don't need a production team to get this look" case.

For the full walkthrough of getting your GPS data synced to video in the first place, see our step-by-step guide.