How to Manage Proxies with ClashX on macOS: Complete Guide

Article 2 cover image

Quick Start

ClashX is a graphical proxy management tool designed for macOS, built on the powerful Clash core with a clean and intuitive user interface. This guide will take you from zero to mastering ClashX comprehensively.

Whether you are a beginner or an experienced user, this guide will help you fully leverage the powerful features of ClashX for efficient and stable proxy connections.

Why Choose ClashX?

Native macOS experience, extremely low resource usage, completely free and open source, active community support

Download and Installation

System Requirements

Before getting started, make sure your Mac meets the following requirements:

  • macOS 10.15 Catalina or later
  • At least 100MB available disk space
  • Supports Intel and Apple Silicon (M1/M2/M3) chips

Download ClashX

Visit the ClashX GitHub Releases page to download the latest version:

Recommended Download Method

1. Visit official GitHub: https://github.com/charlessnow/ClashX

2. Click the Releases tab

3. Download the latest .dmg installer

Installation Steps

Step 1
Open the downloaded DMG file
Step 2
Drag to Applications folder
Step 3
First launch and grant permissions
⚠️
First Launch Note

If macOS shows "Cannot be opened because it is from an unidentified developer", go to "System Preferences" > "Security & Privacy" and click "Open Anyway".

Basic Configuration

Add Subscription Link

ClashX supports quickly importing configurations via subscription links. This is the most recommended configuration method:

  1. Click the ClashX icon in the menu bar
  2. Select "Config" > "Managed Config" > "Manage"
  3. Click the "Add" button
  4. Paste your subscription link URL
  5. Set an easily recognizable name
  6. Click "OK" to save
💡
Auto Update Config

ClashX will automatically update subscription configs periodically to ensure node information is always up to date. You can also manually click the "Update" button to refresh immediately.

Manually Import Config File

If you have a local configuration file (.yaml format), you can import it as follows:

  • Method 1: Click "Config" > "Open Config Folder", copy the .yaml file to the folder
  • Method 2: Double-click the .yaml file in Finder and choose to open with ClashX

Proxy Modes Explained

ClashX offers four proxy modes, each suitable for different usage scenarios:

Mode Description Use Case
Global Mode All traffic goes through proxy Simple scenarios requiring global proxy
Rule Mode Intelligently routes based on rules Daily use (Recommended)
Direct Mode No proxy used Temporarily disable proxy
Script Mode Customize strategy via scripts Advanced user customization

Recommended Settings

For most users, "Rule Mode" is recommended. It can automatically identify domestic and international traffic, with domestic websites going direct and foreign websites using proxy, achieving optimal speed and stability.

Advanced Features

Set System Proxy

ClashX can run as a system proxy, taking over all application network traffic:

  • Click the menu bar icon and check "Set as System Proxy"
  • Select an appropriate proxy mode
  • ClashX will automatically configure system network settings

Latency Testing

Regularly test node latency to select the fastest server:

  • Click "Proxy" > "Benchmark"
  • ClashX will test response speed of all nodes
  • Lower latency values mean faster connection speeds

Dashboard Control Panel

ClashX has a built-in web control panel with real-time monitoring and management features:

🌐
Access Dashboard

Click "Controller" > "Dashboard", or visit http://127.0.0.1:9090/ui in your browser

Common Issue Solutions

Cannot Connect to Proxy Server

If you encounter connection issues, check the following:

  1. Check if subscription link is valid, try updating config
  2. Confirm proxy mode is set correctly (Rule Mode recommended)
  3. Try switching to a different node
  4. Check local firewall settings
  5. Restart ClashX application

Some Apps Cannot Use Proxy

Some apps may not follow system proxy settings, solutions:

  • Enable "Enhanced Mode" (requires admin privileges)
  • Manually configure proxy in the app (HTTP: 7890, SOCKS5: 7891)
  • Check if rule configuration includes the app's domain
💡
Get Help

If the issue persists, visit GitHub Issues or join the community discussion for more technical support.