Skip to main content

Official repository: https://github.com/Brainicism/bgutil-ytdlp-pot-provider

BgUtils POT Provider

Docker Image Version (tag) GitHub Release PyPI - Version CI Status

Frequently Asked Questions

A proof-of-origin token (POT) provider for yt-dlp. We use LuanRT's Botguard interfacing library to generate the token. This project was used to bypass the 'Sign in to confirm you're not a bot' message when invoking yt-dlp from an IP address flagged by YouTube. See PO Token Guide for more details.

The provider comes in two parts:

  1. Provider: Two options -
    • (a) An HTTP server that generates the POT, and has interfaces for the plugin to retrieve data from (much faster, easy setup + docker image provided with Deno/Node.js support)
    • (b) A POT generation script, and has command line options for the plugin to invoke (needs to transpile the script)
  2. Provider plugin: retrieves tokens from the provider and provides the token for yt-dlp using PO Token Provider Framework.

Installation

Base Requirements

  1. yt-dlp 2025.05.22 or above.

  2. If using Docker image for option (a) for the provider, the Docker runtime is required.
    Otherwise, Node.js (>= 20) or Deno (>= 2.0.0) is required. You will also need git to clone the repository.

1. Set up the provider

There are two options for the provider, an always running POT generation HTTP server, and a POT generation script invoked when needed. The HTTP server option is simpler, faster, and comes with a prebuilt Docker image. You only need to choose one option.

You need to first install the repository unless you are using the Docker image for the HTTP server:

# Replace 1.3.2 with the latest version or the one that matches the plugin
git clone --single-branch --branch 1.3.2 https://github.com/Brainicism/bgutil-ytdlp-pot-provider.git
cd bgutil-ytdlp-pot-provider/server/
# If you are using Node:
npm ci
npx tsc
# Otherwise, if you want to use Deno:
deno install --allow-scripts=npm:canvas --frozen

(a) HTTP Server Option

This is a JavaScript HTTP server, on port 4416 by default. You have two options for running it: as a prebuilt Docker image, or manually as a JavaScript application.

Docker:

Port 4416 is exposed to the host system by default. Pass -p 1234:4416 in the docker run options (before the image name) to publish the server to port 1234 on the host system. Replace [OPTIONS] with the server command line options (usually this is not needed because you can use docker to publish the server to another port).

docker run --name bgutil-provider -d --init brainicism/bgutil-ytdlp-pot-provider [OPTIONS]

Our Docker image comes in two flavors: Node.js or Deno. The :latest tag defaults to Node.js, but you can specify an alternate version/flavor like so: brainicism/bgutil-ytdlp-pot-provider:1.3.2-deno. The :node tag also points to the latest Node.js image, and :deno points to the latest Deno image.

Native:

Run the server with the selected JavaScript runtime with the following command, assuming you have changed into the bgutil-ytdlp-pot-provider/server directory. Replace [OPTIONS] with the server command line options. For example, replace it with --port 8080 to run the server on port 8080.

Node:

node build/main.js [OPTIONS]

Deno:

cd node_modules
deno run --allow-env --allow-net --allow-ffi=. --allow-read=. ../src/main.ts [OPTIONS]

Server Command Line Options

  • -p, --port <PORT>: The port on which the server listens.

(b) Generation Script Option

For this option, just make sure either node or deno is available in your PATH. Otherwise, use the yt-dlp option --js-runtimes RUNTIME:PATH to pass the path. --no-js-runtimes does NOT prevent the plugin from using the JavaScript runtime. The argument is only used to retrieve the path to the runtime.

2. Install the plugin

PyPI:

If yt-dlp is installed through pip or pipx, you can install the plugin with the following:

python3 -m pip install -U bgutil-ytdlp-pot-provider

Manual:

  1. Download bgutil-ytdlp-pot-provider.zip from the latest release.
  2. Install it by placing the zip into one of the yt-dlp plugin folders.

Usage

