Clash Verge Rev · Mihomo Core
Configure a desktop proxy with subscription management, rule-based routing, and TUN mode. Choose a compatible client for mobile devices.
Client settings
Understand where configuration comes from, how traffic enters the client, and how rules determine its route before changing settings. These five areas cover the options most often adjusted in everyday use. The interface is illustrative and does not reflect a device's current state.
01 / Profiles
A subscription is a way to obtain configuration, not a network service itself. Clash Verge Rev can fetch a configuration from a subscription URL or load a local YAML file. After importing, select the configuration, check its proxy groups, and then enable a traffic entry point. Saving a URL to the list does not mean you are connected. Keeping configurations as separate entries makes their sources easier to identify and revert than editing downloaded files directly. When updating, check that the download succeeded, the fields parsed correctly, and the proxy group names have not changed.
Configuration workflow
Import a URL or local file
Select the configuration to use
Check proxy groups and update status
Illustrative workflow; no real subscription URL is shown.
02 / Routing
In Rule mode, the client checks destination domains, addresses, and other match conditions in configuration order, then routes each connection to the corresponding policy. Global mode can help with temporary troubleshooting, but it does not automatically capture all system traffic: apps still need to send traffic through a proxy entry point. Direct mode bypasses the proxy for outbound traffic. For everyday use, fixing the matching rule is usually more reliable than repeatedly switching Global mode on and off. Before adding a custom rule, make sure its proxy group exists and check the connection log to see whether the request reached the core and which rule matched.
Rule example
mode: rule
rules:
- DOMAIN-SUFFIX,example.com,DIRECT
- IP-CIDR,192.168.0.0/16,DIRECT
- MATCH,DIRECTThis shows Direct rule syntax. Set the outbound policy to match your configuration.
03 / Traffic entry
The system proxy works with apps that respect the system proxy settings. TUN routes more connections through the core using a virtual network adapter, which can help with apps that ignore the system proxy. These are different traffic entry points, not proxy quality settings. TUN often requires service permissions and takes over system routes and DNS, so first make sure the regular system proxy works. Enabling multiple networking tools at once makes conflicts harder to diagnose; switch entry points one at a time. Corporate VPNs, virtual machines, and other virtual adapters can also affect routing.
Traffic entry point example
Illustrative settings only. Check permissions and service status in the client.
04 / Configuration
Subscription updates fetch remote content again, so edits to a cached copy of a remote configuration may be lost. Overrides or merges can preserve local ports, log levels, and custom rules, but the exact behavior depends on the client's merge logic. Keeping only necessary local changes is easier to maintain than copying the entire configuration. Pay particular attention to the difference between replacing a field and appending to a list: rules and proxy groups may not merge automatically as expected. After editing, inspect the final active configuration and keep a working copy of the previous version.
Common local settings
mixed-port: 7897
allow-lan: false
mode: rule
log-level: infoThese are example fields, not a complete configuration. Make sure the port matches the system proxy settings.
Read about configuration fields and merging05 / Startup
Launch at startup controls whether the client starts after you sign in; start minimized controls whether the main window appears; system proxy controls whether apps use the proxy entry point. Treat these as separate settings. Launching at startup does not guarantee a successful connection. Checking the tray icon, active configuration, and actual requests is more reliable than using the startup window as a connection indicator. First verify that the client connects manually, then enable automatic startup. If the network is not ready when you sign in, subscription updates or remote rule downloads may temporarily fail.
Startup options example
Verify the connection manually before enabling automatic startup.
Downloads by system
Clash Verge Rev is for desktop systems; Android and iOS require different clients. This cross-platform directory brings together apps in the same ecosystem—it does not mean the desktop app has simply been renamed for phones. Before installing, check your operating system, processor architecture, and configuration format, then find the matching download on the installers page.
Options include Clash Plus, Clash Verge Rev, FlClash, and Clash Nyanpasu. If you are switching from an older client, back up your subscription URLs, custom rules, and local port settings first, then move to an actively maintained app.
Check the system proxy when you first run the client. If a browser works but a store app cannot connect, check loopback restrictions instead of assuming the subscription is broken.
Go to downloadsOptions include Clash Plus, Clash Verge Rev, and FlClash. Apple Silicon and Intel Macs use different installers. Check your chip type in About This Mac, then choose the matching download.
Follow system prompts to grant any required network permissions or enable helper services. Test a standard proxy connection after installation before enabling TUN, which may require additional permissions.
Go to downloadsOptions include Clash Plus, Clash Meta for Android, FlClash, and Surfboard. Mobile clients typically route traffic through Android's VPN interface. Check that the client supports your subscription format and required rule features.
Allow the VPN request when connecting for the first time. If the connection drops when the screen locks, check battery optimization, background restrictions, and other VPN apps. Increasing the speed test frequency usually will not prevent the client from being stopped in the background.
Go to downloadsThe download page links to Clash Plus on the App Store and lists its official site at clashplus.io. It is a standalone mobile app, not a desktop installer for Clash Verge Rev.
Check configuration compatibility before importing. When connecting for the first time, allow the VPN configuration as prompted by iOS. After connecting, check the app's policies and test actual access instead of relying only on the status bar icon.
Go to downloadsFor desktop Linux, choose Clash Verge Rev or FlClash. Check your distribution's package format, desktop dependencies, service permissions, and network management before installing. Do not reuse commands intended for another distribution.
For servers or routers, look for the Mihomo core on the download page. A command-line core requires you to prepare the configuration and manage the service yourself; it does not work like a graphical client.
Go to downloadsThe same subscription may appear differently in different clients. When switching, check which fields the new client supports.
View all clients →Quick start
A client reads configuration and handles connections; it does not provide a working proxy endpoint by itself. Once you have a subscription from a trusted source or a local configuration, follow these steps to get started. If an error occurs, troubleshoot the current step before changing ports, DNS, and rules all at once.
Open subscription management and add a configuration URL or import a local YAML file. Make sure the download and parsing succeed, then select the configuration as the active one. If the import is empty, check whether the URL requires sign-in, returns a web page, or uses a configuration format unsupported by the provider.
Never post a subscription URL in a public support request. If you need help, share only redacted error messages, field structure, and steps to reproduce.
For everyday use, start with Rule mode and check that the relevant proxy groups have a working outbound route. On desktop, enable the system proxy first so apps that follow system settings can send traffic to the core. Consider TUN only if an app is not being captured. On mobile, establish the VPN connection as prompted by the client.
The local system proxy port must match the client’s listening port. Do not replace the entire configuration just because one page will not load.
Open a site you want to test and check the connection log. Confirm that the request reached the core, matched the expected policy, and established an outbound connection before testing other apps. If a browser works but a terminal does not, first check whether the terminal uses proxy environment variables rather than importing the subscription again.
Test both proxied and direct connections. Continue using the current rules only if both behave as expected.
Open source context
The graphical client, proxy core, and subscription service are separate layers. Understanding their roles helps you choose update sources and read error logs, and prevents client settings from being mistaken for network service failures. This page provides download links and English-language guidance; refer to the relevant open-source repository for project code and release history.
Clash Verge Rev continues the desktop client approach of Clash Verge, with a graphical interface for configuration, proxies, connections, and settings. It is maintained as a separate project from other historical Clash clients, so similarly named apps do not necessarily share installers, configuration directories, or instructions.
When migrating from an older client, save your subscription sources, local rules, and essential settings, then import them into the new app. Avoid copying the entire application data directory: databases, caches, and service paths may differ, and old paths can leave startup items or helper services pointing to a deleted app.
Mihomo reads the active configuration, matches rules, and handles outbound connections. Clash Verge Rev provides the settings interface, manages configurations, and communicates with the core. Whether an option takes effect depends on the configuration, core support, and the content the client ultimately generates.
Break troubleshooting into three checks: did the interface save the setting, does the active configuration contain the field, and does the runtime log accept it? Seeing a line of YAML in an editor does not prove the running core is using it. Look up individual fields in the configuration reference.
An open-source repository lets you review project documentation, licenses, commit history, and issue discussions. When reading release notes, look for OS compatibility, core changes, configuration behavior, and known issues—not just the release date. Search existing discussions before filing an issue to see whether the behavior is already known.
A useful bug report includes your operating system, reproduction steps, and redacted logs. Never post subscription URLs, passwords, or browsing history as-is. Community discussions can offer troubleshooting clues, but other users' configurations may not suit your network. Understand each field before copying it.
Updating the app, core, subscription, and remote rule sets are separate operations. An app update may change the interface or service management; a subscription update may replace proxies and proxy groups; a rule set update may change match results. If behavior changes, first identify which layer was just updated, then decide what to roll back.
Keep a working configuration and a copy of local overrides before updating. Afterward, check the system proxy, listening port, TUN permissions, and key rules. If an update renames a proxy group, update any local rules that refer to it. Starting the client is only the first check; actual connection results are what matter.
The command below clones the Clash Verge Rev repository for browsing the source or contributing to development. For everyday use, install the client from the download page; you do not need to clone the repository or set up a build environment.
Clash Verge Rev repository →git clone https://github.com/clash-verge-rev/clash-verge-rev.gitRecent notes
Articles are listed in reverse chronological order. Back up your configuration before migrating. If background activity fails, check system restrictions first; if one app cannot connect, start by checking how its traffic reaches the client. Narrowing down the symptoms is more likely to produce reproducible results than changing several network settings at once.
Explore alternatives now that the original client is no longer maintained. Compare cores, platform support, and configuration compatibility, then follow migration steps that preserve subscriptions and custom rules.
Read the migration guide →Learn why proxy apps can drain battery on Android and iOS, including frequent speed tests, rule set updates, and DNS settings, with tips for battery optimization exemptions and background activity.
See background settings tips →Learn why UWP apps are blocked from accessing local loopback addresses by default, how to remove the restriction with CheckNetIsolation or a graphical tool, and when to consider TUN mode.
Read the loopback troubleshooting steps →For the basic import steps, see the usage guide. For field-by-field details, go straight to the configuration reference.
View all articles →