Google’s Pixel Watch 5 is real enough to have appeared in U.S. FCC paperwork and, more recently, in a device-selection screen inside Google’s own Health app. But the most consequential claims in NokiaPowerUser’s August 4 leak — 64GB of storage, 3GB of RAM, and more on-watch Gemini processing — do not all carry the same evidentiary weight. The available record supports an incremental Pixel Watch arriving soon; it does not yet support treating every listed specification or health feature as settled. The timing is no longer mysterious. Google has scheduled its Made by Google hardware event for August 12, 2026, in New York, and 9to5Google reported that the company’s invitation teases the next Pixel generation without publicly naming every device. Android Central separately reported that “Google Pixel Watch 5” briefly appeared as a setup option in the Google Health app, an unusually concrete pre-release sign that pairing support is already being prepared.
For Pixel Watch 4 owners, the practical message is more restrained than the leak’s “wait for it” verdict: the Watch 5 looks likely to be a refinement, and the software headline — Wear OS 7 — is already available to eligible older Pixel Watches. The hardware case for upgrading rests on memory, storage, price, charging and any new sensors Google confirms next week. At present, several of those details remain either single-sourced or unsupported.

A smartwatch and smartphone display health tracking, AI features, and technical specifications.Wear OS 7 is already a Pixel Watch 4 feature​

NokiaPowerUser presents Wear OS 7 as a central Pixel Watch 5 upgrade, but Google began rolling Wear OS 7 to eligible Pixel Watches on June 16. Google’s own announcement says the release brings Live Updates, a remote media-output switcher, connected-device integration and power optimizations that can improve battery life by up to 10% for average users upgrading from Wear OS 6.
That changes how the software claim should be read. A Pixel Watch 5 may ship with Wear OS 7, but it will not give buyers exclusive access to the operating system’s major public features. Pixel Watch 2, Pixel Watch 3 and Pixel Watch 4 owners are already the relevant comparison group, rather than owners of a device stranded on an older platform.
Google has also been explicit that its more ambitious Gemini Intelligence features arrive later in 2026 on select Wear OS 7 devices. Those planned features include Create My Widget, which builds custom dashboards from natural-language prompts, and multi-step task automation in supported apps. Google has not said that Pixel Watch 5 will be the only compatible watch, nor has it published a final supported-device list.
The distinction matters because the source material turns a staged software rollout into a new-device capability. If Google enables Gemini Intelligence on Pixel Watch 4, the Watch 5’s software advantage becomes smaller immediately. If it reserves certain functions for newer hardware, Google will need to identify which functions and why.

Gemini on a watch still depends on the paired phone​

The report’s strongest overreach is the suggestion that an additional gigabyte of RAM will allow more Gemini requests to be handled locally on the watch rather than routed through a phone. Google’s published Gemini-on-Wear-OS support documentation says users need an Android phone connected to the watch and must set Gemini as the digital assistant on that connected phone. It also says the feature is rolling out gradually by supported language and region.
That does not prove that no local work happens on a watch. Wearables routinely perform local tasks such as sensor processing, wake-word handling and some inference. It does show that Google has not made the claimed independence from the phone part of its public Gemini model.
Google’s existing documentation also provides the actual access methods: a long press of the manufacturer-designated button, the “Hey Google” hotword when the display is awake, a watch-face complication, or a Gemini tile. A Gemini complication on a new watch face would therefore be plausible, but it would not establish a wholly new “Gemini Watch Face” product category or prove on-device generative processing.
The privacy implication is worth keeping in view. Google says Gemini on the watch uses the permissions selected for the Google app that hosts the digital-assistant functions. If precise location access is enabled, Gemini can use the watch’s precise location. Any Pixel Watch 5 AI pitch will consequently be about both convenience and the same account, location and app-data permissions that underpin Gemini on other Google devices.

The 3GB RAM claim has one trail; 64GB storage does not​

Google’s official Pixel Watch 4 specification page lists 32GB eMMC storage and 2GB SDRAM for both the 41mm and 45mm models. So the supposed move to 3GB RAM and 64GB storage would be a meaningful step up if confirmed, particularly for downloaded music, offline maps, apps and cached workout data.
There is some reporting support for the RAM portion. GoogleWatchBlog reported on July 23 that a Pixel Watch 5 entry in Google Play Console identified a device codename, “godric,” and listed 3GB of RAM. That is still one outlet’s account of a console listing rather than a public Google specification sheet, but it is a more traceable claim than a generic leak table.
The storage claim is weaker. NokiaPowerUser lists 64GB, yet the other pre-launch reporting reviewed for this story — including the FCC coverage, the color-and-pricing reports, the Google Health app appearance, and the claimed Play Console discovery — does not independently confirm a 64GB configuration. GoogleWatchBlog’s report about the alleged console data discusses the 3GB memory figure but does not report 64GB storage.
As of August 5, the correct status is therefore uneven: 3GB RAM has been reported from a purported Play Console listing; 64GB storage remains uncorroborated in the available reporting. Readers should not assume the two claims rise or fall together simply because they appeared side by side in one comparison table.
There is another material omission in the source report: no confirmed processor change. Google’s Pixel Watch 4 uses Qualcomm’s Snapdragon W5 Gen 2 with a Cortex-M55 coprocessor. GoogleWatchBlog claimed the Watch 5 would retain an older Qualcomm SW5100 family platform, a claim that conflicts with the expectation of a fresh chipset but has not been independently verified. Until Google publishes the processor, storage type and battery figures, “more RAM equals smoother performance” is plausible analysis, not a demonstrated result.

