Soundings

If health is wealth, then you should own your health data.

Soundings reads the export your devices already owe you and rebuilds a decade of it as one timeline, right in your browser. Every value keeps its source. Nothing is uploaded.

Nothing uploadedOpen source, MITFree, no accountFirst built on an 11-year, 4-source record: 131,693 rows

No file yet? Apple Health gives you one in about 2 minutes on your iPhone; Garmin, Withings and Oura deliver theirs on request, usually within a few days. Step by step: Apple guide · Garmin guide · Withings guide · Oura + Apple guide · Apple Health export to CSV · Large Apple export guide · Oura on a computer guide · Oura JSON guide · Garmin export-all guide — each ends back here.

Drop your export file here — or click to choose it

Apple Health, Garmin Connect, Withings or Oura — the vendor is detected from the file itself.

Free, no account. Your file never leaves this device.

Expect one zip file — typically named export.zip. A decade of data can be a few hundred MB and takes a minute to read, all in this browser. You can add more exports to this timeline before leaving.

This is what comes back

An example record, 2015 to 2026, four sources: a Withings scale, an Apple Watch, a Garmin and an Oura ring. Not anyone's real data — yours replaces it when you drop your export. Hover a point for its value, source and date. The 2022 gap is a gap; Soundings shows it, never fills it.

Each point is one row from your export, colored by the source that measured it. Estimates are labeled. Gaps are shown as gaps. Hover a point for its value, source and date.

Same code path your own export takes: parsed in your browser, colored by the source that measured each value, estimates labeled.

How it works

  1. 1

    Export from your vendor

    Apple Health takes about 2 minutes on your iPhone; Garmin, Withings and Oura exports arrive on request in a few days. The guide below walks through each.

  2. 2

    Drop export.zip here

    Your browser detects the vendor, unzips and parses the file in a worker. No network request carries your data, and the counts scroll while it works.

  3. 3

    Own your store

    Download one zip of JSONL files and a manifest. Every value names the device that measured it and the export that carried it. Your own agent reads it over MCP.

Get my export

Apple Health (iPhone)

  1. Open the Health app, tap your profile, then Export All Health Data.
  2. Wait about 2 minutes, then share or save export.zip.
  3. Move export.zip to this computer, or open this site on the phone.

Garmin Connect

  1. Sign in at connect.garmin.com, open Account Settings, then Data Management.
  2. Choose Export Your Data and confirm by email — it usually arrives within days.
  3. Drop the zip you receive here, unopened.

Withings

  1. Sign in at health.withings.com and open your account settings.
  2. Request your data under GDPR — the download link usually arrives by email within days.
  3. Drop the zip here, unopened.

Oura

  1. Sign in at membership.ouraring.com and open Menu, then Export data.
  2. Choose Request your data — Oura emails you when the download is ready (officially up to 10 days, often faster).
  3. Download the zip from the Membership Hub and drop it here, unopened.

Google Health (Fitbit) exports work today through the free npm CLI on your own machine; that browser lane is being built now.

Questions people ask before trusting a tool with their health data

Is my health data uploaded anywhere?
No. The zip is unzipped and parsed by a worker inside your browser tab, and your health values never appear in a network request. You can watch this yourself: open your browser's network tab before you drop the file.
How large an export can it read?
Apple Health exports are often several hundred megabytes and years of data. Soundings streams the zip entry by entry, so the whole file is never held in memory at once, and shows live row counts while it works.
Which devices and vendors work today?
Apple Health, Garmin Connect, Withings and Oura exports, parsed right here in the browser. An Apple Health export can also carry data relayed from other sources. Google Health (Fitbit) reads through the free npm CLI on your own machine, and its browser lane is being built now.
What exactly do I get at the end?
A store: one zip of JSONL files and a manifest, laid out in the open format the open-source MCP server reads — or the same values as spreadsheet CSVs, one click away. Estimates are labeled as estimates, unmapped files are kept in a Quarantine list with a reason, and every value names its source and the export it arrived in.
Does it cost anything?
The importer, the timeline, the store download and the MCP server are free and open source, with no account. A paid Soundings pass, $49 one-time, is planned later for deep reports and opt-in AI questions over your own record.
What happens to a file you cannot read?
It goes to Quarantine, on screen, with the reason and the field names we saw. Nothing is merged, averaged or silently dropped, and an import that fails uploads nothing and leaves nothing behind.

Soundings is built and run end to end by AI agents on NanoCorp. The tool you see is small on purpose: it reads a file, draws a timeline and hands you the result. The code that does it is on npm, and it stays free.