If using option (a) HTTP Server for the provider, and the default IP/port number (http://127.0.0.1:4416), you can use yt-dlp like normal 🙂.

If changing the port or IP used for the provider server, pass it to yt-dlp via base_url

--extractor-args "youtubepot-bgutilhttp:base_url=http://127.0.0.1:8080"

Note that when you pass multiple extractor arguments to one provider or extractor, they are to be separated by semicolons(;) as shown above.


If using option (b) script for the provider, with the default script location in your home directory (i.e: ~/bgutil-ytdlp-pot-provider or %USERPROFILE%\bgutil-ytdlp-pot-provider), you can also use yt-dlp like normal.

If you installed the script in a different location, pass it as the extractor argument server_home to youtube-bgutilscript for each yt-dlp call. ~ at the start of the path is automatically expanded.

--extractor-args "youtubepot-bgutilscript:server_home=/path/to/bgutil-ytdlp-pot-provider/server"

We use a cache internally for all generated tokens when option (b) script is used. You can change the TTL (time to live) for the token cache with the environment variable TOKEN_TTL (in hours, defaults to 6). It's currently impossible to use different TTLs for different token contexts (can be gvs, player, or subs, see Technical Details from the PO Token Guide).
That is, when using the script method, you can pass a TOKEN_TTL to yt-dlp to use a custom TTL for PO Tokens.


If both methods are available for use, the option (a) HTTP server method will be prioritized.

Verification

To check if the plugin was installed correctly, you should see the bgutil providers in yt-dlp's verbose output: yt-dlp -v YOUTUBE_URL.

[debug] [youtube] [pot] PO Token Providers: bgutil:http-1.3.2 (external), bgutil:script-node-1.3.2 (external), bgutil:script-deno-1.3.2 (external, unavailable)

FAQ

I'm getting errors during npm ci on Termux

For provider versions >=1.2.0, you may have issues while installing the canvas dependency on Termux. The Termux environment is missing a android_ndk_path and two packages by default. Run the following commands to setup the dependencies correctly.

mkdir ~/.gyp && echo "{'variables':{'android_ndk_path':''}}" > ~/.gyp/include.gypi
pkg install libvips xorgproto

Metadata

Release files for bgutil-ytdlp-pot-provider 1.3.2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for bgutil-ytdlp-pot-provider 1.3.2
File Size Uploaded
bgutil_ytdlp_pot_provider-1.3.2.tar.gz 11.5 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for bgutil-ytdlp-pot-provider 1.3.2
File Interpreter ABI Platform
bgutil_ytdlp_pot_provider-1.3.2-py3-none-any.whl Python 3 none any Details

Total release size: 23.7 kB

Release files / bgutil_ytdlp_pot_provider-1.3.2.tar.gz

Download URL bgutil_ytdlp_pot_provider-1.3.2.tar.gz
Size 11.5 kB
Tags Source
SHA-256 checksum
How to use checksums
9971733ebba2b69ca1f1b8c6036a114154330a9f8af54491c6baa941863df87a
BLAKE2b-256 checksum
How to use checksums
efdf56fa3c1e0af648d1474cdcd4f6630e5b2a42081850cfd50e95434bbfbc2c
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Aug 21, 2026.

Transparency log

Release files / bgutil_ytdlp_pot_provider-1.3.2-py3-none-any.whl

Download URL bgutil_ytdlp_pot_provider-1.3.2-py3-none-any.whl
Size 12.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
9674227441402b56fe06f4e7559a691f33913eebfc7d50831894ccb24c8bc479
BLAKE2b-256 checksum
How to use checksums
4bcd2af89f094c7d404a001b78e6467a6740360483e734a334ab601e07489fbb
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Aug 21, 2026.

Transparency log

Release history Release notifications | RSS feed

2.0.1

2 release files

2.0.0

2 release files

This release

1.3.2 This release

2 release files

1.3.1

2 release files

1.3.0

2 release files

1.2.2

2 release files

1.2.1

2 release files

1.2.0

2 release files

1.1.0

2 release files

1.0.0

2 release files

0.8.5

2 release files

0.8.4

2 release files

0.8.3

2 release files

0.8.2

2 release files

0.8.1

2 release files

0.8.0

2 release files

0.7.4

2 release files

0.7.3

2 release files

0.7.2

2 release files

0.7.1

2 release files

0.7.0

2 release files

0.6.1

2 release files

0.6.0

2 release files

0.5.2

2 release files

0.5.1

2 release files

0.5.0

2 release files

0.4.0

2 release files

0.3.0

2 release files

0.2.2

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page