A great route deserves a great video. But anyone who has tried to animate a GPX track in After Effects or Blender knows the brutal truth: the workflow is hostile to anyone who does not work in motion graphics for a living. This guide walks through the whole process — what file formats to use, what tools exist in 2026, how to think about camera angles, and what to do once the video is rendered.
Step 1 — get the right file off your device
The single biggest source of friction is the file format. Your GPS device probably supports two or three of these:
- GPX — the universal exchange format. Every device exports it.
- FIT — Garmin's binary format. More compact and accurate; needs a tool that speaks FIT.
- KML — Google Earth's format. Good for static paths; less common for live activity logs.
- TCX — older Garmin format. Still common from older devices and training apps.
- IGC — paragliding / glider flight logs. The standard for free flight.
- NMEA — raw GPS sentence logs. Mostly hobbyist GPS loggers.
- CSV — custom GPS loggers and spreadsheet exports.
GPX is the safest default — it works everywhere. If you can keep your file in its native FIT or IGC format though, you avoid a conversion step and lose no precision. cine.tours imports all of the above natively, no conversion required.
Step 2 — pick a tool
Your options range from "fully automatic, no control" to "fully manual, infinite control". The 2026 landscape:
- Relive: zero-effort, zero-control. Auto-generated short clips. Fine for a quick share, no good for a YouTube intro.
- Strava 3D activity view: a personal preview only. Cannot be exported as a video.
- After Effects + GEOlayers: pro motion-graphics workflow. Full control, hours-to-days of effort, requires AE skill.
- Blender + Blender-GIS: open-source 3D pipeline. Maximum control, days of effort, steep learning curve.
- Google Earth Studio: clean cinematic camera, but limited per-frame data overlays and no native FIT/IGC.
- cine.tours: browser-based, automatic camera with manual override, supports every format directly. Minutes-to-finished.
Step 3 — pick a camera angle
Most homemade route videos use one camera the whole time. That is the single biggest reason they look like a "GPX line slowly drawing on a map" rather than a film. Here is how a film thinks about the camera:
Drone (high overview)
Use this for context. Top of a long climb, the shape of an entire route, the geography. Lasts 3-8 seconds, then cut to something tighter.
Follow-cam
Locks behind the actor. Best when the route is technical and the viewer wants to feel the speed — singletrack, descents, races. Cut away when the action lulls.
Orbit
Circles around the actor. Used at moments of significance — summits, finish lines, transitions. The orbit gives the moment weight. Use sparingly.
Static / locked
Camera does not move; the actor moves through frame. Useful for long flat sections where any camera motion looks fake. Five seconds, then cut.
Step 4 — pick the aspect ratio
Where the video lives drives the aspect ratio:
- 16:9 landscape — YouTube, Vimeo, traditional video.
- 9:16 portrait — Instagram Reels, TikTok, YouTube Shorts. The vertical aspect ratio of where most viewers actually live.
- 1:1 square — Instagram and Facebook feed posts. Less common in 2026 than it used to be.
cine.tours renders all three from the same project — same camera, same map, different framing. Many creators render 16:9 for YouTube and 9:16 for Reels in the same export session.
Step 5 — overlays and story
A route on a map without context is a line. To turn it into a story, layer in:
- Title cards at the start of each chapter (each day of a multi-day trip; each section of a race).
- Stat overlays (distance covered, elevation gained, current speed) when the audience needs to feel the scale.
- Custom icons at meaningful points (summits, feed zones, photo spots, where you crashed).
- Elevation profile strip along the bottom — turns altitude into something legible.
Step 6 — export and finish
Render at 4K if you can. The downscale to 1080p that YouTube does for most viewers is much better starting from 4K than 1080p; the perceived quality is noticeably higher. cine.tours renders 4K on cloud GPU in minutes, not hours, so the cost-benefit math is in your favour.
For chroma-key overlay use cases — laying the route on top of GoPro footage — render with a green-screen mask and key out the green in your editor.
TL;DR
- Keep your file in its native format if possible (FIT, IGC); otherwise GPX.
- Pick a tool that matches the effort you are willing to spend. cine.tours sits at the "minutes, full control" end.
- Vary the camera. Drone for context, follow for action, orbit for moments, static for breathers.
- 4K is worth it. So is 9:16 if you post to Reels or Shorts.
- Layer in overlays and title cards. A route without story is just a line.