Choose v2rayN, v2rayNG, or v2flyNG for your operating system. Download links are organized by interface edition, CPU architecture, and package format. Check your device details first, then select the matching package.
Switching platforms updates the page URL as well. Copy the link with the platform marker to reopen the page at the corresponding download section.
Windows offers Desktop and the classic WPF interface. Both manage subscriptions, routing rules, and the system proxy; the main difference is the interface technology and layout. Desktop is generally the best starting point for a new installation. If you already prefer WPF or need its familiar menu paths, continue with the classic edition.
Current version 7.24.1
Desktop is the next-generation cross-platform UI, with a structure closer to the macOS and Linux editions. WPF is the classic Windows desktop interface with stable menu placement, making it suitable for users who want to keep their existing workflow.
| Check | Recommended requirement | Selection guidance |
|---|---|---|
| CPU architecture | x64 | The Windows packages on this page target common 64-bit desktop and laptop computers. |
| Interface edition | Desktop preferred | Choose Desktop for a first installation; choose WPF if you prefer the classic menu layout. |
| Installation permissions | Permission to install desktop applications | The system may request permission confirmation when installing or enabling certain network features. |
macOS packages are split between Apple Silicon and Intel architectures. Open System Information and check the chip or processor field: download arm64 for an Apple M-series chip and x64 for an Intel processor. The architecture must match; choosing the wrong package commonly results in the app failing to open or requiring an additional translation environment.
Current version 7.24.1
The two dmg packages provide the same client features; only the compiled architecture differs. The Apple Silicon edition is for devices with M-series chips, while the Intel edition is for Intel-based Macs. Confirm the architecture before downloading to reduce repeated installation and compatibility troubleshooting.
| Device information | Package | How to identify it |
|---|---|---|
| Apple M-series chip | Apple Silicon arm64 | The Chip field in System Information shows an Apple M-series name. |
| Intel processor | Intel x64 | The Processor field in System Information shows an Intel model. |
| Installation format | dmg | Open the disk image and follow the system interface to install the application. |
v2rayNG is the preferred Android option and uses the Xray core ecosystem. Choose v2flyNG when you need a compatibility path based on the v2fly core. Both clients offer arm64 and universal packages. Most mainstream phones released after 2015 use arm64; use the universal build when the architecture is unknown.
Current version 2.2.6
v2rayNG is a widely used graphical client for Android, suited to importing subscriptions, scanning shared configurations, switching routing modes, and managing multiple configuration groups. Most modern phones can use the arm64 package directly.
Current version 1.10.31
v2flyNG targets Android use cases that require a v2fly core implementation. Its interface supports configuration imports, group management, routing selection, and connection controls, making it an alternative core path to v2rayNG.
| Option | Recommended choice | Best for |
|---|---|---|
| Primary client | v2rayNG | Preferred for everyday use and Xray core configurations. |
| Alternative client | v2flyNG | Choose this when you need a v2fly core compatibility path. |
| CPU architecture | arm64 | Usually suitable for mainstream Android phones released after 2015. |
| Compatibility choice | Universal | Choose this when the CPU architecture is unknown or the dedicated package will not install. |
Choose the Linux package by distribution packaging system and CPU architecture. Debian, Ubuntu, and derivatives typically use deb; Fedora, Rocky Linux, AlmaLinux, and other RPM-based distributions use rpm. Most desktop computers are x64, while ARM devices use the matching arm64 package.
Current version 7.24.1
Run uname -m first to check the architecture: choose x64 for x86_64, and arm64 for aarch64 or arm64. Then select deb or rpm according to the distribution’s package management system.
| System or architecture | Matching package | How to identify it |
|---|---|---|
| Debian and Ubuntu family | deb | The system manages packages with dpkg and apt. |
| Fedora, Rocky Linux, and more | rpm | The system uses the RPM package format. |
| x86_64 | x64 | Common Intel or AMD 64-bit desktop processors. |
| aarch64、arm64 | arm64 | 64-bit ARM devices, including some development boards and mini PCs. |
The same client name does not mean every file fits your device. Check the platform, CPU architecture, and package format in that order to usually choose the right file on the first try.
Windows, macOS, Android, and Linux use different, non-interchangeable application formats. Use the top tabs to open the matching platform first; do not download based only on a client name appearing in the filename. For desktops, v2rayN is generally the first choice. On Android, start with v2rayNG for regular use and choose v2flyNG when you need the v2fly core path.
macOS distinguishes Apple Silicon from Intel; Android mainly distinguishes arm64 from the universal package; Linux distinguishes x64 from arm64. Dedicated architecture builds have a clearer size and runtime target, so prefer one after confirming the device is arm64. If the Android architecture is completely unknown, the universal package is the safer compatibility choice.
Windows Desktop and WPF differ in interface approach, so Desktop is a good starting point for a first installation. Linux deb and rpm packages are determined by the distribution’s packaging system and cannot be swapped based on interface preference. After the file finishes downloading, follow the system’s standard installation process and read permission prompts on first launch.
Installation is only the first step. The sequence below works for most graphical clients and helps avoid repeatedly troubleshooting subscriptions, proxy modes, and system permissions.
Obtain a valid subscription URL or shared configuration from your service provider, then create a group from the client’s subscription management section. Save it and refresh the subscription so the client can load the remote configuration list. If the list remains empty, check that the URL is complete, the group filter is not hiding configurations, and the subscription format is supported by the client.
Clients typically offer separate control layers such as the system proxy, routing rules, and TUN. Start with the system proxy and a preset route, then confirm that your browser and target applications connect as expected before considering TUN. Record the current mode before changing advanced rules so you can restore it quickly if an application becomes incompatible.
After selecting a configuration and starting the client, confirm that the status shows the core is running, then check the system proxy switch and current routing mode. If an application is not handled by the client, restart it first, then look in the logs for configuration parsing, port conflicts, or permission messages. Change only one setting at a time to make the result easier to interpret.
Most issues involve the interface edition, CPU architecture, package format, or initial configuration. Confirm the device information first, then adjust client settings to shorten the troubleshooting path.
Desktop is the next-generation cross-platform interface, suited to first-time installations and users who want a similar workflow across desktop systems. WPF is the classic Windows interface with established menu paths for users familiar with the older layout. Both manage subscriptions, configurations, and routing; Desktop is the recommended starting point for first-time users.
Open System Information and check the chip or processor field. Choose Apple Silicon arm64 when it shows an Apple M-series name, or Intel x64 when it shows an Intel model. The two packages have the same features and differ only in their compiled target architecture. Matching the package to the device chip provides a direct, predictable runtime environment.
Most mainstream Android phones released after 2015 use arm64, so the arm64-v8a package is preferred. The universal build supports a broader range of architectures and is suitable when the processor type is unknown or a dedicated package reports an architecture mismatch. The two packages provide the same core features.
Debian, Ubuntu, and derivatives generally use deb; Fedora, Rocky Linux, AlmaLinux, and other RPM-based distributions use rpm. After choosing the format, confirm the architecture: x86_64 corresponds to x64, while aarch64 or arm64 corresponds to arm64.
After launching the client, import a valid subscription or individual configuration and refresh the subscription. Then select the configuration to use and set the system proxy and routing mode for your needs. To route more application traffic through the client, configure TUN after understanding its permission and routing effects. See the site’s usage guide for the complete procedure.