EOL.WikiEOL.Wiki
← ← Back to all products

Google Pixel Watch

Active
DevicesLatest Version: 5Latest Release: N/A

Google Pixel Watch is Google's smartwatch line with Fitbit integration and Wear OS.

Support summary

Google Pixel Watch 2 reaches EOL in 41 days. Start upgrade planning and compatibility testing now.

What do EOL and support statuses mean?

Next EOL

Oct 1, 2026

Google Pixel Watch 2 · 41 days left

Supported cycles

4

0 lts

Versions

5

Latest Version

5

Active Support

4

EOL

1

Lifecycle Timeline

Today
5
5
4
4
3
3
2
2
1
1
Active SupportSecurity SupportEOL

Versions

ReleaseRelease DateActive SupportEOLLatest VersionLTSStatus
5Aug 20, 2026Oct 1, 2029Oct 1, 20295No
Active
4Oct 9, 2025Oct 1, 2028Oct 1, 20284No
Active
3Sep 10, 2024Oct 1, 2027Oct 1, 20273No
Active
2Oct 12, 2023Oct 1, 2026Oct 1, 20262No
Active
1Oct 13, 2022Oct 1, 2025Oct 1, 20251No
EOL

Data sources

Frequently Asked Questions

Which versions of Google Pixel Watch have reached end of life?
The following Google Pixel Watch versions have reached end of life and no longer receive security updates: 1. It is recommended to upgrade to a supported version.
Is it safe to continue using Google Pixel Watch 1?
Google Pixel Watch 1 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of Google Pixel Watch?
The latest version of Google Pixel Watch is 5, released in the 5 release cycle.
How many versions of Google Pixel Watch are currently supported?
Google Pixel Watch currently has 4 actively supported version(s): 5, 4, 3, 2.
When does Google Pixel Watch 5 reach end of life?
Google Pixel Watch 5 is scheduled to reach end of life on Oct 1, 2029.
What should I do when Google Pixel Watch reaches end of life?
When a Google Pixel Watch version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.