Recognised file types at a glance
| Category | Recognised examples | What to expect |
|---|---|---|
| Video | MP4, MKV, MOV, WebM, M4V, AVI, MPG, MPEG, TS, M2TS, MTS, FLV, WMV, ASF, 3GP, 3G2, OGV, VOB, DIVX, MXF | Actual tracks are inspected. Compatible streams are repackaged; other tracks may need local conversion. |
| Audio | MP3, M4A, AAC, WAV, FLAC, OGG, OGA, Opus, AIFF, AIF, AIFC, WMA, WebA, MKA | Prepared as audio-only playback. Converted sound uses stereo AAC at 256 kbps. |
| Images | JPG, JPEG, JPE, JFIF, PNG, WebP, GIF, BMP, TIF, TIFF, AVIF, HEIC, HEIF | A PNG still is prepared. GIF animation and image collections show the first image. |
| Vector image | Static SVG | Checked for unsupported or unsafe content, then rasterized. |
| Document | Individual pages render locally as PNG images with page controls. | |
| Sidecar subtitles | SRT, VTT, ASS, SSA | Added after choosing a video. Selectable ASS/SSA text can lose styling. |
An extension is not a compatibility guarantee
Containers such as MP4, MOV and MKV can hold different video, audio and subtitle codecs. The app checks their contents. Compatible H.264 video can avoid picture re-encoding during preparation, while other tracks depend on supported local decoding and encoding. A recognised extension is not a promise that every profile or unusual track combination will play.
Renaming a file does not convert it. Damaged, incomplete, encrypted or DRM-protected media can be rejected. Browser and TV support also differ, so playback on a computer does not establish compatibility with every television. Start with the detailed MKV or MP4 and MOV guide for those containers.
Size limits depend on the operation
- Compatible video and audio: incremental reading can handle multi-GB files without a general 256 MiB whole-video cap.
- Whole-file fallback conversion and subtitle burn-in: 256 MiB input and output bounds still apply.
- Images: 100 MiB input and 40 million decoded pixels.
- Static SVG: 5 MiB and 20,000 nodes, with scripts, external resources and unsupported content rejected.
- PDF: 100 MiB and 200 pages; use an unlocked copy for password-protected documents.
- Sidecars and converted caption text: 5 MiB.
Image and PDF output fits within 3840 × 2160 pixels and is reduced further if necessary to stay within an 8 MiB rendered-PNG budget. Only two PDF pages are cached.
One current file, automatic preparation
Drop or choose a file on the main page. Preparation starts automatically, and the gear menu contains audio and video-quality options. The Subtitles menu holds track selection, sidecar files, text size and caption settings. There is no library to populate before you can cast.
Press Cast to display the prepared file. When you choose another file, press Cast for that selection rather than assuming it has already replaced the TV picture. Video and audio provide playback controls; PDFs provide page navigation. Media is not uploaded to our cloud. Website loading, accounts and playback verification still use network services.
The connection route has its own limits
Desktop Chrome uses its built-in casting route. Android Chrome has a direct Cast route, with an explicit system screen-casting alternative when discovery fails. iPhone and iPad use manual AirPlay screen mirroring and require an AirPlay-compatible display; a Cast-only television cannot receive that mode.
Original quality retains source detail where preparation supports it, but mirroring can re-encode the result. HDR passthrough, lossless output and every-TV compatibility are not guaranteed. Converted audio is stereo AAC rather than a promise of surround passthrough. Use the linked guides for audio, images, PDFs or large films before troubleshooting an individual file.
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