Choose v2rayN, v2rayNG or v2flyNG by operating system and processor architecture. This page covers desktop interface differences, mobile architecture guidance, system requirements and installation order.
Each platform panel lists only the GUI clients available for that system. Switching tabs updates the page URL, so refreshing or sharing the link opens the selected platform directly.
Windows offers Desktop and the classic WPF interface. Choose Desktop for a first installation or if you want a similar workflow across desktop systems. If you already know the legacy menus, tray controls and configuration flow, continue with WPF. You do not need both versions installed; choose one.
Current version 7.24.1
Desktop is the new cross-platform UI, with a consistent layout for settings, subscription management and routing. It suits first-time installations and users who want similar workflows across Windows, macOS and Linux. The installer is a ZIP archive containing the desktop setup program. Extract it first, then run the installer inside.
For 64-bit Windows. File: v2rayN-Desktop-Setup-x64-7.24.1.zip
Current version 7.24.1
WPF is the stable classic Windows edition, preserving the familiar menus, server list and tray controls. Choose it if you have existing v2rayN experience or rely on a classic-interface workflow. Before upgrading, quit the old tray process and note the current configuration directory.
For 64-bit Windows. File: v2rayN-Setup-x64-7.24.1.zip
| Item | Requirements and actions |
|---|---|
| Processor architecture | The current installer targets x64 devices. Confirm this under System type in Windows settings. |
| Write permissions | When installing to a protected directory, Windows may ask you to confirm administrator privileges. |
| Upgrade preparation | Quit the client and tray process before installing the new version; export important subscriptions and custom configurations in advance. |
| First launch | After launch, check the core status first, then import your subscription and choose a system proxy mode. |
macOS installers 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. The wrong architecture typically causes the app to fail to open or macOS to report incompatibility.
Current version 7.24.1
The Apple Silicon build targets Apple M-series chips and is the usual choice for newer Mac hardware. The Intel build is for Macs with Intel processors. Client features and configuration workflows are the same; the main difference is the processor architecture targeted by the executable.
Apple Silicon：v2rayN-arm64.dmg
Intel：v2rayN-64.dmg
| Item | Requirements and actions |
|---|---|
| Chip type | Choose Apple Silicon for Apple M-series chips and Intel for Intel processors. |
| Installation method | Open the DMG, move the app to Applications, and launch it from there. |
| System prompts | On first launch, follow the system prompts to approve app access and network configuration permissions. |
| Menu bar status | After launch, check the client icon in the menu bar, then import your subscription and configure the system proxy. |
v2rayNG is the preferred choice on Android. It uses the Xray core and suits common subscriptions and modern protocol configurations. Choose v2flyNG only when the provider explicitly requires the V2Fly core or an existing configuration depends on it. Each client offers arm64 and universal builds; for most phones released after 2015, start with arm64.
Current version 2.2.6
v2rayNG is a widely used V2Ray GUI client for Android, handling subscription imports, node selection, routing and VPN connections. The arm64 package contains only the components needed for mainstream 64-bit ARM devices; the universal build supports more processor types and suits devices with unknown architectures or failed arm64 installations.
arm64：v2rayNG_2.2.6_arm64-v8a.apk
Universal build: v2rayNG_2.2.6_universal.apk
Current version 1.10.31
v2flyNG uses the V2Fly core. Its interface and mobile connection flow are similar to v2rayNG, but the underlying implementation branch differs. Choose based on subscription requirements and protocol compatibility rather than running both clients. When switching clients, reimport the subscription and check routing and local port settings separately.
arm64：v2flyNG_1.10.31-fdroid_arm64-v8a.apk
Universal build: v2flyNG_1.10.31-fdroid_universal.apk
| Item | Requirements and actions |
|---|---|
| Architecture | Most mainstream phones released after 2015 use arm64; use the universal build when the architecture is unknown. |
| Installation permission | When opening an APK from a browser or file manager, follow the system prompt to allow installation from that source. |
| Connection permission | The first connection displays a VPN configuration confirmation. The client can create local forwarding only after you approve it. |
| Background operation | For long-running connections, adjust battery optimization and background activity settings according to the device's system rules. |
Linux installers must match both the distribution's package format and the processor architecture. Debian, Ubuntu and derivatives typically use deb; Fedora, Rocky Linux, AlmaLinux and other RPM-based distributions typically use rpm. Most desktop computers use x64; choose arm64 for ARM desktops and development boards according to the system architecture.
Current version 7.24.1
x64 is the standard architecture for many desktop computers and workstations. Choose deb or rpm according to your distribution, then install it with the system package installer. After installation, launch v2rayN from the application menu, check for the client in the tray or status area, and then import your subscription.
deb：v2rayn_7.24.1_amd64.deb
rpm：v2rayN-7.24.1-1.el10.x86_64.rpm
Current version 7.24.1
The arm64 packages are for devices running 64-bit ARM Linux. Confirm the architecture in system information before downloading; choose this group when it shows aarch64 or arm64. The package format still depends on the distribution: deb for Debian-based systems and rpm for RPM-based systems.
deb：v2rayn_7.24.1_arm64.deb
rpm：v2rayN-7.24.1-1.el10.aarch64.rpm
| Item | Requirements and actions |
|---|---|
| Package format | Debian- and Ubuntu-based systems typically use deb; RPM-based distributions typically use rpm. |
| Processor architecture | Standard desktop computers are usually x64; choose arm64 packages for aarch64 or arm64 systems. |
| Desktop environment | The client requires a graphical desktop and an available status area; tray behavior may vary between desktop environments. |
| Proxy takeover | After importing your configuration, choose the system proxy or TUN according to your desktop environment and confirm any required permissions. |
Installation issues are often caused by the platform, architecture, package format or a running old process. Complete these four checks before downloading to avoid repeated installations and configuration migrations.
v2rayN is for Windows, macOS and Linux desktops; Android uses v2rayNG or v2flyNG. Desktop and mobile clients have different configuration interfaces, but both can import server settings through a subscription URL. When moving between devices, use the same subscription source where possible instead of copying internal client directories.
The current Windows entry is x64. macOS requires a choice between Apple M-series and Intel. Mainstream Android phones usually use arm64; choose the universal build when uncertain. On Linux, identify both x64 versus arm64 and whether the distribution uses deb or rpm packages.
Before upgrading an existing client, save the subscription URL, custom server settings, routing rules and local port settings. Routine updates usually continue reading the original configuration, but interface changes, installation-directory changes or client migrations may use different configuration directories. Keeping an importable backup makes recovery easier.
After closing the main desktop window, the client may remain in the tray or menu bar. Before installing a new version, use the client menu to quit and prevent files from being locked. Before overwriting a mobile installation, disconnect the current connection, then reopen the app after installation and check the subscription and routing status.
Downloading is only the first step. After launch, the client still needs permission approval, subscription import, node selection and proxy mode configuration. The following workflow applies to the GUI clients listed on this page.
For Windows ZIP packages, extract the archive before running the installer. On macOS, open the DMG and move the app to Applications. On Android, open the APK and follow the system prompts. On Linux, use the package installer for your distribution to handle deb or rpm packages; if dependencies are required, follow the package manager's instructions.
Keep the installation directory stable. Frequently changing it on desktop systems can leave old shortcuts, configuration paths and auto-start entries pointing to the previous location. For in-place upgrades, keep the original installation method; when switching between Desktop and WPF, verify the configuration directory and launch entry first.
GUI clients need to read configuration, open local listening ports, and, depending on your choices, change the system proxy or establish a VPN or TUN connection. When a permission prompt appears, verify the app name before approving it for the current operation. On desktop systems, some network permissions may not appear until the first connection if you are only importing or editing settings.
The first Android connection shows a system VPN configuration confirmation. TUN use on macOS and Linux may require additional authorization. Windows may also request confirmation when installing to a protected directory or changing system settings. Test the connection only after permissions are handled, so a system denial is not mistaken for a node failure.
Open subscription management in the client, enter the subscription URL provided by the service, save it, and run an update. Afterward, check whether server entries appear in the current group. Saving a subscription URL alone does not create selectable nodes; run an update after adding it for the first time.
A subscription is a centralized configuration source. When the provider changes servers or protocol parameters, update it again to retrieve the changes. Self-hosted nodes are maintained individually. Both sources can coexist in one client, but separating them into groups makes it easier to troubleshoot a failed subscription update or incompatible configuration fields.
Select a node from the server list, then enable the system proxy or TUN. The system proxy mainly affects apps that follow system proxy settings; TUN covers more network programs but requires higher privileges. For an initial connectivity test, start with the system proxy. Enable TUN later if the required app coverage calls for it.
Routing determines which requests pass through the proxy. The common “bypass LAN and mainland China” mode preserves local-network access while splitting traffic by rules; global proxying sends more requests through the current node. After changing the routing mode, reconnect the current node to apply the new rules.
After connecting, check the client status bar to confirm that the system proxy, current node and routing mode match your expectations. Then test access with an app that actually needs network connectivity. A running client does not by itself mean system traffic is being intercepted; a disabled system proxy, revoked VPN permission or unselected node can leave apps on their original network path.
When a connection fails, troubleshoot in this order: client status, subscription content, node settings, system proxy, then local network. Change one setting at a time and reconnect after each change. This helps identify whether the issue is installation, permissions, configuration or the node itself, instead of losing the point of comparison by changing several settings at once.
The guide follows the setup sequence for adding subscriptions, choosing servers, configuring the system proxy and routing mode, and verifying the connection.
This section covers the most common download-stage choices. If the client is installed but cannot import a subscription or connect, continue to the configuration guide and Troubleshooting section.
Desktop is the new cross-platform interface for users who want a consistent desktop experience; WPF is the classic Windows interface for those who prefer familiar workflows and settings. Both use the v2rayN configuration system, so you do not need to install both. Choose Desktop for a first installation; if you already have WPF settings and an established workflow, continue with the classic edition.
Open About This Mac from the system menu and check the chip or processor field. Choose Apple Silicon for an Apple M-series chip and the Intel installer for an Intel processor. Client features are the same; the installer difference only reflects processor architecture. If you download the wrong architecture, macOS will usually report incompatibility when you open it.
Most mainstream Android phones released after 2015 use 64-bit ARM processors, so arm64 is usually the best choice. Use the universal build if the architecture is unknown, installation reports incompatibility, or broader processor coverage is needed. The universal build includes more architecture components, so it is typically larger, but the configuration and usage workflow are the same.
Start with v2rayNG, which uses the Xray core. Choose v2flyNG only when the subscription provider explicitly requires the V2Fly core or an existing configuration depends on it. The two clients differ in core branches, some protocol features and configuration compatibility, so choose according to the subscription requirements. Running both at once or sharing internal configuration directories is not recommended.
Routine upgrades normally preserve your settings. Before upgrading, export important configurations or save subscription URLs, quit the running client, and then install the new version. When switching interface editions, back up your settings and verify the configuration directory used by the new version. Android in-place upgrades usually preserve app data, but record the subscription source so you can reimport it if needed.