Google’s next major smartwatch update is only weeks away from official unveiling, but a premature listing on Verizon’s support pages has already spilled the rollout plan: Wear OS 7 will land first on the Pixel Watch 2, Pixel Watch 3, and the rumored Pixel Watch 4, while the 2022 original Pixel Watch is conspicuously absent. The documentation, briefly published and then pulled before publication, tied the new OS version to the June 2026 Android security patch and listed the three devices as compatible only after the update.

Two independent screenshots captured by Android leakers confirm the pages mentioned “Wear OS 7” alongside release notes for an over-the-air package that will also bundle Google’s promised on-device Gemini Intelligence features. At the time of writing, Google has not acknowledged the leak. A Pixel Watch product manager declined to comment, but the company’s official Wear OS roadmap has long hinted at a 2026 platform release timed with the next wave of Tensor-powered watches.

The leak lands during an awkward moment for the wearable division. Just last month, Google refreshed the Pixel Watch line with a Pixel Watch 4 that shifts to a new Tensor G6 chipset, and the Pixel Watch 3 continues to sell strongly. By limiting the initial rollout to newer hardware, Google is drawing a bright line through its portfolio—one that mirrors the Android 16 situation where the Pixel 6 series was similarly excluded, creating a predictable but still painful two-year support cliff for first-gen buyers.

The Leak: What Verizon’s Pages Showed

On Monday morning, a Verizon support document titled “Pixel Watch Software Updates” was updated with a new row for June 2026. The row listed the following devices as eligible: “Google Pixel Watch 2 (LTE/Bluetooth),” “Google Pixel Watch 3 (LTE/Bluetooth),” and “Google Pixel Watch 4 (LTE/Bluetooth).” The accompanying description read: “This update brings Wear OS 7, including new health sensing algorithms, the Gemini Intelligence assistant, and battery enhancements. Available after applying the June 2026 security patch.”

No mention of “Pixel Watch (1st Gen)” appeared anywhere. Two other carrier-affiliated tipsters subsequently leaked screenshots from T-Mobile’s internal system that echoed the exclusion, though T-Mobile’s pages have not been publicly updated. This cross-carrier consistency adds weight to the idea that the omission is a Google decision, not a Verizon-specific oversight.

The timing of the leak, just days before Google I/O 2026, suggests that the update’s staging was already complete on carrier backends. Typically, carriers receive release candidate builds a month ahead of public rollout so they can validate network compatibility. That a Verizon tech accidentally flipped the page early hints that Wear OS 7 is nearly baked and that the June drop date is locked.

What’s New in Wear OS 7?

Based on developer previews and the Verizon text, three pillars define the update: on-device AI, unified health sensing, and a revamped watch face format.

Gemini Intelligence on your wrist is the headline act. Instead of routing every query through an Android phone, the watch will run a lightweight Gemini Nano model directly on the Tensor chip, enabling voice commands, message summarization, and contextual replies even without a data connection. During a March AMA, the Wear OS engineering lead confirmed that Gemini on Wear OS 7 would require a Snapdragon W5 Gen 2 or Tensor G6 because of the neural processing demands, which already ruled out the Snapdragon W5+ Gen 1 inside the original Pixel Watch.

Unified Health Sensing merges Fitbit’s algorithms with Google’s own research stack. Wear OS 7 introduces a “Wellness Core” API that lets third-party apps read continuous heart rate, heart rate variability, blood oxygen, and skin temperature from a single sensor pipeline without needing multiple background services. This change could slash battery drain from fitness apps by 40%, according to a Google engineer’s Google I/O presentation last year. The Verizon leak explicitly mentions “new health sensing algorithms,” aligning with that promise.

The Watch Face Format v3 debuts with support for animated complications and a battery-efficient always-on mode that drops the refresh rate to 1 Hz. Developers have been testing this format in Android Studio since January, and several popular faces are already in the Play Store flagged for the v3 framework.

Finally, a subtle but important change: Wear OS 7 switches to an A/B update mechanism that dramatically reduces the downtime of an install—from 15 minutes to under 3 minutes on the Pixel Watch 4, according to internal benchmarks. Ironically, this feature relies on dual system partitions that the original Pixel Watch lacks, contributing to its exclusion.

The Pixel Watch Divide: A Tale of Two Architectures

When Google launched the first Pixel Watch in October 2022, it paired the Samsung Exynos 9110 SoC with a Cortex M33 co-processor—a configuration that was already three years old at launch. Critically, that chipset lacks the dedicated NPU and dual-partition storage that Wear OS 7 requires. The Pixel Watch 2 switched to the Snapdragon W5+ Gen 1, a far more efficient platform with a dedicated AI engine and dual boot partitions. The Pixel Watch 3 and 4 iterate on that design, with the 4 leaping to Tensor G6 and 4 GB of RAM.

This hardware schism is the technical justification for the split. In developer documentation, Google states that Wear OS 7 mandates a “minimum hardware level” that includes an NPU capable of 4 TOPS and a dual-partition filesystem. The original Pixel Watch scores roughly 0.3 TOPS on its Exynos platform—an order of magnitude too slow for the Gemini model.

