HealthSave vs Apple Health export: XML archive or usable CSV?
A balanced comparison of Apple Health’s built-in XML export and HealthSave’s CSV, JSON, PDF, API, and self-hosted sync paths.
Apple Health export is good for archival ownership
Apple’s built-in export is valuable because it is official and broad. It gives you a large XML archive of HealthKit records. If the job is “I want a raw archive in case I need it later,” that export matters.
Where the XML archive becomes painful
The file is large, nested, hard to inspect, and awkward for people who just want a CSV, a chart, a doctor-visit summary, a Grafana dashboard, or a Home Assistant sensor. Most users do not want to parse XML before answering a simple trend question.
Where HealthSave fits
HealthSave is for usable exports: CSV, JSON, PDF, category-specific views, and Pro self-hosted sync/API workflows. It is not trying to replace HealthKit as the system of record. It makes the data easier to move into tools you already use.
Recommendation
Use Apple Health export for a raw archive. Use HealthSave when the next step is analysis, dashboarding, sharing a readable summary, or piping selected metrics into your own infrastructure.