Clash Verge Rev Install Guide for macOS Apple Silicon (2026)

What You Need Before Installing

Clash Verge Rev is a desktop graphical client for macOS that provides access to a Clash-compatible proxy core, profile management, rule-based routing, system proxy control, and optional TUN mode. On an Apple Silicon Mac, the important choice is not simply whether the application is labeled “macOS.” You should select an arm64 or Apple Silicon build when the download center offers separate packages. A Universal build also works, while an Intel-only build may rely on Rosetta and can introduce unnecessary compatibility overhead.

This guide covers the complete first-run path: choosing the correct installer, moving the application into the Applications folder, handling macOS security prompts, importing a subscription profile, selecting a proxy group, enabling the system proxy, and checking whether traffic is actually being routed through Clash Verge Rev. Menu names can differ slightly between releases, but the sequence remains broadly the same in 2026.

• Apple Silicon Mac: Mac models with an M1, M2, M3, M4, or newer Apple chip should use the ARM64 build whenever one is available.
• Supported macOS: macOS 11 Big Sur or later is a practical baseline, but always check the requirement shown for the specific Clash Verge Rev release.
• Installer: The usual macOS package is a .dmg disk image. Some releases may provide a compressed archive instead.
• Profile source: You need a valid Clash-compatible YAML profile or subscription URL. Installing the application alone does not provide proxy nodes.
• Permissions: Your macOS account may need administrator approval when the application changes system proxy settings or creates a TUN/network extension.

Choose the Correct Apple Silicon Build

Start from the site's download center rather than an unknown mirror. Open the macOS section and compare the architecture labels. The preferred order is Apple Silicon or arm64 first, Universal second, and Intel or x64 only when no native build is available.

To confirm your hardware, open the Apple menu, choose About This Mac, and look for the chip description. “Chip: Apple M…” indicates Apple Silicon. “Processor: Intel…” indicates an Intel Mac. If you have already downloaded the application, select it in Finder, press Command-I, and check the Kind or Application information. A Universal application should show both Apple and Intel architectures in its details.

After downloading the .dmg, double-click it and wait for macOS to mount the disk image. Do not run the application permanently from the mounted image. Drag Clash Verge Rev into the Applications shortcut shown in the installer window, then eject the disk image from Finder. Keeping the app in Applications makes Gatekeeper permissions, updates, and login-item management more predictable.

Complete the First Launch and macOS Permissions

Open Finder, go to Applications, and double-click Clash Verge Rev. macOS may display a warning because the application was downloaded from the internet. A warning does not necessarily mean the application is damaged; it means Gatekeeper wants an explicit decision before opening an application obtained outside the Mac App Store.

1. Open the application once from the Applications folder. If macOS blocks it, close the warning instead of repeatedly double-clicking the icon.
2. Open System Settings, choose Privacy & Security, and scroll toward the bottom of the page.
3. Find the message stating that Clash Verge Rev was blocked, then select Open Anyway. Authenticate with Touch ID or your administrator password if requested.
4. Confirm the second warning by selecting Open. macOS normally remembers this approval for the application.
5. Return to Clash Verge Rev and allow it to finish creating its configuration directory and background components.

On newer macOS versions, enabling the system proxy or TUN mode may trigger additional dialogs. A system proxy changes the proxy settings used by macOS and applications that honor them. TUN mode works at a lower network layer: it creates a virtual interface and routes more traffic through the Clash core, including applications that do not use the system HTTP or SOCKS settings. TUN therefore requires more privileges and can affect local network behavior.

If a helper or network extension requests an administrator password, verify that the request appeared immediately after an action you initiated, such as enabling System Proxy or TUN. If the app remains stuck after authentication, quit it completely with Command-Q, reopen it from Applications, and try the setting again. Avoid running multiple proxy clients at the same time because they can compete for the same system settings, DNS path, or virtual interface.

Import a Profile or Subscription

Once the main window opens, locate the profile area. Depending on the release, it may be called Profiles, Subscriptions, or 配置 if the interface language is set to Chinese. The profile is the configuration document that tells the mihomo-compatible core which proxies, proxy groups, DNS options, and rules to use.

Import from a Subscription URL

1. Copy the complete subscription URL from your provider's account page. Make sure the URL has not been truncated by a line break or copied with surrounding quotation marks.
2. In Clash Verge Rev, choose the option to add a remote profile or subscription, then paste the URL into the address field.
3. Give the profile a short local name such as Home-September. A clear name helps when several profiles are stored.
4. Save or confirm the entry and wait for the download to finish. The profile should appear in the list with a successful update time or an active status.
5. Click the profile or its activation control so it becomes the configuration currently used by the core.

A subscription download can fail even when the URL is correct. Typical causes include an expired token, provider-side traffic limits, a captive portal on the current Wi-Fi, an invalid certificate chain, or a profile format that the selected core cannot parse. Test the URL in a normal browser only if the provider permits it, and remember that opening the link may expose the token to browser history or extensions. The safer approach is to use the client's built-in remote-profile importer.

Import a Local YAML File

If you were given a configuration file instead of a URL, use the local-file import option and select the .yaml or .yml file in Finder. Keep the file in a stable folder if the client stores a reference rather than copying its contents. A profile can be syntactically valid but still unusable when it contains expired nodes, unsupported proxy types, missing rule providers, or an incorrect external controller address.

Select a Proxy Group and Start the Core

After activating a profile, open the proxies or groups view. A typical profile contains groups such as Proxy, Auto, Fallback, or a provider-specific name. The group may initially be set to DIRECT, or it may not have a usable node selected. This is why an imported profile does not automatically prove that the proxy connection works.

