NeverChill

Free tool

Prepend stationary GPS records to the start of a FIT.

Make a FIT activity look like it started a minute earlier at a specific spot. Drop the file, pick how many seconds to backdate, drag a pin on the map for the prepend coordinate, and the tool inserts one stationary record per second at the head of the activity. Perfect for fixing a forgotten-to-start head unit, anchoring an indoor warmup to a real coordinate, or padding the start of a course for navigation cues.

starts at 0.0 kmbecomesstarts at -1.2 km

How it works

  1. 1

    Drop a FIT file

    GPX and TCX don't carry the lap and session messages we need to extend properly.

  2. 2

    Set duration and start coordinate

    How many seconds to prepend, and the lat/lon for those records. Drag the map pin or type the numbers.

  3. 3

    Download the extended file

    Session start is shifted earlier, a new leading lap covers the prepended seconds, totals are updated.

What you get

  • One stationary record per prepended second
  • New leading lap message covering the extended segment
  • Map-pin drag updates lat/lon live
  • Session start time shifted earlier and total elapsed time updated
  • Re-encoded via the official Garmin SDK - the output stays valid for Strava and Garmin Connect
  • Works offline - your FIT stays on your device, never uploaded

When to use this

The two real use cases: you forgot to press start on your head unit and the activity is missing the first minute or two (anchor it back to where you actually began), or you wanted a brick session's indoor warmup to appear on the same activity timeline as the outdoor ride that followed. Both cases are about making the timeline honest rather than gaming any numbers. The tool does not inflate your moving time, distance, or elevation - it just adds the seconds at the start so the activity covers the real beginning.

How it works under the hood

The tool decodes your FIT in your browser. It computes the new start time as (original first-record timestamp - prepend seconds), generates one new record per second between the new start and the original first record, and stamps each new record with the chosen lat/lon, the elevation of the original first record, and zero speed/distance/HR/power/cadence. It then inserts a new lap message at the head of the lap list covering the prepended seconds, shifts the session message's start_time field, and updates the session total_elapsed_time by adding the prepend duration. The file_id.time_created is shifted to match. Everything is re-encoded through the official Garmin FIT SDK with correct CRC and headers, so the output is round-trip safe.

Common mistakes

Three common ones. First, dropping a GPX or TCX in and being surprised it does not work - the tool needs FIT specifically because GPX/TCX do not carry the session and lap messages we modify. Convert first. Second, prepending a huge duration (an hour, two hours) thinking it will "anchor" a complex multi-stage activity - it will not, because the prepended records are stationary and look like a stationary nap to any platform reading the file. Use [FIT Combiner](/tools/fit-combiner) for legitimate multi-segment activities. Third, setting the prepend coordinate to a random pin without checking the map - the resulting file will show the activity beginning miles from where it actually started, which is worse than no prepend at all.

Frequently asked questions

Why would I extend the start of an activity?
Two main reasons. First, forgot-to-press-start: you rode the first kilometer from your house before realizing the Garmin was not recording, and you want the activity to cover the real beginning. Second, anchor an indoor warmup to a real coordinate so it slots correctly on a map view before the outdoor portion of a brick session or commute begins. A third niche reason: padding the start of a course file so the head unit shows the route a little before you reach the actual start line.
Does the prepended segment count as moving time?
No - speed and distance on those records are zero, so any moving-time calculation (Strava, Garmin Connect, our own analytics) treats them as a stationary warmup. Total elapsed time goes up by the prepended seconds; moving time stays the same. This is what you want - the prepend exists to fix the timeline, not to inflate your numbers.
GPX or TCX support?
Not for this tool. FIT only. Start extension needs the lap and session messages and the file_id.time_created field that GPX and TCX do not carry. If you have a GPX or TCX recording you want to backdate, convert it to FIT first with our [FIT Converter](/tools/fit-converter), then extend.
Will Strava accept the extended file?
Yes - the output is a fully valid FIT re-encoded via the official Garmin SDK with proper CRC and headers. Strava will treat it as a normal activity. If you are re-uploading because the original was missing the start, delete the original from Strava first or the duplicate-detection logic may reject the new upload.
How accurate does the prepended coordinate need to be?
It does not need to be perfectly precise - a real lat/lon close to where you actually were is fine. The point is to give the file a believable starting position rather than (0, 0) or some weird default. Drag the map pin or paste in coordinates from Google Maps. A few meters of error makes no difference to anything downstream.
What if I want a non-stationary prepend (a virtual warmup that moves)?
That is not what this tool does - all prepended records have zero speed and the same coordinate. If you need a moving warmup, you really want to merge two FIT files together, which our [FIT Combiner](/tools/fit-combiner) handles. Record the warmup separately and combine, rather than synthesising a fake moving warmup.
Will the prepend affect my elevation gain?
No - the prepended records all share the elevation of the first original record (extrapolated from the activity's actual start altitude). They form a flat plateau at the start of the elevation profile and add zero meters of gain. Cumulative ascent for the activity stays unchanged.
Can I prepend more than a few minutes?
Technically yes, but the longer the prepend, the weirder the activity gets - hours of stationary records at the start looks suspicious to platforms and to anyone reading the file. Keep it under 10 minutes for sane results. For longer backdating, you usually want a different tool: use [FIT Time Adjuster](/tools/fit-time-adjuster) to shift the whole activity, or combine two recordings.

More from the FIT toolkit

See all tools

Clone and Retime

Re-stage any ride for any clock.

ride.fit, 11 Marbecomescopy.fit, today

Open

FIT Time Adjuster

Fix the clock without re-doing the workout.

started 2024-03-11 07:02becomesstarted today 06:30

Open

FIT Combiner

Merge 2+ files into one activity, in your order.

3 filesbecomes1 activity

Open

FIT Section Remover

Snip out the part of the ride you don't want.

84.2 kmbecomes71.6 km

Open

Save your training to a real log

Pad the start once, then keep every ride and run analyzed in one place. Domestique reads the data for you.

Create free account