Step 1: Identify the active connection
There are two different Android routes. Chrome can send locally prepared data through its Cast connection; alternatively, Settings → Use Android screen casting opens a local player for the operating system to mirror. The latter depends on the phone’s capture session as well as Chrome.
On iPhone and iPad, this website uses Safari’s local player with Control Centre → Screen Mirroring to an AirPlay-compatible display. Desktop Chrome mirrors a local presentation. Check the device guides before applying an instruction intended for another protocol.
Step 2: Keep the source available
Keep Chrome or Safari visible, retain the selected file and keep the source device awake. The app requests a screen wake lock on supported browser paths, but the operating system can still suspend pages or stop capture. A website cannot promise uninterrupted background execution.
Android documents that a media-projection session can end when the device locks. In that case, waking the phone does not establish that its previous capture session resumed. Reopen the phone’s Cast controls, reconnect the TV if necessary and return to the local player. On iPhone, retain Safari in the foreground while mirroring and use its Play control.
For a computer, prevent sleep during the screening and keep the player page open. Do not reload merely to wake it up: reloading discards the browser’s selected File reference, so you must choose the media again.
Step 3: Restart only the connection that ended
- Check whether the phone still reports an active system casting or Screen Mirroring session.
- If it ended, reconnect in the system control used to start it.
- Return to the website’s local player and press Play on this phone on Android, or Play on this iPhone on iPhone.
- If the page was closed or refreshed, select the file again and allow preparation to finish.
Stop playback in the local player and stopping the phone’s TV connection are separate actions. The website cannot inspect which AirPlay TV you chose or stop Android’s system connection. See the complete Android and iPhone flows.
Distinguish a sleeping device from a playback limit
| What you see | What to check |
|---|---|
| Capture ends when the phone locks | Reconnect system mirroring and keep the source awake |
| Plus allowance reached | Read the player’s policy message; the plan allows 25 minutes per screening |
| Verification cannot complete | Restore internet connectivity; playback can pause while retaining its source |
| Stuttering with the page visible | Check source decoding, local network conditions and quality settings |
Pausing for a plan limit or verification is not the same as losing the TV connection. A verified upgrade applies to the existing screening. Your deliberate pause is preserved. Read the on-screen message before assuming that sleep, the file or Wi-Fi caused every stop.
If playback stops even while the screen stays awake
Check for a guest network or access-point isolation, weak Wi-Fi and a VPN that blocks local traffic. TV and phone must be able to communicate on the local network; matching radio bands is not a universal requirement. Compare a short compatible file before trying another long film.
The buffering guide covers processing and wireless constraints, while troubleshooting separates missing sound and black pictures. Keep expectations specific: this browser workflow does not promise full-film endurance on every phone, background playback or a TV that keeps playing after its local source disappears.
Ready when you are
Start with your file.
Open the player, choose one file, then use the casting option for your device. Any preparation stays on your device.
Open Cast to Your TV