Skip to content
OBSBot + Google Data Portability

Use your own public YouTube videos locally in OBSBot

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 Request your archive, download it locally, and import it into OBSBot
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
  • local import into your normal OBSBot cache
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

  • Google authorization runs locally in OBSBot, not as a normal website download.
  • A dedicated Google project is intended for this flow.
03

Data stays local

  • The website only provides the system configuration for the OAuth client.
  • Tokens and exported files stay local in OBSBot.
04

Safe operation

  • Safe mode, cache limits, and free-space checks help with large archives.
  • You should regularly delete exports and backups you no longer need.

How it works at a glance

  1. The Google client is set up for OBSBot.
  2. You enable YouTube only if you really want to use this optional flow.
  3. Authorization and later synchronization run locally in OBSBot.
  4. Imported content is integrated locally into your playlist workflow.

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

  • system configuration for the Google OAuth client
  • standard account, license, and API data of the website
  • no regular storage of your YouTube tokens for this flow

Locally in OBSBot

  • secure host, cache, and bot configuration against unauthorized access
  • regularly delete exports, archives, and tokens you no longer need
  • 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?

Login, tokens, exports, and imported files stay in OBSBot.

04

What do I need to get started?

A suitable Google project, the correct redirect URI, and a properly secured OBSBot.

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.