iSponsorBlockTV

iSponsorBlockTV is a self-hosted application for compatible YouTube TV apps that automatically skips sponsor, intro, and ad segments in YouTube videos using…

  • Automation
  • Media Applications
  • Media Servers
  • Other
  • Productivity
  • Tools & Utilities
iSponsorBlockTV is a self-hosted application for compatible YouTube TV apps that automatically skips sponsor, intro, and ad segments in YouTube videos using the SponsorBlock API to reduce interruptions, and can also mute or press the Skip Ad button when available.

Platform availability

Available on 3 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

81/100 Excellent

Maintained
95last commit 13 days ago
Popular
777,242 GitHub stars
Easy to install
553 install platforms, install notes, Docker image
Light to run
No data
Security check
85no serious findings, CI

Based on 4 of 5 factors.

Availability: platform listings confirmed today, links checked 6 days ago

GitHub stars
7,242
Open issues
80
Last commit
2026-11-08
Latest release
v2.11.0
License
GPL-3.0
Activity
rising

Checked 4 days ago - source: GitHub (dmunozv04/iSponsorBlockTV)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Add at least one TV in setup Run the command-line setup (`iSponsorBlockTV setup-cli`) and add at least one TV screen (the TV or compatible device you want to control) before starting the app. If the device list is empty, the app can fail to start, so this first-run step keeps it from breaking. source
  • Keep the config file safe The configuration file holds your TV names, screen IDs (unique codes for each TV), API key (a code the app uses), and skip settings, so keep a copy somewhere safe. If that file is lost or corrupted, you will need to set up the app again. source
  • Use a persistent folder in Docker If you are using Docker (container software), point the container to a local data folder that stays around and run `--setup-cli` inside it. That folder is where your settings are stored, so it must survive between container runs. source

Fetched 54 days ago - each note links to its source

Alternatives (6)

  • AdAway - An ad blocker that uses the hosts file.
  • AdGuard - AdGuard is the best way to get rid of intrusive ads and online tracking, and to protect your computer from malware.
  • Blokada - Blokada is the popular ad blocker and privacy app for Android and iOS.
  • NextDNS - NextDNS protects you from all kinds of security threats, blocks ads and trackers on websites and in apps and provides a safe and supervised…
  • SponsorBlock - SponsorBlock is an open-source crowdsourced browser extension to skip sponsor segments in YouTube videos.
  • Tubular - Fork of a lightweight streaming client adding SponsorBlock to skip sponsor segments and ReturnYouTubeDislike to display dislikes, with supp…

Checked 27 days ago - source: AlternativeTo

Common questions

Why does iSponsorBlockTV fail to start on first run?

Run the setup command line and add at least one TV screen before starting the app. If the device list is empty, the app can fail to start.

Do Apple TV users need an extra authentication step?

Some Apple TV setups may require you to authenticate the Apple TVs separately before iSponsorBlockTV can work.

Answers sourced from community.home-assistant.io, github.com

Community

Collected 27 days ago - public community threads