iSponsorBlockTV

Self-hosted SponsorBlock for YouTube TV apps, honestly reviewed. What works, what doesn’t, and whether it’s worth the setup.

TL;DR

• What it is: A self-hosted daemon that connects to YouTube TV applications on Smart TVs, streaming sticks, and consoles, then auto-skips sponsor segments and presses “Skip Ad” using the crowdsourced SponsorBlock database [README].
• Who it’s for: Anyone who watches YouTube on a TV device and is tired of manually fast-forwarding through sponsor reads. Browser extension users who moved to the living room and lost their quality-of-life tools.
• Cost savings: There’s no SaaS equivalent that does exactly this. The closest alternative — YouTube Premium — runs $13.99/mo and removes pre-roll ads but does nothing about in-video sponsor segments. iSponsorBlockTV self-hosted costs $0 on existing hardware, or $3–5/mo if you deploy it on a cheap VPS [README].
• Key strength: Works across 12+ device types — Apple TV, Roku, Fire TV, Samsung Tizen, LG WebOS, Android TV, Chromecast, Google TV, Nintendo Switch, Xbox, PlayStation [README]. One deployment covers your entire living room.
• Key weakness: Requires a always-on computer or server to run. No web UI for management — configuration is done via a terminal TUI. Not plug-and-play for non-technical users.

---

What is iSponsorBlockTV

iSponsorBlockTV is a Python daemon that acts as a remote control intermediary between a server you run and your YouTube TV application. When you watch a YouTube video on your TV, the daemon monitors your playback position in real time and, when it hits a segment flagged in the SponsorBlock community database, automatically issues a seek command to jump past it — or mutes the audio for categories where jumping would be disruptive [README].

The core problem it solves is a real one: SponsorBlock exists as browser extensions and mobile app integrations, but YouTube’s TV applications — whether baked into your Samsung TV, running on a Roku, or installed on an Apple TV — are closed environments where extensions can’t run. iSponsorBlockTV gets around this by talking to the YouTube Lounge API (the same protocol YouTube’s mobile remote control uses), which lets it monitor and control any paired TV session without modifying the TV device itself [README].

The project is maintained by dmunozv04, is licensed GPL-3.0, and sits at 5,153 GitHub stars with 226 forks and 29 contributors [GitHub]. It ships Docker and docker-compose support, which is the recommended install path. The most recent release at the time of this review is v2.6.1 (October 19, 2025), with 22 releases total across 564 commits — a sign of active maintenance over multiple years [GitHub].

There’s no company behind this. It’s a community tool solving a community problem.

---

Why people use it

The audience for this tool is specific and the motivation is consistent: you use SponsorBlock in your browser and have gotten used to never hearing “this video is sponsored by” read aloud for 90 seconds. Then you open YouTube on your TV and the sponsors are back. iSponsorBlockTV exists to close that gap.

What makes it compelling versus just buying YouTube Premium:

Premium doesn’t solve the actual problem. YouTube Premium removes pre-roll and mid-roll ads inserted by YouTube. It does nothing about sponsor segments, product placements, self-promotions, intros, outros, and subscription pitches that creators embed directly into the video timeline. SponsorBlock covers all of those categories. A Premium subscriber still manually fast-forwards through “before we start, check out my Patreon” [README][SponsorBlock API].

Breadth of device support. iSponsorBlockTV works with Apple TV, Samsung TV (Tizen), LG TV (WebOS), Android TV, Chromecast, Google TV, Roku, Fire TV, CCwGTV, Nintendo Switch, Xbox One/Series X, and PlayStation 4/5 [README]. This is not a tool for one device — one running instance handles every YouTube TV app on your network that you pair with it.

The setup cost is one-time. Once deployed, it runs silently in the background. You don’t think about it again. It’s not a subscription. It doesn’t have pricing tiers. The SponsorBlock database it queries is free, crowdsourced, and has been running since 2019 with millions of submissions [SponsorBlock].

The fmhy.net community wiki — a widely-followed free media resource — lists iSponsorBlockTV as a recommended tool in its curated self-hosted utilities index [1][2], which is a reasonable signal of community trust in a tool with no marketing budget.

---

Features

Segment skipping:

• Auto-skips sponsor segments, intros, outros, self-promotions, interaction reminders, and any other SponsorBlock category you enable [README]
• Configurable per-category: you can choose to skip sponsors but only mute interaction reminders, for example
• Uses the SponsorBlock public API — same database as the browser extension [README]

Ad interaction:

• Auto-presses the “Skip Ad” button the moment it becomes clickable on YouTube pre-roll ads [README]
• Auto-mutes YouTube ads when skip isn’t available
• Note: ad muting doesn’t work on Apple TV when using AirPlay to route audio to a separate speaker [README]

Device pairing:

• Auto-discovery via SSDP for devices on the same network during initial setup [README]
• Manual pairing via YouTube TV code (found in the TV app’s settings) — this works even if the server and device are on different networks, as long as the server has outbound internet access to youtube.com [README]
• Multiple devices can be paired to a single running instance

