CLIENT PACKAGE MATRIX

V2Ray Client Downloads

Choose v2rayN, v2rayNG, or v2flyNG for your operating system. Use v2rayN on desktop platforms; on Android, choose between v2rayNG and v2flyNG according to the core you need. This page also lists processor architectures, package formats, and the recommended post-install configuration order.

Free forever Open source Four platforms Chinese configuration docs
PLATFORM SELECTOR

Choose an installer by platform

The platform label is reflected in the page address. Copy the address with its platform marker and reopen it to show downloads for that operating system directly.

WIN / X64

Windows · v2rayN

Windows offers two entry points: the desktop edition and the classic WPF edition. The desktop edition uses the newer cross-platform interface and is closer to the macOS and Linux versions. The classic WPF edition preserves the long-established Windows workflow for users who want familiar menus and habits.

Top pick Windows desktop client

v2rayN · Windows

Current version 7.24.1

Choose the desktop edition for a first installation or the current interface system. Choose the classic WPF edition if you already know its menus, tray controls, and WPF interface. Both installers target x64 Windows, so there is no need to install both. Before switching editions, record your subscription URL, routing rules, and custom settings.

DESKTOP Desktop edition

A newer cross-platform UI for first-time installations and users who want a consistent desktop experience.

WPF Classic WPF edition

Keeps the classic Windows interface and workflow for users who prefer their existing habits.

Download desktop edition Download classic WPF edition
SYSTEM NOTES / WINDOWS

Windows installation requirements

Check Recommendation Why it matters
Processor architecture x64 Both Windows installers on this page use the x64 architecture.
Installation permissions Use an account that can install desktop applications Installation writes application files and may create Start menu or desktop shortcuts.
First launch Allow the client to make necessary network connections The client needs network access to update subscriptions, connect to servers, and apply system proxy settings.
Edition choice Choose either the desktop or classic WPF edition This avoids both editions running at once and competing for the local proxy port or system proxy state.
AFTER INSTALLATION

Post-install configuration order

The installer only deploys the client. A working connection also requires a valid subscription or share link, configured in a set order to avoid repeatedly changing nodes, routing, and network modes.

  1. 01
    IMPORT

    Import a subscription or share link

    Obtain a valid subscription URL from your service provider, then add it in the client using Import from Clipboard or the subscription manager. A subscription and a single share link serve different purposes: subscriptions usually update a server list in bulk, while a share link adds one configuration. Make sure the copied content is complete and does not include instructions or extra spaces.

  2. 02
    SELECT

    Update the list and choose a node

    After adding a subscription, update it first, then choose one node from the list as the current server. Names are mainly for identifying routes and do not prove availability. For the first connection, select a configuration and run a real connection test. If it fails, check node status, network conditions, DNS, and local proxy settings step by step.

  3. 03
    ROUTING

    Choose system proxy or TUN mode

    System proxy mainly affects browsers and apps that follow the operating system proxy settings, making it suitable for everyday web access and standard desktop software. TUN mode can route traffic from a wider range of apps but usually requires additional system permissions and makes DNS and routing more important. Start with system proxy to confirm the node works, then enable TUN only if broader app coverage is needed.

  4. 04
    VERIFY

    Verify it with a real connection

    A client showing that it is running only confirms that the local process started; it does not prove a working connection. Open a webpage or app that should use the proxy and confirm that content loads normally. Also check the system proxy state, current node, and client logs. If one app works while another does not, first check whether the latter follows the system proxy instead of replacing the entire subscription.

View the complete setup guide Read the advanced configuration manual
CLIENT RELATION

How clients and cores relate

V2Ray is a broad term for the related protocol, configuration structures, and implementation ecosystem. In everyday use, graphical clients manage subscriptions, nodes, routing, and system proxy settings. The client handles the interface and workflow; the core parses configurations and manages network connections. Their roles are distinct.

v2rayN covers Windows, macOS, and Linux desktop platforms, while v2rayNG and v2flyNG target Android. v2rayNG uses the Xray core, and v2flyNG uses the v2fly core. For a standard installation, download the matching graphical client; it manages the required runtime components according to its distribution.

A

Choose v2rayN for desktop platforms

Windows, macOS, and Linux use the same client family, making subscription management, node switching, routing, and system proxy workflows easier to keep consistent. On Windows, choose between the desktop and classic WPF editions; on macOS, match the chip architecture; on Linux, match the package system and processor architecture.

B

Choose v2rayNG first on Android

v2rayNG suits most Android use cases and supports common subscription imports, node management, and routing settings. Use the arm64 package for a confirmed 64-bit ARM device; use the universal build when device information is unclear to reduce installation failures caused by an incorrect architecture choice.

C

Choose v2flyNG when v2fly is required

v2flyNG is an alternative Android client. Choose it when an existing configuration, routing behavior, or environment is explicitly built around the v2fly core. Without a clear core dependency, starting with v2rayNG keeps the selection process simpler.

DOWNLOAD FAQ

Common download and installation questions

These questions cover versions, architectures, package formats, and first-time configuration. For deeper guidance on connection speed, routing rules, DNS, and TUN settings, continue to the advanced manual.

Should Windows users download the v2rayN desktop edition or the classic WPF edition?
For a first installation, the desktop edition is a good choice if you want the newer cross-platform interface. Choose the classic WPF edition if you already know its interface and want to keep the familiar workflow. Both are for Windows; keep one primary edition installed. Before switching, record your subscription URL and custom rules so no settings are lost during migration.
How do you choose between the Apple Silicon and Intel installer on macOS?
Open About This Mac and check the Chip or Processor field. Choose Apple Silicon for an Apple chip and the Intel installer for an Intel processor. Device model, appearance, and purchase date are only clues; the processor field in System Information is the direct basis for the choice.
What is the difference between the arm64 and universal Android builds?
The arm64 package targets mainstream 64-bit ARM devices and is usually smaller, while the universal build supports a broader range of architectures. Most mainstream phones from 2015 onward should start with arm64; use universal when the architecture is unclear or installation fails. Changing package architecture does not change subscription content or node parameters.
How should you choose between v2rayNG and v2flyNG?
For everyday Android use, start with v2rayNG and its Xray core. Choose v2flyNG when an existing configuration depends on v2fly core behavior or must remain consistent with an established v2fly setup. Both clients can manage subscriptions and nodes, but their core implementations and some configuration behavior may differ; avoid switching back and forth without a clear reason.
Should Linux users download a deb or rpm package?
Debian, Ubuntu, and derivatives generally use deb; Fedora, Rocky Linux, AlmaLinux, and other RPM-based distributions generally use rpm. Also choose x64 or arm64 to match the processor. The distribution’s package format and processor architecture must both match; checking only one is not enough.
What should you configure after installation?
After installing the client, import a valid subscription or single share link, update the subscription, and choose a node. Then select system proxy or TUN mode based on the traffic you need to route, and verify it with a real webpage visit. During first-time setup, change one thing at a time so connection failures are easier to diagnose.