YTKACE: an open-source YouTube tweak for iOS, and its version-locking cost
YTKACE is a free, open-source YouTube enhancer and downloader for iOS with SponsorBlock, background playback, player controls, and interface customization.
At a glance
- What is it?
- YTKACE is an MIT-licensed iOS tweak that injects downloads, SponsorBlock, background playback and interface changes into the YouTube app. It requires a decrypted YouTube IPA you supply, and it locks to specific YouTube versions.
- Who is it for?
- Use YTKACE if you are on iOS 16 or newer, can source a decrypted YouTube IPA you are entitled to use, and want SponsorBlock plus real downloads badly enough to accept version chasing and terms-of-service risk. Do not use it if you want something that survives every YouTube update untouched, in which case YouTube Premium is the sanctioned path.
- Can I use it commercially?
- Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 6 days ago.
- What is it written in?
- Mainly Objective-C++, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on October 4, 2026, and from our analysis. They are not legal advice.
Editorial analysis
What YTKACE changes about the YouTube app on iOS
YTKACE is a modification for the official YouTube app on iOS. It does not replace YouTube; it hooks into it and adds behavior the app does not ship. The README's feature table is concrete: video, audio and Shorts downloads with queues and backup, background playback and picture-in-picture, speed and loop controls, SponsorBlock with category controls and skip modes, an OLED mode, tab reordering, and a downloaded-media library with resume. It also states a clear privacy posture: no activation service, no analytics, no telemetry and no updater. The audience is iOS users who want these capabilities inside YouTube and are already comfortable with sideloading or a jailbroken device. It runs on iOS 16.0 and newer, arm64 only.
A Theos tweak injected into a decrypted YouTube IPA
The mechanism is a classic iOS tweak. YTKACE is written in Objective-C++, built with Theos, and its Makefile targets a rootless package scheme on iphone:clang:latest:16.0. The source is organized as runtime hooks into the YouTube app, grouped by feature: an Ads and promo hook set, a SponsorBlock client with its own preferences and a DeArrow component, and a downloads stack with a stream resolver, a SABR downloader, an FFmpeg muxer and a backup manager. Because it patches the app from inside, it must be injected into a copy of the YouTube app. The README's build path is a GitHub Actions workflow: fork the repository, enable Actions, run the IPA workflow, and give it a direct link to a decrypted YouTube IPA you are legally allowed to use. The completed workflow hands back the injected IPA as an artifact.
Installing on jailbroken and sideloaded devices
There are two supported paths. On a jailbroken device you add the project's repository to Sileo, Zebra or Cydia, with both rootless and roothide packages published. The repository URL is:
https://itzzace.github.io/ytkace/On a non-jailbroken device you download the prebuilt IPA for your iOS version from the latest release and install it with TrollStore, AltStore, SideStore or LiveContainer. The version pairing matters: because YouTube 21.36.6 requires iOS 17, the project publishes two IPAs, one built on YouTube 21.33.6 for iOS 16 and newer, and one on 21.36.6 for iOS 17 and newer. You pick the 21.36.6 build unless you are on iOS 16.
SponsorBlock and downloads, against the version-locking problem
The features that draw people in are the ones YouTube does not offer: skipping sponsor segments through SponsorBlock, saving videos and audio for offline playback, and keeping audio going in the background. The cost is baked into how the tweak is built. Each release is pinned to a specific YouTube base version, 21.33.6 or 21.36.6 in the current release, and the changelog shows the project chasing YouTube updates release by release, for example updating for YouTube 21.36.6 and 21.35.3 in consecutive versions. When YouTube ships a new build, the tweak does not automatically follow. You wait for a matching YTKACE release or rebuild it yourself against a new base, and there is no in-app updater to smooth that over.
The IPA sourcing requirement and the legal boundary
The requirement that shapes everything is that YTKACE needs a decrypted YouTube IPA to inject into, and the README is explicit that this must be one you are legally allowed to use. The project ships the tweak, not YouTube, so sourcing that base app is on you, and modifying and redistributing a client app runs against YouTube's terms of service regardless of the tweak's own license. This is the honest boundary: the code is open and free, the capability is real, but using it means stepping outside the sanctioned app and accepting the terms-of-service and account risk that comes with a modified client. For anyone who will not or cannot source a decrypted IPA, the project has no runnable path.
YTKACE versus YouTube Premium
The sanctioned alternative is YouTube Premium, the official paid subscription. The difference is one of approach, not just price. Premium delivers background playback and ad-free viewing through the unmodified app, so it never breaks on an update, needs no sideloading, and carries no account risk. What it does not do is skip community-sourced sponsor segments the way SponsorBlock does, or save videos as files you control outside the app. YTKACE inverts that: it is free and adds SponsorBlock and real file downloads, but you pay in setup effort, version chasing and the risk of running a modified client. If update-proof simplicity matters most, Premium wins; if SponsorBlock and downloads are the point, that is what YTKACE exists to provide.
MIT license, a candid disclosure, and release cadence
YTKACE is available under the MIT License, with a Third-Party Notices file for components under separate terms, so the code itself is permissively reusable. The README also carries an unusually direct disclosure: the author acknowledges that a playback fix shipped after version 0.8.0 was taken from another project and has since been removed, and that earlier code resembled another developer's interface, while stating that from 0.9.0 onward nothing remains from another project and inviting the named developer to point out anything still present. On cadence, releases are frequent and reactive: version 0.9.3 arrived on 2026-09-12 tracking YouTube 21.36.6, following 0.9.2 on 2026-08-31, which is the pattern you should expect from a tweak that has to keep pace with a moving host app.
Editorial conclusion
Use YTKACE if you are on iOS 16 or newer, can source a decrypted YouTube IPA you are entitled to use, and want SponsorBlock plus real downloads badly enough to accept version chasing and terms-of-service risk. Do not use it if you want something that survives every YouTube update untouched, in which case YouTube Premium is the sanctioned path. Before installing, match the IPA to your iOS version: the 21.33.6 build for iOS 16, the 21.36.6 build for iOS 17 and newer.
Frequently asked questions
What does YTKACE add to YouTube on iOS?
It adds video, audio and Shorts downloads, SponsorBlock, background playback and picture-in-picture, speed and loop controls, an OLED mode, and tab customization, injected into the official YouTube app. It has no analytics or telemetry.
Do I need a jailbreak to install YTKACE?
No. On a jailbroken device you add its repository in Sileo, Zebra or Cydia. On a non-jailbroken device you install the prebuilt IPA with TrollStore, AltStore, SideStore or LiveContainer.
Why does YTKACE publish two IPAs?
Because YouTube 21.36.6 requires iOS 17, the project ships one build on YouTube 21.33.6 for iOS 16 and newer, and one on 21.36.6 for iOS 17 and newer. You pick the 21.36.6 build unless you are on iOS 16.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/itzzace-ytkace)