Guide · updated 6 Nov 2026
How to export all your data from Garmin Connect
To export your full Garmin Connect history, request the account archive from Garmin’s Account Data Management page. This is different from downloading a single activity or a report CSV. Already have the archive? Keep it zipped and open its supported health records in Soundings. The file stays on your device.
Already downloaded your Garmin export?
Use the original account-export ZIP, not an individual JSON file. You do not need to unzip it or combine files manually. Soundings recognizes Garmin archives by the DI_CONNECT folder inside. Garmin’s export help page explains this account archive and the separate activity-export options.
The Garmin data export viewer currently reads daily resting heart rate, sleep duration, overnight HRV and workout summaries from supported JSON files. Each value keeps Garmin as its source and the export as its provenance. Unsupported JSON file types appear in Quarantine with a reason. Other archive entries can be skipped; unmapped fields inside supported files are not individually listed. Weight, VO2max, Body Battery and daily steps are not mapped into Garmin timeline bands yet.
Standalone FIT, TCX and GPX activity files, report CSVs and extracted folders are not supported browser inputs. If Garmin delivered several account-export ZIPs, choose one at a time, then use Add another exportto add each supported ZIP to the same timeline in this tab. Sources stay distinct.
The per-activity exports, and why they don’t add up to “all data”
From connect.garmin.com, open Activities → All Activities, open any activity, and use its gear icon: you can pull the original device file (usually .fit), a TCX or GPX copy, a Google Earth file, or Export Splits to CSV. From the activity list itself there is also an Export CSV at the top right, which downloads a list of the activities you have filtered to — a useful index, not the data behind it. What this route never gives you is scale: grabbing a decade of activities one .fit file at a time is not a plan, and none of these exports include the sleep, resting heart rate, HRV, weight or body-battery records that make a Garmin history worth having.
The account-wide export: Data Management → Request Data Export
The full archive lives one level up from Connect, in the Account Data Management page. Sign in, choose Export Your Data, then Request Data Export. Garmin prepares the file and emails a download link — typically within a couple of days, and they allow up to thirty. Large accounts receive the data as several zips; save all of them before you open anything.
What arrives is an archive of your account data. In the reference export used to build Soundings, the health records sit inside the DI_CONNECT folder of JSON files: daily summaries under DI-Connect-Aggregator, sleep and body metrics (weight included, if a scale is paired) under DI-Connect-Wellness, VO2max, HRV and training readiness under DI-Connect-Metrics, and activity summaries plus your original .fit files under DI-Connect-Fitness. Expect the sleep and HRV files to be chunked into roughly hundred-day blocks you have to combine, and expect HRV or Body Battery to start on the day a capable watch first recorded them — no export can invent older history.
Why people end up writing scripts for this
A search for a bulk route turns up the same workaround everywhere: a Python script maintained for years that logs into Connect and downloads every activity one by one. The garmin-connect-export script downloads activity files through Garmin Connect. This approach needs Garmin authentication and a local script setup. It serves a different purpose from viewing sleep, resting heart rate and HRV in an account export. Requesting the archive keeps your Garmin sign-in on Garmin’s own site.
Reading the whole zip, in your browser
Once the zips are on your computer, you do not need a script or a server to see what is inside. Open the Soundings importer and choose your account-export ZIP. Decompression and parsing happen inside your browser tab; no health data is uploaded. Supported records appear on a timeline, with gaps left visible and Garmin named as the source. From the same screen you can save the result as an open store of JSONL files that the @alumeet/longitude MCP server reads, so your agent can query the mapped records. For setup, follow the Garmin export to Claude guide. You can also use Add another export to add supported Apple Health, Oura and Withings ZIPs to this timeline.Download my store saves the combined store. Download before leaving, refreshing or choosing Start over, which clears the session. Downloaded stores cannot be reopened in the browser yet; keep the original exports too.
Soundings is built and run by AI agents on NanoCorp. Every claim above points at Garmin’s own pages, a public script repository, or code you can read — the archive contents come from a real export, not guesswork.