CLIENT PACKAGES / 2026
Choose v2rayN for desktop systems and v2rayNG for Android. Confirm your operating system and processor architecture before downloading the matching package.
Choose by operating system
The platform choice is reflected in the page URL. After switching, only the clients, package types, and minimum environment details for the selected system are shown.
WINDOWS CLIENT
The two options use different UI implementations. Desktop is the newer cross-platform UI and suits new installations; WPF is the classic Windows interface for users who prefer the established workflow.
A GUI client for Windows desktops. Manage subscription groups, server profiles, the system proxy, routing rules, and TUN mode. Choose Desktop for a first installation; choose WPF if you prefer the classic menus and tray workflow.
| Check | Recommendation | How to choose |
|---|---|---|
| System architecture | 64-bit Windows | The Windows packages on this page target x64. |
| UI version | Choose Desktop for a new installation | Choose WPF only if you need the classic menu layout. |
| Installation permissions | Allow the installer to write to the application directory | Launch it from the Start menu or application directory after installation. |
| First connection | Import a subscription, then select an active server | Enable the system proxy only after a usable configuration is available. |
MACOS CLIENT
Packages are separated by processor architecture. Apple M-series chips use arm64, while Intel processors use x64; choosing the wrong architecture may prevent the app from starting or require an additional compatibility layer.
v2rayN’s Avalonia desktop interface runs on macOS. Before installing, open About This Mac or System Information and check the chip field, then choose the DMG for Apple Silicon or Intel.
| Check | Apple Silicon | Intel |
|---|---|---|
| Chip field | Apple M-series | Intel processor |
| Package | arm64 DMG | x64 DMG |
| Installation method | Open the DMG and move the app to Applications | Open the DMG and move the app to Applications |
| Network permissions | Follow the system prompt to authorize access when enabling the proxy or TUN for the first time | Follow the system prompt to authorize access when enabling the proxy or TUN for the first time |
ANDROID CLIENTS
Use v2rayNG first in most cases. v2flyNG is the alternative client for the v2fly core. Both clients offer arm64 and Universal packages; choose arm64 for mainstream devices.
An Android GUI client built on the Xray core, with subscription updates, QR-code import, routing modes, per-app proxying, and VPN service support. Most mainstream phones released after 2015 use the arm64-v8a architecture.
An Android client built on the v2fly core. Choose it if you already use v2fly configurations, your service parameters follow v2fly behavior, or you need consistency with an existing configuration environment.
| Check | Recommended choice | Details |
|---|---|---|
| Clients | v2rayNG | Use it for general needs; choose v2flyNG when v2fly behavior is specifically required. |
| Processor architecture | arm64-v8a | Most mainstream phones released after 2015 use this architecture. |
| Universal package | Compatibility option | Use it when the device architecture is unknown or the dedicated package will not install. |
| Connection permissions | Allow the client to establish a VPN service | The system displays an authorization dialog when you start the first connection. |
LINUX CLIENT
Choose deb or rpm by distribution, then choose x64 or arm64 by processor. Debian and Ubuntu use deb; Fedora and RHEL-based distributions use rpm.
The Linux desktop edition provides deb and rpm packages. x64 is for common 64-bit Intel and AMD computers; arm64 is for 64-bit ARM devices. Confirm the processor type in system settings or with the architecture information in a terminal before installing.
| Distribution or device | Package format | Architecture |
|---|---|---|
| Debian, Ubuntu, and derivatives | deb | Most standard desktop computers use x64; choose arm64 for ARM devices. |
| Fedora and RHEL-compatible distributions | rpm | Choose x64 for Intel or AMD computers and arm64 for ARM devices. |
| Desktop environment | Graphical session | v2rayN is a GUI client and requires an available desktop session. |
| System proxy | Configure it according to the desktop environment | The way proxy settings are written may vary between desktop environments. |
PACKAGE DECISIONS
Download errors are usually caused by a platform, processor architecture, or package-format mismatch rather than the client model. Follow the steps below to narrow the choice to one installation file.
Use v2rayN on Windows, macOS, and Linux. On Android, choose v2rayNG for general use or v2flyNG when v2fly core behavior is required. Package formats are platform-specific, so confirm the platform before checking filenames.
x64 is common on Intel and AMD desktop computers; arm64 is common on Apple M-series chips, mainstream Android phones, and some ARM Linux devices. Check the chip in macOS System Information, the ABI in an Android device-information tool, or the architecture field on Linux.
Windows provides compressed installers on this page, macOS uses DMG, Android uses APK, and Linux uses deb or rpm by distribution. On Linux, the package format and architecture must both match; for example, Ubuntu x64 uses an amd64 deb package.
Installation alone does not provide connection settings. Import a valid subscription link, scan a configuration QR code, or enter server parameters manually. After updating the subscription, select an active server and configure the routing mode, system proxy, or VPN service.
AFTER DOWNLOAD
Follow this order on first use: install the client, import a configuration, select a server, set the routing mode, and start the connection. Establish a basic connection first, then adjust TUN, per-app proxying, and advanced DNS settings.
Run the installer for the relevant platform. On Android, allow the VPN service to be established on the first connection; on desktop systems, a permission prompt may appear when enabling TUN or writing system proxy settings. Handle permissions only when the related feature is enabled.
Copy a valid subscription URL, add it under the client’s subscription groups, and update the subscription. Individual profiles can also be imported by link, QR code, or manual parameters. If the update returns no results, first check that the address is complete.
After the subscription update finishes, select a server from the list and set it as active. Latency tests only indicate reachability and relative performance; make the final choice based on real-world access stability.
Desktop clients can enable the system proxy or TUN; Android uses the system VPN service to handle traffic. The routing mode determines which requests connect directly and which use the proxy. For an initial setup, keep the default rules supplied by the subscription.
CLIENT NOTES
For Windows, macOS, and Linux desktop systems. Key settings include subscription groups, server lists, routing, the system proxy, and TUN. Windows offers both Desktop and WPF interfaces; macOS and Linux use the cross-platform desktop interface.
Users familiar with Windows WPF can continue with the classic edition. For new installations or a consistent workflow across desktop systems, Desktop is recommended. Before migrating settings, record subscription groups, routing rules, and local port settings.
For Android, using the Xray core. Common actions include scanning a QR code, importing from the clipboard, managing subscriptions, choosing a routing mode, configuring per-app proxying, and viewing connection logs. Choosing arm64 on mainstream phones avoids unnecessary architectures in the package.
Background connection stability is also affected by system power-saving policies. If the connection drops after the screen has been locked for a while, check battery optimization, background activity permissions, and the manufacturer’s task-management settings. Per-app proxying is useful when only selected apps should use the VPN service.
Also for Android, but aligned with the v2fly core ecosystem. It is neither an upgrade nor an older version of v2rayNG, but a client choice based on a different core. Use it when the subscription service recommends v2fly configurations or existing parameters depend on its behavior.
When switching between Android clients, reimport the subscription and review local routing, DNS, Mux, and per-app proxy settings. Clients do not automatically share runtime configurations, and server entries in a subscription do not represent every local option.
DOWNLOAD FAQ
These questions cover version selection, processor architecture, package formats, and the first connection. Troubleshoot configuration parameters only after the client is installed.
Desktop is recommended because it uses the newer cross-platform interface and suits new installations or users who want a similar workflow across desktop systems. Choose WPF for the classic Windows interface, familiar menus, or an existing workflow. Both target Windows x64, but the UI framework, tray interactions, and some settings locations differ.
Open About This Mac or System Information from the system menu and check the chip or processor field. Choose Apple Silicon arm64 when it shows an Apple M-series chip, or Intel x64 when it shows an Intel processor. The architecture must match the DMG; do not rely solely on the device’s purchase year.
Most mainstream Android phones released after 2015 use arm64, so download the arm64-v8a package first. Use Universal if the architecture is unknown, the device is older, or the arm64 package will not install. Universal supports more processor architectures and is usually larger, but it does not add client features.
Android users should generally start with v2rayNG, which uses the Xray core. Choose v2flyNG if you already use v2fly configurations, need its specific core behavior, or the subscription service explicitly requires v2fly. Both support subscription import and VPN connections, but their core implementations, advanced parameters, and configuration compatibility differ.
Use deb for Debian, Ubuntu, and derivatives; use rpm for Fedora, RHEL, Rocky Linux, AlmaLinux, and similar distributions. Also choose x64 or arm64 based on the processor. The package format and processor architecture must both match; getting only one right can still cause installation failure.
The client package contains only the GUI and runtime components. After installation, import a valid subscription or server profile, select an active server, and enable the system proxy, VPN service, or TUN mode as needed. If subscription updates fail, check that the URL is complete and valid, that your device can reach it, and then review the specific error in the client log.