Clash Verge
Windows
- The download below is for x64 processors
- Check the release requirements and WebView2 availability
Download Clash
Desktop Proxy Client
Get Clash Verge Rev for Windows, macOS or Linux, with Mihomo built in. Import your subscription or local profile, choose a proxy and configure routing rules. Select a build that matches your device; proxy servers and subscription services are supplied separately.
- GPL-3.0 open source
- Windows, macOS & Linux
- Mihomo core included
- System proxy & TUN
GitHub Releases
Project builds and release notes
Desktop platforms
Windows / macOS / Linux
CPU architecture
Match the build to your device
GPL-3.0
Open-source desktop client
Bring your own profile and proxy endpoints. The client manages routing; your provider or server supplies the connection.
Choose your desktop build
The direct downloads below are version 2.5.2. Match the operating system and CPU architecture before installing. For other builds and release notes, browse the project’s GitHub Releases.
macOS
- Apple Silicon uses
aarch64.dmg - Intel Macs need the matching
x64.dmgbuild
Linux
- Debian and Ubuntu typically use
.deb - Fedora uses
.rpm; verify system dependencies
More builds & source
- Browse all assets attached to a release
- Review version-specific changes and compatibility notes
Clash Verge Rev is a desktop project and does not provide Android or iOS builds. Mobile Clash clients are separate projects with their own features and configuration requirements.
Import a profile and configure your connections
Clash Verge provides the desktop controls; Mihomo handles the active configuration. Once a profile is loaded, you can choose proxies, adjust routing policies and inspect connections handled by the core.
Routing rules
Match requests to proxy groups, direct access or other policies
Proxies & groups
Review available endpoints and choose a group’s active proxy
Profiles & subscriptions
Import a subscription URL or select a local configuration file
Routing modes
Use Rule, Global or Direct to control traffic entering the core
Local settings & logs
Store configuration locally and use logs to investigate errors
Proxy latency tests
Compare response times to a test target when choosing a proxy
WebDAV backups
Back up and restore settings through your chosen WebDAV service
Connection details
Inspect active connections and traffic processed by Mihomo
Set up your first connection
Have a working subscription URL or local profile ready. The configuration supplies your proxies and routing policies; connection performance depends on those endpoints and your network.
-
1
Install a compatible build
Match your system and CPU, then follow the release requirements for dependencies and permissions
-
2
Import your profile
Add a subscription URL or load a compatible local configuration containing usable proxy endpoints
-
3
Select a proxy and policy
Activate the profile, choose a proxy in the relevant group and review the routing mode
-
4
Enable system proxy or TUN
Choose the appropriate setup for your apps, then check connection details and logs
Stable or development build?
Start with Stable for everyday use. AutoBuild tracks ongoing development and may introduce unresolved issues or compatibility changes. Read the build notes and back up your settings before switching.
| Comparison | Stable | AutoBuild / Development |
|---|---|---|
| Intended use | Everyday proxy management | Testing changes and reporting issues |
| Code version | Tagged release | Specified development commit |
| Stability expectations | Preferred for routine use | Changes may need further testing |
| Before installing | Check requirements and back up settings | Review build notes, known issues and backups |
The desktop app and Mihomo core have separate versions. Check the relevant changes and configuration compatibility when updating the app or switching cores.
Check proxies and connection activity
After activating a profile, review its proxies and groups. Once app traffic reaches Mihomo, connection details and traffic statistics help you verify routing. A successful latency test alone does not establish download speed or access to every destination.
Compatibility, permissions and backups
An app that opens successfully may still need service permissions or configuration changes before it can route traffic. Check the relevant part of the setup rather than treating every connection issue as an installation failure.
System requirements
Check the release tag, CPU architecture and dependencies. On Windows, confirm that WebView2 is available.
TUN and service access
TUN needs appropriate privileges to configure a virtual adapter and routes. Verify service status and authorization.
Profile preparation
Import a working subscription or a local configuration. Proxy endpoints come from your provider or your own servers.
App and core compatibility
Read the relevant notes before changing versions. Afterward, verify core startup and custom rules.
Backup and restore
Keep a WebDAV backup before reinstalling or moving devices. Review local paths and permissions after restoring.
Startup troubleshooting
Record your system, app version and exact error. Use logs and existing GitHub issues to narrow down the cause.
Clash download FAQ
Answers about builds, device compatibility, proxy profiles and upgrading.
Which Clash client do these downloads install?
These links install Clash Verge Rev, the continuation of the Clash Verge desktop project with Mihomo built in. The three direct download buttons point to version 2.5.2 for Windows x64, macOS Apple Silicon and Linux amd64 DEB.
How do I check which build my computer needs?
On Windows, check System type in your device information. On macOS, use About This Mac to identify an Apple chip or Intel processor. Linux users should check both CPU architecture and package compatibility. In release filenames, amd64 generally means x64, while aarch64 means ARM64.
Is there a Clash Verge app for Android or iOS?
No. Clash Verge Rev targets Windows, macOS and Linux desktops. Mobile Clash clients belong to separate projects, so their supported protocols, routing features and configuration formats need to be checked independently.
Do I need to buy a subscription to use the client?
The client does not require a particular paid subscription and does not include proxy servers. You need working endpoints, which can come from an existing provider or your own infrastructure. Any service fees and usage limits are separate from the desktop app.
What should I back up before upgrading?
Keep a recoverable copy of your profiles, Merge or Script extensions and important custom settings. Read the target version’s migration notes before upgrading. Afterward, confirm that the profile loads, the core starts and your routing rules still behave as intended.
Why does the Windows app start without showing a window?
The Windows interface depends on WebView2. If the process runs but the window is blank or the tray icon does not open the interface, check whether WebView2 is missing or disabled. If it is available, compare your system and app version with the relevant project troubleshooting notes.
Why won’t TUN mode turn on?
First confirm that the profile loads and Mihomo is running. Then check service status, required permissions and the exact log message. Adapter, routing or DNS conflicts may also affect TUN. Opening the desktop interface does not by itself confirm that TUN has the access it needs.
Where can I find other builds and previous versions?
Browse the project’s GitHub Releases and expand the assets for the relevant tag. Available architectures and package formats can differ between versions, so read the requirements and known issues alongside the filename.
Browse Clash Verge releases
Find a build for your device and review its compatibility notes. If you already use the client, back up your settings before installing a different version.