Download

Download Magisk v31.1

Magisk is published only on its official GitHub repository. This page links straight to the current release, lists the checksum GitHub publishes for it, and shows our own check of the file. We do not host or mirror any files.

Last updated 7 sourcesHow we check pages

Latest stable: Magisk v31.1

Download from GitHub View the GitHub release

The download button points to github.com/topjohnwu/Magisk/releases. Phone on Android 6.0? Use v30.7, the last release that supports it. Updating from v30.7? Read what changed first.

What changed from v30.7 to v31.1

v31.1 is the current stable release: GitHub marks it as Latest, and the Magisk app's stable update channel offers it. It follows the v31.0 pre-release (September 4, 2026) and changes how the app works:

  • Android 7.0 or newer. v31.1 drops Android 6.0. On Android 6.0, stay on v30.7.
  • No root pop-ups. Apps no longer ask for root when they need it; you grant access ahead of time in the app's Superuser tab.
  • No app hiding. The option to hide the Magisk app under another name, and the stub app, are gone. The release notes suggest uninstalling the Magisk app once root access and modules are set up.
  • Easier patching. The app can patch straight from a factory image zip or a link, and on Pixels it offers the matching factory image. (v30.7 already reads full OTA zips and payload.bin.)
  • A new app. v31.0 rewrote the interface and added a built-in terminal for module installs and module actions, plus Android 17 support for Zygisk.

Already rooted with v30.7? Read moving from v30.7 to v31.1 before you update, especially if you hid the app: unhide it first.

Which file to download

Each GitHub release has a normal APK named after its version and an app-debug.apk. Magisk's README accepts bug reports only from debug builds, and its build documentation says switching to an official debug build (and reinstalling Magisk from it) turns off the signature check described below. Everyone else wants the normal APK.

Which APK fits you?

FeatureMagisk-v31.1.apkMagisk-v30.7.apkapp-debug.apk
Runs on Android 6.0NoYesPartlySame as its release
Root permission pop-upsNoGrant in Superuser tabYesPartlySame as its release
Hide the Magisk appNoYesPartlySame as its release
Patch from a factory zip or a linkYesPartlyOTA zip and payload.bin onlyPartlySame as its release
Daemon rejects non-matching Magisk appsYesYesNoCheck turned off
Accepted for bug reportsNoNoYes
For everyday useYesYesNoDevelopers and bug reports
From Magisk's changelog and release notes for v30.7, v31.0 and v31.1, its build documentation and README. Sizes from the GitHub release assets.
FileSizeLink
Magisk-v31.1.apk10.18 MBGitHub
app-debug.apk (v31.1)35.32 MBGitHub
Magisk-v30.7.apk (Android 6.0)11.08 MBGitHub

Recent releases

Recent Magisk releases

  1. v29.0Large internal refactoring; stable
  2. v30.3 (pre-release)Install into vendor_boot; Android 16 QPR2 sepolicy
  3. v30.6Stable; reverts a change that could cause bootloops
  4. v30.7Previous stable; the last release that supports Android 6.0
  5. v31.0 (pre-release)New app, built-in terminal, Zygisk on Android 17
  6. v31.1Current stable: Android 7.0 minimum, no root pop-ups, no app hiding
Dates and labels from Magisk's GitHub releases page, where v31.1 is marked Latest; changes from its changelog. Full list: release history.

Only use the official APK

Many websites offer "Magisk" downloads. Magisk's README says GitHub is the only source for official downloads. Magisk's build documentation explains that release builds use the certificate of the key that signed the official APK as a reference, and Magisk's root daemon rejects and uninstalls Magisk apps that don't match, to protect users from modified APKs.

"Magisk Manager" is an old name. Since v22.0 the manager and Magisk itself are a single app, the Magisk app, so there is nothing separate to download.

Verify the download

Compare the file's SHA-256 hash with the value above, which is the digest GitHub lists for the release asset:

Check the hash
# Linux $sha256sum Magisk-v31.1.apk # macOS $shasum -a 256 Magisk-v31.1.apk # Windows (PowerShell) >Get-FileHash Magisk-v31.1.apk -Algorithm SHA256

Our check of v31.1 on October 26, 2026

We downloaded Magisk-v31.1.apk from the GitHub release on a Linux x86_64 machine and ran the same checks. This is the unedited output. The hash matches the release digest above, and the APK is signed by the same John Wu certificate as v30.7: the fingerprints are identical. This was a check of the download only, not an install on a phone.

