Google Health and Apple Health: how they differ and how to keep them in step
Updated 1 November 2026. Written by Minima Apps Ltd, the makers of Tandeo, so we mention Tandeo as one option. We try to be fair about the others.
Google Health is now where Fitbit data lives, and Apple Health is the place iPhone and Apple Watch data lives. They are separate systems, and as far as we know neither company's own app copies data across to the other, so keeping them in step takes a bridge app. This guide explains what Google Health is, how it relates to Fitbit, how it differs from Apple Health, and what your options are. Tandeo, from Minima Apps, is one of those options.
What is Google Health now?
Google Health is the new name for the Fitbit app and the home for Fitbit data. If you wore a Fitbit tracker or watch, your steps, sleep, heart rate and workouts are now associated with Google Health and a Google account. The App Store listing for the official app at the time of writing is called "Google Health (Fitbit)". Names and screens change, so check the current Fitbit / Google Health app for exactly how your own account looks.
How does Google Health relate to Fitbit?
Fitbit is the hardware and the brand you already know. Google Health is the app and the service that holds the data. Developers now reach Fitbit data through the Google Health API, which replaced the older Fitbit Web API. The old Fitbit Web API and Fitbit sign-in were turned off on 2 November 2026.
For you, this has one practical effect. An app that used to read your Fitbit data through the old connection stops working until its developer rebuilds it on the Google Health API. When it does, you usually sign in with your Google account and approve access again. If a connection you relied on has gone quiet, see Fitbit not syncing with Apple Health.
Google Health vs Apple Health: what is the difference?
Both collect health and fitness data in one place and let other apps contribute. The differences that matter for syncing are these.
| Google Health | Apple Health | |
|---|---|---|
| Where it runs | The Google Health app and Google's service, tied to a Google account | The Health app on iPhone, fed by iPhone, Apple Watch and other apps through HealthKit |
| Typical data source | Fitbit trackers and watches | iPhone, Apple Watch and apps you allow |
| How other apps connect | Google Health API, with a Google sign-in and your approval | HealthKit, with permission per data type on your device |
In short, they do the same kind of job for different ecosystems. If you use a Fitbit with an iPhone, your data ends up split between the two.
What does the Google Health API mean for third-party apps?
Any app that wants your Fitbit data now has to use the Google Health API. In practice that means three things for you as a user.
- Re-approval. You sign in with a Google account and approve what the app may read or write.
- Rebuilt apps. Apps that were not updated may no longer sync, and a stale app listing is not proof an app has been moved over. Check its release notes or description for Google Health support.
- Controlled access. Google reviews apps that ask for health data, so a new app can take time to become available to everyone. This is Google's process, not something a user can speed up.
The Google Health developer documentation describes the API for developers.
Can Google Health and Apple Health sync automatically?
As far as we know, no. Check the current Fitbit / Google Health app and Apple's Health app in case that changes. Today you need a third-party app that is allowed to read from one side and write to the other. For the step-by-step version, read how to sync Fitbit with Apple Health.
What can move in each direction?
The two directions are not symmetrical, and this surprises people. Google Health does not accept every type of data from other apps.
- Google Health to Apple Health: steps, distance, active energy, heart rate, resting heart rate, heart rate variability, blood oxygen, sleep with stages, weight, body fat and workouts.
- Apple Health to Google Health: only weight, body fat, workouts and sleep. Google Health does not accept steps or heart rate written by other apps, so no sync app can push those across.
If you wear an Apple Watch and a Fitbit and wonder why your Apple Watch steps never appear in Google Health, this is why. The details are in our guide to sending Apple Health data to Fitbit and Google Health.
How can I keep Google Health and Apple Health in step?
- Decide which side is the source for each kind of data. Fitbit steps and sleep usually start in Google Health. Weight from a smart scale might start in Apple Health.
- Pick a bridge app that uses the Google Health API. Check that it says so, shows which data types it copies, and explains where your data goes.
- Sign in with the Google account that holds your Fitbit data and approve only the data you want to share.
- Allow the matching permissions in Apple Health when iOS asks.
- Run a first sync manually, then check a few days of steps and sleep against the Fitbit / Google Health app.
Several apps do this job. Our comparison of Fitbit and Apple Health sync apps looks at the main ones.
Syncing with Tandeo
Tandeo is our two-way bridge between Google Health and Apple Health for iPhone and iPad. It runs on your device, needs no Tandeo account, and no developer servers receive your health data. It is coming soon to the App Store.
The free plan covers steps and sleep from Google Health to Apple Health with manual sync. Pro is $2.99 a month or $14.99 a year (the yearly plan has a 1-week free trial), and Lifetime is a one-time $29.99 with background auto-sync and 2 years of history. See Tandeo pricing for the plans, and the data Tandeo syncs for the full list.
Why can sync be delayed or duplicated?
iOS decides when background work runs, based on battery, connectivity and how you use the app, so any sync app can be delayed. Opening the app and syncing manually always works. If two apps write the same kind of data into Apple Health, the Health app combines sources using a priority list you can reorder under the data type, then Data Sources & Access. Tandeo also tracks what it has already written in each direction so it does not copy records back and forth.
Questions about privacy are covered in the privacy policy, and you can reach us through support.
Tandeo is not affiliated with, endorsed by or sponsored by Google, Fitbit or Apple.
Frequently asked questions
What is Google Health?
Google Health is the new name for the Fitbit app and the place where Fitbit data now lives, tied to a Google account. Check the current Fitbit / Google Health app for how your own account and screens look.
Is Google Health the same as Fitbit?
Not exactly. Fitbit is the hardware and brand. Google Health is the app and service that holds the data, and developers reach it through the Google Health API, which replaced the old Fitbit Web API turned off on 2 November 2026.
Does Google Health sync with Apple Health?
As far as we know, neither company's own app copies data between them. Check the current Fitbit / Google Health app and Apple's Health app in case that changes. A third-party bridge app such as Tandeo can read from one and write to the other.
Why can't I send my Apple Watch steps to Google Health?
Google Health does not accept steps or heart rate written by other apps. From Apple Health to Google Health, only weight, body fat, workouts and sleep can be sent.
What does the Google Health API change for my sync apps?
Apps that used the old Fitbit connection must be rebuilt on the Google Health API. You usually sign in with your Google account and approve access again. Apps that were not updated may no longer sync.
Is Tandeo available yet?
Tandeo is coming soon to the App Store and is not available yet. It is made by Minima Apps and is not affiliated with Google, Fitbit or Apple.