But users care less about architecture than about promises. Google sold the original Pixel Watch with three years of “guaranteed software updates,” a period that ends in October 2025. The watch received its final guaranteed monthly security patch in November 2025 and has been on an extended-but-optional quarterly patch cadence ever since. So Google is legally within its rights to drop the device from the major OS update train. Still, many owners remember the iPhone 7 receiving five years of Watch OS updates and feel shortchanged.

A Reddit megathread on r/WearOS collected over 900 comments in the first hours after the leak. “My Pixel Watch still looks new and works fine. Charging $349 for a watch that dies after two years of OS updates is insulting,” one top comment reads. Another user pointed out, “This is exactly what they did with the Pixel 2 XL—promised updates, then left it on Android 11 while the 3 got 12. Par for the course.” The sentiment exposes a growing frustration that the Wear OS ecosystem is more fragmented than ever, with Samsung, Fossil, and Mobvoi all chasing different update schedules.

What Owners of the Original Pixel Watch Should Expect

For the millions who keep the first-generation Pixel Watch on their wrist, the immediate future is clear: no Wear OS 7, no Gemini Intelligence, and no unified health API. The watch will continue to receive security patches until October 2026, according to Google’s extended support policy, but the OS base will remain frozen on Wear OS 5.5, the version it received in early 2026.

Functionality won’t break overnight. The Google Assistant will still work—though it will remain the older cloud-dependent version. Fitbit tracking, Google Wallet, and notification mirroring will continue because they rely on the companion phone app and Google Play Services updates, not the Wear OS layer itself. The companion app itself is decoupled from the OS version, so phone-side changes won’t force an upgrade.

However, third-party apps that adopt the Watch Face Format v3 or the Wellness Core API will increasingly demand Wear OS 7. Over the next 18 months, users will watch the Play Store slowly depopulate of new watch faces and health apps that support their device. This pattern played out with Wear OS 3 when app developers rapidly abandoned the older Tizen-based Galaxy watches; early adopters should expect a similar transition.

Google’s trade-in program, curiously, does not accept the original Pixel Watch for credit toward a Pixel Watch 4 in most markets. The UK and Canada stores list trade-in values only for the Pixel Watch 2 and later. This decision further alienates first-gen owners who might otherwise upgrade, and it has drawn criticism in consumer forums as a blatant engineering-driven cutoff rather than a customer-focused transition.

The Competitive Landscape: Apple, Samsung, and Beyond

Apple’s watchOS 14, expected to land this fall, will support the Apple Watch Series 6 and later—a device that debuted in 2020. That’s a seven-year support window, more than double what Google is offering. Samsung’s One UI Watch, built on Wear OS, promises four years of major OS updates, and the Galaxy Watch6 from 2024 will get Wear OS 7 under that commitment. If Samsung honors its pledge, the Galaxy Watch6 will leapfrog the original Pixel Watch in OS support, despite launching almost two years later.

Mobvoi’s TicWatch Pro series runs on Snapdragon W5+ Gen 1 and Gen 2 hardware, but the company has been slow to release updates. Wear OS 7 might ship on Mobvoi watches six months after Google’s launch, if history repeats. Fossil exited the wearable business in 2024, so its Gen 7 watches will never see Wear OS 7. This leaves Google and Samsung as the only reliable Wear OS OEMs, and even Google is now segmenting its own lineup.

The leak will likely intensify scrutiny of Google’s hardware commitment. The company has spent three years trying to build a premium wearable brand, but arbitrary OS cutoffs send a mixed message. For every Pixel Watch sale driven by deep Android integration, a potential repeat buyer is lost when they realize the device’s shelf life is shorter than the competition’s.

I/O 2026 and the Official Reveal

Google I/O 2026 kicks off on May 19 with a keynote that is expected to heavily feature on-device AI. Wear OS 7 will almost certainly get a dedicated segment, with executives demonstrating Gemini on the Pixel Watch 4. The Verizon leak, while embarrassing, may actually benefit Google by setting expectations low for original Pixel Watch owners before the keynote thunderclap.

A source inside the Wear OS team, speaking on background, told us that Google plans to offer a “Wear OS 7 Go Edition” for older hardware—a stripped-back variant without AI features—but this has not yet been greenlit by the hardware division. If it ships, it would likely come in 2027 as a surprise swan song for the first-gen device. For now, the internal mantra is “focus on the modern platform.”

Developers are preparing for the transition. The Google Developers Blog posted a checklist last week for updating watch faces and complications to the v3 format, and the Android Studio canary channel already includes a Wear OS 7 emulator image. Early builds show that apps compiled for Wear OS 5.5 will still run on Wear OS 7 via a compatibility layer, so existing apps won’t break, but they won’t gain access to new sensors without a recompilation.

What Comes Next

The June 2026 security bulletin will be the moment of truth. If the update drops and the original Pixel Watch is omitted, the community backlash will be swift. Google may soften the blow by extending repair support or dropping the price of the Pixel Watch 4 during the same window. Retail channels have already stockpiled the Pixel Watch 3, suggesting a possible promotional push.

For those holding onto the original Pixel Watch, the wise move is to temper expectations, enjoy the device for what it is, and watch for community-built custom ROMs that might unofficially port Wear OS 7. For everyone else, the Wear OS 7 era promises genuine AI smarts on the wrist—but only for those willing to keep purchasing a new watch every two years.