What Is Clash Verge Rev? Latest Version, GitHub & Migration

Clash Verge Rev is the actively maintained community continuation of the archived original Clash Verge. It uses the Mihomo kernel and is the version new desktop users should normally choose.

Choose the path that matches your intent:

• Need a Windows, macOS or Linux installer? Choose the correct release asset.
• Need to verify the repository or avoid fake downloads? Check the authoritative GitHub sources.
• Comparing the original with Rev or planning a migration? Continue below.

Clash-verge.com is an independent community guide. The project source is the clash-verge-rev/clash-verge-rev GitHub repository.

What is Clash Verge Rev? #

Clash Verge Rev is a community-maintained continuation created after the original Clash Verge repository stopped active development and was archived. It keeps the desktop interface for Windows, macOS and Linux while following the actively maintained Mihomo kernel.

“Rev” is commonly read as revival or revised: a revived and updated continuation rather than a paid edition or a crack.

Original Clash Verge vs Clash Verge Rev #

The key distinction is maintenance status. The original application is still useful as historical source code, but Rev is the branch that receives current desktop releases.

How to tell which version you installed #

Open Settings → About and inspect the project link or package identity:

• github.com/clash-verge-rev/clash-verge-rev means Clash Verge Rev.
• github.com/zzzgydi/clash-verge means the archived original.
• A file or About page that points to neither repository should be verified before you trust it.

Other signs of Rev include a v2.x application version, a current Mihomo core and release notes that link to the clash-verge-rev organization.

Should you migrate? #

Migrate if you still use the original #

Migration is recommended when you need current operating-system compatibility, a maintained Mihomo core, newer protocol support, or recent TUN/DNS fixes.

Stay on Rev if it already works #

If Settings → About points to the Rev repository, you do not need a separate migration. Keep the application and core updated through a current GitHub release.

Treat legacy systems separately #

Windows 7 users cannot move directly to the current v2.x build. Any compatible historical build will be old and unmaintained, so evaluate the security and compatibility cost before installing it.

Migration checklist: original to Rev #

1. Back up subscription URLs and custom work #

Copy each subscription URL to a secure note. Also record:

• custom prepend or append rules;
• manually added nodes;
• proxy-group changes;
• DNS or port overrides;
• whether you use System Proxy or TUN.

Do not assume the application directory alone contains every item you need. Subscription URLs are the most important recovery data.

2. Record the original configuration directory #

Typical original paths include:

Back up the directory before uninstalling. Paths can vary by package and application version.

3. Exit the original completely #

Turn off System Proxy or TUN, exit from the tray, and end leftover Clash/Mihomo processes. This prevents a stale system proxy or virtual adapter from making the computer appear offline after removal.

4. Install Clash Verge Rev #

Use the platform-specific installer list. Most Windows 10/11 x64 computers need Clash.Verge_2.5.2_x64-setup.exe; Apple Silicon Macs need the aarch64 DMG.

5. Re-import subscriptions #

Open Profiles, paste each saved URL, import it, and select the intended profile. If parsing fails, request Mihomo or clash.meta output from the provider.

6. Recreate custom rules and overrides #

• Add domain, IP or process rules with Edit Rule.
• Recreate global DNS, port or application bypass settings with the Global Extended Configuration and verge.yaml guide.
• Do not edit the downloaded subscription file directly; an update will overwrite it.

7. Restore the network mode gradually #

Start with Rule mode and System Proxy. Confirm browsing works, then enable TUN only if you need broader routing. If TUN does not start, follow the Service Mode and TUN diagnosis.

Common migration problems #

The subscription cannot be parsed #

The provider may still generate fields for an older Clash/Clash Meta client. Ask for Mihomo or clash.meta output, then import a fresh URL.

A node disappeared or shows an unsupported type #

The subscription converter may have omitted or malformed the node. Compare the raw profile with the provider’s current Mihomo format rather than copying a node blindly from the old application directory.

Custom rules vanished #

Rules added directly to a downloaded profile are overwritten during refresh. Recreate them through Edit Rule or an Extended Script.

The computer has no internet after uninstalling #

A stale System Proxy setting may remain enabled. Disable the operating-system proxy, close leftover processes, and then launch Rev. For TUN adapter conflicts, use the TUN troubleshooting guide.

Summary #

Next: choose an installer · verify the GitHub project source · follow the setup guide · troubleshoot common errors