Download the Magisk APK — the standard systemless root tool for Android in 2026. The APK serves as both the Magisk Manager app and boot-image patcher, so there is nothing extra to install. Actively maintained by topjohnwu with full module support, root hiding, and Play Integrity bypass.
Download Magisk v30.7Magisk is an open-source suite for Android that provides systemless root access, a boot-image patcher, and a module system for customization. The Magisk APK serves as both the installer and the on-device Magisk Manager app — one download handles patching, module management, and root grants. Created by John Wu (topjohnwu) and first released in 2016, it has become the dominant rooting solution for modern Android devices.
Unlike older tools such as SuperSU or KingRoot that modify the system partition directly, Magisk patches the boot.img (or init_boot.img on newer devices) so the actual system files remain untouched. This “systemless” approach means OTA updates are less likely to break, and root can be toggled on a per-app basis.
The project is hosted on GitHub with over 59,000 stars and an active community on Reddit (r/Magisk). If you are coming from an older rooting workflow, see our SuperSU download guide for a comparison of both tools side by side.
All APK files are built and signed by topjohnwu. Files are mirrored here directly from the official GitHub releases — always the latest stable build.
| Version | Channel | Released | Android | Download |
|---|---|---|---|---|
| Magisk v30.7 | Stable | Feb 2026 | 6.0+ | Download APK |
| Magisk Canary | Canary | Rolling | 6.0+ | Download APK |
The Magisk APK works as both the Magisk Manager app and the boot-image patcher. After installing the APK, use it to patch your boot.img directly — no separate app download is needed since v24.
Works on most modern devices without TWRP.
boot.img (or init_boot.img) from your device’s firmware package.magisk_patched_*.img) to your PC.adb reboot bootloaderfastboot flash boot magisk_patched_*.img (or init_boot on Pixel 7+, Samsung uses Odin).For older devices or those with TWRP already installed.
.apk to .zip..zip file to your phone’s storage.adb reboot recovery or hardware combo).For legacy devices, our SuperSU download page has the TWRP-flashable ZIP if you prefer the older tool.
Modules are small packages that modify system behavior without touching the actual system partition. They load at boot via the overlay mechanism, and can be disabled or removed at any time.
The official module repository is at Magisk-Modules-Repo on GitHub, and community-maintained catalogs like Androidacy Module Manager (MMRL) make browsing and installing modules easier from within the app.
| Module | What It Does | Status |
|---|---|---|
| Shamiko | Hides root from apps using DenyList — the successor to MagiskHide | Active |
| Play Integrity Fix | Passes Google Play Integrity checks (bank apps, GPay, Netflix) | Active |
| LSPosed | Xposed framework for Zygisk — per-app module hooks | Maintained |
| MagiskHide Props Config | Spoofs device fingerprint and build properties | Active |
| Universal SafetyNet Fix | Legacy SafetyNet bypass (deprecated — use Play Integrity Fix instead) | Legacy |
Beyond the official stable release, several forks and pre-release channels exist. Each targets a different audience:
| Fork / Channel | Maintainer | Key Difference | Status |
|---|---|---|---|
| Magisk Stable | topjohnwu | Official release. Recommended for most users. | Stable |
| Magisk Canary | topjohnwu | Rolling beta. Latest features, may have bugs. | Beta |
| Magisk Alpha | vvb2060 (contributor) | Experimental builds with unreleased features. Bleeding-edge. | Experimental |
| Magisk Delta | HuskyDG | Added MagiskHide back after official removal. Built-in Zygisk improvements. Now succeeded by Kitsune. | Archived |
| Kitsune Magisk | HuskyDG | Community continuation of Delta. Enhanced SU management and root hiding. | Active |
Which should you use? Start with the official Magisk Stable. Only consider forks if you have a specific need — for example, Kitsune if you need advanced root hiding that the official DenyList doesn’t cover.
One of the biggest concerns with rooting is losing access to banking apps, Google Pay, and streaming services that detect root. Here’s the current state:
Google retired SafetyNet in 2024 and replaced it with the Play Integrity API. Magisk handles this through a combination of Zygisk (built-in), DenyList (hides Magisk from selected apps), and community modules like Play Integrity Fix and Shamiko.
MagiskHide was the original solution, removed in v24+. It was replaced by DenyList (part of Zygisk), which prevents root-checking apps from seeing the su binary. For apps that check Play Integrity attestation (Google Pay, most banks), you also need the Play Integrity Fix module — it patches the device attestation response so the check passes.
If DenyList alone isn’t enough (some apps use advanced detection), the Shamiko module adds a deeper hiding layer that blocks environment detection probes used by apps like Momo and Hunter.
SuperSU by Chainfire was the dominant Android root manager from 2012 to 2018. It still works well on older devices (Android 5–10) but hasn’t received updates since v2.82. Magisk has taken its place as the modern standard. Here’s a side-by-side comparison:
| Feature | Magisk | SuperSU |
|---|---|---|
| Root method | Systemless (boot.img patch) | System partition modification |
| Last updated | v30.7 — Feb 2026 | v2.82 — 2017 |
| Module system | Yes (Zygisk + modules) | No |
| Play Integrity | Supported (with modules) | Not supported |
| Root hiding | DenyList + Shamiko | None |
| Android 12+ support | Full | No |
| OTA updates | Preserved (systemless) | Breaks (system modified) |
| Open source | Yes (GPLv3) | Closed source |
| Best for | Modern devices (Android 8+) | Legacy devices (Android 5–10) with TWRP |
Bottom line: If your device runs Android 11 or newer, use Magisk. If you have an older device with TWRP and just need basic root, SuperSU v2.82 still works reliably and is simpler to set up.
There are also newer alternatives emerging: KernelSU offers kernel-level root for devices with source-available kernels, and APatch provides a similar kernel-based approach. Both are still maturing and have smaller module ecosystems than Magisk. For most users, Magisk remains the safest and most supported choice.
init_boot.img rather than the traditional boot.img. Grab the correct image from your manufacturer’s firmware package for your exact build number before patching. Older Android versions (5.x and below) may work but are not officially tested./data/adb/modules will be wiped and must be reinstalled. Some Samsung devices will flash a stock boot image as part of the reset process, in which case you would need to re-patch the boot image and reflash via Odin or fastboot to restore root access.SuperSU v2.82 by Chainfire remains the simplest root solution for Android 5 through 10 devices running TWRP custom recovery. While it no longer receives updates, the flashable ZIP and APK continue to work reliably on thousands of legacy devices where Magisk’s boot-image patcher may not be supported. If your phone predates the bootloader-unlock era of modern Android, or you just need basic superuser access without modules or Play Integrity bypass, SuperSU is still a solid choice with a proven track record spanning over a decade. Unlike Magisk, SuperSU does not require a Zygisk layer, does not need module management, and requires only a one-time TWRP flash to grant permanent superuser access. Many users on Android 5, 6, 7, and 8 devices still run SuperSU without issues. It grants root to apps via a familiar permission dialog, just as Magisk does on newer devices. For devices that cannot unlock their bootloader or do not support fastboot patching, SuperSU via TWRP remains the most practical rooting method available.
If you are on a modern device (Android 11+), use Magisk instead. But for older hardware, SuperSU is battle-tested and proven.
Download SuperSU