Zygisk

What is Zygisk?

Zygisk is a Magisk feature that lets modules run code inside every Android app's process. Integrity modules, Xposed frameworks and root-hiding modules all depend on it. It is off by default: you turn it on in Magisk's settings and reboot.

Last updated 13 sourcesHow we check pages

In one paragraph

On Android, every app process is started by forking a system process called zygote. Zygisk ("Zygote" plus "Magisk") runs inside zygote. In the words of Magisk's developer guide, it "allows advanced module developers to run code directly in every Android applications' processes before they are specialized and running". Modules ship their Zygisk code as native libraries in a zygisk/ folder.

Key facts

  • Built into MagiskSince v24.0January 2022, replacing MagiskHide
  • DefaultOffSettings → Zygisk, then reboot
  • Module APIVersion 5Magisk 27.0 and later
  • Newest AndroidAndroid 17Since v31.0; v30.7 supports up to Android 16 QPR2

What it is used for

How it works

Zygisk doesn't patch zygote on disk. Magisk points an Android property, ro.dalvik.vm.native.bridge, at its own loader library. Android's runtime loads whatever native bridge that property names when zygote starts, so the loader ends up inside zygote. From there Zygisk hooks a few functions so that it can replace zygote's app-forking methods (nativeForkAndSpecialize, nativeSpecializeAppProcess and nativeForkSystemServer). If the phone already uses a real native bridge, Zygisk loads it as well.

How Zygisk gets into an app

  1. 1Magisk sets a propertyro.dalvik.vm.native.bridge points to Zygisk's loader
  2. 2Zygote loads itAndroid's runtime loads the “native bridge” at startup
  3. 3Zygisk hooks zygoteReplaces the functions that fork and specialize apps
  4. 4Modules runBefore and after each app is sandboxed
  5. 5Zygisk unloadsIts own code leaves the app process
Simplified from the bootstrap notes in Magisk's zygisk/hook.cpp and zygisk/daemon.rs at v31.1.
  • Where module code runs: each module's preAppSpecialize runs with zygote's privileges, just before the new process is locked into the app's sandbox; postAppSpecialize runs inside the sandbox. Magisk's API header stresses that module code runs in the app or system_server process, not in the zygote daemon, and never as real root. Modules that need root use a separate "companion" process. Details on module development.
  • Safety net: if zygote crashes more than three times after Zygisk loads, Magisk restores the original property and stops loading Zygisk for the rest of that boot. Magisk's automatic Safe Mode also turns the Zygisk setting off.

Enabling Zygisk

  1. Open the Magisk app and tap the settings (gear) icon.
  2. Turn on Zygisk ("Run parts of Magisk in the Zygote daemon").
  3. Reboot. Zygisk only starts at boot.
  4. Check the Home screen: the Zygisk line should read Yes (Enabled in the v31 app). It shows whether Zygisk actually loaded, not just the setting.

Messages you may see on a module's card in the Modules tab:

  • "Module suspended because Zygisk isn't enabled": the module needs Zygisk. Turn it on and reboot.
  • "Zygisk module not loaded due to incompatibility": Magisk created an unloaded file in the module's zygisk/ folder because its native libraries don't fit your system (for example, no library for your CPU architecture). Look for an update from the module's developer.

Zygisk and the DenyList

Magisk v24.0 introduced Zygisk and, alongside it, the DenyList, described in the changelog as a feature "to revert Magisk features in user selected processes". The same release removed MagiskHide. You choose apps and processes under Configure DenyList in Magisk's settings, and the Enforce DenyList switch decides what happens to them:

Enforce DenyListWhat happens in a listed app's processTypical use
OnMagisk's and modules' mounts are unmounted, and no Zygisk module is loaded into the process.Plain Magisk, keeping modules away from banking and work apps
OffNothing is reverted. Zygisk modules still load and can see that the process is on the DenyList (the PROCESS_ON_DENYLIST flag).Hiding modules such as Shamiko, which use the list as their target list

Since v28.0 the DenyList can be enforced even when Zygisk is off, and v31.0 added webview_zygote as an unmount target. From a root shell, magisk --denylist ls, add PKG [PROC], rm, enable and disable manage the same list.

