What can this player render?
Browser/Pi have the broadest renderer; Roku uses a native Relay Plan with explicit widget/media compatibility and should surface unsupported content instead of pretending browser parity.
What you may be seeing
- A board works in the browser preview but one platform cannot render one or more elements the same way.
- A Roku screen hides or substitutes an unsupported widget/content type.
What usually causes it
- Browser and Raspberry Pi use the browser renderer and therefore have the highest feature fidelity.
- Roku is a real native SceneGraph/BrightScript player using a server-compiled Relay Plan, not a general-purpose WebView.
- Some live widgets have native-data, snapshot, marquee, local, or unsupported Roku strategies defined by the widget registry.
- Arbitrary web embeds and YouTube-style web content cannot be assumed to work on the native Roku renderer.
Do this
- Check the Widgets & player compatibility reference in Docs; Roku widget support is generated from the same registry used by the Relay compiler.
- For browser-only elements, replace them with supported uploaded media, native/snapshot widgets, or use a browser/Raspberry Pi player for that screen.
- Do not re-pair a healthy screen to fix unsupported content. Pairing changes identity; it does not add renderer capabilities.
- After replacing unsupported content, publish a new release and confirm the affected screen becomes active on it.
You know it is fixed when
- The board contains only elements supported by the target player, or an intentional fallback is documented.
- The physical screen renders the new published release without hidden/unsupported primitives.
Search phrases this guide covers
player compatibility · Roku unsupported element · what works on Roku · web embed Roku · YouTube Roku · which player should I use · board has unsupported content
