Client installation packages and platform selection

V2Ray Client Download
v2rayN, v2rayNG, v2flyNG

Use v2rayN on desktop systems, choose v2rayNG on Android, or use v2flyNG when you need the V2Fly kernel line. Confirm your operating system and processor architecture before downloading the matching package.

Free forever Open source Chinese documentation Four platform options
Download by platform

Choose your system and package

The selected platform is preserved in the page URL, so refreshing keeps the current platform open. Version text and download URLs are updated from same-origin version data; if the network is unavailable, the current version entry on the page is retained.

Windows

v2rayN desktop client

Windows offers Desktop and classic WPF interfaces. For a first installation, Desktop is recommended; choose classic WPF if you already know its workflow and want to keep the original menus and navigation.

v2rayN

Recommended 7.24.1

A subscription and node management client for Windows desktops, with system proxy, routing, TUN mode, log viewing, and automatic subscription updates. The two entries use different interface technologies but share the same core workflow.

Desktop edition A new cross-platform UI for first-time installations and users who prefer the newer interface.
Download Desktop
Classic WPF edition The classic Windows interface for users familiar with the older menu structure and workflow.
Download WPF

Windows system requirements

Check Requirement Selection guidance
Processor architecture x64 Both Windows installers on this page are x64 versions.
Installation permissions Allow the installer to run Managed devices may require administrator approval.
Network settings System proxy changes permitted Enabling the system proxy or TUN mode modifies local network settings.
Pre- and post-installation checks

From package selection to the first connection

The client only reads configuration, establishes connections, and handles local proxy traffic. Installation alone does not provide usable nodes; you still need to import a valid subscription, update the group, choose a node, and set a proxy mode.

1

Confirm the system and architecture

First identify the device platform, then check the processor architecture. The Windows page provides x64 packages; macOS requires Apple Silicon or Intel; Android requires arm64 or universal; Linux also requires choosing deb or rpm according to the distribution.

An architecture mismatch commonly causes the installer not to open, an incompatibility warning, or failure to launch after installation. Recheck the architecture first instead of changing subscription or routing settings immediately.

2

Complete client installation

Complete the desktop installation through the system installer; on Android, open the APK and confirm installation as prompted. Computers managed by organizational policies may restrict installation or network-setting changes and require administrator approval.

After first launch, familiarize yourself with subscription groups, the node list, system proxy, routing modes, and logs. Avoid running multiple similar clients at once, as they may repeatedly modify the system proxy or compete for local connections.

3

Add and update a subscription

Copy the complete URL from your subscription provider and add it under the client's subscription group or subscription settings. Save and update, then wait for the node list to appear. If the update fails, check that the URL is complete and contains no extra spaces, then review network errors or format warnings in the logs.

A subscription URL is a configuration entry point. Store it only on your own devices and in a trusted password manager. Sharing it publicly may let others use your configuration and make future URL replacement and reconfiguration more costly.

4

Choose a node and proxy mode

After the subscription updates, choose a node and set the system proxy for your needs. For regular web browsing, start with automatic configuration or a routing mode that bypasses the local network and mainland China; to handle more application traffic, read the TUN mode guidance and confirm the required permissions.

After changing the routing mode, reopen the test page or create a new connection because existing connections may continue using the old path. Check the client logs, target application behavior, and system proxy status rather than relying on a single status label in the interface.

Package selection

The difference between versions, architectures, and package formats

Download and installation failures often come from confusing three concepts: the client model determines the feature path, the processor architecture determines whether the program can run, and the package format determines how the system installs it.

Client

v2rayN、v2rayNG、v2flyNG

v2rayN targets Windows, macOS, and Linux desktops; v2rayNG targets Android and uses the Xray kernel; v2flyNG targets Android and uses the V2Fly kernel. Choose the client by platform first, then handle architecture.

Architecture

x64, arm64, and Apple Silicon

x64 is common on Intel and AMD desktop processors, while arm64 is common on mobile devices and some ARM desktops. Apple Silicon is Apple's chip line, so use the specifically labeled package on this page.

Format

ZIP, DMG, APK, deb, and rpm

Different systems use different installation media. The format itself does not indicate greater functionality or performance; it only identifies the installation method. Linux users must also choose deb or rpm according to the distribution's package system.

Version maintenance

Keep your configuration approach when updating the client

Before updating, note the current subscription groups, routing mode, system proxy method, and automatic update interval. Updates normally retain existing settings, but menus and defaults may change across several versions. After updating, verify subscription refreshes, node selection, system proxy status, and any configuration parsing errors in the logs.

If the new version behaves unexpectedly after launch, close other proxy clients and restart the current program, then check configuration-directory permissions and subscription format. Do not change the client, node, routing mode, and subscription URL in the same troubleshooting pass, or it will be difficult to identify the cause.

Common download questions

Package selection and first-time setup

These questions cover desktop edition differences, processor architectures, Linux package formats, and subscription import. Expand a question to see how to determine the right option.

Should you download v2rayN Desktop or the WPF version on Windows?

For a first installation, Desktop is preferred because it uses a newer cross-platform interface. If you are familiar with the classic Windows interface and want to keep the same workflow, choose WPF. Both support subscription management, node selection, system proxy settings, and routing configuration, and you do not need to install both.

How do you tell whether to download the Apple Silicon or Intel version for macOS?

Open System Information and check the Chip or Processor field. Choose Apple Silicon for an Apple M-series chip and Intel when an Intel processor is shown. The package architecture must match the device processor; relying only on the model or appearance can lead to the wrong choice.

Should you choose arm64 or the universal version on Android?

Most mainstream Android phones released after 2015 should use arm64 first. Choose the universal version if the architecture is unknown, the device is older, or arm64 installation fails. The universal version supports more devices but is usually larger, while the feature and setup flow remain the same.

Should you download deb or rpm on Linux?

Use deb for Debian, Ubuntu, and derivatives; use rpm for Fedora, RHEL-based systems, and RPM-based distributions. Also check whether the processor is x64 or arm64. Both the package format and architecture must match.

How do you import a subscription after installation?

Copy the complete subscription URL from your subscription provider, open the client's subscription group or subscription settings, add the URL, and update it. Once nodes appear, choose a suitable system proxy mode and verify the connection by opening a real webpage. If updating fails, check the URL and client logs first.

Download v2rayN