The familiar casing and colors are the best-supported leaks​

The physical design story is more solid. FCC-related reporting from Droid Life and 9to5Google identified four Pixel Watch 5 model numbers — G25QD, G1XJ6, G0F3Y and GFW3R — and found Wi-Fi and LTE connectivity in the filings. The filings substantiate that Google is preparing multiple wearable variants, but they do not reveal RAM capacity, storage, battery longevity, display dimensions or Fitbit software.
Leaked imagery and color reporting have also converged on a familiar round Pixel Watch silhouette in 41mm and 45mm sizes. 9to5Google, citing Dealabs and Nieuwe Mobiel, reported four case colors: Natural Silver, Dark Anthracite, Pyrite and Warm Gold. Its reporting says Warm Gold may be limited to the 41mm model, while the others could span both sizes.
Android Central’s Google Health app report reinforces the visual continuity, though with an important caveat. The setup process showed artwork that looked like Pixel Watch 4 imagery, which may mean the app was using a placeholder rather than revealing the final Watch 5 design. It is credible evidence of software support, not final proof of bezel thickness, case dimensions or charging hardware.
NokiaPowerUser’s promise of backward-compatible bands and charging pucks should be separated into two claims. Band compatibility is plausible if Google retains the existing attachment system, but Google has not confirmed it for Pixel Watch 5. Charger compatibility is even less safe to assume: the Pixel Watch 4 already uses a Quick Charge Dock, and charging changes can be invisible in marketing images while breaking compatibility with earlier accessories. Existing owners should wait for Google’s accessory matrix before buying a Watch 5 on the assumption that every band and charger will transfer.

Fitbit’s health features need a confirmed hardware basis​

The health section is almost entirely prospective. Pixel Watch 4 already has red and infrared SpO2 sensors, ECG-compatible electrical sensors, a multi-path optical heart-rate sensor, cEDA, a far-field skin-temperature sensor, a barometer and a magnetometer. Google also already markets Fitbit features such as Cardio Load and Daily Readiness Score across the current Pixel Watch line.
As a result, “AI sleep coach,” proactive recovery prompts and analysis of skin-temperature variance may describe new presentation or advice layers, but they do not establish new sensing hardware. No reviewed regulatory filing or Google support material verifies a new Pixel Watch 5 health sensor, a revised clinical metric, or the availability terms for any enhanced Fitbit guidance.
That is important for buyers because Fitbit-derived readiness and sleep features often vary by country, account status, subscription terms and device generation. A feature shown in a pre-release render is not a promise that it will ship in every market or be free after any trial period expires. NokiaPowerUser did not identify those conditions.
Google has less than a week to close these gaps. The August 12 event should settle the processor, memory, storage, battery, sensors, bands, chargers, pricing and Gemini feature eligibility in one release. Until then, the defensible conclusion is narrower: Pixel Watch 5 appears headed for a familiar 41mm-and-45mm design with new colors and likely more RAM, while the headline 64GB storage, on-device Gemini claim, health additions and accessory compatibility remain unconfirmed.

References​

  1. Primary source: nokiapoweruser.com
    Published: 2026-08-04T15:34:56+00:00
  2. Related coverage: androidcentral.com
  3. Related coverage: androidcentral.com
  4. Related coverage: t3.com
  5. Related coverage: tomsguide.com
  6. Related coverage: forbes.com
  7. Related coverage: blog.google
  8. Related coverage: support.google.com
  9. Related coverage: support.google.com
  10. Related coverage: store.google.com
  11. Related coverage: techadvisor.com
  12. Related coverage: 9to5google.com
  13. Related coverage: droid-life.com
  14. Related coverage: gadgets360.com
  15. Related coverage: engadget.com
  16. Related coverage: wareable.com
  17. Related coverage: storage.googleapis.com
  18. Related coverage: gadgets360.com
  19. Related coverage: newsbytesapp.com
  20. Related coverage: 9to5google.com
  21. Related coverage: meteoraweb.com
  22. Related coverage: nieuwemobiel.nl
  23. Related coverage: gazyekichi96.com
  24. Related coverage: play.google.com
  25. Related coverage: tuttoandroid.net
  26. Related coverage: memeburn.com
  27. Related coverage: netzwelt.de
  28. Related coverage: android-mt.ouest-france.fr
  29. Related coverage: youtube.com
  30. Related coverage: store.google.com
  31. Related coverage: developers.google.com
  32. Related coverage: blog.google
  33. Related coverage: developers.google.com
  34. Related coverage: tomsguide.com
  35. Related coverage: t3.com
  36. Related coverage: techtimes.com
  37. Related coverage: phonearena.com
  38. Related coverage: technosports.co.in
  39. Related coverage: 1und1.de
  40. Related coverage: podcasts.apple.com
  41. Related coverage: get.google.com
  42. Related coverage: googlewatchblog.de
  43. Related coverage: youtube.com
  44. Related coverage: storage.googleapis.com