dmunozv04 /iSponsorBlockTV
SponsorBlock client for all YouTube for TV clients.
★ 7,098⑂ 310👁 20⑃ 267● 227▤ 28◈ 27
7,098
stars
310
forks
20
watchers
267
prs
227
issues
28
releases
27
discussions
README
iSponsorBlockTV iSponsorBlockTV is a self-hosted application that connects to your YouTube for TV app (see compatibility below) and automatically skips segments (like Sponsors or intros) in YouTube videos using the SponsorBlock API. It can also auto mute and press the "Skip Ad" button the moment it becomes available on YouTube ads. Installation Check the wiki Compatibility Legend: ✅ = Working, ❌ = Not working, ❔ = Not tested Open an issue/pull request if you have tested a device that isn't listed here. | Device | Status | |:-------------------|:------:| | Apple TV | ✅ | | Samsung TV (Tizen) | ✅ | | LG TV (WebOS) | ✅ | | Android TV | ✅ | | Chromecast | ✅ | | Google TV | ✅ | | Roku | ✅ | | Fire TV | ✅ | | CCwGTV | ✅ | | Nintendo Switch | ✅ | | Xbox One/Series | ✅ | | Playstation 4/5 | ✅ | Ad muting won't work when using AirPlay to send the audio to another speaker. Shorts aren't fully supported due to limitations on YouTube's side. A single short can be seen by either selecting the "Disconnect" option in the warning shown or by long pressing the thumbnail to open the menu and clicking play from there Usage Run iSponsorBlockTV on a computer that has network access. It doesn't need to be on the same network as the device, only access to youtube.com is required. Auto discovery will require the computer to be on the same network as the device during setup. The device can also be manually added to iSponsorBlockTV with a YouTube TV code. This code can be found in the settings page of your YouTube TV application. Libraries used - pyytlounge Used to interact with the device - asyncio and aiohttp - async-cache - Textual Used for the amazing new graphical configurator - ssdp Used for auto discovery Projects using this project - Home Assistant Addon Contributing 1. Fork it () 2. Create your feature branch (git checkout -b my-new-feature) 3. Commit your changes (git commit -am 'Add some feature') 4. Push to the branch (git push origin my-new-feature) 5. Create a new Pull Request Contributors Made with contrib.rocks. License
Top issues
#283Autoplay toggle not working as expected20 comments · 2025-03-26#74Web Interface12 comments · 2023-10-16#471AutoPlay "false" not working on tvOS9 comments · 2026-06-08#201SponsorBlock skips the segment but gets stuck in a loop, and keeps skipping and playing the part of the video9 comments · 2024-11-19#152Request for instructions and guide for installing on Unraid9 comments · 2024-05-05#480Does not work on Google Streamer 4K8 comments · 2026-06-29#256iSponsorBlockTV 3.08 comments · 2025-02-22#252You can test via a website if it makes things easier8 comments · 2025-02-21
Discussions
#520Created Webui front end for iSponsorBlockTV1 comments · 2026-11-10#511What to expect with iSponsorBlockTV1 comments · 2026-10-21#500Feature idea: Automatically retry a video when an unskippable ad appears0 comments · 2026-09-05#498Exitting Pop-Up Ads0 comments · 2026-08-27#446iSponsorBlockTV stopped running, how to debug?1 comments · 2026-04-18#434A strange experience last night - one of my friends could connect to my YouTube App from his home, and YouTube said he used iSponsorBlockTV to connect1 comments · 2026-03-31#433Automatically Reduce Volume of Adverts1 comments · 2026-03-30#431Would be nice to specify an IP address of the streamer box on a segregated network?1 comments · 2026-03-22
Latest release
v2.11.0: fixing a blind SSRF on DIAL auto discovery v2.11.0 2026-08-21Fixed blind SSRF on DIAL auto discovery Fixes advisory: GHSA-56v3-jrq2-4q9m / CVE-2026-77597 It's recommended for all users to update to this latest version (v2.11.0) This issue could allow an attacker controlled device on the same lan as iSponsorBlockTV to request an arbitrary URL by abusing the DIAL auto-discovery. It'd be able to either: - show a debug log line - __main__ - DEBUG - Discovered device at , processing... (which is normally disabled and won't be shown in the actual configurator since textual doesn't show logs unless running in dev mode and launching a second terminal to in