Last month, Netflix quietly removed broad casting support from its mobile apps, limiting casting to legacy Chromecast adapters without remotes, Nest Hub displays, and select Vizio and Compal televisions. The change abruptly narrowed a capability that had long allowed phones to launch playback on many smart TVs and streaming boxes. Users and developers noticed the shift without advance notice, and the move has reignited debate about whether casting remains essential as televisions ship more capable native apps. Industry players from Google to the Connectivity Standards Alliance are responding with competing approaches that could reshape how phones, speakers and TVs interoperate.
Key Takeaways
- Netflix removed wide casting support in its mobile apps last month; casting now works only on older Chromecast adapters without remotes, Nest Hub displays, and select Vizio and Compal TVs.
- Netflix pioneered second-screen casting in 2012 after early collaboration with YouTube on the DIAL protocol; Google’s first Chromecast followed in 2013.
- Google has sold more than 100 million Chromecast adapters, and casting was once an important discovery and playback vector for services and TV makers.
- Streaming usage patterns shifted: one streaming operator told reporters that only about 10% of its Android users still cast to TVs, down from much higher rates a decade ago.
- Netflix declined to comment on the removal; public speculation links the change to feature priorities such as cloud gaming and interactive voting.
- The Connectivity Standards Alliance has introduced Matter Casting as an open alternative; so far support is limited to Fire TV and Echo Show devices, and a small number of apps like Tubi.
- Google continues to invest in Google Cast and says it will expand support and experiences across devices this year.
Background
Casting traces back to efforts in the early 2010s to let mobile devices and TVs work together more seamlessly. Engineers at Netflix and Google explored second-screen workflows around 2011, and TV manufacturers such as Sony and Samsung joined to produce DIAL (Discovery And Launch), an open protocol that formalized remote launch and handoff scenarios. Netflix added casting features to its mobile app in 2012 to let phones trigger playback on devices like the PlayStation 3, helping spur the technology’s early adoption.
Google’s 2013 Chromecast product translated DIAL ideas into a widely adopted, proprietary implementation. Manufacturers such as Vizio even experimented with casting-first products; Google later reported more than 100 million Chromecast devices sold. Over time, however, smart TVs improved their native apps and streaming services invested in first-class TV applications, eroding some of casting’s centrality.
Main Event
In a recent, unannounced change, Netflix removed casting support from a broad set of smart TVs and streaming devices when accessed from its mobile apps. The company kept compatibility with a narrow set of endpoints—older Chromecast adapters that lack remotes, Google Nest Hub displays, and specific Vizio and Compal models. Users who had relied on casting to bridge mobile and television experiences found the capability gone without an official rollout note.
Before the change, Netflix supported Google’s casting standard across many Android TV models from vendors such as Philips, Sharp, Sony and Vizio, and it also offered a separate “Netflix 2nd Screen” feature that worked with PlayStation consoles, LG and Samsung TVs, Roku devices and more. The recent pruning therefore represents a meaningful contraction in cross-device interoperability after years in which casting functioned as a near-ubiquitous fallback.
Netflix did not provide an on-the-record explanation for the decision when asked. Industry observers suggest the company may be prioritizing new interactive and cloud-powered features—capabilities that often require tighter device coordination or different connectivity models than simple video handoff. For affected users, the immediate impact ranges from minor inconvenience to loss of a preferred way to discover and control TV playback.
Analysis & Implications
The Netflix change highlights a broader tension in the streaming ecosystem between device-level integration and platform-specific features. When TVs and set-top boxes run robust native apps, services can deliver richer, more consistent experiences without relying on a phone as a control surface. That reduces the technical need for casting but also concentrates control in platform app stores and vendor ecosystems.
For device makers and standards groups, the shift is a fresh prompt to clarify interoperability strategies. Google remains committed to Google Cast as a widely deployed proprietary solution and is investing in improved cross-device experiences. At the same time, the Connectivity Standards Alliance is promoting Matter Casting as an open alternative intended to lower friction for services and manufacturers that prefer non‑Google pathways, with Amazon as a public backer.
Adoption dynamics will drive the next phase. Matter Casting’s current footprint is small—primarily Amazon devices today—and content support beyond Amazon’s apps has been limited. Conversely, Google Cast benefits from decades of ecosystem momentum and tens of millions of installed endpoints. The technical competition is therefore also a contest of commercial relationships and platform economics: which parties can secure developer buy‑in, device firmware integration, and consumer comprehension?
Comparison & Data
| Year | Milestone | Impact |
|---|---|---|
| 2011–2012 | DIAL and Netflix 2nd Screen | Formalized second-screen launch workflows |
| 2013 | Google Chromecast launch | Mass adoption of phone‑to‑TV casting |
| 2024–2025 | Netflix limits casting | Significant narrowing of mobile‑to‑TV interoperability |
The table above compresses two decades of device and protocol evolution into three snapshots. While Chromecast sales (100+ million units) attest to casting’s reach, usage metrics reported by operators—roughly 10% casting among Android users in one example—show the function’s decline as native TV apps matured. Those two facts together help explain why a streaming giant might deprioritize casting in favor of novel features that require different architectures.
Reactions & Quotes
“Google Cast continues to be a key experience that we’re invested in — bringing the convenience of seamless content sharing from phones to TVs.”
Neha Dixit, Google (Android platform PM)
Google frames Cast as a continuing strategic product, signaling investment in cross‑device convenience even as the ecosystem fragments.
“We welcome and support media developers that want to build to an open standard with the implementation of Matter Casting.”
Tapas Roy, Amazon (VP, Device Software & Services)
Amazon positions Matter as an open alternative that could attract media developers seeking more choice than proprietary solutions offer.
“To be honest, I have Fire TVs, and I’ve never used it.”
Christopher LaPré, Connectivity Standards Alliance (technology strategist)
That admission underlines the current limits of Matter Casting’s consumer traction despite its theoretical advantages.
Unconfirmed
- Netflix’s internal rationale: industry reporting and analysts suggest cloud gaming and interactive features may have driven the change, but Netflix has not confirmed this publicly.
- Complete device compatibility: claims about which individual TV models and firmware builds lost casting support vary by report and have not been exhaustively verified across all vendors.
- Matter Casting adoption timeline: while audio casting and camera support are planned, exact rollout dates and broad app support remain uncertain.
Bottom Line
Netflix’s abrupt removal of broad casting support marks a notable contraction in a capability that helped shape early connected‑TV behavior. The move is as much a reflection of shifting technical priorities—native TV apps, cloud features and interactive experiences—as it is a catalyst for new standards and vendor strategies. Consumers who relied on casting will need to adapt: some devices and apps will continue to support Google Cast, others may adopt Matter Casting, and some services will prefer in‑app TV experiences.
For the industry, the key questions are commercial as well as technical: which standards will developers and manufacturers choose, and how quickly will consumers understand the differences? Watch for increased activity from Google, the Connectivity Standards Alliance, and major OEMs over the next year—especially as Matter adds audio casting and camera support, and as companies decide whether to prioritize open standards or platform‑specific integrations.