1. Open the proxy group that your rules send overseas or selected traffic to.
2. Choose a concrete node, or choose an automatic group such as url-test if the profile provides one.
3. Wait a few seconds for the selection to take effect. If latency testing is available, run it against a stable URL and compare several nodes rather than choosing only the smallest single result.
4. Open the dashboard or status area and confirm that the mihomo core is running without a configuration error.
5. Leave the profile in rule mode for normal use unless you specifically need global proxy mode for troubleshooting.

Rule mode is usually the sensible starting point. It sends traffic according to the profile's rules, often keeping local services on DIRECT while routing selected destinations through a proxy group. Global mode sends almost every supported request to the selected proxy, which can help determine whether a rule set is the cause of a problem but may increase latency for local sites and services. Direct mode bypasses proxy forwarding and is useful as a control test.

Enable System Proxy or TUN Mode

Clash Verge Rev can expose traffic through different operating modes. System Proxy is the least invasive option and is normally the right first test. It updates macOS network proxy settings, commonly using local HTTP and SOCKS listeners such as 127.0.0.1:7890 or another port defined by the profile. The exact port is not universal, so read the port shown in the client's settings instead of assuming a fixed value.

1. Open the settings or dashboard page and find the System Proxy switch.
2. Turn it on and approve the macOS permission prompt if one appears.
3. Check macOS under System Settings › Network › Wi-Fi › Details › Proxies and confirm that the proxy entries correspond to the local listener shown by Clash Verge Rev.
4. Keep TUN disabled for the first connection test. This separates basic profile and proxy-listener problems from system-wide routing problems.
5. Enable TUN later only when an application ignores the system proxy or you need broader traffic capture. Approve the network-extension request and check that no other VPN is active.

System Proxy does not capture every application. Some software uses its own proxy configuration, opens direct sockets, or relies on a separate DNS and networking stack. TUN mode can cover more of these cases, but it also changes routes, DNS handling, and access to local resources such as printers, NAS devices, and corporate networks. If local devices stop responding after TUN is enabled, inspect the profile's LAN rules and bypass settings before assuming that the node is broken.

Verify That the Connection Actually Works

A green switch is not enough. Confirm the connection at three levels: the Clash core, the local listener, and an actual application request. First, open the logs and look for a new connection after visiting a test page. The log should show the destination, the matched rule or policy group, and the selected outbound. A profile that loads successfully but has no selected node may show requests going to DIRECT.

1. With System Proxy enabled and a node selected, open a normal browser window and visit a site that displays your public IP address. Compare the result with System Proxy disabled.
2. Open the Clash Verge Rev connections view and refresh a page. Confirm that the browser request appears there and has the expected policy group.
3. Switch temporarily from Rule mode to Global mode and repeat the request. If Global works but Rule mode does not, inspect rule order, geosite data, or the selected rule group.
4. Use macOS Terminal to inspect the local listener only if needed. For example, replace 7890 with the actual HTTP port and run curl -x http://127.0.0.1:7890 https://example.com -I.
5. Turn the system proxy off after testing if you want macOS applications to return to their normal network path.

The public IP result is useful but limited. It confirms the path used by that browser request; it does not prove that every application uses the same path. DNS can also follow a different route from web traffic. If you are investigating a DNS issue, check the client's DNS settings and logs separately, and avoid treating a successful page load as proof that there is no DNS leak.

Common macOS Installation Problems

macOS Says the Developer Cannot Be Verified

Confirm that the file came from the intended download source, then use System Settings › Privacy & Security › Open Anyway after the first blocked launch. If the button does not appear, launch the application once, close the warning, and return to Privacy & Security. Moving the app out of a mounted disk image and into Applications is also important.

System Proxy Will Not Stay Enabled

Quit other proxy and VPN tools, check whether the macOS network service is connected, and reopen Clash Verge Rev from Applications. Then verify the HTTP and SOCKS port values in the client. A profile update may also replace port settings, so do not copy an old port into macOS manually without checking the current configuration.

The Profile Imports but Shows an Error

Check whether the subscription has expired and whether the downloaded content is actually Clash YAML rather than an HTML login page. A provider may also require a particular user-agent or core feature. Update the profile from the client's subscription page and inspect the error text. If only one profile fails while another loads, the problem is probably the profile format or provider response rather than the Apple Silicon installation.

TUN Mode Cannot Start

Disable other VPN extensions, restart the application, and approve the network-extension prompt again. Check whether the profile contains valid TUN settings and whether the selected mihomo core supports the required options. Start with System Proxy mode first; TUN is an optional system-wide routing layer, not a requirement for proving that the client and node work.

FAQ: Clash Verge Rev on Apple Silicon

Do I need Rosetta on an M-series Mac?

Not when you install an Apple Silicon or Universal build. Rosetta is only needed for an Intel-only application. If the client opens normally but macOS reports that Rosetta is required, recheck the package architecture and download the native build when available.

Can I use Clash Verge Rev without a subscription?

Yes, if you have a compatible local YAML profile containing usable proxy definitions. Without either a local profile or a remote subscription, the application can launch but has no nodes or routing instructions to use.

Should I enable TUN immediately?

No. Enable System Proxy first and verify one browser request. Turn on TUN only when you need applications that ignore system proxy settings or require broader traffic capture. TUN needs additional permissions and can change local-network and DNS behavior.

Why does the proxy stop working after sleep or Wi-Fi changes?

The network interface may receive a new route, the node may time out, or macOS may temporarily disable a network extension. Check that Clash Verge Rev is still running, refresh the profile or node health check, and toggle System Proxy off and on. If the issue repeats, inspect the logs and test another node before reinstalling the application.