Clash for Mac macOS client

Clash for Mac Client downloads and setup

Choose the installer for Apple silicon or Intel, enable System Proxy or TUN mode as needed, then use rule-based routing to control where connections go.

  • Architecture and installation
  • Subscriptions and configuration
  • Connection diagnostics

macOS proxy and routing settings

System Proxy and TUN determine how traffic reaches the Clash client; outbound mode determines what happens next. Choose a traffic capture method, then check your configuration and outbound rules. After making a change, test with the same app to see which setting took effect.

System Proxy and local ports

If you mainly use a proxy in your browser, start by enabling System Proxy. Import and activate a configuration, then turn on “System Proxy” from the menu bar. To check the address and port, go to “System Settings → Network → Current network service → Details → Proxies.” The address is usually the local loopback address, and the port must match the one the Clash client is listening on. The example below uses one mixed port for HTTP and SOCKS. System Proxy only affects apps that read these settings; terminal tools may need separate configuration. The bypass list excludes matching hosts from the system proxy.

See the relevant guide →

Local server127.0.0.1

HTTP port example7897

SOCKS port example7897

Bypass listlocalhost, *.local

Choose a Clash client for your device

Choose an installer based on your device’s operating system, architecture, and OS version. Even if several devices use the same subscription, install a suitable Clash client on each one and test the connection with its own network settings. Desktop System Proxy steps don’t apply directly to phones.

macOS

For Mac users who want to switch proxies, inspect connections, and adjust rules from the menu bar. Check “About This Mac” to identify the chip or processor before choosing an installer; don’t guess based on the Mac’s appearance, purchase year, or another Mac’s setup. Start with System Proxy for your first connection. If your browser works but a terminal tool doesn’t use the proxy, check whether that tool needs separate configuration before enabling TUN.

Go to downloads

Windows

Check your system type under Settings → System → About, then choose a compatible installer. Turn off any previous app’s System Proxy and test in the app you want to use.

Go to downloads

Android

Match the installer to your device’s OS and architecture. Disconnect any active VPN before approving the new VPN connection. If it drops when the screen locks, check battery and background settings.

Go to downloads

iOS

Check the Clash Plus requirements in the App Store. After importing, allow the VPN configuration and select your subscription. If only Wi-Fi works, check the app’s cellular data permission.

Go to downloads

Linux

Choose a graphical client that matches your Linux distribution, package manager, and CPU architecture. If a terminal tool ignores the desktop proxy, check the tool’s own proxy settings.

Go to downloads

View all clients →

Open-source projects, core, and updates

Graphical interfaces, network cores, and subscription configurations in the Clash ecosystem are maintained separately. When troubleshooting or choosing an update, first identify which layer is involved, then consult the relevant project’s documentation.

Project history: from Clash to mihomo

Clash began as a proxy core that routes connections by rules. Over time, the community maintained different core forks and graphical Clash clients. mihomo continues the configuration system of the Clash.Meta branch, while Clash Verge Rev carries on development of the Clash Verge desktop interface. Older guides may use names that differ from those on the download page. If the steps don’t match your app, check which project the guide covers instead of searching the current interface for an old setting. Even when two Clash clients can import the same configuration, their menu names, system permissions, and supported fields may differ.

Community resources: release notes and issue discussions

Commit history helps trace code changes, release notes show which changes made it into an installer, and public issue discussions can reveal whether a problem is already known. These serve different purposes: a fix merged into the source code isn’t necessarily included in the current release. When reporting an issue, note your device architecture, operating system, traffic capture method, and outbound mode, then describe the steps to reproduce it, what happened, and what you expected. You can include log excerpts relevant to the error, but remove subscription URLs, account details, internal hostnames, and unrelated browsing records first.

Roles: interface, core, and configuration

A graphical Clash client handles the menu bar, configuration imports, and system integration. mihomo parses the configuration, matches rules, and establishes outbound connections. The configuration file defines settings such as policy groups, rules, and proxy servers. Seeing the main window only confirms that the interface has launched; a successful import doesn’t prove that the system is sending traffic to the core. To investigate, first confirm that the test app created a new connection, then check whether it appears in the Clash client. If there’s no record, check the traffic capture method first. If there is a record but the outbound route is unexpected, review the rule order and selected policy group.

Update scope: app updates and subscription refreshes

Updating the Clash client, updating the core, and refreshing a subscription are three separate actions. Some desktop Clash clients update the core along with the app; others provide a separate core update option. Refreshing a subscription usually only replaces remote configuration content—it can’t fix system permissions or installation issues. Before upgrading, back up local configurations and note the current outbound mode, proxy ports, and bypass entries. After upgrading, keep the existing settings and test with the same app. If you update the app, refresh the subscription, and switch to TUN all at once, it’s difficult to tell which change caused a problem.

Common setup questions

Will enabling System Proxy also make the terminal use it?

Not necessarily. Browsers may read macOS proxy settings, while some terminal programs only use their own configuration or environment variables. Test the two separately, even on the same device. First check whether your terminal program supports proxy options, then verify the local listening port. See Glossary: System Proxy and mixed ports.

After importing, how can I tell which configuration is active?

Return to the subscription list and check which configuration is marked as active, then review its proxy groups and rules. If you imported a local file, give it a recognizable name to avoid refreshing or switching the wrong one later. See Glossary: Subscriptions and configuration files.

Does setting outbound mode to Direct turn off System Proxy?

No. In Direct mode, the Clash client can still receive traffic and the core can establish outbound connections directly. Turning off System Proxy or TUN disables the corresponding traffic capture method. To compare with your original network connection, also check whether the app has its own proxy settings. See Glossary: Proxy modes and outbound policies.

How can I tell a DNS resolution failure from a connection timeout?

First check whether the destination domain resolves, then review the logs before and after the connection attempt. If resolution fails, focus on the DNS settings in use. If an address is returned but the connection fails, check routing, rule matches, and the selected policy. Change one setting at a time to avoid obscuring the cause. See Glossary: DNS and domain resolution.

Recent configuration and troubleshooting articles

Choose an article based on the issue. If you’ve just installed a Clash client, start with how configuration files, outbound modes, and traffic capture methods work together. If it worked before and only recently started failing, think back to the last change and choose the relevant troubleshooting guide.

View all articles →