Clash Setup Guide for macOS
First, get your browser working through the system proxy, then check that rules route traffic as expected. If you’ve installed a Clash client and have a subscription URL, follow these four steps to get set up.
If you haven’t installed a client yet, open “About This Mac” from the Apple menu. If it lists a “Chip” with an Apple M-series name, choose arm64; if it lists an Intel “Processor,” choose x64. Select the right installer in the macOS downloads section, and check the client’s stated system requirements. After installing, open the main window. For your first test, run only one Clash client to avoid two clients changing your system proxy at the same time.
1. Add and Enable a Subscription
Open the Clash Verge Rev main window and select “Subscriptions” in the sidebar. Copy the full Clash or Mihomo subscription URL from your provider’s website, paste it into the URL field at the top of the Subscriptions page, and click “Import.” If your version puts this option under “New,” choose a remote configuration, enter the URL, and save. Use the URL that retrieves the configuration—not an account sign-in page, plan details page, or individual node share link. If your copy includes an extra line of text, keep only the URL.
After importing, a configuration card should appear in the subscription list. Check its name and last updated time to make sure it isn’t an old configuration. Click the card or select it from its menu until the interface marks it as active. If another configuration was already enabled, note its name so you can switch back later. If your provider supplied a local YAML file instead of a URL, use “Import File,” then confirm which configuration is active.
Next, open the Proxies page and check that the proxy groups defined by this configuration appear. Proxy groups determine how certain connections are handled. They may contain multiple nodes, an automatic selection option, or a direct connection option. A card in the subscription list only confirms that the configuration was imported; seeing its groups on the Proxies page is the right cue to continue. If you have several subscriptions with similar names, don’t guess based on their order. Confirm the selected configuration on the Subscriptions page, then check that the groups on the Proxies page change accordingly.
If the import fails immediately, first check that you copied the complete URL and that your provider supplied a configuration format supported by your client. Don’t turn on both the system proxy and TUN just to get the import to work, and never post the full URL in a public screenshot or comment—it may contain access credentials. If the import succeeds but you can’t enable the configuration, or the Proxies page stays empty after enabling it, follow the subscription troubleshooting steps in Troubleshooting. Once the proxy groups appear, choose a mode.
2. Choose Rule Mode and a Proxy Group
Keep the configuration you just imported selected. On the Proxies page, find the mode switch and choose “Rule.” Some versions also let you choose “Outbound Mode” from the menu bar icon. Make sure “Rule” is highlighted after switching. This only changes how requests sent to the Clash client are handled; it does not enable the macOS system proxy. Choose how traffic should be routed first, then decide which apps should send traffic through the client.
Check the Current Routing Policy
In rule mode, requests are matched against the rules in the active configuration, in order. When a rule matches, its assigned policy handles the request: the result may be a direct connection, a proxy, or a rejection. Open the Rules page, find a rule whose purpose you recognize, then check which group it points to on the Proxies page. Group names are set by the configuration provider; they aren’t always called “Node Selection.” If the site you’re testing matches a dedicated group, changing another group that looks like a master switch may have no effect.
Expand the proxy group you plan to test. If it’s a manual selection group and should use a proxy, start by choosing one of the nodes already in the configuration. If the configuration offers automatic selection, you can keep its default and check the connection list to see which node was actually used. A node’s test result can help you choose, but a successful test doesn’t mean your browser traffic will use that node. For your first setup, note the selected group and node; there’s no need to keep switching just to chase a lower test time.
“Global” usually sends requests handled by the client to the global policy, though the result still depends on what that policy has selected. “Direct” sends traffic without a proxy. Neither option turns the system proxy on or off. Keep “Rule” selected for your first setup so you can verify both proxied and direct connections. If you’re unsure why a policy was selected, complete the browser test below first, then see Platform Guides for the differences between “proxy group,” “rule,” and “proxy mode.” You don’t need to edit configuration files just to get started.
3. Enable the System Proxy
Once you’ve selected the configuration and mode, open “Settings” in the Clash client and find “System Proxy” or “Set as System Proxy.” You can also click the client icon in the macOS menu bar and enable the corresponding option in its menu. Make sure the toggle stays on. If macOS asks for authorization, confirm that the prompt matches the action you just took, then follow the on-screen instructions. Keep the Clash client running; don’t choose “Quit” from the menu. Closing the main window and quitting the client are not the same thing.
Check the Proxy Settings for Your Current Network
Open macOS “System Settings → Network,” select the Wi-Fi or Ethernet service you’re currently using, then go to “Details → Proxies.” Paths vary slightly by macOS version; on older versions, look under “System Preferences → Network → Advanced.” Check which proxy options the client enabled and compare the displayed server address and port with the client settings. The server is usually the local address 127.0.0.1; use the port shown in your client. You don’t need to manually check HTTP, HTTPS, and SOCKS, and you shouldn’t assume someone else’s port number is the right one for your setup.
If the menu bar shows the proxy is on but the current network service’s proxy page hasn’t changed, make sure you’re not looking at a different network interface, then check whether another proxy client is running. Stay on the same network throughout the test if possible; don’t change Wi-Fi and switch configurations at the same time. If your Mac is managed by your organization and already has proxy settings, keep the existing configuration and follow your organization’s instructions. Once the system settings look right, open Safari to continue. There’s no need to add another proxy in the browser.
Test Your Browser Before Enabling TUN
The system proxy is mainly used by apps that read macOS proxy settings. Some command-line tools and other apps ignore these settings, so a working browser doesn’t mean they’ll use the same route. Leave TUN off for your first test. Enable TUN in the client settings only if the target app doesn’t use the system proxy and you need to route its traffic through Clash; follow the prompts to grant permissions or install the required service. Note the original setting before enabling it, then test only the target app so you can tell what changed. For more on the differences, see Platform Guides.
4. Verify the Connection and Routing
Choose two sites you can normally access under your current configuration: one that should use a proxy and one that should connect directly. Keep “Rule” mode selected. Open the “Connections” page in the Clash client, then visit the first site in a new Safari window or reload the page to trigger a request. Simply switching back to an already-open tab may show cached content, which doesn’t confirm that your settings are working. If the request finishes before you can check it, make another request and watch for a new entry.
Find the connection for the domain you just visited and check its matched rule and outbound route. If the interface shows a proxy group and node, confirm they’re the ones you expect. Modern websites often load images, fonts, and other resources from different domains, which may match different rules. Check the main domain in the address bar first; don’t assume the whole page connected directly just because you see a direct connection for another domain. Then test the second site the same way and confirm its outbound route is direct. If its address is on the system proxy bypass list, the request may never reach the Clash client. Choose a different site that isn’t bypassed and is routed directly by your configuration.
Setup is verified when both sites load and their outbound routes match the configuration. If a site loads but you don’t see the expected proxy connection, first make sure the browser sent a fresh request, then revisit the system proxy settings for your current network service from step 3. If you can find the connection but it uses the wrong policy, return to step 2 and check the matched rule and its group. If the rule and proxy node look right but the request keeps timing out, try another node in the same group and test the same URL again. Change one thing at a time so you know what you’ve ruled out, even if the result doesn’t change.
When you’re done testing and won’t be using Clash for now, turn off the system proxy from the menu bar. If you enabled TUN for an app, turn that off separately. Visit a site that normally connects directly to confirm your network is back to the expected state. When you change networks, update your subscription, or switch proxy groups later, there’s no need to reinstall—just repeat the connection check. If you still have a subscription import failure, node timeout, DNS issue, or a problem that affects only command-line tools, open Troubleshooting and include the app you used, the mode you were in, and whether a connection entry appeared.