ClashX is a lightweight macOS client that provides a graphical interface for Clash-style proxy configurations. On an Intel Mac, the basic installation process is straightforward: download the correct DMG package, move ClashX to the Applications folder, approve macOS security prompts when necessary, import a configuration, and enable the system proxy. The details matter, however, because recent macOS releases may block older applications, and ClashX is no longer maintained as actively as newer clients based on maintained cores.

This guide focuses on installing ClashX on an Intel-based Mac and verifying that it is actually working. It covers the DMG workflow, macOS permissions, menu bar controls, configuration import, local proxy ports, and the differences between an application that has launched successfully and one that is routing traffic correctly.

How to Install ClashX on Intel Mac: Simple Setup Guide

Check Your Intel Mac and ClashX Compatibility First

Before downloading anything, confirm that the Mac uses an Intel processor rather than Apple silicon. Open the Apple menu, choose About This Mac, and check the processor line. An Intel Mac normally shows a processor such as “Intel Core i5” or “Intel Core i7.” Apple silicon models show “Chip” followed by an Apple M-series name. This distinction matters because some macOS applications provide separate Intel and Apple silicon packages, while others rely on Rosetta 2 to translate Intel code on newer Macs.

ClashX was designed for macOS and commonly distributed as a DMG disk image. Older releases may still run on Intel Macs, but compatibility depends on the macOS version, signing status, embedded helper components, and the specific build you obtain. A successful download does not guarantee that macOS will allow the application to open. Gatekeeper may display an unidentified developer warning, report that the application is damaged, or silently prevent a helper from starting.

Item What to verify Why it matters
Processor Intel Core processor in About This Mac Confirms that the Intel build is appropriate
macOS version System version and security behavior Older clients may need an explicit security approval
Package type DMG containing a macOS application Prevents installing an unrelated archive or mobile package
Configuration Valid YAML file or working subscription URL The client can open without a configuration, but it cannot proxy useful traffic until one is loaded

Download and Open the ClashX DMG File

Obtain the DMG package from a source you trust and make sure the file name identifies it as a macOS application package. Avoid installing a random executable, browser extension, or configuration profile simply because it uses the ClashX name. A DMG should normally appear in the Downloads folder with a filename ending in .dmg. If macOS reports that the download came from the Internet, that is a normal quarantine attribute; it does not by itself indicate that the file is unsafe.

Double-click the DMG file in Finder. macOS will verify the disk image and mount it as a temporary volume. A Finder window usually appears with the ClashX application icon and an Applications shortcut. Drag ClashX.app onto the Applications shortcut and wait for the copy operation to finish. Do not run the application directly from the mounted DMG if you intend to use it regularly. Running from the disk image can cause confusing behavior after ejecting the volume, and it does not complete the normal installation path.

After copying the application, eject the mounted DMG by clicking the eject icon beside its name in Finder’s sidebar. Open the Applications folder and locate ClashX there. Keeping the application in /Applications gives macOS a stable location and makes later permission, update, and removal steps easier to understand.

If the DMG does not open, check whether the download completed fully. A partial download may have a small file size or trigger a checksum error. Re-download the package rather than repeatedly opening a damaged copy. If macOS says that the disk image cannot be opened, restart Finder or the Mac and try again. Persistent errors usually indicate a corrupted package, an incompatible build, or a source that supplied an invalid file.

Approve macOS Security Prompts Carefully

The first launch may produce one of several macOS messages. You may see “ClashX cannot be opened because the developer cannot be verified,” a warning that the application was downloaded from the Internet, or a message stating that the app is damaged and should be moved to the Trash. These messages are related to code signing, notarization, quarantine, or application integrity. They should not be bypassed blindly.

First, try the normal launch by opening /Applications/ClashX.app. If macOS blocks it, close the alert, open System Settings, choose Privacy & Security, and scroll to the security section. On some macOS versions, a message about ClashX appears with an Open Anyway button after the blocked launch attempt. Use that control only if you have verified the application source and expected file.

Another macOS-supported method is to Control-click the application in Finder, choose Open, and then confirm the prompt. This is different from double-clicking because it records your deliberate decision to open the application. If there is no Open option or the warning says that the application is damaged, do not immediately disable Gatekeeper system-wide. Re-download the package, compare its expected checksum if one is published, and check whether the build is compatible with the installed macOS version.

ClashX may also request permission to control system network settings or install a helper component. Read each prompt and grant only the access required for the feature you intend to use. Basic system proxy mode and TUN-style traffic interception are not the same feature. A client may need additional privileges for a network extension, transparent routing, or privileged helper, while ordinary HTTP and SOCKS proxy usage may work without those components.

Complete the First Launch and Load a Configuration

After the application starts, ClashX normally places an icon in the macOS menu bar rather than opening a large dashboard window. Click the menu bar icon to view the available commands. The exact labels can vary between builds, but the menu commonly includes configuration management, proxy mode selection, system proxy controls, and access to logs or preferences.

