When exactly does Google Fit stop working?

Google's documentation says Fit APIs 'will be supported until the end of 2026' — that is the most specific commitment published, verified against developer.android.com as of July 2026. There is no announced day or month. Treat the end of support as the point after which breakage goes unfixed rather than a guaranteed switch-off date, and plan to be off Fit well before December 2026, because a migration under deadline pressure is where data gets lost.

Does the Google Fit app on my phone stop too?

This page is about the developer APIs — the Android SDK and the REST API that apps integrate. Google has communicated app-side changes separately, and the app is outside our scope as a developer site. What is documented for developers is that all Fit API surfaces, including the REST API, are supported only until the end of 2026, and that new developer signups already closed on May 1, 2024.

Which Google Fit successor applies to which integration?

Match the successor to where your integration runs, not to feature lists. An Android app reading on the device moves to Health Connect. A backend calling the Fit REST API has no URL-swap option, because Health Connect has no server endpoint — it moves to Google's newer cloud surface, to an aggregator in front of the devices, or to an app-reads-locally-and-syncs design. Wear OS capture moves to Health Services. Multi-vendor products should consider consolidating behind one aggregator instead of migrating Fit in isolation.

We built on Fit years ago and it still works. Can we wait?

You can, but the economics get worse every month. The platform is frozen — no new signups since May 2024 means no new provider features, and after support ends, anything that breaks stays broken. Teams that migrate early do it calmly with both systems running in parallel; teams that migrate in November 2026 do it under pressure with users watching. Our migration guide covers running the old and new paths side by side so nothing is lost.

Migration Event

Google Fit Is Shutting Down

Google documents that all Google Fit APIs — including the REST API — are supported only until the end of 2026, and new developer signups closed on May 1, 2024. There is no drop-in replacement: where you migrate depends on how you used Fit. On-device reads go to Health Connect, server-side REST usage needs Google’s newer cloud surface or an aggregator, and Wear OS capture goes to Health Services.

The verified timeline

May 1, 2024 — signups closed
No new developer projects can onboard to Fit. Existing projects keep working.
Now — the parallel-running window
The time to migrate calmly: run Fit and its successor side by side, reconcile the data, and cut over when the numbers agree. This window shrinks every week.
End of 2026 — support ends
Google’s exact words: Fit APIs “will be supported until the end of 2026.” No day or month is published — and a plan that depends on the exact date has already failed. (Verified against developer.android.com, July 2026.)

Where you migrate depends on how you used Fit

Android app reading fitness data on the device

→ Google Health Connect

The documented successor for on-device reads. Follow the migration playbook and the Health Connect integration guide. Budget for the semantic differences — permissions, the limited read-history window, and changed data types; the type reference maps them.

Backend calling the Fit REST API

→ Google's newer Health API surface, or an aggregator

The hard case: Health Connect has no server endpoint, so there is no URL swap. Either move to Google’s cloud-side successor for account-level data, or put a health-data aggregator in front of the devices you care about, or have your app read Health Connect locally and sync to your backend — the sync architecture guides cover doing that without corrupting history.

Wear OS app

→ Health Services

Google’s documented path for watch-side capture. Then decide separately how watch data reaches your backend — that is the same on-device-store problem as above, not a Fit-specific one.

Multi-vendor product (Fit was one of several sources)

→ Consolidate behind an aggregator

If you were juggling Fit alongside Fitbit, Garmin or Oura integrations, the turndown is the natural moment to consolidate behind one aggregator instead of migrating one integration and keeping four. And if one of those sources is the legacy Fitbit Web API, note that it has its own, separate retirement on a reported ~September 2026 timeline — the Fitbit API shutdown page keeps the two events apart.

Two pages to go deeper

If you landed here from a deprecation notice and want the immediate triage, start with the Google Fit deprecation fix page. When you’re ready to execute, the step-by-step migration playbook covers the parallel-run, reconciliation, and cutover — including keeping users connected while you move.

Frequently asked questions

When exactly does Google Fit stop working?: Google's documentation says Fit APIs 'will be supported until the end of 2026' — that is the most specific commitment published, verified against developer.android.com as of July 2026. There is no announced day or month. Treat the end of support as the point after which breakage goes unfixed rather than a guaranteed switch-off date, and plan to be off Fit well before December 2026, because a migration under deadline pressure is where data gets lost.
Does the Google Fit app on my phone stop too?: This page is about the developer APIs — the Android SDK and the REST API that apps integrate. Google has communicated app-side changes separately, and the app is outside our scope as a developer site. What is documented for developers is that all Fit API surfaces, including the REST API, are supported only until the end of 2026, and that new developer signups already closed on May 1, 2024.
Which Google Fit successor applies to which integration?: Match the successor to where your integration runs, not to feature lists. An Android app reading on the device moves to Health Connect. A backend calling the Fit REST API has no URL-swap option, because Health Connect has no server endpoint — it moves to Google's newer cloud surface, to an aggregator in front of the devices, or to an app-reads-locally-and-syncs design. Wear OS capture moves to Health Services. Multi-vendor products should consider consolidating behind one aggregator instead of migrating Fit in isolation.
We built on Fit years ago and it still works. Can we wait?: You can, but the economics get worse every month. The platform is frozen — no new signups since May 2024 means no new provider features, and after support ends, anything that breaks stays broken. Teams that migrate early do it calmly with both systems running in parallel; teams that migrate in November 2026 do it under pressure with users watching. Our migration guide covers running the old and new paths side by side so nothing is lost.

Timeline facts verified against Google’s developer documentation on July 31, 2026. Deprecation communications change — check Google’s current guidance before committing a migration plan.