Fitbit not syncing with Apple Health? A step-by-step fix
Updated 1 November 2026. Written by Minima Apps Ltd, the makers of Tandeo, so we mention Tandeo as one option among several fixes.
If Fitbit has stopped syncing with Apple Health, the most likely cause is the shutdown of the old Fitbit Web API on 2 November 2026. Apps that read your Fitbit data through it have to be rebuilt on the Google Health API, and you have to sign in again with a Google account. The checklist below starts with the quick checks and works up to the fixes that need a bit more digging.
Why did Fitbit stop syncing with Apple Health?
Fitbit data now lives in Google Health. The old Fitbit Web API, together with Fitbit sign-in (OAuth), was turned off on 2 November 2026. Many sync apps relied on that service to read your data, so a connection that worked for years can simply stop, even though your phone and your tracker are fine.
It helps to know what the problem is not. Apple Health and Google Health are separate systems, and as far as we know neither the Fitbit app nor the Health app copies data across to the other by itself. Check the current Fitbit or Google Health app in case that changes. Copying needs a third-party bridge, and that bridge needs to use the new Google Health API. Our overview of how Google Health and Apple Health fit together explains the background.
How do I fix Fitbit not syncing with Apple Health? A step-by-step checklist
Work through these in order. Each one is quick, and stopping as soon as data reappears saves time.
1. Make sure the Fitbit device syncs to its own app first
A bridge can only pass on what Google Health already has. Open the Fitbit or Google Health app that came with your tracker and check that today's steps and last night's sleep appear there. If they do not, the problem is between your device and its own app, not Apple Health. Look for a sync option in that app, check Bluetooth is on, and follow the current Fitbit or Google support instructions for pairing problems.
2. Check your Fitbit account is linked to a Google account
Fitbit data is moving to Google accounts, and apps that use the Google Health API sign you in with Google rather than with Fitbit. If you are still on a Fitbit-only account, check Google's current instructions for linking or moving it. The steps change, so follow the up-to-date guidance on Google's support site rather than an old tutorial. The developer side is described at developers.google.com/health.
3. Reconnect through Google Health sign-in in your sync app
An old connection made with Fitbit sign-in will not come back to life. In your sync app, disconnect the old account if there is an option, then connect again using the Google Health sign-in and choose the Google account your Fitbit data now lives in. If your app does not offer Google sign-in yet, it has probably not been updated for the change. That is a question for its developer, and we cannot say how other apps work internally.
4. Approve every permission when Google asks
During sign-in Google shows a list of the data the app wants to read, such as activity, sleep or heart rate. If you untick any of them, those data types simply will not arrive, and the app may look as if it is working while one category stays empty. Reconnect and approve all the data types you want synced. You can change this again later in your Google account settings.
5. Check HealthKit permissions in the Health app
Writing into Apple Health is a separate permission. On your iPhone, open the Health app, tap your profile picture, then look for Sharing and Apps (Apple has reworded these menus over the years, so check support.apple.com for the current names on your iOS version). Pick your sync app and make sure the categories you want, for example steps, sleep or heart rate, are switched on for writing.
6. Check Background App Refresh and Low Power Mode
iOS decides when apps get to work in the background. Check Settings > General > Background App Refresh is on for your sync app, and remember that Low Power Mode pauses most background activity. Even with everything on, timing is up to the system and a sync can be late. Opening the app and syncing manually avoids that wait.
7. Look for duplicate data and source priority
Sometimes the data did arrive but looks wrong. If your iPhone, an Apple Watch and a sync app all record steps, Apple Health combines them using a source priority list. In the Health app, open the data type, then Data Sources & Access, and reorder the list so the source you trust most comes first. A sync app can only be as good as the data it is handed, and doubled totals usually come from two devices recording the same walk.
| What you see | Check first |
|---|---|
| Nothing new since the Fitbit change | Reconnect with Google Health sign-in (step 3) |
| Steps arrive but sleep does not | Approved data types and HealthKit write access (steps 4 and 5) |
| Data arrives late | Background App Refresh and Low Power Mode (step 6) |
| Numbers are doubled | Source priority in Health (step 7) |
| Missing in Google Health too | Device sync to its own app (step 1) |
What can I do if my sync app is not updated for Google Health?
You have three honest options. Wait for the app to be updated, switch to an app already built on the Google Health API, or use Fitbit and Apple Health separately for now. Our comparison of Fitbit to Apple Health sync apps lists the alternatives, and the full walkthrough in how to sync Fitbit with Apple Health covers the setup from scratch.
How does Tandeo handle this?
Tandeo is our iPhone and iPad app. It is built on the Google Health API and works as a two-way bridge between Google Health and Apple Health. It runs on your device, has no Tandeo account, and no developer servers receive your health data.
- From 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.
- From Apple Health to Google Health: weight, body fat, workouts and sleep only, because Google Health does not accept steps or heart rate from other apps. More in sending Apple Health data to Fitbit.
Free covers steps and sleep from Google Health to Apple Health with manual sync. Pro is $2.99 a month or $14.99 a year, and the yearly plan has a 1-week free trial. Lifetime is a one-time $29.99 and adds background auto-sync and 2 years of history. See the Tandeo plans and pricing. Background timing is still up to iOS, but manual sync always works. The App Store listing is coming soon, and it is not live yet.
Still stuck?
Tell us what you see on the support page, and read how we treat your data in the privacy policy. If the issue is on the Fitbit or Google side, their own support is the right place.
Tandeo is not affiliated with, endorsed by or sponsored by Google, Fitbit or Apple.
Frequently asked questions
Why did my Fitbit stop syncing with Apple Health?
The old Fitbit Web API was turned off on 2 November 2026, and many sync apps depended on it. Apps have to move to the Google Health API, and you usually need to sign in again with a Google account and approve access. Check your tracker syncs to its own app first, then reconnect your sync app.
Does the Fitbit app sync to Apple Health on its own?
As far as we know, no. Apple Health and Google Health are separate systems and neither company's app copies data to the other by itself. Check the current Fitbit or Google Health app in case that changes. A third-party bridge that uses the Google Health API is needed.
I reconnected but some data is missing. Why?
Usually a permission was not approved. When you sign in with Google you choose which data types to share, and skipped ones will not sync. Reconnect and approve them all, then check in the Health app that the sync app is allowed to write those categories.
Why is my Fitbit data duplicated in Apple Health?
More than one source may be recording the same activity, for example an iPhone, an Apple Watch and a sync app. In the Health app, open the data type, choose Data Sources & Access and put your preferred source first.
Can Tandeo fix Fitbit not syncing with Apple Health?
Tandeo is built on the Google Health API and copies data between Google Health and Apple Health on your device. It cannot fix a tracker that does not sync to its own app. The App Store listing is coming soon, so it is not available yet.
Why does background sync sometimes run late?
iOS decides when apps run in the background based on battery, connectivity and usage, and Low Power Mode pauses most of it. Any sync app can be delayed. Opening the app and syncing manually always works.