Migrate from ClashX to ClashFX: Backup, Import, Verify & Rollback

Published on 2026-03-01 · Last updated 2026-11-11

Understanding Product & Directory Differences

Before beginning migration, understand how ClashFX handles configurations compared to legacy ClashX:

• Active Development Focus: Development focus has shifted to ClashFX. The legacy ClashX website remains accessible as an archive for older builds, documentation, and troubleshooting resources.
• Independent Configuration Directories:
  • Standard ClashX default directory: ~/.config/clash
  • ClashFX 1.1.11 default directory: ~/.config/clashfx
• One-Time Copy Behavior: On its very first startup, ClashFX 1.1.11 checks if ~/.config/clashfx exists. If the folder does not exist, ClashFX copies your legacy ~/.config/clash directory into ~/.config/clashfx. If ~/.config/clashfx already exists (even if empty), this auto-copy is skipped to protect existing files.
• Subscriptions Must Be Re-Added: Remote subscription URLs are stored in application preferences, not inside the configuration directory. You will need your subscription links handy to register them in ClashFX.
• No License Needed: ClashFX current core features (Enhanced Mode, remote subscriptions, and the YAML editor) are completely free. ClashFX Pro is a separate concept plan in preparation and is not required for migration.

Step 1: Create a Timestamped Terminal Backup

Before modifying any configuration files, create a safe, isolated backup of both directories. Open Terminal (Cmd + Space → Terminal) and execute this shell script:

(
  set -e
  task_stamp="$(date +%Y%m%d-%H%M%S)"
  task_backup_dir="$HOME/.config/clashfx-migration-backup-$task_stamp"
  mkdir -p "$HOME/.config"
  mkdir "$task_backup_dir"
  if [ -d "$HOME/.config/clash" ]; then
    cp -a "$HOME/.config/clash" "$task_backup_dir/"
  fi
  if [ -d "$HOME/.config/clashfx" ]; then
    cp -a "$HOME/.config/clashfx" "$task_backup_dir/"
  fi
  printf 'Backup successfully created at: %s\n' "$task_backup_dir"
)

Verify that the command outputs the backup directory path without errors. Keep this path handy in case you ever wish to roll back.

Step 2: Fully Quit ClashX

To avoid local port collisions on port 7890 or 9090:

1. Click the ClashX icon in your top menu bar.
2. Uncheck Set as System Proxy.
3. Select Quit ClashX.
4. Confirm that the icon disappears from your menu bar.

Step 3: Install & Launch ClashFX

1. Download the latest Universal binary from our Download Page.
2. Open ClashFX.dmg and drag ClashFX to your Applications folder.
3. Launch ClashFX from /Applications.
4. If prompted with a developer verification alert, navigate to System Settings → Privacy & Security and click Open Anyway.
5. Once launched, ClashFX creates ~/.config/clashfx (copying your older configs if this is a fresh install).

Step 4: Re-register Remote Subscriptions

Because subscription links are stored in application preferences rather than YAML files, re-add your providers into ClashFX:

1. Click the ClashFX menu bar icon.
2. Select Remote Config Management → Manage Remote Configs.
3. Click the + button.
4. Input your subscription name and paste your provider’s subscription URL.
5. Set the auto-update interval (e.g., 24 hours) and click Confirm.
6. Repeat for any secondary subscription providers you maintain.

Step 5: Post-Migration Verification Checklist

Follow this checklist to confirm that ClashFX is operating correctly:

• Config Loaded: In Config, verify that your preferred YAML file is selected and has a checkmark.
• Nodes Available: Open Proxies and confirm your proxy nodes and groups appear.
• Latency Test: Click the latency test icon to ensure servers respond with valid millisecond ping times.
• System Proxy Active: Toggle on Set as System Proxy, then test web browsing in Safari or Chrome.
• Enhanced Mode (TUN): Toggle on Enhanced Mode, enter your macOS password once to approve the helper tool, and verify that terminal commands (curl https://api.ipify.org) route successfully.

Step 6: Safe Rollback Procedure

If you encounter unexpected issues and need to revert back to ClashX immediately:

1. Open ClashFX menu, turn off Enhanced Mode and Set as System Proxy.
2. Quit ClashFX completely.
3. Launch your original ClashX application.
4. If configuration files in ~/.config/clash were altered, restore them from your backup:

   # Replace with your actual timestamped backup folder
   cp -a ~/.config/clashfx-migration-backup-<TIMESTAMP>/clash/* ~/.config/clash/

5. Select Set as System Proxy in ClashX to resume your previous setup.

Next Steps

• Explore the Enhanced Mode (TUN) Guide for system-wide routing.
• Check out the Built-in Config Editor to customize rules without external tools.
• Consult the macOS Troubleshooting Guide if any connectivity issues arise.