Clash Verge Rev Tutorial
Import a Subscription and Make Your First Connection

STEP 01 / PROFILE

Import a Subscription and Activate the Profile

Launch Clash Verge Rev and click Profiles in the left sidebar. Paste the full URL into the subscription field, then click Import. Button placement may vary between versions, but choose the option to import from a URL rather than creating a blank profile manually. Check that the URL has no extra spaces, line breaks, or punctuation added by a messaging app. Keep the original parameters; don’t remove anything after the question mark.

During import, the client fetches the profile from the subscription URL. When it succeeds, a profile card appears, usually showing its name, last update time, or information returned by the provider. Click the card or use its menu to activate the profile. Seeing a card alone doesn’t mean it’s active: confirm that the selected indicator is on that card before continuing.

Open the Proxies page and check that proxy groups and their nodes are listed. A proxy group is a collection of egress options referenced by rules. It may be called “Select Node” or “Auto Select,” or have a name chosen by your provider. You don’t need to rename these groups to match this guide. If the profile is active, the groups can be expanded, and actual nodes are listed, you’re ready to choose an egress.

Import a Local File

If you have a .yaml or .yml file, use the file import option on the Profiles page, select the file, and activate it. Don’t paste a file path into the subscription URL field. URL-based subscriptions can usually be refreshed, but a local file may not have a remote update source. If the provider’s service details change, download the file again or edit the profile as instructed by the provider.

What to Check First If Import Fails

Start with the client’s error message. A failed network request usually means the subscription URL is unreachable, the device has a network issue, or the URL has expired. A profile parsing error is more likely to mean the returned content isn’t compatible. The URL should return a profile supported by the client—not a provider sign-in page, sharing instructions, or an error message. Ask your provider to confirm that you’re using a Clash- or mihomo-compatible format; a URL opening in a browser doesn’t prove the format is valid.

If the import succeeds but no nodes appear on the Proxies page, return to Profiles and confirm that the newly imported profile is active. Then try updating it manually and check the logs for parsing errors. Avoid importing the same URL repeatedly, which makes it harder to tell which profile is active. For the difference between subscriptions, profile files, and nodes, see the glossary. Keep one clearly working profile before moving on to choosing a mode.

STEP 02 / ROUTING

Choose Rule Mode and a Proxy Node

Return to the Proxies page and find the running mode selector. For an initial setup, Rule mode is a good starting point: the client uses the rules in the active profile to decide whether each connection goes direct, through a proxy group, or is rejected. This lets you verify the subscription’s routing logic and later troubleshoot why an app isn’t using the proxy. Changing modes doesn’t select a node or turn on the system proxy.

Next, expand the proxy group that provides the egress. If it lists nodes for manual selection, use the group’s test button to check the available nodes, then choose one that passes. A successful test only means the node could reach the configured test address at that time; it doesn’t guarantee that every site or app will work. Don’t choose a node based only on a single latency result. Start by checking whether the connection is stable in practice.

Some proxy groups contain other groups rather than final nodes. For example, “Select Node” may refer to “Auto Select,” which then chooses an egress from several nodes. This nested structure is normal. Follow the selected entry into the next level and make sure the final choice isn’t DIRECT or an unavailable node. For an automatic group, the client typically selects an egress according to the profile’s health-check rules; you don’t need to switch it to manual selection to follow this guide.

What Rule, Global, and Direct Modes Do

Rule mode matches connections against the profile’s rules and is a good everyday starting point. Global mode usually sends connections that reach the core to the global proxy group; you still need to check that group’s egress. It doesn’t mean every app on your device is being routed. Direct mode sends connections that reach the core straight to their destinations. These modes determine how traffic is handled after it reaches the core; the system proxy and TUN determine which traffic reaches it in the first place.

To check whether a destination is being routed through the wrong egress, you can temporarily switch to Global mode for comparison. First note the original mode and selected node. Switch back to Rule mode when you’re done so you don’t forget to restore it. Don’t change the mode, DNS, ports, and rules all at once during initial setup; that makes results hard to diagnose. Keep the subscription’s original settings and choose one working egress.

You don’t need to configure health checks, failover, and load balancing for your first connection. To learn how they work, see the proxy group glossary. For protocol support and core differences, see the protocol guide.

STEP 03 / CONNECTION

Connect and Route Traffic

Desktop: Enable the System Proxy First

In Clash Verge Rev, find the System Proxy switch on the Settings page and turn it on. Some versions also offer this option in the tray menu. This points your operating system’s proxy setting to a port listened on by the local client, so browsers and apps that follow the system proxy send their requests to the core. Keep the default port for now; you don’t need to copy a port number from another guide just to connect.

