Choose a package by operating system, processor architecture, and interface edition. Use v2rayN on desktop systems, and choose between v2rayNG and v2flyNG on Android based on the core family.
Platform tags are synced to the page URL. After switching, read the architecture notes on the card before choosing the primary or compatibility package.
Windows client
v2rayN: Desktop and classic WPF editions
The two packages use different interface technologies. The Desktop edition uses a modern cross-platform UI with a structure more consistent across desktop systems. The classic WPF edition retains traditional Windows menus, server lists, and settings windows for users familiar with the established workflow.
v2rayN
Windows desktop graphical client
Recommended
Current version7.24.1
Preferred choice
Desktop edition
x64
A modern cross-platform interface for first-time installations, users who prefer a contemporary layout, and anyone who wants a similar workflow across desktop systems.
The traditional Windows interface and menu layout, retaining the familiar organization of server lists, subscription groups, and settings windows for existing users.
Before installation, confirm the operating system architecture and runtime permissions. The package uses the x64 architecture and supports common 64-bit Windows desktop devices. On managed enterprise devices, make sure the current account can install applications and modify system proxy settings.
Check
Requirements and recommendations
Processor architecture
x64
Installation permissions
Can install desktop applications and write to the user configuration directory
System proxy
Enable “Automatically configure the system proxy” in the client when needed
Existing older edition
Record subscription groups and custom routing settings before switching editions
macOS client
v2rayN: Choose a DMG by chip
macOS packages are available for Apple Silicon and Intel. Client features are the same; the difference is the processor targeted by the executable. Choosing the correct architecture reduces translation-layer dependencies and keeps the interface and background core on the intended execution path.
v2rayN
macOS desktop graphical client
Desktop edition
Current version7.24.1
M-series chip
Apple Silicon edition
arm64
For devices whose About This Mac page lists an Apple M-series chip, including desktops and laptops with Apple Silicon processors.
After opening the DMG, move the application to the system Applications folder and launch it from the app list. The first time you enable the system proxy, macOS may ask you to approve network settings access. On organization-managed devices, proxy settings, background operation, and login items may be controlled by device policies.
Check
Requirements and recommendations
Processor architecture
Apple Silicon uses arm64; Intel uses x64
Installation format
DMG disk image
System permissions
Allow the application to run and modify network proxy settings when needed
Background operation
For continuous proxy use, confirm that the client is still running and the system proxy status is correct
Android client
v2rayNG recommended; v2flyNG as an alternative core family
The Android platform offers two graphical clients. v2rayNG uses the Xray core, providing a more direct fit for Xray protocols, routing settings, and ecosystem configurations. v2flyNG uses the V2Fly core and suits scenarios that require its behavior or an existing V2Fly configuration setup.
v2rayNG
Android client · Xray core
Recommended
Current version2.2.6
For Android users who need subscription groups, routing settings, VLESS, VMess, Trojan, and configuration capabilities from the Xray ecosystem. After installation, import an existing configuration from the clipboard, a QR code, or a subscription URL.
Mainstream devices
arm64 edition
arm64-v8a
For 64-bit ARM processors. Most mainstream Android phones released after 2015 can start with this edition.
An Android graphical client for the V2Fly core family. Choose v2flyNG when existing configurations were generated for V2Fly, require its core behavior, or you want to compare configuration compatibility between the two core families.
Mainstream devices
arm64 edition
arm64-v8a
For common 64-bit ARM phones and tablets, with package contents focused on the arm64 processor architecture.
For devices with unknown architecture information or when broader device compatibility is needed. Client functionality remains the same as in the arm64 edition.
Before installation, check the processor architecture in the device information or hardware information screen. After the APK is installed, Android displays a network connection permission dialog the first time a connection is established. This permission creates a local VPN interface for the client to manage the network connections it needs to handle.
Check
Requirements and recommendations
Preferred architecture
Mainstream phones released after 2015 usually use arm64-v8a
Architecture unknown
Choose the universal edition
Connection permission
Approve the system network connection permission when establishing a connection for the first time
Background operation
For long-running connections, check whether system battery policies restrict the client’s background activity
Linux client
v2rayN: Choose by distribution package format and processor architecture
Linux packages are available in deb and rpm formats, each with x64 and arm64 builds. First identify the package system used by the distribution, then determine the processor type from system architecture information or device documentation. Install only after both conditions match.
v2rayN
Linux desktop graphical client
Desktop edition
Current version7.24.1
Debian-based
deb package
Ubuntu, Debian, and desktop distributions that use the deb package system.
The graphical client requires an available desktop session. If the application starts but the system proxy does not affect the browser or other programs, check the desktop environment’s proxy settings, whether the application follows the system proxy, and whether the client’s system proxy mode is enabled.
Distribution or device
Package selection
Ubuntu / Debian x64
deb x64
Ubuntu / Debian arm64
deb arm64
Fedora / RHEL x64
rpm x64
Fedora / RHEL arm64
rpm arm64
Desktop environment
Requires an available graphical desktop session and access to system proxy settings
Pre-installation checks
Match the platform, architecture, and client
The operating system, processor architecture, and client model in a package name correspond to different selection criteria. Confirm them in order to reduce reinstalling after downloading the wrong version.
01
Start with the operating system
Windows and macOS use their respective desktop installation formats; Linux also distinguishes deb from rpm; Android uses APK. Packages for different systems cannot be installed interchangeably, and similar device names do not replace an operating system check.
Use v2rayN for desktop systems. On Android, choose v2rayNG or v2flyNG based on the core family. The client model determines the interface, core, and configuration compatibility range, while the operating system determines the package format.
02
Then check the processor architecture
x64 is common on Intel and AMD desktop processors, while arm64 is common on Apple Silicon, some Linux ARM devices, and mainstream Android phones. The architecture label describes the processor instruction set targeted by the program, not the system version.
On macOS, check the chip type directly in About This Mac. On Android, choose the universal edition when the architecture is unknown. On Linux, use distribution system information to identify x86_64 or aarch64, then choose the corresponding x64 or arm64 package.
03
Finally, check the interface and core
The main difference between the Desktop and WPF editions of v2rayN on Windows is the interface technology and workflow. On Android, v2rayNG and v2flyNG correspond to different core families. When an existing configuration specifies a core requirement, follow the provider’s notation.
Installing the client does not automatically create a server configuration. After the first launch, import an existing subscription URL or add a configuration manually, update the subscription group, select an available configuration, and enable the system proxy or the appropriate connection mode.
Installation and updates
What to do after downloading
Installation, configuration import, and proxy activation are three separate stages. Checking them in order makes problems easier to locate than repeatedly switching clients or packages.
Step 1: Install the client
After downloading, install the application using the standard method for the operating system. The Windows package sets up the desktop program and user configuration directory; on macOS, open the DMG and move the application to the system Applications folder; on Android, install the application from the APK; on Linux, install deb or rpm using the distribution’s package management method. At this stage, confirm only that the application launches normally; there is no need to adjust every advanced setting immediately.
If the device is managed by an organization, application installation, network proxy changes, background operation, and login items may be restricted by system policies. First confirm the current account’s permissions. Re-downloading the same package usually cannot change the policy state; focus instead on system prompts, account permissions, and the desktop environment’s proxy settings.
Step 2: Import an existing subscription or server configuration
The client does not provide server configurations. After launching it, use an existing subscription URL, share link, QR code, or manual parameters to create a configuration. In v2rayN, create a subscription group, enter the subscription URL, and run an update; Android clients can import through a subscription group, the clipboard, or a QR code. After a successful import, the entry should appear in the configuration list.
Subscription groups and server configurations are separate layers. A subscription group stores the URL, update interval, and group settings; the server list stores the individual configurations obtained after updating. If you enter a subscription URL without updating it, the list may remain empty. Updating the wrong group can also make it appear that the import failed.
Step 3: Select a configuration and enable the proxy
Once configurations appear, select the entry you want to use and enable the client connection. On desktop systems, you usually also need to enable the system proxy so applications that follow the operating system proxy settings can connect through the client port. Android clients request permission to create a local VPN interface for handling the device traffic that requires processing.
The system proxy, routing rules, and client core have different responsibilities. The system proxy directs applications to the local proxy entry point; routing rules determine which outbound path each destination uses; the client core handles protocol, transport, and security-layer configuration. Check connection problems at these three levels separately instead of changing everything at once.
Step 4: Preserve the configuration structure when updating
Before updating the client, record the current subscription groups, system proxy mode, custom routes, and core type. Routine updates usually preserve user configuration, but switching from the classic interface to the modern Desktop interface, crossing many versions, or changing client models may alter the organization of configuration directories and settings.
Switching between v2rayNG and v2flyNG on Android changes the client and core family, so review subscription formats and protocol support again. When changing a Linux distribution or processor device, select the package format and architecture again rather than reusing the installation file from the old device.
Common download questions
Package and architecture selection
These questions focus on client models, desktop interfaces, processor architectures, and configuration after installation.
Should Windows users download the v2rayN Desktop or classic WPF edition?
The Desktop edition uses a modern cross-platform interface for users who prefer a consistent layout. The classic WPF edition retains the traditional Windows menus and settings flow for users familiar with the older interface. Both are v2rayN; for a first installation, the Desktop edition is the recommended choice.
If you have been using the WPF edition for a long time with many subscription groups, custom routes, and shortcuts, record the current settings before deciding whether to switch interfaces. The interface choice does not replace protocol and core compatibility checks.
How do I choose between the Apple Silicon and Intel package on macOS?
Open About This Mac from the system menu and check the chip or processor field. Choose Apple Silicon when it shows an Apple M-series chip, or Intel when it shows an Intel processor. The package architecture must match the device processor.
Do not identify the chip solely by purchase year or appearance. Devices with similar designs may use different processors; the chip field in system information is the more direct guide.
What is the difference between the arm64 and universal Android editions?
The arm64 edition targets 64-bit ARM processors and focuses on the architecture used by most current devices. Most mainstream Android phones released after 2015 can start with arm64; use the universal edition if the architecture is unknown or installation reports incompatibility.
Both packages provide the same core client functions; the difference is the range of processor architectures they support. Choosing the universal edition does not change subscription formats, routing rules, or the client core family.
Should I choose deb or rpm on Linux?
Ubuntu, Debian, and their derivatives generally use deb, while Fedora, RHEL-based systems, and distributions using the RPM package system use rpm. You must also choose x64 or arm64 based on the processor.
Package format and processor architecture are independent conditions. For example, an Ubuntu ARM device needs deb arm64, while a standard 64-bit Intel or AMD desktop running Fedora needs rpm x64. Matching only one condition can still cause installation to fail.
How should I choose between v2rayNG and v2flyNG?
Both are graphical Android clients. v2rayNG uses the Xray core and suits users who need protocols and configuration capabilities from the Xray ecosystem. v2flyNG uses the V2Fly core and is an alternative for V2Fly-based configurations. Without a specific compatibility requirement, start with v2rayNG.
When an existing subscription or manual configuration specifies a core requirement, follow it. Some basic configurations may retain a similar structure across the two core families, but protocol features, transport options, and extension fields still need separate verification.
What if there is no server configuration after installation?
The client package contains only the application. After installation, import an existing subscription URL or add a server configuration manually, then update the subscription group, select a configuration, and enable the system proxy.
If the list remains empty after importing a subscription, first confirm that the subscription group was updated, the URL is complete, and you are viewing the correct group. Then open the usage guide and check import, update, selection, and connection in order.