On this page
On a Mac, “won’t open” can mean the app itself or a web page accessed through the proxy, and they need different checks. During download and installation, focus on the chip, file source, and system security prompts. Once the app opens, check the configuration and requests. When replacing an old client, also remove the proxy settings it left behind.
Mac Downloads: Apple Silicon or Intel?
Check the chip or processor field in About This Mac under the Apple menu, then choose the matching macOS asset from the table below. Do not guess the architecture of a used or workplace device from its purchase year.
Download the macOS asset from the Release page of the actual project, such as Clash Verge Rev; the file list should match the version tag and release notes. Do not use a similarly named “cracked Mac edition” from a file-sharing site or assume a file is maintained merely because Clash appears in its name.
Mac and asset labels
| What the Mac reports | Option |
|---|---|
| Apple M1, M2, M3, or Later Apple-Series Chips | arm64 / Apple Silicon |
| Intel processor | x64 / Intel |
| Universal | Contains both architectures and is usually larger |
| Unable to determine | Return to “About This Mac” and check instead of guessing |
Install the App from the DMG into Applications
Standard installation process
Open the downloaded DMG
Wait for Finder to show the app icon and Applications folder.
Drag the app into Applications
After copying finishes, launch it from the Applications folder; do not keep running it from the DMG.
Eject the disk image
Once the app is copied, eject the DMG from the Finder sidebar.
Keep the original Release information
You will need the version and architecture later for troubleshooting and updates.
If an older version with the same name already exists in Applications, completely quit its menu bar process before replacing it. An old ClashX instance, another Mihomo client, or VPN software may alternately change the system proxy and make the new installation look broken.
Handling Developer Verification and Damaged-App Warnings
When macOS first opens an app downloaded from the internet, it may say the developer cannot be verified or the app was blocked. Recheck the project Release, version, and filename, then open “System Settings > Privacy & Security,” find the recently blocked item, and follow the system's “Open Anyway” flow.
Do not run a global command that disables Gatekeeper or install an unknown signing patch to bypass the prompt. A per-app exception from the system is sufficient, while other downloads remain protected. If the app is reported as damaged, redownload the asset for the correct architecture instead of immediately removing security attributes.
Menu-Bar Icon and Mihomo Startup Status
On first launch, seeing the interface does not mean Mihomo is ready. Open settings or logs and check that the core is not repeatedly exiting and the client can read and write its configuration directory. No subscription has been imported yet, so core failed or permission denied points you to the local installation and permissions, rather than the subscription.
If the app opens only after a Rosetta prompt, you probably chose an Intel build. Although Apple silicon can run some Intel apps, use the project's arm64 version to reduce extra dependencies and avoid confusion during future updates.
Import a Subscription and Enable the System Proxy
This example uses Clash Verge Rev. Add a Clash- or Mihomo-compatible subscription in Profiles, update it manually, and select it. Select a specific node in Proxies, keep Rule, then enable System Proxy. If macOS asks for permission to change the proxy, confirm the request comes from the client you just installed.
When the browser opens a familiar site, the corresponding connection should appear in Connections. Do not enable TUN or install a network extension until the ordinary system proxy works. Otherwise, one failure will involve the subscription, node, system proxy, and network permissions at once.
For other macOS clients, use their own subscription and connection controls. Not finding Profiles does not mean installation failed.
Visible results of the first connection
- The Profile shows the current update time
- You can select a specific node in Proxies
- The current client writes the macOS system proxy
- Connections shows the browser request you just made
Handling an App That Will Not Open or a Page That Will Not Load
The app icon has a prohibited symbol
Check the macOS version requirement and app architecture, then download the matching build.
The app says it is damaged
Redownload it from the original Release and confirm that the file is complete and from the same source.
Subscription update returns 401 / 403
The link credential or account status has a problem unrelated to macOS permissions.
The browser fails and Connections is empty
Confirm that System Proxy was written, and quit other proxy clients.
The connection enters Clash but shows timeout
Switch to another verified node; there is no need to reinstall the DMG.
Remove macOS Proxy Settings When Uninstalling or Migrating
Before uninstalling, rolling back a version, or moving to another client, disable the system proxy and TUN in the current app, then quit it fully from the menu bar. Closing only the window may leave the background process listening on the local proxy port. If you drag the app straight to the Trash, the browser will still try to connect to the proxy port that has stopped.
In macOS network settings, confirm that HTTP, HTTPS, and SOCKS proxies have been removed; the browser should directly reach locally accessible sites. After direct access returns, delete the app from Applications and remove data you no longer need. During migration, reimport the subscription instead of overwriting one client's data directory with another's.
After enabling System Proxy in the new client, new browser requests should appear in Connections. When changing versions or clients later, keep exiting the program and checking direct access as part of the process.