Google Health ends Fitbit login support

What changed and when

Google Health announced that the ability to sign in using Fitbit credentials will be removed. The update was rolled out in early September 2026. Existing connections between Fitbit accounts and Google Health were automatically disconnected, and users are now asked to choose a different sign in method.

Why the decision matters

The removal of Fitbit login affects three main groups: users who rely on a single sign in for health data, developers who build apps around the integration, and the broader digital‑health ecosystem that depends on seamless data flow.

Impact on everyday users

Loss of automatic data sync between Fitbit devices and the Google Health dashboard.
Need to re‑enter health information manually or connect through a third‑party platform.
Potential interruption of health insights that depend on continuous tracking.

Effect on developers

Applications that previously accessed Fitbit data via the Google Health API must now update authentication flows. Many developers will need to adopt the Fitbit Web API directly, which requires separate OAuth tokens and different rate limits.

Industry implications

Google’s move signals a shift toward tighter control over data partnerships. Analysts note that the decision aligns with recent regulatory scrutiny over how large tech firms handle personal health information.

Background of the partnership

Google and Fitbit have collaborated since Fitbit became part of Google in 2021. The integration allowed users to view step counts, heart rate trends, and sleep metrics within the Google Health app. Over the years, the partnership faced criticism for data privacy concerns, especially after the 2023 U.S. Department of Health and Human Services privacy guidance highlighted the need for clear consent when sharing health data across platforms.

Official statements

Google’s blog post explained that the change is part of a broader effort to simplify authentication and enhance security. The statement emphasized that users can still connect Fitbit devices to Google Health by using the Fitbit app as an intermediary.

Fitbit’s support page reassured customers that their data remains safe and that alternative sync options are available. The page also provides step‑by‑step instructions for setting up the new connection method.

How to transition your data

Users who want to continue viewing Fitbit data in Google Health should follow these steps:

Open the Fitbit app and verify that all recent activity is synced.
Navigate to the settings menu and select "Connect to Google Health".
Complete the sign in process using a Google account rather than Fitbit credentials.
Allow the requested permissions for data sharing.
Check the Google Health app to confirm that metrics appear correctly.

If any issues arise, the Fitbit help center offers troubleshooting tips and a contact form for personalized assistance.

Privacy considerations

Separating the login processes may reduce the amount of data that moves between the two services without explicit user consent. Privacy advocates argue that this could be a positive step toward greater transparency.

However, the change also means that users must manage two separate accounts, which could increase the risk of weak passwords or forgotten credentials. Security experts recommend using a password manager and enabling two‑factor authentication on both Google and Fitbit accounts.

Alternatives for health data aggregation

Several platforms offer similar aggregation capabilities without relying on a direct Fitbit login:

Apple Health – integrates with a wide range of wearables and provides a unified view on iOS devices.
Samsung Health – supports many Android wearables and offers robust analytics.
Microsoft HealthVault – focuses on enterprise solutions and medical record integration.

Each alternative has its own privacy policies and data export options, so users should compare features before switching.

What the future may hold

Analysts predict that Google will continue to refine its health ecosystem, possibly prioritizing partnerships that align with its broader AI and cloud strategy. The company has hinted at upcoming features that leverage machine learning to provide personalized health recommendations, but those are expected to rely on data sources that are directly managed within Google’s own services.

For Fitbit, the focus appears to be on strengthening its own app ecosystem and expanding third‑party integrations through the Fitbit Web API. The company recently announced new developer tools that aim to simplify data access for fitness and wellness apps.

Overall, the removal of Fitbit login from Google Health reflects a growing emphasis on data sovereignty and regulatory compliance. Users who adapt quickly can still enjoy a seamless health tracking experience, while the industry watches to see how other tech giants respond to similar pressures.