Open your browser and refresh a page. If it uses a separate proxy extension or manual proxy settings, switch it back to using the system proxy so requests aren’t sent elsewhere. Also quit any other client that changes the system proxy, to prevent two programs from overwriting each other’s settings. Don’t decide whether the setup works based only on whether a page loads after enabling the switch. In the next step, check the actual route on the Connections page.

If the client says the core isn’t running, the listener failed to start, or the port is in use, resolve that issue before toggling the switch again. A port is often occupied because another proxy app is still running in the background. Quitting the conflicting app is usually better than changing ports at random. If you do need to change a port, update any browser, terminal, or other app that depends on it as well. See Clash port configuration issues.

Mobile: Approve the System VPN Prompt

In the mobile client, select the imported profile and a node, then tap Connect on the home screen. The first time you connect, the system will usually ask permission to create a VPN connection. Approve it, then return to the client and check the connection status. This VPN uses an operating system interface to route traffic; it doesn’t change the node protocol. If you only import a profile without tapping Connect, mobile apps will usually continue using their existing network connection.

If another VPN app is already connected on your device, disconnect it before starting this client. On Android, battery optimization can interrupt background activity. For your first test, keep the client in the foreground; once the connection is confirmed, adjust background permissions if prompted. On iOS, check the client’s connection status and the system VPN status. You don’t need to follow desktop instructions for services or ports.

Enable TUN Mode Only If Needed

Consider TUN mode only if your browser works through the proxy but a game, command-line tool, or other app ignores the system proxy. TUN routes traffic through a virtual network interface and covers different traffic from the system proxy. The desktop client may require you to install a service or grant administrator privileges. Follow the prompts for your version, confirm the service is running, and then enable TUN. Don’t keep retrying while a permissions prompt is unresolved.

For your first test, use the system proxy to establish a route you can inspect, then test TUN separately. If previously working connections fail after enabling TUN, turn it off and return to the verified system proxy setup. Keep the logs from before and after the issue. UWP apps also have a separate loopback access restriction, so don’t mistake it for a node problem. See the UWP loopback guide.

STEP 04 / VERIFICATION

Verify the Proxy Egress and Rule Matches

Leave the client running, visit a destination that should clearly match a proxy rule in your browser, and open the Connections page in Clash Verge Rev. The list can change quickly, so clear any search filters first, then search for the destination domain. Check the entry’s destination, matched rule, and connection chain. Confirm that the request passed through the expected proxy group and reached the node you selected. Don’t rely only on whether the system proxy switch is on.

Short-lived requests may disappear from the active connections list quickly. If that happens, refresh the destination page or use the Logs page to check rule matches. Browsers may reuse existing connections, so make a new request after switching nodes; if needed, close and reopen the page. Don’t upload complete logs publicly just to make the entry visible—they may contain visited domains and personal network information.

Cross-Check with Your Egress IP

In the same browser, open a trusted IP lookup site. First confirm that the lookup domain uses a proxy group under the active profile, then check the reported public egress IP. It should match the expected egress for your selected node, though it may differ from the public IP of your device’s current network. Lookup services can use different data sources and location labels, so treat the reported region as a rough guide. The connection chain on the Connections page is a better way to confirm how the client routed the request.

An unchanged IP doesn’t necessarily mean the proxy failed. The lookup site may match a Direct rule, or some requests may use a different address family. Check the lookup request’s rule and egress on the Connections page before investigating further. If the connection shows that it went through the proxy but the destination is still unreachable, check connectivity between the node and the destination instead of changing the system proxy again.

Verify a Direct Connection Too

Rule mode is designed to route connections selectively, not to show every connection going through a proxy. Visit a destination that clearly matches a Direct rule in your profile and confirm that the Connections page shows DIRECT. If the proxy and direct destinations each match the expected policy, your profile, node selection, and traffic routing are working together. You don’t need to switch to Global mode just to make every entry look the same.

An egress IP alone can’t tell you whether DNS is leaking. DNS resolution and app connections are related but don’t always follow the same path. Results from a test page may also be affected by encrypted DNS in the browser, the system cache, and the client’s DNS settings. Start by verifying egress and rule matches as described above. If you do find unusual DNS results, see Clash DNS leaks and troubleshooting rather than disabling all DNS features without checking.

If Verification Fails, Trace the Connection Path

If the request doesn’t appear on the Connections page, first check whether the app follows the system proxy, another program has overwritten the switch, or the mobile VPN is actually connected. If the request appears but shows Direct, check the running mode and matched rule. If a proxy node is selected but the connection fails, check the node test, subscription status, and error logs. Change one thing at a time and retry. This usually makes issues easier to isolate than changing several settings at once.

You’ve now checked the full path from subscription to real requests. For everyday use, you’ll usually only need to update the subscription, choose an egress, and make sure the required traffic-routing switch is on. To learn more about choosing a protocol or how the mihomo core works, see the core and client reference. For a specific issue, find it by symptom in the Troubleshooting guide instead of repeating the entire setup.