Why Move to ClashX
At the end of 2023 the popular Clash for Windows (CFW) project was discontinued and its GitHub repository removed. For users who relied on CFW—especially those on macOS—finding a maintained replacement quickly became critical.
Unmaintained software no longer receives security patches or bug fixes, leaving you exposed. Switch to an actively maintained tool as soon as possible.
Reasons to Migrate
- Security risk: no more security patches, potential vulnerabilities stay unpatched
- Compatibility: new macOS releases and system updates are no longer supported
- Feature freeze: modern proxy protocols and features never arrive
- Community support: official channels are gone, so help is hard to find
- Future proofing: only active projects guarantee long-term stability
Why ClashX
ClashX is one of the most mature Clash clients on macOS and brings several advantages:
- Native macOS app optimized for Apple Silicon
- Ongoing maintenance with frequent fixes and community support
- Open-source transparency and trustworthy security
- Completely free—no paid tiers, all features unlocked
- Subscription/config compatibility with CFW formats
- Full feature set: rule engine, TUN mode, DNS tuning, and more
Pre-Migration Preparation
Before switching, export everything important from Clash for Windows so the transition is seamless.
Step 1: Export Subscription Links
Your subscription URLs are essential—keep them safe:
- Open Clash for Windows
- Click the “Profiles” tab on the left
- Locate the profile you currently use
- Right-click the profile and choose “Copy URL” or view its details
- Store the subscription link somewhere secure (a password manager is ideal)
If you have multiple subscriptions, export each URL separately. They usually start with http:// or https:// and include your provider credentials.
Step 2: Back Up Custom Config Files
If you use custom rules or config files, back them up:
- In CFW, open the “Profiles” tab
- Right-click the profile and choose “Open Folder”
- Copy the .yaml/.yml file to a safe location
- Copy any custom rules directories as well
Step 3: Record Important Settings
Write down the following settings so you can recreate them in ClashX:
- Proxy ports: HTTP and SOCKS5 ports (usually 7890/7891)
- System proxy mode: Global / Rule / Direct
- TUN mode: enabled or not
- DNS configuration: servers and mode
- Launch at login: whether auto-start was enabled
✓ Subscription links exported ✓ Config files backed up ✓ Critical settings noted ✓ Stable internet ready for downloading ClashX
Download and Install ClashX
Installing ClashX takes only a few minutes. Follow the steps below.
Download ClashX
Official download options (recommended):
- Visit the ClashX website: https://clashx.tech/download
- Or open GitHub Releases: ClashX GitHub
- Download the latest .dmg installer
Installation Steps
- Open the .dmg: double-click the downloaded ClashX.dmg file
- Drag to install: drop the ClashX icon into Applications
- First launch: find ClashX in Applications and choose “Open” via right-click
- Security prompt: macOS may warn “Cannot verify developer” — click “Open”
- Install helper: ClashX requests helper privileges; enter your macOS password to approve
ClashX requires helper permissions to manage system proxy settings. This is standard for any macOS proxy client. Always download from official sources to stay safe.
Initial Setup
Once installed you’ll see the ClashX cat icon in the menu bar:
- Click the menu-bar icon
- Leave “Set as system proxy” unchecked until configuration is done
- Open “Config” → “Open Config Folder” to review file locations
Import Subscription Configurations
This is the most important migration step. ClashX fully supports CFW subscription formats, so importing is straightforward.
Method 1: Import via Subscription Link (Recommended)
- Open config manager: menu bar icon → “Config” → “Managed Config” → “Manage”
- Add subscription: click the “+” icon in the bottom-left corner
- Paste the subscription URL you exported from CFW
- Name the config something recognizable (e.g., “Primary Subscription”)
- Click “OK” and ClashX downloads the configuration automatically
- Select the newly imported config to activate it
Method 2: Import Local Config File
Use this if you have custom YAML configs or cannot access the subscription link:
- Menu bar icon → “Config” → “Open Config Folder”
- Copy the backed-up .yaml file from CFW into this folder
- Return to ClashX and click “Config” → “Reload Config”
- Choose the imported config under the “Config” menu
Verify the Config
- Open the “Outbound Mode” menu from the ClashX icon
- Confirm you can see Global / Rule / Direct modes
- Open the “Proxies” menu to view node groups
- Make sure every server node appears correctly
If the “Proxies” menu lists all nodes and you can pick different outbound modes, the import worked. Now you can check “Set as system proxy” and start using ClashX.
Configuration Reference Table
Terminology differs between CFW and ClashX. Use the table below to find equivalent features quickly.
| Feature | Clash for Windows | ClashX | Notes |
|---|---|---|---|
| System proxy | System Proxy | Set as system proxy | Enable system proxy when checked |
| Proxy mode | Mode: Global/Rule/Direct | Outbound mode: Global/Rules/Direct | Same functionality |
| Proxy Select | Proxies tab | Proxy menu | Select node from menu bar |
| Profile management | Profiles tab | Config → Managed config | Manage subscriptions and configs |
| Config folder | Profiles → Open Folder | Config → Open config folder | View config path |
| Logs | Logs tab | Show realtime logs | View connection logs |
| Latency test | Speed button | Proxy → Latency test | Test latency for all nodes |
| Enhanced mode | TUN Mode | Enhanced mode | Helper required |
| Launch at login | General → Start with Windows | Settings → Launch at login | Auto start settings |
| Dashboard | Dashboard button | Console → Yacd Dashboard | Web dashboard |
| Port settings | General → Port | Edit in config file | Default 7890/7891 |
| rule providers | Rules tab | View config file | View in config file |
Quick Navigation
Where to find common actions inside ClashX:
- Enable proxy: menu bar icon → check “Set as system proxy”
- Switch nodes: menu bar icon → Proxies → choose a group → select a node
- Update subscriptions: menu bar icon → Config → Managed Config → Manage → select config → Update
- Latency test: menu bar icon → Proxies → Benchmark (or run tests in Dashboard)
- View logs: menu bar icon → Show Real-time Log
Migration FAQ
These are the issues most users encounter while migrating.
Q1: No nodes after importing the subscription?
Try the following:
- Make sure the subscription URL is correct and not expired
- Verify your network can reach the provider’s server
- Manually update the config: Config → Managed Config → Manage → Update
- Check the realtime log for detailed error messages
- If the link contains special characters, encode it before pasting
Q2: ClashX shows “connection failed” and nothing loads?
Potential causes:
- System proxy disabled: ensure “Set as system proxy” is checked
- No node selected: pick an active node under “Proxies”
- Port conflict: confirm ports 7890/7891 aren’t in use by other apps
- Firewall blocking: allow ClashX in System Settings → Privacy & Security → Firewall
- Config errors: validate the YAML syntax
Q3: TUN (Enhanced) mode won’t turn on?
Fixes:
- Ensure the helper was installed during first launch
- If not, click “Install” → “Install Assistant”
- Enter your admin password to grant permission
- Restart ClashX and enable Enhanced Mode again
Q4: Can I keep CFW and ClashX running together?
Running two proxy clients simultaneously causes port conflicts and proxy-setting confusion. Finish the migration, verify ClashX works, then uninstall CFW.
Q5: ClashX feels slower than CFW—what now?
Optimization Tips:
- Run latency tests and pick the fastest node
- Enable DNS optimizations inside your config
- Disable unnecessary rule sets to reduce overhead
- Limit heavy scripts or plugins
- Temporarily switch to Global mode for a speed comparison
Q6: Certain apps still bypass the proxy?
Solutions:
- Enable Enhanced/TUN mode so all traffic is captured
- Add explicit rules for those applications or domains
- Use TUN mode for apps that ignore system proxy settings
Q7: How do I fully uninstall Clash for Windows?
After you confirm ClashX works properly:
- Quit Clash for Windows
- Delete Clash for Windows.app
- Optionally remove its config folder (keep a backup for a short time)
- Reset system proxy settings if anything remains
Post-Migration Optimization
Fine-tune ClashX with the following suggestions.
Foundational Tweaks
- Enable launch at login so ClashX starts automatically
- Schedule latency tests to auto-select the best node
- Configure auto-update intervals (24h recommended)
- Try experimental options like interface-name auto-detection
Performance Focus
- Use Fake-IP mode to accelerate DNS lookups
- Simplify rule sets and remove unused entries
- Leverage the GeoIP database for precise routing
- Enable TCP Fast Open to shorten handshake time
Security Enhancements
- Keep ClashX updated to the latest release
- Enable HTTPS if you expose the web dashboard
- Treat subscription links as secrets—never share them publicly
- Set a strong password for the dashboard if remote access is enabled
Advanced Recommendations
If you’re comfortable with YAML, consider:
- Building custom rule sets for precise traffic control
- Using Rule Providers to keep rules up to date automatically
- Designing proxy groups to implement load balancing
- Leveraging scripts for bespoke logic
Summary
Migrating from CFW to ClashX is both simple and worthwhile. While CFW’s retirement is unfortunate, ClashX offers tighter macOS integration and continued updates.
Migration Recap
- Preparation: export subscriptions and back up configs
- Installation: download ClashX and authorize the helper
- Configuration: import subscriptions and confirm node availability
- Optimization: tweak settings for better performance and security
Why ClashX Stands Out
- Native macOS build with full Apple Silicon support
- Open-source, active community, frequent releases
- Completely free yet feature-rich
- High config compatibility keeps migration costs low
- Excellent performance with minimal resource usage
Keep a CFW backup for 1–2 weeks after migrating so you can roll back if needed. For any issues, reference this FAQ or open an issue on the ClashX GitHub repository.
• ClashX Official Docs – tutorials • ClashX GitHub – open-source repo • Clash configuration reference – Clash Wiki