> For the complete documentation index, see [llms.txt](https://docs.otherside.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.otherside.xyz/platform-documentation/creation/unreal-development/features-and-tutorials/video-players/streaming-video-player/picture-in-picture-mode.md). # \[Deprecated] Picture-in-Picture mode {% hint style="danger" %} Deprecated in release v39. Please speak to support for further info. **07/07/2025:** The `WBP_PiPVideoPlayer` was a prototype widget that has since been moved to `M2Deprecated`, since we have dropped support for it. It will still be available from that plugin, but is not advertised in our platform. This can achieved with native Unreal functionality, similar to the world-space video player example. {% endhint %} `WBP_PiPVideoPlayer` is a prototype screen space widget that can be used for Picture-in-Picture mode. To use it, add it to the relevant HUD and call `SetScreenVisibility` on the widget to show/hide the screen. Call `SetURL` with the url of the source file to play to have the widget open the file in question. The media player is set up to play on open by default. Call `Play`/`Pause` to control the playback further.
--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.otherside.xyz/platform-documentation/creation/unreal-development/features-and-tutorials/video-players/streaming-video-player/picture-in-picture-mode.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.