Zygisk Next vs NeoZygisk (JingMatrix): Differences Explained

Who is JingMatrix?

JingMatrix is an Android developer best known for maintaining a popular LSPosed fork that kept the framework working on Android 15 and 16, and later the Vector project. JingMatrix also maintains NeoZygisk, which started as a fork of Zygisk Next's open-source code and is published under GPL-3.0.

JingMatrix doesn't develop Zygisk Next. The two projects are separate, even though they share early history.

What NeoZygisk does differently

NeoZygisk describes itself as a Zygote injection module implemented via ptrace. It provides Zygisk API support for KernelSU and APatch and works as a replacement for Magisk's built-in Zygisk. Its stated goals include full API compatibility with Magisk's Zygisk and strong concealment. Version 2.0 was a complete rewrite, and v2.4 added Android 17 support.

Concealment approach

NeoZygisk puts a lot of emphasis on hiding traces of root and injection from apps that look for them. Zygisk Next takes a different route, offering denylist modes and integration with hiding modules such as Shamiko. Neither approach is guaranteed to defeat every detection. Banking and game anti-cheat checks change often, so results vary by app and by month. If hiding is your main goal, test with the specific apps you care about rather than relying on general claims.

Comparison table

Choosing between them

• Pick Zygisk Next if you want the richest feature set, WebUI controls and 32-bit app coverage.
• Pick NeoZygisk if you value open-source code and a lean design, and pair it with JingMatrix's LSPosed tooling.
• Either way: install only one implementation and reboot between changes.

A note on LSPosed

LSPosed-style frameworks need a Zygisk implementation underneath. Both Zygisk Next and NeoZygisk can provide it. If you use JingMatrix's LSPosed fork or Vector, follow its current README for the recommended Zygisk implementation and version, because requirements change with new Android releases.

Shared history, different directions

Zygisk Next, ReZygisk and NeoZygisk all trace back to the same early open-source code. After Zygisk Next's licence change, each fork went its own way. ReZygisk focused on transparency and a C rewrite. NeoZygisk focused on a ptrace-based design and concealment. Zygisk Next kept adding features such as the ZN linker, Shamiko integration and diagnostics. That shared history is why standard Zygisk modules generally work on all three.

The 32-bit question

Many modern phones still run a 32-bit zygote for older apps, though newer devices are dropping 32-bit support entirely. Community notes indicate NeoZygisk dropped zygote32 support, while Zygisk Next continues to report 32-bit status where present. If you depend on Zygisk modules inside 32-bit apps, Zygisk Next is the safer choice. On 64-bit-only devices, this difference doesn't matter.

Switching from Zygisk Next to NeoZygisk

1. Remove ZN-only modules, which won't work on NeoZygisk.
2. Uninstall Zygisk Next in your root manager and reboot.
3. Flash NeoZygisk from JingMatrix's official GitHub release and reboot.
4. Reconfigure app unmount or hiding settings, following NeoZygisk's README.

Frequently asked questions

Is NeoZygisk better than Zygisk Next?

It's different rather than strictly better. NeoZygisk is open source and focused on concealment on 64-bit devices. Zygisk Next is more feature-rich and still covers 32-bit zygote.

Does NeoZygisk work with Magisk?

Check the current NeoZygisk README. Standalone Zygisk projects mainly target KernelSU and APatch, and Magisk support and requirements can change between releases.

Can I run NeoZygisk and Zygisk Next together?

No. Only one Zygisk implementation should ever be installed. Running two at once is a common cause of bootloops.

Will my ZN-specific modules work on NeoZygisk?

No. They use Zygisk Next's own API. Only standard Zygisk modules move across.

Which one should a beginner choose?

Zygisk Next is usually easier for beginners because its WebUI shows clear status and flags broken modules. If you want open-source code and don't need a WebUI, NeoZygisk is a reasonable choice.

How do I check which implementation is active?

Look at your root manager's module list. Only one Zygisk implementation should be enabled. With Zygisk Next, the module description and the znctl command also confirm injection status.

Bottom line

The two projects suit different priorities rather than one being clearly better. For a three-way view including ReZygisk, see the comparison on our homepage.