We do not host or distribute ReVanced. The patcher and its Manager come from the ReVanced project itself, published at revanced.app and on GitHub.
How YouTube Music ReVanced Works
ReVanced is a patcher, not a modified app someone hands you. You supply an unmodified YouTube Music APK, the Manager applies a list of patches to its compiled code and resources, and the output is a new APK signed with a key generated on your own device. That signature is why the patched build cannot install over a Play Store copy of the same app: Android refuses to replace an app with one signed by a different key.
The practical consequence is that the patched Music app is a fork frozen at whatever version you patched. It does not update itself. When you want a newer base version or newer patches, you run the process again. That repeat cost is the honest trade for not paying a subscription, and it is worth knowing before you start rather than after your first broken update.
Available Music Patches
- Ad removal - hides audio and visual advertisements
- Background playback - keeps music playing with the screen off
- Custom themes - dark and AMOLED options
- Hide components - strips UI elements you do not want
- Codec and audio quality options, on builds where the patch set includes them
- Exit or minimize behaviour tweaks, such as stopping the app from resuming playback on launch
The exact list shifts between patch releases. Treat the Manager's own patch selection screen as the authority; anything described on a third-party page, this one included, can be out of date by a release or two. Our patches overview explains what the common ones do in more detail.
What patches cannot do is worth stating plainly. Offline downloads, lossless audio tiers, and anything else gated by an entitlement check on Google's servers stay locked. A patch edits the app on your phone. It does not change what your account is permitted to do. If that gap matters, the ReVanced and YouTube Premium comparison lays out the trade honestly.
Requirements and Compatibility
- An Android device. There is no iOS route, and no ReVanced Manager build for Android TV.
- Roughly 2 GB of free storage during patching. The Manager holds the source APK, intermediate files, and the output at the same time.
- The base YouTube Music version the Manager recommends. Patching a much newer or older build is where most failures begin.
- GmsCore for non-root installs, if you want to sign in.
- Permission to install unknown apps, granted to whichever app performs the install.
How to Set Up YouTube Music ReVanced
The process mirrors patching YouTube through ReVanced Manager:
- Download ReVanced Manager from the official GitHub
- Select YouTube Music as the target app
- Choose the supported version
- Pick the patches you want
- Build and install
Two details decide whether step five works. Install GmsCore before the patched app if you are on a non-root device, because the patched build looks for it at first launch. And uninstall the stock YouTube Music first if it is already present, since the signature conflict blocks the install with a message that says nothing useful about the real cause.
After installing, turn off automatic updates for YouTube Music in the Play Store. Otherwise the Store will eventually reinstall the official app over your patched one and every patch disappears at once, which reads exactly like the patches broke.
What Commonly Breaks, and Why
- Login fails or loops. GmsCore is missing, out of date, or was installed after the patched app. Install it first, sign in through GmsCore itself, then open the patched app.
- Patching fails partway. Usually a mismatched base version, occasionally a patch that has not caught up to a recent app release. The patch failed guide works through it.
- Playback stops when the screen locks. Not always a patch problem. Aggressive battery management on Xiaomi, Samsung, and Huawei devices suspends background audio regardless of what the app asks for. Exclude the app from battery optimisation.
- Ads return after weeks of silence. Either the Play Store replaced your build, or the ad delivery changed server-side. Check the app's signature source before assuming the patch failed.
- App not installed. Signature conflict with a leftover copy, including one belonging to a secondary user profile or work profile.
Verifying It Worked
Open a track and let it run past the point where an ad would normally interrupt. Then lock the screen and confirm audio continues and a media notification appears. Then check the app info screen: a patched build shows the ReVanced-signed package rather than the Play Store as its install source. If all three hold, the patch set applied cleanly. If background audio dies at lock but ads are gone, the problem is your device's power management, not the patch.
Honest Status
ReVanced is actively maintained and the Music target is part of the supported set, but it is a community project with no service guarantee. Patches lag behind app releases sometimes, a working combination can stop working after a YouTube backend change, and nobody owes you a fix on any timeline. The old YouTube Music Vanced app, by contrast, is discontinued and frozen at its final 2022 build. If you want something that simply keeps working without maintenance on your part, YouTube Premium is the option that provides that, at a monthly cost.
Frequently Asked Questions
No. They are two separate Android packages, and ReVanced treats them as two separate patch targets. If you patched YouTube and then opened YouTube Music expecting ads to be gone, you will still see ads, because the Music app on your phone is untouched. Run the Manager a second time and select YouTube Music as the target.
Only if you are not rooted. GmsCore stands in for Google Play Services so the patched app can sign in and sync your library. Rooted installs mount the patched app over the original and use the real Play Services already on the device, so GmsCore is not part of that route. Installing GmsCore after the patched app is already running rarely fixes a broken login; uninstall, install GmsCore first, then reinstall.
Two causes account for most reports. The Google Play Store quietly updated YouTube Music underneath your patched build, replacing it with the stock app. Or YouTube changed how ads are delivered on the server side, and the patch that removed them no longer matches. The first is fixed by turning off auto-update for that app and re-patching; the second waits on a patch update.
Offline downloads inside YouTube Music are tied to a Premium entitlement checked on Google's servers, so a local patch does not unlock them. Patches change the app on your device, not what your account is allowed to do. If offline libraries matter to you, a subscription is the route that actually provides them.
Usually not. The two apps ship on different release schedules and their patches are written against different code, so ReVanced Manager often recommends a different base version for each. Check the version the Manager suggests for the Music target specifically instead of assuming the YouTube number carries over.
Yes, provided you sign in with the same Google account. Playlists, uploads, likes, and history live on Google's servers rather than in the app, so a patched client sees the same library the stock app did.