v2rayN
Both downloads are x64 ZIP packages. Desktop is the newer cross-platform interface and a good place to start for a first install. WPF is the classic, stable version for users who prefer its familiar interface and workflow. Choose one.
For desktop, choose v2rayN. For Android, v2rayNG is the first choice; v2flyNG is another option if your configuration requires it. Select the target operating system, then choose the architecture and package format.
Choose a package in this orderOperating system → Processor architecture → Package
Both downloads are x64 ZIP packages. Desktop is the newer cross-platform interface and a good place to start for a first install. WPF is the classic, stable version for users who prefer its familiar interface and workflow. Choose one.
Extract the entire ZIP to a directory you can write to, then run the installer from the extracted folder. Don’t launch it from the archive preview or drag out just the installer and leave its companion files behind. On a managed work device, check your organization’s installation and permission requirements first.
If the app won’t open, check whether the system reports an architecture mismatch, a missing runtime, or insufficient permission to write to the directory. If a runtime is required, follow the prompt for the named component and version. Switching to the other interface won’t fix an architecture mismatch.
Before switching from the classic version to Desktop, save your subscriptions and custom rules, then quit the old client from the system tray. Once the new interface can update subscriptions and connect successfully, you can remove the old version. If you keep the old configuration, don’t point both programs at the same data in active use.
Open About This Mac from the Apple menu. If it shows an Apple M-series chip, choose Apple Silicon (arm64); if it shows an Intel processor, choose Intel (x64). Don’t determine the chip by the computer’s purchase date.
Open the DMG and drag the client to the Applications folder, then launch it from there. You can eject the disk image after installation. If you run the app directly from the disk image window, it won’t be available from that location once the image is ejected.
If macOS displays a warning, first determine whether it’s about an incompatible system version, a processor architecture mismatch, or a device management policy. For the first two, check your system information and package choice. On a managed device, follow your administrator’s installation process instead of disabling system-wide security protections.
Before replacing an older version, quit the client completely—not just its main window. After installation, make sure you’re opening the new copy in Applications, then check whether your subscriptions are still there. If it won’t open, note the exact warning and chip type; repeatedly mounting the same disk image is unlikely to help.
Powered by the Xray core. Most mainstream phones released after 2015 can use arm64; choose this package if your system supports arm64-v8a. If you’re unsure which app architecture your device supports, try the universal package.
Powered by the v2fly core. Choose this client if your existing configuration specifically requires that core. Importing the same subscription into another client doesn’t guarantee compatibility; check the configuration requirements rather than relying on whether nodes appear in the list.
Open the APK in your browser or file manager. If prompted, verify the installation source and grant permission only to the app you’re using to open the file; you can revoke it after installation. The VPN permission requested on first connection is separate from installation permission. Check the app name shown in each prompt.
If the system says the app is already installed but won’t update it, check whether the old version came from the same source and has the same signature. Switching between arm64 and universal packages won’t change the signature. If you need to uninstall the old version, back up subscriptions and manual settings using the app’s backup feature first.
For Debian and Ubuntu, start with the deb package. For distributions that use RPM package management, start with rpm. Matching package formats don’t guarantee compatibility with your distribution or its dependencies. Pay particular attention to the el10 build identifier in this site’s RPM package names.
Check your distribution, system version, and current architecture in system information first. In package names, amd64 and x86_64 correspond to x64; arm64 and aarch64 correspond to arm64. If you’re installing in a virtual machine, use the architecture reported inside the VM.
Open the package for your format and let your distribution’s package installer check dependencies. If dependencies are missing, note their package names and versions, then check whether your configured repositories provide them. Don’t try to convert formats by changing the file extension or force the install while ignoring dependencies.
This is a GUI client, so make sure the device has a usable desktop session before installing. Desktop environments handle system proxy settings differently. If only some apps use the proxy after installation, check whether those apps read the desktop proxy settings; this doesn’t necessarily mean the installation failed.
First identify what you’re doing: installing for the first time, updating an existing version, or switching clients. For a first install, check that the device can run the package. For an update, consider existing settings and the installation source. When switching clients, check whether your subscription’s protocols and settings will carry over. Treating these as separate tasks can save time and avoid unnecessary troubleshooting.
If you’re downloading on a computer for another device, don’t choose a package based on the system running your current browser. Check the target device’s operating system, version, and architecture in its system information, then select a package here. This is especially important when transferring an installer between computers: the same operating system can have different package options.
After starting the download, check the browser’s download list to make sure it has finished. If it’s paused or interrupted, resume it or download the file again; don’t open an incomplete file. Save it somewhere easy to find. If the folder contains multiple versions, compare the download time and full filename instead of relying on the icon.
Subscription addresses and client settings are separate types of data. Updating a subscription can retrieve configurations provided by the server, but it may not restore manually added configurations, custom routing rules, local ports, or app-specific settings. Before updating, use the client’s export feature where available. For settings that can’t be exported, make a note of the non-sensitive details you’ll need to restore.
Subscription addresses may contain parameters that grant access to account settings. Don’t post an address, QR code, or full runtime log in public comments, and don’t upload unredacted configuration backups to shared drives. For troubleshooting, the operating system version, client name, steps to reproduce the issue, and an error message with sensitive details removed are usually enough.
Before updating a desktop version, stop the connection and fully quit the background process. Before replacing an app on a mobile device, check whether it supports an in-place update or requires a reinstall. If the new version has problems, record the error and restore the last working setup from your backup. Avoid changing the package, subscription, and proxy mode all at once.
When you first open the client, check that the main window opens and that settings can be saved. Next, add a subscription group, update it, and select the configuration you want to test. A successful subscription update only confirms that the client retrieved the subscription content; test node connectivity and app traffic separately.
Start by testing an app that reads the system proxy settings. On desktop, begin with the system proxy and look into TUN mode only if needed after confirming the basic connection. On mobile, check whether the system allows a VPN connection and whether another VPN is already active. If the connection works but one app doesn’t, check whether it uses system settings, its own proxy settings, or a direct connection.
When something fails, note which step it happened at. If the installer won’t open, check the architecture and system requirements. If the client opens but has no configuration, check the subscription group and update result. If a configuration appears but won’t connect, check what’s enabled and review the runtime log. Change one thing at a time and test again so installation issues don’t get mixed up with connection issues.
Choose one. For a first install, start with Desktop. If you already use a WPF workflow, stick with the classic WPF version. Don’t run both versions at the same time with the same configuration; their local listening ports or system proxy settings may conflict.
No. Both x64 and arm64 are 64-bit architectures. Check the processor architecture in your system information. For Linux package names, amd64 and x86_64 correspond to x64, while aarch64 corresponds to arm64.
First check system compatibility, available storage, and permission to install from the current source. Then check whether an older version with the same package name but a different signature is installed. A universal package may help with architecture selection, but won’t fix a signature conflict. Back up your subscriptions and settings before uninstalling the old version.
The card version and package download links come from separate manifest entries, so they may not match. To confirm the installed version, check the app details shown by the installer or open the client’s About page after installation. Don’t rely on the card version alone.
The installer provides the client, not a subscription service. Get a subscription address you’re authorized to use, import it, and update it. Then select a configuration on the main screen. If you already have configurations, check that the right group is selected.