No results for “”.
Try different keywords, or email hello@healthexport.app.
If the CSV looks empty or sparse, two things to check first:
If the data is visible in Apple Health but still doesn’t export, email me at hello@healthexport.app with a screenshot and your app + iOS version.
Weight, individual blood pressure readings, and raw heart rate samples all live under Record based types rather than aggregated ones:
Aggregated exports give you summaries (e.g. average heart rate per hour); record-based exports give you the individual readings. If you only need one of these, disable everything else first so the CSV stays focused.
Apple Health stores sleep as stages — Awake, REM, Core, Deep, In Bed — rather than as a single nightly total, so one night may appear as multiple rows.
This is how Apple’s data model works, not a HealthExport bug. For a single value per period, use the Time asleep aggregated type instead.
HealthExport can only export data that’s already in Apple Health. If your wearable or third-party app writes its data to Apple Health, it’ll show up in the export.
If the data isn’t in Apple Health (some apps don’t write everything they record), HealthExport can’t recover it — check Apple Health first to see what’s actually stored.
Yes, if the original workout source wrote the route to Apple Health. Enable Workout Routes in HealthExport’s permissions, then export your workouts — routes are included as GPX files alongside the workout CSV.
If routes are missing, check Apple Health first to confirm they’re stored there. Non-workout location history is not exportable through this path.
No. HealthExport produces a CSV file, designed for analysis in spreadsheets (Excel, Numbers, Google Sheets). If you want charts or a polished report, build one from the CSV in your spreadsheet of choice, or use a HealthExport Remote dashboard for in-browser visualizations.
TL;DR: Health data is end-to-end encrypted between your phone and your browser, so nobody except you can read it. The app does not collect any analytics or crash data.
For more information visit the HealthExport Remote Privacy White paper.
HealthExport Remote lets the user share health data with another person (for example a doctor) by sharing user’s account key. See the data sharing section for more information. The account key cannot be revoked or changed, so the User should be careful with their account key and never share it with an untrusted person. When health data is shared with another person, the data is end-to-end encrypted between user’s phone, user’s browser, and the browser of the person that has been given the account key by the user.
You can share access to your health data with another person (for example a doctor). To share your data, send the person your account key. Be extremely careful with your account key! The key cannot be revoked in the future. Once you send the key to someone, the person can read all of your health data.
To get your account key, or to connect an account key of another person, go to Settings → Data sharing on the Remote website.
Both, depending on which part you use:
I would like to offer Remote as a free feature to all HealthExport users, but there are monthly costs associated with running and maintaining the Remote server. A monthly subscription is unfortunately the only financially sustainable business model for me at this moment.
Yes, you can cancel the subscription at any time. For more information see the guide on Apple’s website. If the subscription is canceled, you will retain access to HealthExport Remote for the rest of the prepaid time period. Your access to the HealthExport Remote website will be revoked when the subscription ends.
Refunds for App Store purchases — both the app and Remote subscriptions — are handled by Apple, not me directly. You can request a refund through Apple at reportaproblem.apple.com.
Yes, it’s possible to license HealthExport Remote for business use (for example as a fitness coach or a clinic). For more information about business use please reach out at hello@healthexport.app.
At this moment, Remote supports all data types found in the mobile application except:
I plan to add support for these types as soon as possible.
Generally speaking, the aggregated data is synced once an hour and the record based data is synced within a few seconds/minutes after it has been inserted into the Health app.
The precise time period of background data upload depends on many factors such as your iOS version, iPhone model, battery level, etc.
Yes. The mobile app has a manual upload feature, which allows you to manually upload health data from a selected time period.
Yes, there is an API.
User’s privacy is a top priority of mine. The data is end-to-end encrypted. This unfortunately means that you can get only encrypted data through the API and you need to decrypt it on your side. HealthExport uses ChaCha20 and Poly1305 algorithms for data encryption and there are many open-source libraries for ChaCha20 Poly1305 data encryption/decryption for most popular programming languages.
API documentation: remoteapi.healthexport.app/api/v2/docs
Yes. HealthExport Remote has an open-source CLI that works well with Terminal, scripts, Codex, Claude Code, and other automations.
The CLI fetches encrypted health records and decrypts them locally on your machine after you authenticate it with your account key.
You can find the CLI repository and installation instructions on GitHub. The setup steps for AI tools are also available on the AI agents page.
Yes, HealthExport works with Apple Shortcuts — with one important limitation: iOS doesn’t reliably grant access to Health data while the phone is locked, so fully unattended, time-scheduled exports may fail.
For reliable background automation, HealthExport Remote is a better fit — it syncs in the background and you can pull data via its CLI or API at any time.
Still have a question? Email hello@healthexport.app.
