Current client packages and platform selection

V2Ray Client Downloads
Choose by system and architecture

Desktop platforms use v2rayN; on Android, choose between v2rayNG and v2flyNG. Identify your operating system first, then verify the processor architecture and package type to avoid installation failures or mismatched packages.

  • v2rayN 7.24.1
  • v2rayNG 2.2.6
  • v2flyNG 1.10.31
  • Four platform entry points

PLATFORM PACKAGES

Choose an operating system

The platform tag is reflected in the address bar. Reopening this page through a link with a platform anchor automatically restores the corresponding download panel.

WINDOWS

Windows：v2rayN

Windows offers Desktop and classic WPF editions. Desktop uses a newer cross-platform UI with a layout closer to the macOS and Linux versions; classic WPF keeps the traditional Windows workflow for users familiar with the older menus and tray controls.

v2rayN
Recommended

v2rayN

Both packages serve the same client purpose. For a first installation with the new interface, download Desktop; choose WPF for the classic Windows interface. Do not run both versions at once, as this can cause confusion between proxy ports and configuration directories.

Desktop edition New-generation cross-platform UI for fresh installs and use across desktop systems.
Download Desktop
Classic WPF edition Traditional Windows interface with familiar, stable menu and tray workflows.
Download classic edition

Current version: 7.24.1

Windows selection criteria

Check Recommendation
System architecture This page provides an x64 package for common 64-bit Windows computers.
Interface edition Choose Desktop for a fresh installation; choose WPF to keep the traditional workflow.
First launch After extracting and installing, launch the client, import a subscription, and select an active node.
Switching editions Exit the running client first, then make sure no leftover process remains in the system tray.

PACKAGE DECISIONS

Package selection logic

The client name, operating system, processor architecture, and package format are four separate criteria. Check them in order to quickly narrow the choice to the one usable package.

01

Check the operating system first

Windows, macOS, and Linux desktop clients use v2rayN; Android offers v2rayNG and v2flyNG. Packages for different systems cannot be installed interchangeably, and their file extensions are clearly different.

02

Then check the processor architecture

x64 and arm64 describe processor architectures, not client editions. Apple Silicon on macOS corresponds to arm64, while Intel corresponds to x64; Linux users should check the system architecture, and newer mainstream Android devices generally use arm64.

03

Confirm the package format

This page provides ZIP packages for Windows, DMG for macOS, APK for Android, and deb or rpm for Linux depending on the distribution. When the format is incompatible, the system package manager usually cannot proceed.

04

Finally, handle interface or core differences

On Windows, choose between the Desktop and WPF interface paths; on Android, choose between the v2rayNG and v2flyNG core ecosystems. Without a specific compatibility requirement, prefer the option marked as recommended for each platform.

AFTER DOWNLOAD

Installation and first connection after downloading

A successful installation does not mean the proxy is active. You still need to import a subscription, select a node, configure the proxy mode, and verify access in practice.

Stage one

Close old instances and install

Before upgrading or switching client editions, exit the running program and check the system tray or background tasks. Run the appropriate installer after extracting on Windows; install the app from the DMG on macOS; open the APK and follow the Android prompts; on Linux, install the deb or rpm with the package manager matching the distribution.

If the device already has configuration data, note the current configuration directory or the client’s export location first. When changing UI editions, do not let two clients control the system proxy at the same time, as this can cause port conflicts, inconsistent tray status, and uncertainty about the source of rules.

Stage two

Import a subscription or single node

After opening the client, find the subscription manager or configuration import entry. A subscription URL usually brings in multiple nodes for easier updates; a single-node link, QR code, or parameter set imports one configuration. Keep the subscription URL complete when copying it, without adding spaces or line breaks.

After importing, run one subscription update and check whether the node list appears. If it is empty, first verify that the subscription URL is complete and still valid, then check the client log for network requests or parsing errors.

Stage three

Choose a node and proxy mode

Select an active node from the list, then enable the system proxy or Android VPN service for your platform. For first-time use, start with the client’s default rule mode; after confirming the basic connection, adjust global proxying, bypass rules, per-app proxying, or routing as needed.

The system proxy works for apps that follow the operating system’s proxy settings; TUN or VPN services cover a broader range of traffic. Do not enable both without understanding their port relationships, or it will be difficult to determine which layer handles the traffic during troubleshooting.

Stage four

Verify the connection and keep logs

After enabling the proxy, open a familiar webpage first to confirm domain resolution and connectivity, then test apps that require the proxy. A connected status only means the local proxy service has started; it does not guarantee that the remote node, DNS, and routing rules are working correctly.

When requests time out or pages fail to load, check in order whether the system proxy is active, the current node works, the subscription is up to date, and the device time is accurate; then review the error log. Keeping the log from the first failure is more useful for diagnosis than repeatedly changing many settings.

Continue configuring the client

The getting-started guide covers subscription import, node selection, proxy activation, and connection verification in order, so you can continue directly after installation.

Read the getting-started guide

DOWNLOAD FAQ

Common download and installation questions

These questions focus on four areas: versions, architectures, package formats, and first-time use. Choose the platform first, then handle the specific differences.

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

Choose Desktop for the newer cross-platform interface. Choose classic WPF if you prefer the traditional Windows interface or want to keep familiar workflows. Both are v2rayN and use the same configuration goals. Exit the running client before switching editions to prevent two instances from controlling the system proxy at once.

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

Open System Information and check the chip or processor field. Choose Apple Silicon when an Apple M-series chip is shown, or the Intel package when an Intel processor is listed. Do not identify the chip type solely from the system version or the device’s appearance.

Should Android users download arm64 or the universal build?

Most mainstream Android phones released after 2015 should use arm64 first. If the device architecture is unknown or the arm64 package will not install, use the universal build instead. The universal build broadens architecture compatibility; it does not provide extra features.

How should I choose between v2rayNG and v2flyNG?

Android users should generally start with v2rayNG, which uses the Xray core. Choose v2flyNG when a subscription service specifically requires V2Fly behavior or when comparing compatibility across cores. Do not share configuration directories directly between clients; re-import through a subscription or standard share link.

Should Linux users download deb or rpm?

Choose deb for Debian, Ubuntu, and derivatives; choose rpm for Fedora, RHEL, and related distributions. Also confirm x64 or arm64 before downloading: x86_64 and amd64 indicate x64, while aarch64 and arm64 indicate arm64.

What else do I need after installation?

The client does not include usable nodes. After installation, prepare a valid subscription URL or single-node parameters, import them, select a node, enable the system proxy or VPN service, and test the connection. If websites remain unreachable, check the system proxy, node status, DNS, routing rules, and device time in that order.