The official Chromecast firmware and release-notes page also reflects this policy. It still lists current firmware versions for multiple Chromecast models and shows ongoing maintenance updates.
The only device clearly labeled as no longer supported is the original Chromecast (1st generation) from 2013. That model no longer receives software or security updates and is no longer supported by Google.
The mistaken documentation change landed at a time when Chromecast users were already dealing with other issues and transitions. Several recent developments made the idea of dropped support seem believable.
Earlier in 2025, owners of Chromecast (2nd gen) and Chromecast Audio experienced a widespread casting failure. The problem was caused by an expired authentication certificate, which prevented devices from verifying connections to Google services.
Because this outage affected older hardware, many users assumed the devices might be reaching end‑of‑life—so when the support-page error appeared later, it reinforced those fears.
There is one Chromecast model that has reached end-of-life: the original 2013 device. Google ended support after roughly a decade, meaning it no longer receives updates or official technical support.
That legitimate support change likely contributed to the assumption that other models might soon follow.
At the same time, Google has been expanding Gemini AI features for Google TV—but only on a limited set of hardware so far.
For example, Google’s documentation shows Gemini for TV currently launching on select devices such as the TCL QM9K series and in limited regions and languages, with broader expansion planned later.
This selective rollout can make the Google TV and Chromecast ecosystem feel fragmented, even when older devices still receive maintenance updates.
The Chromecast support scare was ultimately the result of a documentation mistake—not a real policy change.
Because the error occurred alongside real outages and ongoing platform changes, it created a perfect storm for confusion—showing how quickly a small documentation mistake can turn into a widespread tech rumor.