Choose in-app Google Cast or a Chrome tab

2026-11-13

Google documents Cast-enabled apps and Chrome tab casting as separate sender paths. Start by checking which one the publisher supports for the source.

Confirm the exact product or platform

What to do on your device

1. Check whether the sender app or service exposes its own Cast button and choose a supported receiver.
2. If the publisher supports desktop playback, test the same authorized title through Chrome tab casting as a separate path.
3. Record whether the failure occurs at discovery, connection or playback before retrying.

Test the viewing task

Use one authorized programme with a known audio or caption track. Check the same task after the documented change. If the result differs, report the model, OS or app version and the format or connection that the guide above applies to.

Choose the Cast path the service supports

If the publisher’s app has a Cast control on the programme you want to watch, use that path first. The app controls the session while the receiver plays supported media. Chrome tab casting sends the selected tab to the display. Casting the whole screen is another mode and can expose notifications or other windows. Google documents these as separate options.

Use the same authorised programme in each supported test. End the first session before the next test to avoid an account concurrency error. Write down whether the failure happened before receiver discovery, after selecting the receiver or only when the video began.

Use the first failed stage as the next question

Suppose the receiver shows up in Chrome and in a recognised Cast-enabled app, but the affected app never offers the receiver. Check the affected app’s own casting support and its local network permission. If the receiver appears but refuses the same title only in that app, record the title, receiver model and error for the publisher.