Download check, October 26, 2026 (21:57 UTC)
$ls -l Magisk-v31.1.apk -rw-r--r-- 1 root root 10679283 Oct 26 21:57 Magisk-v31.1.apk $sha256sum Magisk-v31.1.apk 89cefac0a318afa39fb3880c45c87b036c05bc1ebf02a7a715b7f8d7c26ac6e7 Magisk-v31.1.apk $unzip -o -q Magisk-v31.1.apk 'META-INF/*' $openssl pkcs7 -inform DER -in META-INF/CERT.RSA -print_certs -out cert.pem $openssl x509 -in cert.pem -noout -subject -issuer -dates subject=C = TW, L = Taipei, CN = John Wu issuer=C = TW, L = Taipei, CN = John Wu notBefore=Aug 14 17:23:44 2016 GMT notAfter=Jul 21 17:23:44 2116 GMT $openssl x509 -in cert.pem -noout -fingerprint -sha256 sha256 Fingerprint=B4:CB:83:B4:DA:D9:9F:99:7D:BE:87:2F:01:3A:A1:6C:14:EE:C4:1D:16:70:21:F3:71:F7:E1:33:0F:27:3E:E6

Our earlier check of v30.7 on October 26, 2026

We downloaded Magisk-v30.7.apk from the GitHub release on a Linux x86_64 machine and checked it. This is the unedited output. The hash matches the release digest, and the APK is signed by John Wu's certificate. To check the signer yourself, compare the certificate fingerprint with the one below. This was a check of the download only, not an install on a phone.

Download check, October 26, 2026
$ls -l Magisk-v30.7.apk -rw-r--r-- 1 root root 11613864 Oct 26 11:44 Magisk-v30.7.apk $sha256sum Magisk-v30.7.apk e0d32d2123532860f97123d927b1bb86c4e08e6fd8a48bfc6b5bee0afae9ebd5 Magisk-v30.7.apk $unzip -o Magisk-v30.7.apk META-INF/CERT.RSA $openssl pkcs7 -inform DER -in META-INF/CERT.RSA -print_certs -out cert.pem $openssl x509 -in cert.pem -noout -subject -issuer -dates subject=C = TW, L = Taipei, CN = John Wu issuer=C = TW, L = Taipei, CN = John Wu notBefore=Aug 14 17:23:44 2016 GMT notAfter=Jul 21 17:23:44 2116 GMT $openssl x509 -in cert.pem -noout -fingerprint -sha256 sha256 Fingerprint=B4:CB:83:B4:DA:D9:9F:99:7D:BE:87:2F:01:3A:A1:6C:14:EE:C4:1D:16:70:21:F3:71:F7:E1:33:0F:27:3E:E6

Questions people ask

What is the latest version of Magisk?

Magisk v31.1, released October 25, 2026. GitHub marks it as the latest release. It needs Android 7.0 or newer; the previous release, v30.7, is the last one for Android 6.0.

Where can I get Magisk for Android 6.0?

Use v30.7, the last release that supports Android 6.0. It is still on GitHub: Magisk-v30.7.apk (11.08 MB). Its SHA-256 is e0d32d2123532860f97123d927b1bb86c4e08e6fd8a48bfc6b5bee0afae9ebd5. Don't update it from inside the app: v31.1 won't run on Android 6.0.

I updated and apps no longer ask for root. Is it broken?

No. Since v31.1 there are no root pop-ups: grant access ahead of time in the Magisk app's Superuser tab. See root not working for the details.

Android won't let me install the APK

Android blocks apps from outside the Play Store until you allow the app you opened the file with (your browser or file manager) to install unknown apps. Android asks when you open the APK; allow it for that app, then go back and install.

I installed the app. Am I rooted now?

No. The app is the tool that installs Magisk; root needs a patched boot image flashed to the phone. Next step: how to install Magisk.

Where do I download Magisk Manager?

"Magisk Manager" is the old name. Since v22.0 the manager and Magisk itself are a single app, the Magisk app, so there is nothing separate to download.

Where is the Magisk zip?

There isn't a separate one. For the deprecated custom recovery method, rename the APK to .zip. For uninstalling from a custom recovery, rename it to uninstall.zip.

Is it safe to download Magisk from other sites?

Magisk's README says GitHub is "the only source where you can get official Magisk information and downloads". A file from elsewhere may be modified. If you have one, compare its SHA-256 with the value on the GitHub release before installing.

Sources

This page is written from the sources below. If anything here disagrees with them, the upstream source is correct.

Found a mistake or something out of date? Tell us and we will check it against the source and fix the page. Confirmed corrections are listed in the corrections log.

Report a problem with this page