Insights

Clash Verge Rev Setup Guide for Desktop

Configure Clash Verge Rev in four steps: activate a profile, choose a mode and node, enable System Proxy or TUN, and verify the route used by your application.

Clash Verge Rev settings screen with the System Proxy control highlighted

Set up Clash Verge Rev in four steps: import and activate a profile, choose a routing mode and node, enable System Proxy or TUN, then verify that the intended application uses the selected route. Use the links below to jump to the step you need.

Step 1

Install the right build and import a profile

Download a stable build from the project's official GitHub Releases page. Match the package to your operating system and CPU architecture; most Windows PCs use x64, while newer ARM devices need ARM64. The official project supplies Windows, macOS, and Linux packages, and Windows 7 is no longer supported.

To add a purchased endpoint, follow the guide to configure a static HTTP or SOCKS5 proxy.

Clash Verge Rev profile import screen
Official quick-start screenshot. The exact labels and layout may differ by version.

Choose the right source for your profile

What you have

Setup path

A compatible subscription URL

Add a remote profile and download its configuration.

A complete YAML file

Import and activate the local file.

A proxy server, port, username, and password

Generate a local YAML profile with the steps below.

Build a profile from your MIYAIP proxy details

  1. Open the converter

    Open the Proxy Format Converter and prepare your proxy entry with its protocol and authentication fields.

  2. Generate Clash YAML

    Paste the connection details, choose Clash / Mihomo YAML, and convert the entry.

  3. Export and import the profile

    Choose Export file, confirm credential inclusion when prompted, then import and activate the saved YAML file in Clash Verge Rev.

  4. Select your node

    Open the MiyaIP Proxy group and select your node before continuing with the routing and verification steps below.

For manual HTTP, HTTPS, and SOCKS5 settings, use the static proxy configuration guide.

Clash YAML output generated from an HTTP and a SOCKS5 example
Generate the profile, then select its group in the client.
Step 2

Choose a routing mode and node

Open Proxies and start with Rule mode for everyday use: each request follows the active rule set. Global sends eligible traffic through one selected proxy, while Direct bypasses proxy routing.

Inside the relevant proxy group, select a node and run the built-in delay test as a quick availability signal. The smallest number is not always the most stable route, so verify the applications you actually use.

Clash Verge Rev proxy group and node selection screen
Official quick-start screenshot showing mode and node selection.
Step 3

Turn on System Proxy or TUN

For browsers and most applications that respect operating-system proxy settings, enable System Proxy first. The official quick-start guide describes this as the normal choice for most browser traffic.

Use TUN Mode when an application ignores the system proxy—for example, some games and command-line tools. TUN uses a virtual network adapter and therefore covers more traffic, but it can require service installation or administrator authorization. After enabling it, confirm that local-network access, DNS resolution, and the applications you care about still behave as expected.

Clash Verge Rev System Proxy and TUN controls
Official quick-start screenshot showing the System Proxy and TUN controls.

Application behavior

First choice

Applications that follow operating-system proxy settings

System Proxy

Applications that need another traffic-capture method

TUN, following the official quick-start instructions and the platform requirements.

Verify the connection and fix common problems

In the intended application, open What Is My IP to check its exit address, then compare the request route in Connections or Logs.

  • Confirm that the intended profile is active and has refreshed successfully.
  • Confirm the current mode, proxy group, and selected node before changing advanced settings.
  • Open Connections or Logs to see whether requests match a proxy rule, go direct, or fail.
  • If connectivity breaks after a change, turn off TUN and System Proxy, restore a known-good profile, and test again one change at a time.
  • Before quitting or uninstalling, disable the active capture mode so stale operating-system proxy settings do not leave applications offline.

The official platform FAQs document core communication, TUN, service-permission, WebView, DNS, and Linux display issues. Use the platform-specific FAQ when the basic checks above do not isolate the problem.

Keep the interface current

Continue with the official guide

Open the official quick-start page for the latest interface-specific instructions, then use GitHub Releases to download updates from the project source.