How do x64, AMD64, and ARM64 differ in desktop installers?
x64, x86_64, and AMD64 usually refer to the same 64-bit x86 architecture for compatible Intel or AMD devices. ARM64 is a different architecture, so a system being 64-bit does not mean an x64 package will work. Check your processor type in system information first. If only an x64 package is listed, confirm that your device can run it before installing.
Why might an Apple Silicon download link for macOS provide an x64 file?
Apple Silicon uses the native ARM64 architecture, but some clients may link to the same Intel build from both download entries. Check the architecture listed for the actual file and in its release notes before and after downloading. An x64 or x86_64 file is not a native ARM64 build. If you plan to use Rosetta, confirm that the client and its networking components support it.
Do I need a subscription or YAML file after downloading a client?
You’ll need a configuration source supported by the client. The installer installs the app; it does not include a ready-to-use proxy subscription. Open the client’s configuration page and import a subscription link you’re authorized to use or a local YAML file, then select that configuration. Confirm it loads before testing the connection so you can troubleshoot each step separately.
Can I install over an older client or switch to a different one?
Before upgrading the same client, back up your configuration, overrides, and subscription sources, then follow the release notes to see whether installing over the existing version is supported. To switch clients, quit the old app and turn off any system proxy or TUN it started before importing your configuration. Settings and override formats may differ, so avoid copying the old app’s entire data directory to the new client.
Should I download a desktop client or the Mihomo core for everyday use?
Choose a GUI client to import subscriptions, switch proxy groups, and view logs. The standalone Mihomo core is better suited to users comfortable with the command line and service management, such as those deploying it on a server or router. You’ll need to provide your own configuration and runtime environment; the core won’t automatically appear in an existing client’s configuration list.