To use Clash on a Mac, choose a macOS client, import a profile, and tell your applications how to reach it. This guide uses Clash Verge Rev and covers both Apple Silicon and Intel Macs, including browser setup and a separate terminal test.
Choose a Clash download for your Mac
Open Apple menu → About This Mac and check the chip or processor and macOS version. Clash Verge Rev's current installation guide lists macOS 12 or later and provides separate Intel and Apple Silicon builds.
Your Mac | Build to choose |
|---|---|
Apple M-series chip | Apple Silicon / arm64 build. |
Intel processor | Intel / x64 build. |
ClashX and ClashX Meta are other names you may encounter when comparing Mac clients. For the steps in this article, download Clash Verge Rev from its project releases and follow the same client throughout the setup.
Install the client and import your proxy profile
Install in Applications
Open the macOS package and move the application to Applications.
Launch Clash Verge Rev
Launch Clash Verge Rev from Applications.
Import the profile
Open Profiles and add a local file or compatible subscription URL.
Activate the node
Activate the profile and select the intended proxy in the group used by its rules.
What you have | Next step |
|---|---|
A compatible subscription URL | Add it as a remote profile. |
A complete YAML file | Import and activate it. |
An HTTP or SOCKS5 endpoint and credentials | Generate a local profile with the converter. |
For MIYAIP proxy details, open the Proxy Format Converter, paste your proxy entry, and select Clash / Mihomo YAML as the output. Choose Export file, confirm credential inclusion when prompted, and import the saved YAML file. Select your node in the generated MiyaIP Proxy group.
Enable the system proxy and check your browser
Enable System Proxy in Clash Verge Rev. Open a new request in a browser that uses the macOS proxy settings, then inspect the request in Connections.
In Rule mode, check the policy group matched by that request and select the intended MIYAIP node. Open What Is My IP in the same browser and compare its result with the expected proxy exit.
If another proxy application is running, turn off its system proxy control before switching to Verge Rev. This lets you verify one active setup at a time.
Send a Mac terminal request through Clash
A browser may use macOS System Proxy while curl uses its explicit proxy option. Verify each application separately.
Read the local mixed port from your client settings. If it is 7890, test one terminal request with:
curl -I --proxy http://127.0.0.1:7890 https://example.com/Replace 7890 if your client uses another port. Check the response headers and the matching connection entry in Verge Rev. The explicit proxy option routes this request through the client even when the terminal does not use macOS system proxy settings.
Application behavior | Setup to use |
|---|---|
The app follows macOS proxy settings | Enable System Proxy in the client. |
The app has an HTTP or SOCKS5 proxy field | Enter the local address and port from the client. |
The app needs traffic capture beyond those settings | Configure TUN and complete the service permissions required by Verge Rev. |
Use the desktop routing guide to check how System Proxy, TUN, and routing modes work together.
Fix common Clash setup problems on macOS
Problem | Check | Action |
|---|---|---|
The downloaded app is incompatible | Chip, architecture, macOS version | Choose the matching build and check the project's current requirements. |
Browser traffic works but terminal traffic does not | Terminal's proxy path | Use the explicit local proxy command above. |
The exit IP is unchanged | Matched rule and selected group | Inspect the request and select the intended proxy in that group. |
An app is missing from Connections | App proxy setting or TUN setup | Configure the app's local proxy or complete the TUN service setup. |
Traffic stops after changing clients | Old app and system proxy setting | Quit the old app, then reapply the active client's System Proxy setting. |
The node reports an authentication error | Endpoint and account fields | Correct the profile using the connection details supplied with the proxy. |
For endpoint fields and manual HTTP, HTTPS, or SOCKS5 configuration, use the static proxy guide.
Frequently asked questions
Which Clash client should I use on a Mac?
This guide uses Clash Verge Rev because its current project provides macOS builds and desktop profile controls. Match the package to your chip and macOS version, then use the instructions for that client.
Can I import a ClashX or ClashX Meta profile into Clash Verge Rev?
Start with the base YAML file or subscription URL. Import it into Verge Rev and check the configuration result. Client-specific scripts, overrides, and interface settings may need to be recreated separately.
Why does Safari use the proxy while a terminal command does not?
Applications choose their proxy settings differently. A terminal tool may require its own proxy option or environment settings. Use the explicit curl proxy option above to test the local listener directly.
Should I enable TUN for every Mac application?
Start with the route the application supports. System Proxy works for apps that follow macOS settings, while an app-level proxy field can target the local listener directly. Use TUN when the application needs traffic capture beyond those routes, then verify its requests in Connections.
Connect a MIYAIP residential proxy on your Mac
Choose a static residential plan, turn its endpoint details into a Clash profile, and use the same connection checks for your browser and desktop applications.
Sources
- Clash Verge Rev installation guide — accessed 19 October 2026.
- Clash Verge Rev quick-start guide — accessed 19 October 2026.
- Clash Verge Rev project releases — accessed 19 October 2026.
- curl command-line manual — accessed 19 October 2026.