Interface:

• Graphical TUI configurator built with Textual — a proper terminal UI, not just config file editing [README]
• Docker and docker-compose for deployment [README]
• Home Assistant addon available for Home Assistant OS users [README]

Limitations worth knowing upfront:

• YouTube Shorts are not fully supported — there are workarounds (long-pressing the thumbnail) but it’s not seamless [README]
• The daemon needs to run continuously; if the server goes down, your TV gets sponsors back
• No web UI — management is terminal-only
• Apple TV ad muting has the AirPlay limitation noted above [README]

---

Pricing: SaaS vs self-hosted math

iSponsorBlockTV has no SaaS equivalent — there’s no paid cloud service that does what it does. The relevant cost comparison is between self-hosting this and the alternatives people actually consider:

YouTube Premium: $13.99/mo (individual), $22.99/mo (family). Removes pre-roll ads. Does not skip sponsor reads, intros, outros, or anything embedded in the video by the creator. Annual cost: ~$168 individual.

Manual fast-forwarding: Free. Requires attention and effort. Fails silently when you’re distracted. Not a real solution for passive viewing.

iSponsorBlockTV on existing hardware (an old Raspberry Pi, a NAS, a spare mini PC): $0/mo operational cost. One-time setup time of roughly 30–90 minutes for a technical user.

iSponsorBlockTV on a cheap VPS (Hetzner CAX11, Contabo VPS S, DigitalOcean Basic): $3–6/mo. The daemon itself is lightweight — it’s monitoring playback position and making occasional API calls, not transcoding video. A $4 ARM instance is enough.

Concrete math: If you were considering YouTube Premium for sponsor-skipping on the TV, self-hosting iSponsorBlockTV saves you $168/year minus $48–72/year VPS cost = $96–120/year saved, while actually doing more (sponsors, intros, outros vs. just pre-rolls). On existing hardware, that’s $168/year straight savings.

The SponsorBlock API itself is free, donation-supported, and requires no account or API key for basic use [SponsorBlock].

---

Deployment reality check

The recommended install is Docker Compose, and the repository ships a docker-compose.yml [README]. The basic flow:

1. Clone the repo or pull the Docker image (dmunozv04/isponsorblocktv on Docker Hub or ghcr.io/dmunozv04/isponsorblocktv)
2. Run the graphical configurator via docker run -it to pair devices and set preferences
3. Start the daemon in detached mode

What you need:

• A machine that stays on — Raspberry Pi, NAS, old laptop, VPS, or Home Assistant OS (there’s a dedicated addon for HA users) [README]
• Docker installed
• Outbound internet access to youtube.com
• For auto-discovery during setup: the server needs to be on the same local network as the TV device

What can go sideways:

• Network changes break pairing. If your TV gets a new IP or you change network configurations, you may need to re-pair
• YouTube API changes. The tool depends on the YouTube Lounge/TV API, which is undocumented and can break without notice when Google pushes updates. The project has 22 releases partially because it has needed to chase API changes [GitHub]
• Shorts limitation. The README explicitly notes this is a known issue due to YouTube’s implementation, not something iSponsorBlockTV can fully fix [README]
• No persistent web UI. If you’re used to managing tools through a browser dashboard, this will feel spartan. Configuration is a TUI session, not a settings page you revisit

The Home Assistant addon is the smoothest path for users already running HA — it integrates iSponsorBlockTV as a supervised addon with automatic startup and GUI access through the HA interface [README].

---

Pros and cons

Pros

• Broad device compatibility. 12+ device types confirmed working in the README compatibility table, including gaming consoles that no other ad-blocking tool touches [README].
• GPL-3.0 license. Genuinely open source. You can fork it, modify it, run it privately, contribute back.
• Does what YouTube Premium doesn’t. Skips sponsor reads, intros, outros, self-promos — not just pre-roll ads. Addresses the actual annoyance that makes YouTube watching on TV worse than browser [README][SponsorBlock].
• Lightweight resource footprint. Runs comfortably on a Raspberry Pi or tiny VPS. Not a resource-intensive service.
• Home Assistant integration. First-class HA addon means the largest self-hosted home automation community has a clean install path [README].
• Active maintenance. 22 releases, 564 commits, last release October 2025 — not an abandoned project [GitHub].
• Graphical TUI configurator. The Textual-based setup UI is significantly better than hand-editing JSON configs [README].
• No account required. No sign-up, no API key, no cloud dependency beyond querying the SponsorBlock public API.

Cons

