Free tool

Hide your home address from any activity file.

Strip your home address out of a shared GPX, FIT, or TCX before anyone can stalk it. Set a privacy radius around the start and end, scrub athlete name, device serial, and sensor IDs from the metadata, and download a cleaned file in the same format. Free, in-browser, your activity never gets uploaded.

home: 51.5074, -0.1278becomeshome: hidden

How it works

  1. 1

    Drop a file

    GPX, FIT, or TCX - whatever your watch or head unit wrote.

  2. 2

    Set the trim radius

    Default 500m on each end. Drag the slider to widen or tighten the privacy zone.

  3. 3

    Download the clean file

    Trimmed track, scrubbed metadata, same format you uploaded.

What you get

  • Configurable trim radius for start and end (100m to 2km)
  • Optional metadata scrub - athlete name, device serial, sensor IDs
  • Before-and-after map preview so you can see exactly what is being cut
  • Works on GPX, FIT, and TCX with full elevation and stats preserved
  • Re-encodes FIT via the official Garmin SDK - the output stays valid for Strava and Garmin Connect
  • Works offline - your file stays on your device, never uploaded

When to use this

Use this any time you are about to share a GPX file with someone you do not fully trust, post a ride on a public forum, upload a route to a community planner, or attach an activity file to an email. The classic case: someone asks you for the route of a nice weekend ride, you export the GPX from Strava, and you forward it - except the file starts and ends at your front door. A two-minute trim hides that. Same idea for forum posts, route packages, ride reports, and any time you are about to make an activity file publicly downloadable.

How it works under the hood

The tool decodes your file in your browser, finds the first and last trackpoints, draws a circle of the radius you chose around each, and removes every trackpoint that falls inside either circle. For FIT files, it then re-encodes via the official Garmin SDK so the output is a valid FIT with correct CRC and headers - Strava and Garmin Connect will accept it. For GPX and TCX, it rewrites the XML with the kept points and updates the metadata block. If metadata scrub is enabled, it also clears the athlete-name field in the GPX metadata block, the device_info serial in FIT, and the author/creator fields in TCX, then strips any extension fields that carry sensor IDs.

Common mistakes

Three common mistakes. First, using too small a radius - 100m only covers your house and immediate driveway; a stalker with the file can extrapolate the missing bit back to your door. 300-500m is the realistic minimum. Second, forgetting that the end of a ride often ends at a different address from the start (you left from home but ended at a coffee shop, or vice versa) - the tool handles both ends independently, but you should check the preview. Third, sharing the file before running the tool, then sharing the trimmed file later - the original is already out there. Trim before sharing.

Frequently asked questions

Why trim the start and end of a shared ride?
Most people start and end activities at home or near it. When you share the raw GPX with a friend, post it on a forum, or upload it to a route-sharing site, you are also handing out your home address - every trackpoint is GPS-accurate to within a few meters, and the cluster of points at the start tells anyone where you live. A 500m privacy radius removes those breadcrumbs while keeping the meaningful part of the ride intact.
Will Strava's privacy zone do the same thing?
Inside Strava, mostly - the privacy zone blurs the start and end of activities on the Strava map for other users. But the moment you export the GPX (or someone else exports your public activity), the full unblurred track is back in the file. Strava's privacy zone is a display layer, not a data layer. This tool modifies the file itself, so the protection survives any export.
What metadata gets scrubbed?
Athlete name in the GPX metadata block. FIT device serial number, user_profile fields, and any optional personal-info fields. TCX author and creator fields. The scrub is optional - leave the checkbox off if you want to keep that info. Stats (distance, time, elevation, HR, power) always stay intact.
How big a privacy radius should I use?
For sharing a route with friends, 200-500m is plenty. For posting a public route on a forum or a route-aggregator site, lean toward 500m or more, because anyone who downloads it might also be running scripts to find clustered start points across thousands of files. If you live in a quiet rural area where 500m only covers your driveway, go bigger.
Does this break my Strava upload?
No - the trimmed file is still a valid GPX/FIT/TCX. It will upload to Strava as a shorter activity, with the start and end trimmed to where you left and re-entered the privacy zone. If you want the full activity in Strava but want to share a trimmed version separately, upload the original first, then run this tool on a copy of the file for sharing.
Will this hide me from the Strava heatmap?
Not directly. The Strava heatmap is built from activities uploaded to Strava, not from files you share elsewhere. To get off the heatmap, you need to mark activities private in Strava itself. This tool protects the file you share outside Strava.
What about all the trackpoints in the middle of the ride?
Those stay intact - the point of this tool is to hide your home, not your route. If you also want to obfuscate the entire route, run it through our [Route Simplifier](/tools/route-simplifier) first to reduce points, or upload it as private to whatever platform you use.
Can I see where the trim cuts before downloading?
Yes - the before-and-after map preview shows the full original track in one color and the trimmed track in another, with the privacy circles drawn. You can drag the radius slider and watch the cut update live before downloading anything.

Share routes safely

Save your training to a real log with privacy zones built in from day one.

Create free account