Open-source project
verback2308/Opaline avatar
verback2308/Opaline

Opaline: an iOS 12 YouTube client that has to be side loaded

A lightweight, privacy-focused YouTube client for iOS built entirely with UIKit. No ads, no tracking, no dependencies.

401 stars45 forksSwiftGPL-3.0

At a glance

What is it?
A native UIKit YouTube client that targets iOS 12 hardware Google stopped supporting, distributed as an IPA or a Cydia package rather than through the App Store. The feature list is long and specific, but the install channel is the decision that matters.
Who is it for?
Opaline is for a device the official YouTube app abandoned, and on that device the feature set is unusually complete rather than a stripped fallback. The choice you have to make before anything else is the channel: an IPA through SideStore, AltStore or LiveContainer, or a rootful or rootless package from the Cydia repo, because installing both leaves an icon your Home Screen cannot delete.
Can I use it commercially?
Yes, with conditions. GPL-3.0 is a copyleft licence: if you distribute software that includes it, you must release that software's source code under the same licence. Running it internally without distributing it does not trigger that obligation.
Is it still maintained?
Yes. The repository last received commits 67 days ago.
What is it written in?
Mainly Swift, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • verback2308/Opaline401 ★ · +54
Star history
Repository2026-09-282026-11-15
verback2308/Opaline347401

54 Stars in the last 48 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

It shipped as YTLite until August, then took a different name

Opaline was released under the name YTLite until August, and the readme gives the reason plainly: it was renamed to avoid confusion with an unrelated tweak that goes by the same old name, and the project has nothing to do with that tweak. Anything you look for under YTLite lands you in the wrong place, so the rename is part of the project's story rather than a cosmetic change.

The scope is narrow on purpose. It is a native client for iOS 12 and above, written in Swift with UIKit, carrying no third party dependencies and no ads or tracking. The licence is GPL-3.0 and the default branch is main.

The origin story is the design constraint. When Google dropped support for the official YouTube app on older devices there was no way to watch properly, and browsers capped quality at 360p, which on that hardware barely ran. So the target is a specific iPhone or iPad that still works and is simply ignored, and the three most recent releases are all about media controls, downloads and playback.

1080p everywhere, and 2K only where AV1 decode exists

Playback quality is split by hardware rather than by setting. Every device gets up to 1080p at 60fps. Anything higher, 2K and 4K, needs hardware with AV1 decode, and the hardware list is given as iPhone 15 Pro and newer, plus M3 or newer iPads. That boundary is a decode capability, not a preference, so a device outside the list has no quality option to find.

The other hardware-facing decision is how much work happens at once. Thumbnails and channel details are fetched and decoded a few at a time rather than all at once, and that is what keeps scrolling smooth on a dual-core A7. On a device from that era, batch loading is the difference between a feed you can scroll and one you cannot.

Pinch to zoom fills the screen in fullscreen, and a Zoom to Fill setting does the same automatically. Autoplay is automatic and offers replay, previous and next when a video ends, background audio keeps playing with the screen off, Picture-in-Picture floats over other apps, and media controls work from Control Center, the lock screen and headphones. Playback position is restored the moment you reopen a video, without waiting for the server to catch up, and progress indicators are synced across devices.

A download brings the page it came from with it

Offline saving is treated as more than a video file. Saving a video also keeps its page: thumbnail, description, like counts and the comments as they stood at the moment you saved. That timestamped snapshot is the point, because an offline item still tells you what you found and why rather than being a bare file with no context.

The settings decide what travels. Under Settings, then Downloads, you pick the quality, how many comments to keep, and which subtitle languages to carry. There is a language detail worth noting: a video that plays dubbed in your language is saved dubbed, so the audio track you get offline is the one you were actually listening to.

Release 1.10.0 in August introduced video download and reworked playlists, mixes and jams. Release 1.12.0 on 10 September 2026 added hold to seek, channel search, and saving a download to Files. That last one is the small change that matters most on older hardware, where storage is tight, because the file can now be moved out of the app and into the system file manager.

Three ways to install, and a fourth that is not this project

There is no App Store build, so installation is the first real task. For a device that is not jailbroken, the recommended path is to add the source to a sideloading app to receive automatic updates. The manual path is to download the latest IPA from the releases page and install it with SideStore, AltStore or LiveContainer.

The third option is building it yourself, which takes three commands and one file you have to create:

bash
git clone https://github.com/verback2308/Opaline.git
cd Opaline
cp Config/Local.xcconfig.example Config/Local.xcconfig
./make_ipa.sh

The cp line is the step people miss. Config/Local.xcconfig does not exist in the repository, only Config/Local.xcconfig.example does, so the build script has nothing to read until you make the copy.

For a jailbroken device the address is different, and it is a channel to add rather than a file to download:

code
https://verback2308.github.io/repo/

Rootful (iphoneos-arm) and rootless (iphoneos-arm64) packages are both provided, and Sileo, Zebra and Cydia are supported. Every released version stays in the repo, so installing or rolling back to an older version happens from the package page version list in Sileo or Zebra. A separate downport by another developer, Joeviocoe/Opaline, covers armv7 devices on iOS 9.3 such as the iPad 2, iPad 3, iPad mini and iPhone 4S, with hardware keyboard support and account-free local subscriptions and history, and the readme states that project is not built, tested or supported here.

The repo package and the IPA fight over one bundle identifier

One warning in the install section is worth reading twice, because the failure is not recoverable from inside the app. Pick one channel and stay on it. The repo package and the IPA share a bundle identifier, and having both installed leaves an app icon on the Home Screen that the Home Screen cannot delete.

