Fake GPS on Strava: Why It Gets Flagged and What Works Instead

Searching for "fake GPS Strava" usually leads to location-spoofing apps: they feed the phone a made-up position while the Strava app records. They are popular because they are free, and they are also the fastest way to get an activity flagged. This guide explains why, and what a generated activity file does differently.

How fake GPS apps fail on Strava

A spoofing app replaces the phone's GPS fix with one you pick. The Strava app has no idea; it records whatever the phone reports. The problems come from how that recording looks afterwards:

• Teleport jumps. Moving the fake position by hand creates instant jumps of hundreds of metres, which show up as spikes to 80 km/h between two points.
• Unrealistic speed. Automated "walk this route" modes move at a perfectly constant speed. Real runners never do; every kilometre differs by a few seconds.
• Straight lines. Many apps interpolate between waypoints without following roads, so the track cuts through buildings and rivers.
• No heart rate, no cadence. The app records position only. A 10K with no biometrics next to your usual watch-recorded runs stands out.
• Mock-location and root flags. Android marks positions from a mock provider; rooted or jailbroken devices are detectable. Strava has removed activities and closed accounts on this basis.

Even when it "works", the result is a map with no elevation profile, no splits worth looking at, and a speed graph that looks like a ruler.

What a generated activity file does instead

A TCX file is the same format a Garmin watch produces: a list of trackpoints, one per second, each with latitude, longitude, altitude, a timestamp, and optionally heart rate and cadence, grouped into laps. Strava reads it as a recorded activity.

Fakepace generates that file from a route you draw:

• Points snap to real roads through Mapbox, so the track follows streets and trails.
• Elevation comes from terrain data, so climbs and descents match the ground.
• Pace varies per segment with natural fluctuation, slower uphill, faster downhill, no flat line.
• On Pro, heart rate and cadence streams respond to effort, and a Garmin or COROS device profile adds the laps and auto-pause behaviour of a real watch.

You upload the file yourself on the Strava website. Nothing runs on your phone, nothing needs root, and the data streams are complete and consistent with each other.

Step by step

1. Open the builder, search a location, and click points along the route you want. Keep the distance in line with your history.
2. In Pace & Biometrics, set a target pace you actually run. Adjust variation; on Pro, enable heart rate and cadence and pick a device profile.
3. Fill in the name, date, and a plausible start time. Download the TCX (sign in with Google; from IDR 5K per file).
4. On strava.com, click + → Upload activity → File, choose the TCX, then edit the title, type, and privacy. The mobile app cannot upload files; on a phone, use the browser in desktop mode. Details in how to upload a TCX to Strava.

Fake GPS vs generated file

Use it responsibly

Nothing on this page makes an activity "undetectable", and uploading activities you did not do violates Strava's terms of service; Strava can remove them and action your account. The sensible uses are narrow: keeping a weekly streak alive in a week you genuinely cannot train, testing how an activity renders, or replacing a lost recording of a run you actually did. Stay inside your normal pace range, keep it off segments and leaderboards, and do not do it often. If you were considering paying someone to run for you instead, read about the Strava jockey trade-offs first; handing a logged-in device to a stranger is a bigger risk than any of the above.