• Always-on dependency. The daemon must run continuously. If your server reboots and the container doesn’t auto-restart, sponsors come back silently. Requires proper Docker restart policies.
• YouTube API fragility. Depends on undocumented YouTube internal APIs. Google has never blessed this use case and can break it intentionally or accidentally with any YouTube update. The project has had to patch this before.
• No web UI. Terminal-only management. Non-technical users will need help setting it up and will have no friendly interface for changes.
• Shorts aren’t fully supported. YouTube Shorts have a different playback mechanism and iSponsorBlockTV can’t reliably skip segments in them [README].
• Apple TV ad muting limitation. If you AirPlay audio to a soundbar or HomePod, ad muting breaks. Segment skipping still works, but the audio gap behavior is off [README].
• No dedicated third-party reviews. Unlike tools like n8n or Activepieces, iSponsorBlockTV has no independent review coverage in tech publications. You’re mostly going on README, GitHub issues, and community word-of-mouth.

---

Who should use this / who shouldn’t

Use iSponsorBlockTV if:

• You already use SponsorBlock in your browser and watch YouTube on a TV device
• You have a Raspberry Pi, NAS, old mini PC, or Home Assistant server that can run a Docker container continuously
• You watch enough YouTube TV content that 90-second sponsor reads genuinely bother you
• You’re willing to spend an hour on initial setup and never think about it again
• You want to cover multiple TV devices — Apple TV and Roku in the living room, Fire TV in the bedroom — from a single running instance

Skip it if:

• You don’t have an always-on machine and don’t want to pay for a VPS
• Your YouTube TV usage is casual and sponsor reads aren’t a pain point for you
• You want a web GUI for managing the tool — this isn’t that
• You primarily watch YouTube Shorts on the TV

Consider the Home Assistant path if:

• You’re already running Home Assistant OS — the addon install is the path of least resistance [README]

---

Alternatives worth considering

YouTube Premium ($13.99–22.99/mo): Removes pre-roll and mid-roll ads from YouTube’s ad network. Does not address creator-embedded sponsor segments. If your complaint is the 5-second pre-roll, Premium solves it. If your complaint is sponsor reads, it doesn’t.

SmartTubeNext (Android TV only): A third-party YouTube client for Android TV with built-in SponsorBlock support, no server required. If your device is Android TV or Google TV and you’re okay replacing the YouTube app, this is simpler than iSponsorBlockTV — no server needed. Doesn’t work on Apple TV, Roku, Samsung Tizen, LG WebOS, gaming consoles, or Chromecast.

uBlock Origin (browser only): The standard answer for desktop YouTube. Not applicable to TV apps.

Pi-hole / AdGuard Home (network-level DNS blocking): Blocks ad domains network-wide but cannot block YouTube pre-roll ads served from youtube.com itself, and cannot skip sponsor segments embedded in videos. Solves a different problem.

Sponsorblock browser extension (browser only): The original, best-supported implementation. Use this on desktop. iSponsorBlockTV exists specifically because this doesn’t work on TV apps.

For the specific problem — SponsorBlock on TV devices — iSponsorBlockTV is effectively the only self-hosted option that works across the major platforms. SmartTubeNext is the Android TV-only alternative that requires no server.

---

Bottom line

iSponsorBlockTV is a narrow tool that does one thing well: it brings SponsorBlock to every YouTube TV app in your house, including devices that have never had any ad-blocking capability. The setup is real — you need a server, Docker knowledge, and patience for the initial pairing — but once it’s running, it runs invisibly. There’s no subscription, no cloud service to trust with your viewing data, and no vendor to raise prices on you.

The main risks are practical: it depends on undocumented YouTube APIs that Google can break, and it needs a machine that stays on. For users already running Home Assistant or a home server, those aren’t blockers. For users with no existing server infrastructure, the VPS math still works out well against YouTube Premium if sponsor skipping is genuinely important to you.

If you’ve been manually fast-forwarding through sponsor reads on your TV for years while SponsorBlock handles it silently in your browser, this is the tool that fixes the inconsistency.

---

Sources

1. FMHY — Free Media Heck Yeah (Video & Tools section) — Community wiki listing curated self-hosted media utilities including iSponsorBlockTV. https://fmhy.net/video
2. FMHY Vercel Mirror — Mirror of the FMHY wiki. https://fmhy.vercel.app/video
3. Track Awesome Self-Hosted — awesome-selfhosted/awesome-selfhosted — Aggregated updates to the awesome-selfhosted list, which includes iSponsorBlockTV. https://www.trackawesomelist.com/awesome-selfhosted/awesome-selfhosted/
4. SponsorBlock API — Crowdsourced sponsor segment database that powers iSponsorBlockTV. https://sponsor.ajay.app/

Primary sources:

• GitHub repository and README: https://github.com/dmunozv04/iSponsorBlockTV (5,153 stars, GPL-3.0, 29 contributors, last release v2.6.1 Oct 2025)
• Docker Hub image: https://hub.docker.com/r/dmunozv04/isponsorblocktv
• GitHub Container Registry: https://ghcr.io/dmunozv04/isponsorblocktv
• Installation wiki: https://github.com/dmunozv04/iSponsorBlockTV/wiki/Installation
• Home Assistant addon: https://github.com/bertybuttface/addons/tree/main/isponsorblocktv