CLIENT PACKAGES · 2026

V2Ray client downloads and version selection

Choose your operating system first, then download the package matching your processor architecture. Use v2rayN on desktop platforms and v2rayNG on Android by default; choose v2flyNG when you need the V2Fly core implementation.

GUI client Free forever Open source Subscriptions and routing

PLATFORM SELECTOR

Choose a package for your platform

Version labels are updated from the same release manifest. If dynamic information is temporarily unavailable, the download buttons still point to the current package paths.

WINDOWS · X64

Use v2rayN on Windows

For a first installation, choose Desktop; select the classic WPF version if you prefer the traditional Windows interface or need to preserve an existing configuration workflow.

v2rayN

Windows · x64 · 7.24.1
Recommended

v2rayN is a desktop GUI client for importing subscriptions, switching nodes, configuring the system proxy, editing routing rules, and enabling TUN. The two Windows packages use different UI technologies but support the same configuration tasks.

Desktop Modern cross-platform UI; recommended for first-time installations
Download Desktop
Classic WPF Familiar, stable interface for existing workflows
Download classic WPF

Windows requirements and installation guide

Check Recommendation Why
Processor architecture x64 The Windows packages on this page target common 64-bit desktop devices.
Interface choice Start with Desktop Desktop uses a modern cross-platform UI and is the default choice for a new installation.
Existing workflow Choose WPF if preferred The classic version’s window layout and navigation are closer to traditional v2rayN.
First launch Allow access to the user configuration directory Subscriptions, routes, and interface preferences must be saved in the current user environment.

BEFORE INSTALL

Make three checks before downloading

The client name, platform, and processor architecture are three separate decisions. Check them in order to avoid confusing the wrong app with the wrong package.

01

Choose the client first

For desktop environments on Windows, macOS, and Linux, start with v2rayN. On Android, choose v2rayNG by default; use v2flyNG only when the configuration source explicitly requires V2Fly core behavior or you need a compatibility comparison. A client is not a node and does not create a usable connection automatically after installation.

02

Then confirm the processor architecture

The architecture determines whether the package can run correctly on the device. This page provides x64 packages for Windows; macOS is split between Apple Silicon and Intel; Android uses arm64 first, with the universal version when uncertain; Linux requires an explicit choice between x64 and arm64. x64, amd64, arm64, and aarch64 are architecture labels, not release rankings.

03

Finally match the package format

DMG is for macOS, APK is for Android, and deb and rpm target different Linux package systems. The two Windows ZIP archives provide separate Desktop and WPF installation paths. Once the format matches, complete installation, import a subscription, and configure the proxy through the client interface.

NEXT STEPS

Configuration order after installation

Get the smallest working configuration running first, then handle routing, DNS, and TUN. This makes it easier to identify which layer is failing.

IMPORT

Import a subscription or node

Desktop clients usually add links from the subscription settings. On Android, use the clipboard, QR code, or a subscription group. After adding the link, run an update; the import is complete only when the node list appears. If the list is empty, check the link, group status, and update errors.

SELECT

Test with one configuration

For the first connection, select one node and avoid changing many routing and DNS settings at once. Confirm that the client can connect, then check whether the system proxy works. If every node fails, first investigate the subscription, system time, and local network instead of repeatedly replacing the installer.

PROXY

Start with the system proxy

The system proxy works well for browsers and desktop apps that follow system network settings. It is simple to configure and easy to observe. To handle more application traffic, read the TUN configuration guide. Android clients create a local network interface through the system VPN service, so confirm the authorization prompt at startup.

ROUTING

Configure routing after the connection is stable

Routing rules determine which domains or addresses connect directly, use the proxy, or are blocked. Rule order affects the final match, so avoid importing multiple unknown rule sets before the first connection. Keep the client defaults initially, verify the basic connection, and adjust rules one at a time for your actual needs.

Read the Getting Started guide View the full documentation

DOWNLOAD FAQ

Common download and installation questions

This section covers client choice, package formats, and the first step after installation. For detailed troubleshooting of connections, subscriptions, and routing, continue to the FAQ and full documentation.

Should Windows users download the v2rayN Desktop or classic WPF version?

For a first installation, start with Desktop, which uses a modern cross-platform interface. Choose the classic WPF version if you prefer the traditional Windows interface or need to keep an established workflow. Both manage nodes, subscriptions, the system proxy, and routing settings; there is no need to run both for testing.

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 Apple M-series devices and Intel for Intel devices. The architecture must match; the purchase date is only a reference and should not replace system information.

Should Android users download arm64 or the universal version?

Most mainstream Android phones released after 2015 should use arm64 first. If installation reports an incompatibility or the architecture is unknown, use the universal version. It supports more devices and is usually larger; both packages provide the same client functionality.

How should I choose between v2rayNG and v2flyNG?

For Android, start with v2rayNG. It uses the Xray core and works with most common subscriptions. Choose v2flyNG only when you need the V2Fly core family or the configuration explicitly requires it. Manage the two clients separately and stop the current connection before switching.

Should Linux users download deb or rpm?

Choose deb for Debian, Ubuntu, and derivatives; choose rpm for Fedora, Rocky Linux, AlmaLinux, and other rpm-based systems. Then distinguish between x64 and arm64. x86_64 or amd64 usually means x64; aarch64 or arm64 means arm64.

Why can’t I connect immediately after installation?

The client package contains only the GUI and runtime components, not a ready-to-use server configuration. Import a valid subscription or individual node, select a working configuration, and enable the system proxy or TUN as needed. If no nodes appear after import, update manually and check that the link is complete.

To troubleshoot subscription updates, DNS, the system proxy, or TUN, open the full troubleshooting categories.

View all FAQs