That is the specific shape of the problem. The duplicate is not visible in either package manager, so you cannot uninstall it there, and the extra icon lives in the one place that has no delete option for it. The fix described is to remove the other install first, the IPA from the Home Screen or the repo package from the package manager, and the sentence explaining which goes where is cut off before it finishes.

So decide before installing. Staying on the jailbroken repo gets automatic updates and a version list to roll back through. Without a jailbreak you are on the update cycle of whichever sideloading app you use, and there is no rollback list to browse.

Shorts preloads the next video and the tab can be deleted

Shorts get a native full screen viewer with vertical swiping, likes, comments and sharing, and the next short is preloaded so the viewer opens on video rather than on a poster frame. Tapping a short anywhere on the page carries the current list into the viewer, so a short opened from search keeps the context it arrived with. The whole Shorts tab can be switched off, which is the sort of control that matters when the feature competes with everything else for attention.

Kids content is handled by a dedicated playback source, and the reason given is concrete: it plays videos the standard API sources refuse. That is a workaround rather than a documented catalogue, so what is available depends on what those sources decline to serve.

The rest of the browse surface is built the same way. Search offers live suggestions, recent-search history and filters for sort, upload date, type and duration, with channel pages and playlists alongside. The home feed is endless recommendations with category chips read from the shelves in your own feed, and subscriptions run as a local feed. Notifications arrive through a bell in the top bar carrying app news and new version announcements with the full release notes in the message, while system notifications stay optional and everything still collects in app if you decline them.

Thirteen languages, and titles that follow the one you picked

Localization is two layers rather than one. The interface is localized into 13 languages, and separately, video titles, search results and feeds follow your language rather than staying in whatever language the video was uploaded in.

Media handling has the same attention to detail. Subtitles and captions are fully supported with VTT parsing, and audio tracks can be switched on multi-language videos or started dubbed automatically, with AI generated dubs marked with (AI) in the track name so you know what you are hearing. SponsorBlock skips sponsored segments automatically, and Return YouTube Dislike brings the dislike counts back. A feature list this specific is unusual for a side loaded client, and it says the work was in the media layer rather than the interface.

Appearance follows the system on iOS 13 and above, while iOS 12 gets scheduled hours, with a manual override always available. The layout is yours to choose as well: pick the tab the app opens on, force the app icon light or dark, and browse settings as a nested menu rather than one long list. On iPad the player and related videos sit side by side in a native layout.

make_ipa.sh is documented and make_deb.sh is not

The top level lists what you would expect for an Xcode project plus the two packaging paths around it: Opaline.xcodeproj/, the Opaline/ directory, OpalineOpenIn/, Config/, scripts/, source/, screenshots/, Makefile, make_ipa.sh, make_deb.sh, .swiftformat and .swiftlint.yml.

The build walkthrough covers make_ipa.sh and the Config copy, and stops there. Nothing visible describes how make_deb.sh is invoked, which is the gap that matters most, since the jailbroken channel is the one built on packages while the documented command produces an IPA. The scripts/ and source/ directories are likewise unexplained, OpalineOpenIn/ has no description anywhere visible, and the readme links to a Localization section that does not appear in what can be read here.

The Makefile is the tidiest part. It is six targets around two overridable tool paths, SWIFTLINT and SWIFTFORMAT:

text
lint:
	$(SWIFTLINT) lint --strict

analyze:
	$(SWIFTLINT) analyze --strict --compiler-log-path build.log

format-check:
	$(SWIFTFORMAT) . --lint

Strict mode on lint and on the analyzer, a build.log path for the compiler log, and a lint-only format check are the entire quality setup. There is no test target, so nothing in the Makefile runs a test suite.

Editorial conclusion

Opaline is for a device the official YouTube app abandoned, and on that device the feature set is unusually complete rather than a stripped fallback. The choice you have to make before anything else is the channel: an IPA through SideStore, AltStore or LiveContainer, or a rootful or rootless package from the Cydia repo, because installing both leaves an icon your Home Screen cannot delete. Check that your hardware falls inside the AV1 list if you care about 2K and 4K, treat the iOS 9.3 armv7 downport as a separate project, and read the bundle identifier conflict before you install anything.

Frequently asked questions

What is Opaline and what devices does it support?

Opaline is a native UIKit YouTube client for iOS 12 and above, written in Swift with no third party dependencies and no ads or tracking. It was released as YTLite until August and was renamed to avoid confusion with an unrelated tweak.

How do I install Opaline on a device that is not jailbroken?

Add the source to a sideloading app for automatic updates, or download the latest IPA and install it with SideStore, AltStore or LiveContainer. Building from source needs Config/Local.xcconfig copied from its example file, then ./make_ipa.sh.

Why should I not install both the Opaline IPA and the Cydia repo package?

They share a bundle identifier, so installing both leaves an app icon on the Home Screen that cannot be deleted from there. The readme says to pick one channel and remove the other install first.

Does Opaline work on an iPad 2 or an iPhone 4S?

Not from this repository. Those armv7 devices on iOS 9.3 are covered by a separate downport, Joeviocoe/Opaline, with hardware keyboard support and account-free local subscriptions and history, which is not built, tested or supported here.

Official sources

  1. Issues
  2. License: GPL-3.0
  3. README
  4. Releases
  5. verback2308/Opaline on GitHub
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.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/verback2308-opaline.svg)](https://hysenlabs.com/projects/verback2308-opaline)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/verback2308-opaline.svg)](https://hysenlabs.com/projects/verback2308-opaline)

Was this useful?