Skip to content
OBS plugin + YouTube embedded player

Play your own public YouTube videos in the StreamWizard OBS plugin

The YouTube flow can optionally extend your normal OBSBot setup with your own or authorized public videos. Local files still remain the base.

Open OBSBot in dashboard Terms of service Privacy policy
Suitable for your own or authorized public videos
Flow Enter the channel, name a browser source, done
Important Local files remain the base of your playlist workflow
Not meant for

No general channel downloading

  • no third-party download of arbitrary YouTube channels
  • no use for content without your own rights or clear authorization
Suitable for

Your own and authorized public videos

  • your own public uploads as a requestable archive
  • public videos with explicit authorization
  • playback in the embedded player, mixed with your local files
What matters for usage

What you should know before you start

For users, four things matter most: the right permissions, a local flow, local data storage, and a clean OBSBot host setup.

01

Suitable rights

  • Use only videos that belong to you or for which you have clear authorization.
  • If you are unsure, it is better not to use the YouTube extension.
02

Local flow

  • There is no Google authorization: the plugin never signs in and requests no tokens.
  • Setup needs nothing on Google's side: enter the channel in the dock, name a browser source - done.
03

Data stays local

  • The website only hands the plugin the central YouTube Data API key used to fetch your channel's video list.
  • Neither tokens nor exported files are created.
04

Safe operation

  • Playback runs through the embedded player - nothing is written to your drive, so there is no cache and no archive size to manage.
  • Local video files you placed yourself are managed as before.

How it works at a glance

  1. You enter your YouTube channel once in the dock, on the "Setup" tab.
  2. You enable YouTube only if you really want to use this optional flow.
  3. The plugin fetches the video list through the YouTube Data API v3 - no sign-in and no file synchronization.
  4. The videos play in a browser source through the YouTube embedded player; if a video is available locally as a file, the file takes precedence.

Important boundary

If platform or legal requirements change, the YouTube flow may be adjusted or restricted.

Secure it locally

What the website and OBSBot each handle

For users, what matters most is what happens on the website and what stays local in OBSBot.

On the website

  • central YouTube Data API key for the video list
  • standard account, license, and API data of the website
  • no YouTube tokens - nothing signs in anywhere

Locally in OBSBot

  • secure host, cache, and bot configuration against unauthorized access
  • no archives and no tokens that would need deleting
  • keep the system and backups up to date
Quick FAQ

The most important questions at the end

Short and in the same order as the page: purpose, allowed use, local data, and setup requirements.

01

What is the flow for?

For your own or authorized public video archive in OBSBot.

02

What is allowed?

Your own uploads and expressly authorized public videos.

03

What stays local?

Nothing is downloaded and nothing is exported.

04

What do I need to get started?

Your channel in the dock and a browser source in OBS. No Google project, no redirect URI, no sign-in.

If you need more: the OBSBot dashboard contains the operational short version. The website-level legal and privacy framework is described in the terms of service and the privacy policy.