The DenyList is not a root-hiding system. Magisk's FAQ says root hiding is left to modules. See banking apps that detect root.

History

VersionChangelog entry
v24.0 (2022-01-26)"Introduce new feature: Zygisk" and "Introduce DenyList feature". MagiskHide removed.
v24.3 (2022-03-10)"Update API to v3, adding new fields to AppSpecializeArgs"
v26.0 (2023-04-05)"Release new API version 4"
v27.0 (2024-02-03)"Introduce new code injection mechanism". The module sample lists API v5 as needing Magisk 27.0 (version code 27000).
v28.0 (2024-10-10)"Support enforcing denylist when Zygisk is disabled"
v30.7 (2026-02-23)"Support Android 16 QPR2 and higher"
v31.0 (pre-release, 2026-09-04; included in stable v31.1)"Support Android 17 (API 37)"

Zygisk Next vs ReZygisk vs NeoZygisk

KernelSU and APatch do not include Zygisk, so standalone implementations provide the same module API there. Three are maintained. They can also replace Magisk's built-in Zygisk, but on Magisk the built-in one is the default choice and most users need nothing else.

Which Zygisk should you use?

Which root solution do you use?
  • Magisk
    Does a module you rely on ask for a specific implementation?
    • No
      Magisk's built-in Zygisk
    • Yes
      That one, with built-in Zygisk turned off
  • KernelSU or APatch
    Must it be open source?
    • Yes
      NeoZygisk or ReZygisk
    • No
      Zygisk Next on KernelSU (closed source; APatch isn't listed in its README)
Based on each project's README and releases, checked October 26, 2026.
Magisk built-inZygisk NextReZygiskNeoZygisk
MaintainertopjohnwuDr-TSNGPerformanCJingMatrix
Source codeOpen (GPL-3.0; the Zygisk API headers are 0BSD)Closed since v4-0.9.2, “all rights reserved”Open; README says AGPL-3.0, repository lists GPL-3.0Open (GPL-3.0)
Latest releasePart of Magisk v31.1 (stable)v1.5.2, Oct 15, 2026v1.0.0, May 10, 2026v2.4, Aug 8, 2026
Root solutionsMagiskKernelSU (10940+), Magisk (26402+)KernelSU, APatch, MagiskKernelSU, APatch; can replace Magisk's built-in Zygisk
On MagiskSettings → ZygiskREADME: built-in Zygisk must be offREADME: turn built-in Zygisk off, they conflictLeave Magisk's Enforce DenyList off (README)
Android 17v31.0 and later (stable since v31.1)QPR2 betas supported since 1.4.5 and 1.5.0Not statedv2.4 and later
DenyListMagisk's DenyList, optionally enforcedAdds an “Unmount only” mode (lets modules inject while mounts are reverted); 1.3.0 integrated most of Shamiko's featuresNot documented in its READMEIts own handling of Magisk's DenyList: unmounts in zygote, or switches the app to a clean mount namespace

Which one should I use?

  • Magisk users: the built-in Zygisk. It is maintained with Magisk itself, gained Android 16 QPR2 support in v30.7 and Android 17 support in v31.0 (stable from v31.1), and modules such as Vector and PlayIntegrityFork work with it. Switch only if a module you rely on asks for a specific implementation.
  • KernelSU or APatch users who want open source: NeoZygisk or ReZygisk. ReZygisk describes itself as a fork of Zygisk Next rewritten in C; NeoZygisk is maintained by the developer of Vector and added Android 17 support in v2.4.
  • KernelSU users who want the most features: Zygisk Next, accepting that it is closed source. Its “Unmount only” DenyList mode lets modules inject while mount changes are reverted.
  • Never run two at once. Install one implementation and turn the others off; on Magisk that includes the built-in Zygisk when you use a standalone one. Two at once is a common cause of a bootloop.

Versions and dates are from each project's GitHub releases as of October 26, 2026. All three standalone projects are listed with their status in the module catalog.

Writing a Zygisk module

Magisk points developers to the official Zygisk module sample, whose zygisk.hpp header is the API reference. Our walkthrough of the API, a minimal module and the build is in module development.

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