CLIENT PACKAGES · 4 PLATFORMS

V2Ray Client Download

Choose an installer based on the operating system and processor architecture. Use v2rayN on desktop systems; on Android, choose between v2rayNG and v2flyNG.

Graphical clients Official latest releases Architecture guide System requirements

PLATFORM SELECTOR

Choose an operating system

Platform choices are synced to the page URL. After opening a panel, check the system version and processor architecture before choosing the primary or compatibility installer.

WINDOWS

v2rayN Windows installer

Windows offers Desktop and classic WPF interfaces. Desktop is the newer cross-platform UI, suited to first-time installations and users who want a consistent desktop experience; WPF is the classic, stable option for users who prefer the established workflow.

Recommended

v2rayN

7.24.1

v2rayN is the primary Windows desktop choice for managing subscriptions, nodes, the system proxy, and routing rules. Both interfaces use the same client name, but the installer filename alone—especially the word Setup—does not identify the interface. Use the labels below.

  • Desktop: Newer cross-platform UI with a structure similar to the macOS and Linux versions.
  • WPF: Classic Windows interface for users familiar with the older menu layout and workflow.
Primary choice · x64 Download Desktop v2rayN-Desktop-Setup-x64-7.24.1.zip
Classic interface · x64 Download WPF v2rayN-Setup-x64-7.24.1.zip

Windows requirements and selection guide

Item Requirement or recommendation Selection guidance
Processor architecture 64-bit x86 processor Both Windows packages on this page are x64 and support today’s mainstream Intel and AMD desktop devices.
System permissions Administrator confirmation may be required during installation After installation, the current user account is usually enough for everyday launches; confirm the system prompt when changing the system proxy.
Upgrade preparation Quit the older client before installing Export subscription groups, routing rules, and manual settings before installing the new version.

PACKAGE DECISIONS

Package selection order

Client name, operating system, processor architecture, and package format are four separate layers. Checking them in order prevents downloading a file the system can store but cannot run.

01

Identify the operating system first

Start with v2rayN on desktop systems; on Android, choose between v2rayNG and v2flyNG. v2rayN files for Windows, macOS, and Linux are not interchangeable. Even when the client name and version match, use the installer for the current platform.

02

Confirm the processor architecture next

x64 is common on Intel and AMD desktop computers; arm64 is common on Apple M-series computers, mainstream Android phones, and some ARM Linux devices. A mismatch usually causes installation failure or prevents startup. On Android, use Universal when uncertain; on desktop systems, check the device information first.

03

Choose the interface or package format last

Windows Desktop and WPF are interface choices; Linux deb and rpm are distribution package choices. Choose the former according to your workflow, and the latter to match the system package manager. For macOS, select the DMG by chip type without considering a package format.

BEFORE INSTALLATION

Before installation and updates

For a first installation, verify the system, architecture, and permissions. An in-place update also requires the running client and existing configuration to be handled. These steps do not change subscription content, but they reduce the chance of reorganizing settings after an upgrade.

View setup guide View troubleshooting

  1. Record the current client state

    Note the current client name, version, subscription groups, system proxy mode, and listening port. If the configuration includes manual nodes or custom routing rules, use the client’s export feature to save a copy first.

  2. Quit the old process

    Close the main window, then check the tray or menu bar to ensure the client has exited. During Windows and Linux updates, running files may block replacement; on Android, disconnect the current connection before updating.

  3. Check the filename

    The filename directly indicates the platform, architecture, and version. For arm64, arm64-v8a, or aarch64, confirm that the device is ARM64; for x64, amd64, or x86_64, confirm a 64-bit Intel or AMD architecture.

  4. Import subscriptions after installation

    On first launch, complete the system network permission prompt before importing a subscription link or restoring configuration. Then update subscriptions, select a server, enable the required proxy mode, and test actual access to confirm that the system proxy works.

VERSION NOTES

Version display and download behavior

Page versions update dynamically

Version text, filenames, and download URLs in client cards are read from a shared version manifest. If the manifest is temporarily unavailable, the page keeps the current static installer URL, so buttons still point to complete file paths.

An update does not mean rebuilding configuration

A normal in-place update of the same client usually preserves its configuration. When switching interface lines, changing clients, or moving to another device, export the configuration first and re-import it using the new client’s supported method.

Subscription compatibility depends on the content

A client’s ability to import a subscription URL does not mean it supports every protocol, transport, or field in that subscription. If some nodes are missing, update the subscription first, then check the client version and configuration type.

DOWNLOAD FAQ

Download questions

These questions cover installer selection, client differences, and in-place updates. For subscription imports and connection settings, continue to the setup guide.

Should Windows users download v2rayN Desktop or the WPF edition?

Choose Desktop for the newer cross-platform interface; choose WPF if you prefer the classic Windows interface or want to preserve an established workflow. Both are v2rayN and serve the same core configuration and subscription needs, but their layouts and some control locations differ. Desktop is usually the best starting point for a first installation.

How do I choose between the Apple Silicon and Intel macOS installers?

Open “About This Mac” from the system menu. Choose Apple Silicon arm64 when the Chip field shows an Apple M-series chip; choose the x64 installer when the Processor field shows Intel. Do not infer this from the computer’s appearance or purchase year—System Information is more reliable.

Should Android users download arm64 or the universal build?

Most mainstream Android phones released after 2015 use arm64, so the arm64 installer is usually the first choice. Use Universal when the device architecture cannot be confirmed, a device-information tool gives no clear result, or the arm64 package will not install. Universal covers more devices and is usually larger.

How should I choose between v2rayNG and v2flyNG?

Android users should generally start with v2rayNG, which uses the Xray core. Choose v2flyNG when you need the v2fly core, an existing configuration is built specifically for it, or you want to manage two configurations separately. When switching clients, recheck subscription groups, routing rules, and system VPN permissions.

Should Linux users download deb or rpm?

Use deb for Debian, Ubuntu, and derivatives; use rpm for Fedora, RHEL, and derivatives. Then check the architecture: choose x64 for x86_64, and arm64 for aarch64 or arm64. The package format and architecture must both match.

What should I preserve before updating the client?

Export your subscription groups, routing rules, and manually configured nodes first, and note the current system proxy mode and listening port. Then quit the running client before installing the new version. After updating, check the subscription list and routing settings before resuming normal connections.