At this stage, confirm that the client is actually running before testing a website. A menu bar icon proves that the graphical process has started, but it does not prove that a Clash core is active or that a local listener exists. Open the preferences or configuration area and check whether a profile is loaded. A configuration may come from a local YAML file or from a subscription URL supplied by your proxy service.

For a local file, use the configuration import command, select the YAML file, and wait for it to appear in the profile list. For a subscription, add the URL through the client’s profile or configuration management screen and trigger an update. Do not paste a subscription URL into a browser address bar and assume that the resulting web page is a valid YAML file. The URL must return configuration data in a format that the installed core understands.

After loading the profile, inspect the names of the proxy groups and nodes. If the profile imports but displays no usable proxies, the file may be incomplete, the subscription may have expired, or the configuration may depend on features unsupported by the old ClashX core. A modern configuration can include Mihomo-specific fields that an older core does not recognize. In that case, replacing random lines may create a configuration that loads but routes incorrectly; using a maintained client is usually safer.

Configure the System Proxy Step by Step

Now perform the practical setup in a controlled order. Begin with one known-good configuration and avoid changing the proxy mode, DNS settings, and system proxy switch at the same time. This makes it easier to identify the cause if a test fails.

  1. Open the ClashX menu from the macOS menu bar.
  2. Select the imported configuration or profile and wait for it to become active.
  3. Choose a proxy group and select a reachable node, or use the group’s automatic selection if the profile provides one.
  4. Set the operating mode to Rule for ordinary rule-based routing. Global mode sends matching application traffic through the selected proxy, while Direct mode bypasses the proxy.
  5. Enable the ClashX system proxy option from the menu.
  6. Open macOS network settings and verify that the HTTP and HTTPS proxy entries point to the local address and port shown by ClashX.
  7. Open a new browser window and visit a test page or service that shows the public IP address.
  8. Return to ClashX and inspect the connection log for the domain, matched rule, selected group, and connection result.

The local address is normally 127.0.0.1 or localhost. The port is not guaranteed to be 7890; it depends on the active profile and the client’s settings. A typical configuration might contain the following values:

mixed-port: 7890
allow-lan: false
mode: rule
log-level: info

mixed-port can accept both HTTP proxy and SOCKS5 proxy connections on one port when supported by the core. Some profiles instead define separate port and socks-port values. Use the values displayed by the running client rather than copying the example into a configuration without checking the rest of the file.

On macOS, system proxy settings can be checked under System Settings, Network, the active network service, and Details or Advanced, depending on the macOS release. Look for the proxy section and confirm that the enabled HTTP or HTTPS proxy points to the same local port as ClashX. If ClashX has a dedicated system proxy switch, use that switch first; manually editing macOS values while the client is also managing them can produce conflicting settings.

Verify the Installation and Resolve Common Errors

Verification should test three separate layers: the application process, the local listener, and actual routed traffic. If the menu bar icon is visible but no connection appears in the log, the profile may not be active or the browser may be bypassing the system proxy. If the log shows requests but the browser reports an error, check the selected node, rule result, DNS behavior, and remote connection status.

Symptom Likely cause First action
ClashX does not appear after opening Blocked launch, incompatible build, or background process failure Check Privacy & Security and launch the copy in Applications
Menu icon appears but no proxies are listed No profile, failed subscription update, or unsupported YAML fields Reload the profile and inspect the startup log
Browser has no connection after enabling proxy Wrong port, unavailable node, or incorrect mode Compare the system proxy port with the active ClashX listener
Some sites work while others fail Rule order, DNS resolution, or node-specific restrictions Inspect the matched rule and test another node or mode
Traffic bypasses ClashX Browser-specific proxy, VPN, or application-level networking Disable competing proxy extensions and check the connection log

If a browser works but another application does not, do not conclude immediately that ClashX is broken. System proxy mode only affects applications that honor the macOS proxy configuration. Some command-line tools, development environments, virtual machines, containers, and applications with their own networking stack may ignore it. In those cases, configure the application’s HTTP and HTTPS proxy variables or use a supported TUN feature in a maintained client, provided the operating system and client support that mode.

To test a local listener from Terminal, use a command such as:

curl -I -x http://127.0.0.1:7890 https://example.com

Replace 7890 with the actual HTTP or mixed port. This command tests whether a program can connect to the local proxy and whether the proxy can reach the destination. It does not prove that every application uses the same path. If the command fails with “connection refused,” the port is not listening or the address is wrong. If it connects locally but returns a remote error, inspect the selected node, rules, DNS, and remote service response.

When removing ClashX, first disable the system proxy from the ClashX menu. Then quit the application, remove it from the Applications folder, and check macOS network settings to make sure no manual proxy entries remain. If a helper or network extension was installed, remove it through the client’s own uninstall option or the corresponding macOS settings rather than deleting random files from system directories.

For a simple Intel Mac installation, the final checklist is short: ClashX is copied to Applications, macOS has allowed the verified app to open, a compatible profile is active, a reachable node is selected, the local proxy port is listening, the system proxy points to that port, and a request appears in the ClashX connection log. If any one of these conditions is missing, troubleshoot that layer before changing the entire configuration.

Download Clash