# The Split > The Split (thesplit.fit) is a free web editor for GPS/heart-rate activity files > (FIT, TCX, GPX) from sports watches and bike computers. Uploaded files are processed in > server memory and automatically discarded after a short TTL — nothing is stored beyond that. ## What it does - Merge: combine two recordings of the same session, aligning them by timestamp with a manual or auto-detected clock offset. Either replace a Garmin (or other FIT) activity's per-record heart rate with a more accurate Polar Verity Sense (or other TCX-exporting chest/arm strap) heart-rate stream, or — for a ride recorded on both a watch/bike computer and a virtual platform (Zwift, MyWhoosh, TrainingPeaks Virtual) — bring the platform's route, distance, speed and altitude into the watch's own recording, which keeps the device identity training platforms credit the ride to. For that pair the source of each stream (route, power and cadence, heart rate, temperature, laps) is chosen per stream; route, distance, speed and elevation move together as one choice. - Crop / Split: trim an activity to a time or distance range, or split one recording into two separate activities. Works on indoor recordings with no GPS; the totals of what remains (distance, time, averages, calories) are recalculated. - Concatenate: join two activities recorded back-to-back (e.g. a watch that stopped recording mid-workout) into one continuous file. - Multisport boundary editing: move the transition point between two sessions in a multisport file (e.g. triathlon swim→bike→run), including bulk-entering official race transition times and trimming the tail of a recording. - Substitute leg: splice a single-sport secondary recording into the matching leg of a multisport primary, when a watch missed or mis-recorded one leg. - Export: download the result as FIT, TCX, or GPX. - Workflows for AI assistants: four plan-then-confirm jobs, each proposing numbered steps with a plain-English reason, changing nothing until the user confirms them, and never changing the uploaded files: clean up wrong data in a recording that opens fine (heart-rate spikes, an idle start or end), combine two recordings of one workout, fix a multisport file, and join the pieces of a workout the watch stopped and restarted. ## Problems it solves - A sports watch's built-in wrist HR is often inaccurate; a separate HR strap is accurate but usually can't be paired live with every watch. This tool merges the two after the fact instead of requiring live pairing. - Multisport race files frequently have wrong or missing transition times between legs; this tool corrects them without re-recording or hand-editing binary FIT data. - Recordings that got split by an accidental pause, or that need trimming/cropping for privacy or accuracy, can be fixed without specialized desktop software. ## Key pages - Home / tool: https://thesplit.fit/ - How it works: https://thesplit.fit/help - API (anonymous HTTP API, same operations as the site): https://thesplit.fit/api - Interactive docs: https://thesplit.fit/api/v1/docs - OpenAPI description: https://thesplit.fit/api/v1/openapi.json - MCP server (hosted, no account or key): https://thesplit.fit/mcp (Streamable HTTP, stateless). Add it as a remote MCP server in Claude, Cursor or any MCP client. Nine tools: upload_activity, get_activity_summary, export_activity, delete_activity, analyze_cleanup, analyze_dual_recording, analyze_multisport, analyze_interrupted_workout, apply_plan. The workflows are also REST: POST /api/v1/workflows/{cleanup, dual-recording, multisport, interrupted-workout}/analyze, then POST /api/v1/workflows/plans/{planId}/apply. - Articles: https://thesplit.fit/articles - Article, merging a watch's wrist heart rate with a chest or arm strap's heart rate (Polar): https://thesplit.fit/articles/merging-garmin-and-polar-heart-rate - Article, trimming, splitting and joining activity files: https://thesplit.fit/articles/splitting-and-cropping-activity-files - Article, merging a watch recording with an indoor trainer ride (Zwift, MyWhoosh, Rouvy, TrainingPeaks Virtual): https://thesplit.fit/articles/merging-watch-and-indoor-trainer-recordings - Guide, triathlon transitions and swapping in a bike-computer leg: https://thesplit.fit/articles/fix-triathlon-transitions-and-swap-a-leg - Guide, merging two Garmin activities (joining recordings made one after the other): https://thesplit.fit/articles/merge-two-garmin-activities - Guide, joining recordings of different sports into one multisport activity: https://thesplit.fit/articles/join-different-sports-into-one-multisport-activity - Guide, why your heart rate spikes at the start of a run, and how to repair the data: https://thesplit.fit/articles/why-your-heart-rate-spikes-at-the-start-of-a-run - Guide, what cadence lock is and how to spot it in your heart-rate data: https://thesplit.fit/articles/what-is-cadence-lock-heart-rate - Guide, how to fix a heart rate spike on a Garmin watch (repair the recorded file, and what to change next run): https://thesplit.fit/articles/how-to-fix-a-heart-rate-spike-on-garmin - Guide, how to automate FIT file fixes with an AI agent (repair spikes, merge a strap, crop and relabel a folder through the API): https://thesplit.fit/articles/automate-fit-file-fixes-with-an-ai-agent - Guide, how to connect Codex, Claude Code or Antigravity to The Split and fix a file by chatting (no commands to learn): https://thesplit.fit/articles/use-the-split-from-your-ai-assistant - Supporter wall (optional paid listing, funds hosting): https://thesplit.fit/supporters - Privacy: https://thesplit.fit/privacy - Terms: https://thesplit.fit/terms ## Markdown versions Every page listed under Key pages (except the API's interactive docs and OpenAPI file) is also available as clean Markdown (no HTML), generated from the same text the page shows. Two ways to ask: - Add `.md` to the page's URL: https://thesplit.fit/help.md, https://thesplit.fit/articles.md, https://thesplit.fit/articles/.md for every guide and article, and https://thesplit.fit/index.md for the homepage. Works for fetchers that cannot set headers. - Or request the normal URL with `Accept: text/markdown` (ranked above `text/html`, or named next to it at the same weight). Each document starts with the title, a one-line description, and `Canonical:` and `Last updated:` lines. Links are absolute and point at the HTML pages. Each Markdown answer names its HTML page in a `Link: <...>; rel="canonical"` header; cite that canonical URL. ## Notes for agents - Anonymous HTTP API, no key and no account: https://thesplit.fit/api/v1 - Machine-readable description (OpenAPI 3.1): https://thesplit.fit/api/v1/openapi.json - Health check: https://thesplit.fit/api/v1/health - Upload a file as multipart form field `file` (.fit, .tcx or .gpx, up to 15 MB) to POST /api/v1/activities. The response carries `activityId` and `expiresAt` (epoch ms). Files are held in server memory only and expire; nothing is written to disk. - Read-only calls return data and stage nothing; the input is never modified: - GET /api/v1/activities/:id: summary (sport, start, duration, distance, streams, warnings). - GET /api/v1/activities/:id/series: heart rate, pace, power, cadence or temperature over time. - GET /api/v1/activities/:id/route: simplified GPS polyline. - GET /api/v1/activities/:id/export?format=fit|tcx|gpx: download the file. - GET /api/v1/activities/:id/merge/detect and .../merge/auto-offset: inspect a merge (what the second file is, the clock offset). - POST /api/v1/activities/:id/merge/preview: preview a merge without staging it. - GET /api/v1/activities/:id/substitute-leg/detect: find the matching multisport leg. - POST /api/v1/activities/:id/autolaps/preview: preview automatic laps. - GET /api/v1/activities/:id/hr-glitches: find heart-rate spikes; POST .../hr-glitches/detect-range inspects one range. - Staging operations create a new activity and return its `activityId` (the input stays untouched): - POST /api/v1/activities/:id/merge/apply: merge a heart-rate strap or a second recording of the same ride. - POST /api/v1/activities/:id/crop: trim by time or distance. - POST /api/v1/activities/:id/split: returns two activities, `partA` and `partB`, each with its own `activityId`. - POST /api/v1/activities/concatenate: join activities end to end. - POST /api/v1/activities/:id/sport: relabel the sport. - POST /api/v1/activities/:id/move-boundary: move a multisport transition. - POST /api/v1/activities/:id/substitute-leg/apply: replace one multisport leg. - POST /api/v1/activities/:id/autolaps/apply: apply automatic laps. - POST /api/v1/activities/:id/hr-glitches/apply: repair heart-rate spikes. - DELETE /api/v1/activities/:id: discard a staged activity now. - Lifetime: every 2xx JSON response about a live staged activity carries `expiresAt` (epoch ms) in the body (for split, on `partA` and `partB`); export carries it in the `X-Activity-Expires-At` header. An activity expires 30 minutes after its last use and at most 2 hours after creation (defaults; the deployment may change them). - Clean up: DELETE /api/v1/activities/:id every activity you no longer need, including intermediate results. Uploads and operation results all count toward the per-client cap (12 by default); staging beyond it evicts your oldest derived result first, then your least recently used upload, and a later call using that id answers 404 `activity_evicted` (expired, deleted or unknown ids answer 404 `activity_not_found`); upload the file again. - Size: an upload may hold up to 80,000 records by default (about 22 hours at one record per second); a larger one, or a join that would be larger, answers 422 (`activity_too_large`; `details.maxRecords` is the limit in force). - Errors use the envelope `{ "error": { "code", "message" } }`. Requests are rate limited per client address and route class. A 429 (`rate_limited`), a 503 (`capacity_exceeded`) or a 503 (`server_busy`: the service is running as many heavy operations as it allows) carries a `Retry-After` header; honour it and send the same request again. Every refusal counts against the call's rate budget like any other answer. Health and openapi.json count against the same per-client `read` budget as activity reads, so do not poll them in a tight loop. - Usage counting: each call is counted in our self-hosted analytics with its route pattern, a status class, a coarse caller kind and a one-way token that changes every day; never your address, User-Agent, activity ids or files. MCP and workflow calls are counted the same way; an MCP connection also records the kind of app it says it is, from a short fixed list, never its name or version as written. See https://thesplit.fit/privacy. - Only /api/v1 is a stable contract. Do not script the site's other internal endpoints; they are not a public contract and may change without notice.