The official Clash Verge Rev release page drops a dozen files on you at once, and they all look alike. Pick the wrong one and you either cannot install it, or you end up running an x64 build through a translation layer. This page answers one question: how to tell from the filename whether a package is meant for your machine.

Start with your architecture

The architecture field in the filename decides everything else. Ten seconds to confirm it:

  • Windows: Settings → System → About, read "System type"; or run echo $env:PROCESSOR_ARCHITECTURE in PowerShell. AMD64 means x64, ARM64 means you want the ARM build.
  • macOS: Apple menu → About This Mac. An Apple M-series chip needs the ARM build, an Intel chip needs x64.
  • Linux: run uname -m. x86_64 maps to amd64/x64, aarch64 maps to arm64.

The same silicon goes by different names across projects: x64 = x86_64 = amd64, and arm64 = aarch64. Whichever spelling you see, it means the same chip.

Sponsored Where does the subscription link come from? Our partner provider gives you 1 GB of high-speed Hong Kong data at signup — import it in one click. Get high-speed nodes

Windows: setup.exe or msi

Clash Verge installation wizard showing the version number and install progress
The wizard is the last step — the filename decides whether it runs at all

Both contain the same program. The -setup.exe file is the usual graphical installer — double-click, next, next. The .msi is a Windows Installer package, which is what you want for group policy or a silent command-line rollout. For a single machine either one is fine.

Two prerequisites are worth remembering: Clash Verge Rev needs Windows 10 or newer, and it relies on the WebView2 runtime. Windows 11 ships with it and most Windows 10 machines got it with Edge. If it really is missing, the app launches but the window stays blank — that case is covered in startup and core crash troubleshooting.

Package formats on macOS and Linux

  • macOS: .dmg. Mount it and drag the icon into Applications. Being blocked on first launch is normal; the fix is in the macOS install guide.
  • Debian / Ubuntu: .deb, installed with sudo apt install ./filename.deb so dependencies come along.
  • Fedora / openSUSE: .rpm, via dnf or zypper.
  • Anything else: .AppImage. Run chmod +x and launch it directly — nothing is written into system directories.

Arch users can go through the AUR, but those are community packages and usually lag a little behind the official release. Full commands live in the Linux install guide.

Three downloads people get wrong

  1. Grabbing the source: every release page ends with Source code (zip). That is the source tree, not an installer.
  2. Grabbing a pre-release: builds tagged alpha or pre-release exist for testing new features. For daily use, go back to the latest stable release.
  3. x64 on an ARM machine: Apple Silicon and Windows on ARM will happily run an x64 build through emulation. Nothing errors out, but you pay for it in speed and battery life.

Once the file is down, do not double-click yet. Verify the SHA256 the way spotting official installers describes — especially if you did not download straight from the official release page.