V2Ray Client Download Choose an installer by system and architecture
Use v2rayN on desktop systems, v2rayNG on Android by default, and v2flyNG when the v2fly core is needed. Confirm the operating system, processor architecture, and package format before opening the download section for your platform.
Free forever
Open source
Four platforms
Chinese configuration guides
platform selector
Platform Installers and System Requirements
Switching platforms updates the URL anchor, so copying the current page address opens the selected system directly. Before installing, read the version differences and architecture notes on the relevant card.
download > windows > v2rayN
Windows：v2rayN
Windows always offers the Desktop and classic WPF editions. Both installers use the same product configuration system; the main differences are the UI framework, runtime environment, and interaction layout. New installations should generally start with Desktop. Continue using WPF if you already know its classic interface or have workflows built around it.
Recommended
v2rayN
7.24.1
v2rayN is a graphical desktop client for subscription management, server configuration, system proxy settings, routing rules, and TUN settings. After downloading, extract the package and run its installer. On first launch, follow the getting-started guide to import a subscription and select an active configuration.
Preferred install
Desktop edition
A modern cross-platform UI with a layout more consistent across desktop systems, suited to newer Windows environments and first-time installations.
Uses the traditional Windows interface framework, with menus and settings following the classic layout. It suits experienced users and anyone who prefers traditional desktop interactions.
Confirm a 64-bit operating system under System type in Windows Settings
Interface edition
Choose Desktop for a first installation
Choose the classic edition if you already use the WPF workflow
Configuration migration
Record your subscription URLs and custom rules first
Exit the running client before upgrading or switching editions
download > macos > v2rayN
macOS：v2rayN
macOS installers come in Apple Silicon and Intel variants. The architecture must match the device chip, or the installer may not launch. Open About This Mac from the system menu, check the Chip or Processor field, and then choose the appropriate download.
Desktop client
v2rayN
7.24.1
The macOS version of v2rayN provides subscription updates, configuration selection, routing rules, and system proxy management. The Apple Silicon and Intel installers have the same features; choose between them solely according to the device chip architecture.
M-series chip
Apple Silicon
For devices whose system information shows an Apple M-series chip. This arm64 build should be the preferred choice for recent Mac devices.
For devices that explicitly show an Intel processor in About This Mac. Do not rely only on the device's appearance or purchase year; use the system information.
Open the DMG and move the app to Applications as instructed
Intel processor
Intel x64
Open the DMG, complete the app setup, then launch it from Applications
First launch
Confirm the system security prompt
After launch, import a subscription, select a configuration, and set the proxy scope
download > android > v2rayNG / v2flyNG
Android: v2rayNG and v2flyNG
On Android, v2rayNG is listed first, followed by v2flyNG. v2rayNG uses the Xray core and suits most common subscription and graphical configuration workflows. v2flyNG uses the v2fly core and is an alternative for users who need that core ecosystem. Both clients offer arm64 and universal installers.
Recommended
v2rayNG
2.2.6
v2rayNG is a popular graphical client for Android and uses the Xray core. It can create configurations from a subscription URL, clipboard content, or manually entered parameters, and provides settings for routing, per-app proxying, and connection logs.
Best for most phones
arm64 edition
For most mainstream Android phones and tablets released after 2015, using the arm64-v8a architecture.
Use this when the device architecture is unknown or the arm64 installer reports incompatibility. The universal build supports more processor types and is usually larger.
v2flyNG is an Android graphical client built on the v2fly core. Use it as an alternative when matching v2fly core behavior, following an existing v2fly-based configuration workflow, or comparing compatibility between the two core families.
Mainstream architecture
arm64 edition
For most newer Android devices. Choose this version directly when the processor is identified as arm64-v8a.
The Linux version of v2rayN is split by package format and processor architecture. Choose deb for Debian, Ubuntu, and derivatives; choose rpm for Fedora, Rocky Linux, AlmaLinux, and other distributions using RPM package management. Standard desktop computers usually use x64, while ARM devices use arm64.
Desktop client
v2rayN
7.24.1
The Linux version of v2rayN provides a graphical desktop interface for subscription management, configuration switching, routing rules, and system proxy controls. Before downloading, verify both the distribution's package system and the CPU architecture; both must match for installation to succeed.
Debian / Ubuntu family
x64 deb
For common x86_64 desktop computers and distributions that use the deb package system.
Identify the platform first, then the processor architecture, and finally the client or interface edition within that platform. Following this order keeps product differences, package formats, and CPU architectures from being confused.
01
Confirm the operating system
Use v2rayN on Windows and macOS; choose between v2rayNG and v2flyNG on Android; on Linux, also confirm the distribution's package system.
02
Confirm the processor architecture
x64 is common on desktop computers; Apple M-series chips and some Linux devices use arm64; most newer mainstream Android devices also use arm64.
03
Confirm the edition or branch
Windows requires a choice between Desktop and WPF, Android requires a core family, and Linux additionally requires a choice between deb and rpm.
04
Import configuration after installation
Installation is only the preparation stage. Next, import a subscription, update the configuration list, select an active server, and set the proxy scope.
after installation
After installation: configuration order
The client, subscription, active configuration, and proxy mode are four separate layers. Handling them in order makes it easier to determine whether a problem lies in installation, configuration parsing, or the system proxy.
01
First launch and permission checks
Run the client and complete any permissions required by the system. Desktop systems may require permission to launch the app; Android requires confirmation of the local connection service on first connection. At this stage, focus on the conditions needed to run the client rather than changing advanced routing parameters.
02
Import a subscription or single configuration
A subscription URL is useful for centrally maintaining multiple server configurations, while a single shared entry is convenient for temporary imports. After importing, run a subscription update and check that the configuration list contains names, addresses, ports, and protocol fields.
03
Select an active configuration
Select an available configuration in the client so it becomes the current active item. Importing a subscription without selecting an active configuration usually does not establish the target connection. If a configuration reports an error, check the protocol and transport parameters first.
04
Set the proxy scope
Use the system proxy for apps controlled by the operating system's proxy settings. Routing mode determines the outbound path for different destinations, while TUN mode is suited to taking over traffic from more applications. For a first setup, establish a basic connection before enabling advanced modes.
download faq
Download and installation FAQ
These questions cover edition branches, processor architectures, package formats, and initial configuration. For the complete workflow, continue to the getting-started guide or the platform tutorial.
Should Windows users choose the v2rayN Desktop or WPF edition?
The Desktop edition uses a modern cross-platform interface for newer Windows environments. The WPF edition retains the classic Windows interface for users who prefer traditional layouts or want to preserve established configuration habits. Both are v2rayN editions, and Desktop is a sensible choice for a first installation. Before switching editions, record subscription URLs, custom routing rules, and local listening ports so personalized settings are not lost.
How do I know whether to download the Apple Silicon or Intel version for macOS?
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. The two client versions offer the same features; only the compiled architecture differs. The purchase year is merely a reference—use the chip name shown in system information.
Should Android users download arm64 or the universal build?
Most mainstream Android phones released after 2015 use arm64, so choose arm64 first. Use the universal build when the architecture is unknown, installation reports incompatibility, or broader processor coverage is needed. It usually includes more architecture components and may be larger, but the client setup is the same regardless of installer architecture.
How should I choose between v2rayNG and v2flyNG?
Android users generally start with v2rayNG, which uses the Xray core and offers a more complete graphical configuration experience. Choose v2flyNG when the v2fly core ecosystem is required. Both clients manage subscriptions and connection configurations, but supported protocols, transports, and routing behavior depend on the core. Confirm that the service configuration uses a protocol supported by the client before importing a subscription.
Should Linux users download a deb or rpm package?
Use deb for Debian, Ubuntu, and derivatives; use rpm for Fedora, Rocky Linux, AlmaLinux, and other RPM-based distributions. Also choose x64 or arm64 based on the processor. If the system returns x86_64, choose x64; if it returns aarch64, choose arm64.
Why can't I connect immediately after installing the client?
The installer only provides graphical management and connection capabilities. After the first launch, import a working subscription or enter server parameters manually, select an active configuration, and enable the system proxy, routing mode, or TUN mode as needed. If the list is empty after importing a subscription, update it manually first and check whether the current client can parse its contents.
