Clients and installation packages

V2Ray Client Download
Choose a package for your system

Choose v2rayN for desktop systems, or v2rayNG or v2flyNG on Android. Confirm your operating system and processor architecture before downloading the matching package.

Free forever Open source Graphical interface Subscription and routing configuration
Platform packages

Choose your device platform

The platform tab is synced to the page URL. When you share a link with a platform anchor, the page opens directly at the corresponding package section.

Windows：v2rayN

v2rayN provides desktop features including subscription management, server switching, system proxy, TUN mode, routing rules, and log viewing. For a new installation, the desktop edition is usually preferred; choose the WPF edition if you prefer the classic Windows interface and familiar workflows.

Recommended

v2rayN for Windows

Current version 7.24.1

x64
Next-generation cross-platform UI

Desktop edition

Suitable for first-time installations and users who want the newer interface. The download is a ZIP archive; extract it, run the installer inside, and follow the system prompts to complete installation.

Download v2rayN desktop edition v2rayN-Desktop-Setup-x64-7.24.1.zip
Classic Windows interface

Classic WPF edition

Suitable for users who prefer the classic layout, menu placement, and workflow. Some entry points differ from the desktop edition, but the subscription, server, and proxy configuration logic remains the same.

Download classic WPF edition v2rayN-Setup-x64-7.24.1.zip

Windows requirements and edition guide

Check Requirement and action
Processor architecture This page provides an x64 package for common 64-bit Intel and AMD processor PCs.
Installation permissions The installer needs to write to the application directory. On managed computers, a system administrator may need to approve the installation.
First launch When the system firewall asks to confirm network access, decide whether to allow client communication based on the network you are using.
Edition selection If unsure, start with the desktop edition. Choose the WPF edition when you need the classic interface and familiar menu layout.
Before configuration

Download, installation, and first launch

Installing the client does not enable the proxy by itself. The complete process also includes importing a configuration, selecting a server, starting the core, and setting the system traffic entry point.

01

Confirm the platform and architecture

Confirm the operating system first, then the chip or processor architecture. Desktop devices commonly use x64 or arm64, while Android users can choose between arm64 and a universal package. A mismatched package may be rejected or fail to start correctly.

02

Install the GUI client

On Windows, extract the ZIP and run the installer; on macOS, open the DMG and move the app to “Applications”; on Android, open the APK and follow the system prompts; on Linux, use the package installer matching the distribution.

03

Import a subscription or share link

Obtain a valid subscription URL from your service provider, then add and update it through the client's subscription manager. For a single-node vmess, vless, or other share link, use an entry such as “Import from clipboard” to add it to the server list.

04

Choose how the proxy takes over traffic

System proxy works for apps that read the system proxy settings; TUN mode handles a broader range of traffic; routing rules determine whether each destination uses the proxy, a direct connection, or a specified outbound. For a first setup, establish a basic connection before fine-tuning split routing.

Workflow

Checks for the first connection

  1. Update subscription: Confirm that the server list contains valid entries. If the update fails, check the client logs first.
  2. Select a server: Choose a configuration and set it as the active server.
  3. Start the core: Check the logs for port conflicts, invalid fields, or mismatched transport parameters.
  4. Set the proxy: Choose system proxy or TUN mode according to your current use case.
  5. Verify traffic: Open an internet-connected app and test it, then use the logs to confirm that requests reach the expected outbound.
View the quick start guide Read the full manual
Package identification

Filename and architecture markers

Package filenames usually include the client name, version, processor architecture, and file format. Understanding these fields helps prevent choosing the wrong package.

x64 · amd64 · x86_64

Common desktop 64-bit architecture

Across operating systems and package systems, these names refer to the same mainstream 64-bit Intel and AMD processor architecture. Windows and most traditional desktop Linux PCs generally use this category.

arm64 · aarch64 · arm64-v8a

64-bit ARM architecture

Apple Silicon, some Linux devices, and most recent Android phones use 64-bit ARM architecture. Names vary by platform, so check the file format as well when choosing a package.

DMG · APK · deb · rpm

Platform package formats

DMG is used for macOS, APK for Android, and deb and rpm for different Linux package systems. After matching the file format to the platform, confirm the processor architecture as well.

Common download questions

Package selection and first run

These questions cover edition selection, chip architecture, package formats, and basic configuration after installation.

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

For a first installation, the desktop edition is usually the better choice because it uses a modern cross-platform interface. Choose the WPF edition if you prefer the classic Windows workflow. Both manage servers, subscriptions, system proxy settings, and routing rules; the main differences are the UI technology and some menu layouts.

How do I know whether to download the Apple Silicon or Intel version for macOS?

Open the system menu in the upper-left corner and choose “About This Mac” or “System Information.” If the chip field shows an Apple M-series chip, choose Apple Silicon; if the processor field shows Intel, choose the Intel version. Do not rely only on when the device was purchased.

Should Android users choose arm64 or the universal version?

Most mainstream Android phones released after 2015 use 64-bit ARM architecture, so arm64 is a good first choice. Use the universal version if the architecture is unknown or the arm64 package cannot be parsed. The universal edition supports more architectures while retaining the same client features.

How should I choose between v2rayNG and v2flyNG?

Android users generally start with v2rayNG, which uses the Xray core and provides common subscription, routing, and proxy-mode controls. Choose v2flyNG when you need the v2fly core ecosystem. Whether a configuration imports successfully also depends on the subscription content, protocol parameters, and client version.

Should Linux users download a deb or rpm package?

Choose deb for Debian, Ubuntu, and derivatives; choose rpm for Fedora, RHEL-based systems, and RPM-based distributions. Also select x64 or arm64 for the processor, which you can check with uname -m.

Why can't I connect immediately after installation?

The client only reads configuration and manages the proxy. After installation, import a valid subscription or single-node share link, select a server, start the core, and enable system proxy or TUN mode for your use case. If the connection fails, use the log window to locate the failing stage first.