When exactly does Google Fit stop working?

Google's Fit migration guide says the Fit APIs 'will be supported until the end of 2026' — that is the most specific commitment published, re-checked on developer.android.com on October 2, 2026 (the guide was last updated September 10, 2026). There is no announced day or month, and no switch-off date. Treat it as end of support: the point after which Google has committed to nothing, rather than a date on which requests are guaranteed to fail. 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 that apps integrate, and the consumer app is outside our scope as a developer site. Google's Fit migration guide gives no date for the app. It says apps that let users connect to the Google Fit app can keep maintaining that integration for current users, and that Google will update that section with information on when to deprecate it. What it documents for developers is that the Google Fit API, including the REST API, will only be supported until the end of 2026.

Which Google Fit successor applies to which integration?

Match the successor to how your integration uses Fit, not to feature lists. Google's Fit migration guide recommends the Google Health API for cloud-based integrations, and lists it for the Fit History and Session APIs. Reading mobile steps through the Recording API moves to Health Connect, which the guide describes as on-device storage with no OAuth. Fit on Wear OS moves to Health Services. The Goals API has no replacement API. Multi-vendor products should also 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 until the end of 2026, but the economics get worse every month. Google's guide recommends migrating and states support only until the end of 2026; after that, assume anything that breaks stays broken, because Google has not said otherwise. 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 the Google Fit APIs — including the REST API — will be supported only until the end of 2026. That is end of support: Google publishes no switch-off date. There is no drop-in replacement: Google’s Fit migration guide recommends the Google Health API for cloud-based integrations, Health Connect for step tracking and mobile-first apps, and Health Services for Wear OS, and lists no replacement for the Goals API. When we checked on July 31, 2026, Google’s documentation stated that new developer sign-ups closed on May 1, 2024; the current guide no longer repeats it.

The verified timeline

May 1, 2024 — sign-ups closed
As Google’s documentation stated it when we checked on July 31, 2026: no new developer projects could onboard to Fit, and existing projects kept working. The migration guide as updated on September 10, 2026 no longer mentions the date.
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 caution in its Fit migration guide (updated September 10, 2026): “The Google Fit API (including the REST API) will only be supported until the end of 2026. We recommend migrating to the Google Health API for cloud-based integrations or Health Connect for step tracking and mobile-first apps.” No day or month is published, and no switch-off date — and a plan that depends on an exact date has already failed. (Re-checked on developer.android.com, October 2, 2026.)

The sign-up closure was the signal

Closing registration to new developers is the cheapest first move a vendor retiring a platform has. It creates no support load, no press and no scramble from partners with contracts, and nobody files a bug about something they could not sign up for. There is no benign reason to stop accepting new developers on a platform you intend to keep. And existing integrations kept working after the May 1, 2024 closure above, so a team already on Fit had no incident to respond to and no forcing function. When we laid the dates out on September 1, 2026, that closure had been the clearest signal, more than two years ahead of the end of documented support.

The check generalises. For every third-party dependency you hold, ask whether a new developer can still sign up for it today; it costs one browser tab per vendor per quarter. Migrating off a deprecated fitness API is the playbook for acting on what it finds.

Where you migrate depends on how you used Fit

Step tracking or a mobile-first Android app

→ Google Health Connect

Google’s recommended path for step tracking and mobile-first apps, and the listed successor for reading mobile steps through the Fit Recording API. Follow the migration playbook and the Health Connect integration guide. Budget for the semantic differences — manifest permissions instead of OAuth scopes, a default read window that Google’s Health Connect docs put at 30 days before permission was first granted unless you request the history permission, and changed data types; the type reference maps them.

Cloud or backend integration (Fit History, Session or REST API)

→ The Google Health API, or an aggregator

Google’s recommended path for cloud-based integrations, and the listed successor for the Fit History and Session APIs: a cloud API on a Google Cloud project with web-application OAuth. Health Connect is not the server-side answer, because Google describes its storage as on-device. If you would rather not rebuild against the Google Health API, 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 listed path for the Fit API on Wear OS. Then decide separately how watch data reaches your backend — that is the same on-device-store problem as above, not a Fit-specific one.

App using the Goals, Sensor or BLE APIs

→ No direct replacement

Google lists these as features without a direct API replacement. For the Goals API its words are “No replacement API available”, on phone and Wear: manage goal tracking and daily targets in your own app logic. For the Sensor API it points to the Android Sensors framework or the Fused Location Provider API, and for the BLE API to the Android Bluetooth APIs directly.

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: Google’s Google Health API page, read on October 12, 2026, lists end of support on September 30, 2026 and a full turn-off on October 30, 2026. Google’s Fit guide lists the Google Health API as its path too — 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.

Reaching Google Fit through a React Native bridge? The react-native-google-fit package page quotes what its README says about the shutdown.

Frequently asked questions

When exactly does Google Fit stop working?: Google's Fit migration guide says the Fit APIs 'will be supported until the end of 2026' — that is the most specific commitment published, re-checked on developer.android.com on October 2, 2026 (the guide was last updated September 10, 2026). There is no announced day or month, and no switch-off date. Treat it as end of support: the point after which Google has committed to nothing, rather than a date on which requests are guaranteed to fail. 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 that apps integrate, and the consumer app is outside our scope as a developer site. Google's Fit migration guide gives no date for the app. It says apps that let users connect to the Google Fit app can keep maintaining that integration for current users, and that Google will update that section with information on when to deprecate it. What it documents for developers is that the Google Fit API, including the REST API, will only be supported until the end of 2026.
Which Google Fit successor applies to which integration?: Match the successor to how your integration uses Fit, not to feature lists. Google's Fit migration guide recommends the Google Health API for cloud-based integrations, and lists it for the Fit History and Session APIs. Reading mobile steps through the Recording API moves to Health Connect, which the guide describes as on-device storage with no OAuth. Fit on Wear OS moves to Health Services. The Goals API has no replacement API. Multi-vendor products should also 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 until the end of 2026, but the economics get worse every month. Google's guide recommends migrating and states support only until the end of 2026; after that, assume anything that breaks stays broken, because Google has not said otherwise. 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.

The end-of-2026 support line and the successor paths were re-checked against Google’s Fit migration guide (last updated September 10, 2026) on October 2, 2026, and the 30-day Health Connect read window against Google’s Health Connect read-data guide the same day. The May 1, 2024 sign-up date is as Google’s documentation stated it on July 31, 2026. Deprecation communications change — check Google’s current guidance before committing a migration plan.