Your Apple Watch records a lot of useful detail on every run, ride, and swim — but getting it into a file you can actually open is harder than it should be. This is a practical guide to export Apple Watch workout data into formats you can analyze, share, or archive, without building any infrastructure.
There are two broad ways to get workout data off your iPhone. One is the developer path: parse Apple's full Health archive, build a pipeline, maybe stand up a small server, and feed the results to a model. The other is the practical path: produce clean per-workout files — CSV, GPX, TCX, JSON, or PDF — and use them directly. This article is about the second path, which is what most people actually want. If you want a quick start, you can export Apple Watch workout data as files and skip the parsing entirely.
Apple does let you export your data. In the Health app, "Export All Health Data" produces a single large archive — primarily an Apple Health XML export plus separate route files. It is comprehensive, and it is genuinely useful if you are a developer building something custom.
But for ordinary workout analysis it is awkward. The Apple Health XML export bundles every health record you have ever recorded — steps, sleep, heart rate, mindfulness, and more — into deeply nested XML, with GPS routes stored as separate files. If your goal is a simple spreadsheet, a GPX route, a TCX file, a JSON object, or a one-page coach report, you do not need any of that. You need workout-level data, not your entire health history.
Most workout workflows only require a handful of fields per session:
That is a much smaller problem than "parse my entire Health archive," and it is the problem worth solving directly.
If you live in Excel, Numbers, Google Sheets, or a Python notebook, CSV is the natural format. A summary CSV gives you one row of stats per workout; a samples CSV gives you the raw time series for charts and pivot tables. No parsing, no add-ons — just open the file. See the Apple Watch to Excel walkthrough for the exact steps.
Large language models read structured data well. Export a workout as CSV or JSON, attach it to a chat, and ask questions in plain language. JSON keeps the most structure; CSV is the easiest to skim. Some example prompts that work well with ChatGPT or Claude:
If this is your main goal, the dedicated guide on how to analyze Apple Watch workout data with AI goes deeper.
Sharing data with a running coach, cycling coach, triathlon coach, physical therapist, or personal trainer usually does not call for raw records. A PDF report — route map, summary cards, a heart-rate chart, and a stats table on one page — is easy to read and easy to email. A CSV works well when a coach wants to load your sessions into their own tools.
GPX and TCX are the standard portable formats for route-based workouts. GPX carries the GPS track with heart rate; TCX adds structured laps and metrics like cadence and power. They are useful for mapping, for archiving a route, and for importing into fitness platforms where that is supported.
If you are moving to a new device or want a portable history, exportable files help. You can upload a GPX or TCX file to Garmin Connect, Strava, or TrainingPeaks manually, where the platform supports it. Field-level import varies depending on the platform, so this is best treated as a manual workflow rather than an automatic sync — useful for recovering a missed activity or bringing older Apple Watch workouts into a new account. See the guides for sending workouts to Garmin Connect and Strava.
Developer-focused projects are a good reference for what is possible at the technical end — for example, this developer-oriented Apple Health AI workflow walks through turning Health data into insights with a custom pipeline. That approach is powerful if you are building a technical system around your data. Here is the simpler path if you mainly need exportable workout files.
Workout Data Exporter is built for the simpler version of this problem: exporting Apple Watch / Apple Health workouts into files you can actually use. It reads your workouts on your iPhone and writes them as GPX, TCX, CSV, JSON, and PDF — no Apple Health XML export to parse, no server, no account. You can see the full feature set on the Workout Exporter site.
Available on the App Store: Workout Data Exporter on the App Store.
Three honest options, depending on what you are trying to do:
Workout and health data is personal. If you plan to upload files to ChatGPT, Claude, or any third-party service, share only the data you are comfortable sharing, and check that service's data-handling terms first. CSV, JSON, and PDF files are portable by design — which is the point — but that also means a file can be copied and forwarded once it leaves your device. Store and share exports with the same care you would any sensitive document, and keep medical questions with a qualified professional rather than a chatbot.
If you are building a full health-data platform, the Apple Health XML export and developer tooling may be exactly right. But if you just want your Apple Watch workouts in GPX, TCX, CSV, JSON, or PDF — for AI analysis, a spreadsheet, a coach, or a manual upload to another platform — a workout-specific exporter is the faster, simpler route.
Turn any Apple Watch or Apple Health workout into GPX, TCX, CSV, JSON, or PDF — on device, one-time purchase, no subscription. See how it works.
Download on the App StoreNo. The Apple Health XML export is a full archive meant for developers. If you only want workout-level data, a workout-specific exporter can produce CSV, JSON, GPX, TCX, or PDF directly, with no parsing.
CSV is the most accessible, and JSON preserves the most structure. Both can be shared with ChatGPT or Claude so you can ask for summaries, trends, and training reports. Share only the data you are comfortable uploading.
Exporting GPX or TCX files gives you portable workout files you can upload manually where the platform supports it. Field-level support varies by platform, so treat it as a manual workflow rather than an automatic sync.
No. Apple Health and HealthKit remain the source of your data. An exporter simply reads workouts on your iPhone and writes them into files you can use elsewhere.
