Vertical Video GPS Overlays for Instagram and TikTok: What Actually Breaks

Search "cycling video overlay tool" and almost every guide — this one included, historically — assumes you're working with landscape footage. But if you record with your phone for Instagram Stories, Reels, or TikTok, your source video is 9:16, not 16:9. That mismatch causes a specific set of failures most overlay tools were never built to handle. Here's exactly what breaks and what to check before you waste an export on it.

Why landscape-first overlay tools break on vertical footage

Most GPS overlay software — including early versions of ours — was designed around action-camera footage: a GoPro or similar mounted on the handlebars, always landscape, always 16:9. The gauge layouts (speed top-left, elevation bottom-right, that kind of thing) are positioned assuming a wide frame.

Load a 9:16 phone video into one of those tools and two things go wrong:

1. Black bars. The player embeds the vertical video letterboxed inside a landscape canvas, so you get a portrait clip with black space on both sides instead of a full-frame vertical result.
2. Misplaced gauges. The overlay positions were calculated for a wide frame that doesn't exist anymore. Data ends up floating in the black bars, off-center, or overlapping the actual footage.

This isn't a rare edge case. If your target platform is Instagram or TikTok, vertical is the default recording format for most riders — the assumption that everyone shoots landscape is the actual edge case at this point.

What to check before you overlay a vertical clip

Confirm the tool renders natively in 9:16, not landscape-with-letterboxing. The difference matters: a tool that "supports" vertical by centering your footage inside a 16:9 canvas with black bars on top and bottom is not the same as one that renders a true full-frame vertical export. Check a sample export before committing a full ride to it.

Check where the gauges land, specifically. A minimal overlay (2-3 data points, not a dashboard) generally survives the landscape-to-vertical transition better than a data-dense layout, simply because there's less to reposition. If you're not sure what a good minimal layout looks like on a phone screen, we broke down a specific style worth copying here.

Export a short test clip first. Ten seconds is enough to catch a black-bar or misaligned-gauge problem before you spend render time (and, on paid tools, render credits) on a full activity.

The other gap: your GPX file might not have the data you think it does

A separate but related issue: even when the video format is fine, the overlay can come up missing a specific data point — power, most often — even though your head unit definitely recorded it.

The cause is almost always the GPX file itself, not the overlay tool. Different GPS device brands format extended data (power, cadence, temperature) using different XML extension schemas inside the GPX file:

• Garmin devices use one set of extension tags for power data.
• Wahoo computers format the same data with different tags.
• Favero (pedal-based power meters) and Stages (crank-based) each have their own quirks, since power originates from the accessory, not the head unit, and gets folded into the export differently depending on the pairing.

A parser built and tested against one brand's GPX exports can silently drop fields it doesn't recognize from another — not an error, just missing data in the output, which is a much harder thing to notice until you're staring at an overlay with no watts on it and you know for a fact you rode with a power meter.

If your overlay is missing a data field you know you recorded: open the raw GPX file in a text editor and search for the field name (power, watts, cad) inside the <extensions> block of a trackpoint. If it's there but not showing up in the overlay, it's a parser compatibility gap, not a recording problem — worth reporting to whichever tool you're using, since it's usually a quick fix on their end once they know which device format is missing.

Quick checklist

1. Confirm the overlay tool renders true 9:16, not landscape-with-black-bars.
2. Keep the gauge layout minimal — fewer data points survive the format switch cleanly.
3. Export a short test clip before committing a full ride.
4. If a data field is missing (power is the usual suspect), check the raw GPX file's extensions before assuming the tool is broken — it might be a device-specific export format the parser doesn't recognize yet.

SportsSync is built phone-first and vertical-native — no landscape assumption to work around, and GPX parsing covers the major head unit and power meter brands. If you'd rather skip the checklist and just try it: upload a clip and see the overlay render.

Comparing this against the rest of the field first? Start with our full overlay tool comparison, or the step-by-step on syncing GPS data to video if you're setting this up for the first time.