CLIENT PACKAGES / CURRENT RELEASES
Choose a package by operating system, processor architecture, and interface type. Use v2rayN on desktop systems, v2rayNG on Android by default, or v2flyNG when a v2fly core implementation is required.
PLATFORM SELECTOR
Switch to the platform used by the current device, then verify the architecture and package format. Platform tabs are synced to the page URL, so reopening the link restores the corresponding download section.
WINDOWS / X64
Windows offers two interfaces: Desktop and classic WPF. Choose Desktop for a first installation or a desktop layout closer to other platforms. If you already know the classic menus, tray controls, and WPF layout, continue with classic WPF. Both packages target Windows x64; do not install both.
Current version 7.24.1
A new cross-platform UI with consistent desktop layouts for settings, subscription groups, and routing. Suitable for new installations and for users who want similar workflows across desktop systems.
Current version 7.24.1
A stable classic Windows interface with familiar WPF windows, menus, and tray controls. Before migrating existing settings, record subscription groups, routing mode, and local listening ports to avoid confusion from mixing old and new directories.
| Check | Requirement | What to do |
|---|---|---|
| Processor architecture | x64 | Open “Settings → System → About” and check the system type; the Windows packages on this page target 64-bit desktop systems. |
| Installation permissions | Run the installer | When Windows asks for permission, verify the app name and the requested action before continuing. |
| Configuration migration | Record the current settings first | Record the subscription URL, groups, routing mode, local port, and startup status. |
| Connection prerequisites | Subscription or node configuration | After installation, import the configuration, update the subscription, and choose a node before enabling the system proxy or TUN mode. |
Desktop and WPF are two interface choices, not components that must be installed together. When migrating from an older version, close the running client and system proxy first, then install. Afterward, check that its local listening port does not conflict with other network tools.
MACOS / ARM64 · X64
macOS packages are split between Apple Silicon and Intel. Open “About This Mac” from the system menu and check the “Chip” or “Processor” field: choose arm64 for Apple M-series chips and x64 for Intel processors. Matching the architecture correctly helps avoid installation failures and compatibility-layer issues.
Current version 7.24.1
For Macs with Apple M-series chips. This package uses the arm64 architecture for current mainstream Mac devices. After downloading, open the disk image, move the app to the Applications folder, and launch it from there.
Current version 7.24.1
For Macs that show an Intel processor in “About This Mac.” This is an x64 disk image. If the system shows an Apple chip, do not rely on the device’s appearance or purchase year; return and choose Apple Silicon instead.
| Check | Selection basis | Instructions |
|---|---|---|
| Chip architecture | Apple M series or Intel | Check About This Mac; do not guess from screen size, model name, or purchase date. |
| Installation location | Applications folder | After opening the DMG, move the client to Applications instead of running it from the disk image window long-term. |
| Network permissions | Grant permissions for the selected mode | When enabling the system proxy or requesting network-extension access, follow the system prompts, then return to the client and check its status. |
| Menu bar status | Confirm that the client is still running | Closing the main window does not necessarily quit the process; open the client from its menu bar icon before changing settings. |
After the first launch, import the subscription and run an update. If nodes appear but the browser's connection behavior is unchanged, check the routing mode, system proxy status, and whether the client is still running in the background instead of repeatedly changing package architectures.
ANDROID / ARM64 · UNIVERSAL
Android packages are listed in a fixed order: v2rayNG followed by v2flyNG. v2rayNG uses the Xray core and is the primary choice; v2flyNG uses the v2fly core for configurations that specifically require it. Most mainstream phones released after 2015 can use arm64; choose Universal when the architecture is unknown.
Current version 2.2.6
An Android client using the Xray core, with subscription management, node selection, routing settings, per-app proxying, and system VPN service integration. Choose arm64 for most recent phones; use Universal when the architecture is unknown or the arm64 package cannot be installed.
Current version 1.10.31
An Android client using the v2fly core, intended for configurations that explicitly require the v2fly implementation or for comparing behavior between the two cores. The standard setup is to import a subscription, choose a node, authorize the VPN service, and start the connection.
| Check | Recommended choice | Details |
|---|---|---|
| Recent mainstream phones | arm64-v8a | Most mainstream devices released after 2015 can start with the arm64 package, which is focused on the target architecture. |
| Architecture unknown | Universal | If device details are unavailable or the arm64 package reports an architecture mismatch, use the Universal package. |
| First connection | Allow VPN service | The system permission creates a local virtual network interface; without it, the client cannot route app traffic. |
| Background operation | Adjust battery-saving settings | If connections frequently stop after the screen locks, add the client to the system's battery-optimization whitelist and allow necessary background activity. |
Do not start both Android clients at the same time to create VPN services. Before switching clients, stop the current connection, import the configuration, and review the logs. If the subscription updates but nodes cannot connect, troubleshoot in this order: system time, node parameters, network permissions, and routing settings.
LINUX / DEB · RPM
Linux packages are split by distribution package system and processor architecture. Choose deb for Debian, Ubuntu, and derivatives; choose rpm for Fedora, Rocky Linux, AlmaLinux, and RHEL-based distributions. Run uname -m: choose x64 for x86_64 and arm64 for aarch64.
Current version 7.24.1
First identify whether the distribution uses deb or rpm, then confirm the processor architecture. x64 is common on traditional desktop computers and server workstations; arm64 is common on ARM desktops and development boards. The package format and architecture must both match; do not choose based only on the version number in the filename.
Use this when uname -m returns x86_64.
Use this when uname -m returns aarch64.
| Distribution or environment | Package format | Architecture check |
|---|---|---|
| Debian, Ubuntu, and derivatives | deb | Choose amd64 for x86_64; choose arm64 for aarch64. |
| Fedora, Rocky Linux, AlmaLinux, and RHEL-based | rpm | Choose x86_64 for x86_64; choose aarch64 for aarch64. |
| Desktop session | Graphical environment required | v2rayN is a graphical client and should be launched and configured from an available desktop session. |
| System proxy | Configure for the desktop environment | After connecting, confirm that the desktop environment reads the system proxy. Terminal programs may require proxy environment variables to be configured separately. |
If the package manager reports dependency problems, read the complete error message first and install the missing dependencies from the current distribution's repositories. Do not switch back and forth between deb and rpm. After the client starts, check configuration-directory permissions, desktop tray support, and local port usage before importing a subscription.
INSTALLATION ROUTE
Downloading only prepares the client. You still need to import a configuration, choose a node, set the traffic-routing method, and verify the access path. Handling these steps in order helps separate installation, configuration, and network issues.
Windows users should choose either Desktop or classic WPF; Mac users should choose arm64 or x64 based on the chip field; Android users should first distinguish arm64 from Universal; Linux users should verify both the distribution package system and the uname -m output. If the package will not open or reports an architecture mismatch, return to this step instead of changing node parameters.
Place desktop apps using the system installation flow, and follow Android's prompts to finish installation. When establishing the first connection, the system may request network, VPN service, or related extension permissions. These permissions let the client create a local traffic entry point; after granting them, return to the client and confirm that the connection status has changed.
The client does not include subscriptions or nodes. Add a subscription URL through the relevant subscription-group entry and update it; add a single-node sharing link through the clipboard import or scan option. After importing, verify that the server address, port, protocol, and transport fields are populated before continuing.
Select the target configuration from the node list, then choose system proxy, TUN, VPN service, or the relevant client mode based on your needs. Starting the client without enabling traffic routing usually will not send browser or app traffic through it. Routing rules also determine which destinations use proxy egress, direct egress, or blocking.
First open a clearly accessible regular webpage to confirm DNS resolution, the TCP connection, and browser access; then check a destination that requires the proxy. If it fails, note the time and review the client logs. Timeouts, TLS handshakes, DNS, unmatched routes, and local port conflicts are different issues and should be handled according to their log keywords.
PACKAGE DECISIONS
The same client name does not mean a package works across platforms or architectures. Complete these four checks before downloading to avoid common installation problems.
Windows installers, macOS disk images, Android APKs, and Linux deb and rpm packages are handled by their respective systems. The file extension is the first check. Copying a package for another system to the current device does not convert it into a native executable.
x64, arm64, amd64, and aarch64 are common architecture labels. amd64 and x64 refer to the same class of 64-bit desktop architecture, while aarch64 and arm64 refer to ARM 64-bit architecture. Use About This Mac for Mac, uname -m for Linux, and Universal for Android when the architecture is unknown.
deb and rpm differ in more than their extensions: they belong to different package-management systems. Using the native package format helps the installer handle dependencies, menu entries, and later removal. Do not choose a format based on file size or filename length.
Use v2rayN for desktop systems. Choose v2rayNG by default on Android; consider v2flyNG only when the configuration requirement or troubleshooting goal specifically points to the v2fly core. Switching clients will not fix an expired subscription, incorrect node parameters, or an inaccurate system clock.
DOWNLOAD FAQ
These questions cover version selection, chip architecture, package formats, and the first connection. For subscription updates, node timeouts, DNS, and system proxy issues, continue to the Troubleshooting page.
The Desktop version uses a new cross-platform interface for users who want a consistent desktop experience. The classic WPF version retains the native Windows interface and familiar workflows for users who prefer its menu structure. Both target Windows x64; install either one. Before switching interface versions, record subscription groups, routing mode, and local listening ports.
Open “About This Mac” from the system menu and check the chip or processor field. Choose Apple Silicon arm64 for an Apple M-series chip or Intel x64 for an Intel processor. Do not rely only on device color, screen size, or purchase year, because similar-looking models may use different architectures.
Most mainstream Android phones released after 2015 use arm64, so download the arm64 version first. Use Universal when the architecture is unknown or the arm64 package is incompatible. Universal covers more devices, but it is not the required default for every device.
Use deb for Debian, Ubuntu, and derivatives; use rpm for Fedora, Rocky Linux, AlmaLinux, and RHEL-based distributions. Choose x86_64 or arm64 based on the output of uname -m. If the distribution is unclear, read its name and family information from /etc/os-release.
After installation, import a working subscription URL or single-node configuration, choose a target node, and enable the system proxy, VPN service, or relevant traffic-routing mode. The client does not include subscriptions or nodes. If an imported node fails to connect, first check the device time, node parameters, current network, and client logs.
Start with subscription import, node selection, and system proxy settings. If subscriptions fail, nodes time out, or browser and terminal behavior differ, follow the documentation for the observed symptom.