CLIENT PACKAGES · 4 PLATFORMS

V2Ray client download

Choose a client by operating system, CPU architecture, and package format. Use v2rayN on desktop platforms, and choose between v2rayNG and v2flyNG on Android.

v2rayN v2rayNG v2flyNG Free forever Open source Chinese documentation
PLATFORM SELECTOR

Choose a package by platform

After switching platforms, the page URL updates to the corresponding anchor. Copy the current address to return directly to the download panel for the same platform.

WINDOWS · X64

Windows：v2rayN

Windows offers the desktop edition and the classic WPF edition. Both are v2rayN; the main differences are interface technology, menu layout, and workflow. For a first installation, start with the desktop edition. Choose WPF when you need to preserve an existing workflow.

v2rayN

Windows · 64-bit desktop client

Recommended

v2rayN manages subscriptions, server selection, routing rules, and system proxy controls. The desktop edition uses a modern cross-platform interface with settings reorganized by function, making it suitable for first-time installations or users who want a consistent workflow across desktop systems. The classic WPF edition retains the traditional Windows interface, with menus and window layouts closer to older versions, for users with established habits.

DESKTOP

Desktop edition

v7.24.1

Modern cross-platform UI. Choose it first for a new installation, a preference for a contemporary settings layout, or plans to switch between desktop systems.

Download the desktop edition
WPF

Classic WPF edition

v7.24.1

Classic, familiar interface. Choose it if you know the older menus, need to preserve an existing workflow, or are following an older configuration guide.

Download the WPF edition

Windows system requirements and installation

Check Requirement How to choose
System type A supported 64-bit version of Windows Check the system type under “Settings → System → About.”
Processor x64 The Windows packages on this page target common 64-bit Intel and AMD PCs.
Installation method Download the ZIP, extract it, and run the installer Do not launch the installer directly from the archive preview window.
First launch Allow the client to write to the user configuration directory When Windows displays a network access prompt, choose the scope that matches your local network needs.

After installation, open the client and confirm that the main window displays correctly before importing a subscription. If an older version is running, exit it from the tray menu rather than merely closing the main window.

PACKAGE NOTES

How to choose an installation package

The filename contains essential information. Match the client, operating system, CPU architecture, and package format one by one.

A

Classify by device operating system first

Use v2rayN on desktop devices, and choose between v2rayNG and v2flyNG on Android. Do not identify the client from the subscription name alone: it usually describes a service or group, not the package format. Determine the device that will run the client, then open the matching platform panel to reduce the chance of downloading the wrong file.

B

Then verify the processor architecture

macOS distinguishes Apple Silicon from Intel; Android commonly offers arm64 and universal builds; Linux distinguishes x64 from arm64. Architecture labels may vary: amd64 commonly corresponds to x64, while aarch64 corresponds to arm64. If the Android architecture is unknown, the universal build is usually easier to match, though it includes more resources.

C

Finally, check the package format

This page provides a ZIP package containing the Windows installer, DMG for macOS, APK for Android, and deb or rpm for Linux. Linux format depends on the distribution, not the processor brand. Before downloading, read the platform, architecture, and format together—for example, “Linux, arm64, deb”—rather than relying only on the filename suffix.

NEXT STEPS

Configuration steps after downloading

Installing the client is only the first step. Whether the connection works depends on importing a configuration, selecting a server, choosing a proxy mode, and configuring the application.

  1. Finish installation and launch the client

    First confirm that the client’s main window opens. Upgrading users should check that old subscriptions, server notes, and routing rules remain; a first-time installation showing an empty server list is normal.

  2. Import a subscription or individual configuration

    Copy the subscription URL provided by the service provider, add it from the client’s subscription menu, and update it. If you have only one sharing link, use clipboard or QR-code import. After importing, check that the protocol, address, and remarks are complete before changing advanced fields.

  3. Choose a server and routing mode

    Select a configuration from the server list, then choose system proxy, VPN connection, or another mode provided by the client for your use case. Routing rules determine which requests go through the proxy outbound. For an initial setup, use the client’s default rules and refine them only after confirming the basic connection.

  4. Test the browser and terminal separately

    Browsers usually read the system proxy, while terminal programs may require separate environment variables. A working browser with a terminal that connects directly does not necessarily mean the client has failed. First determine where the specific application reads proxy settings, then troubleshoot along that path.

View the complete setup guide Read the advanced configuration guide
DOWNLOAD FAQ

Common download and installation questions

These questions cover versions, architectures, packages, and first-time setup. When a connection fails, first distinguish between “the client did not install successfully” and “the configuration is not working.”

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

For a first installation, start with the desktop edition. It uses a modern cross-platform interface with menus organized for new users; the classic WPF edition retains the traditional Windows workflow for users familiar with the older interface and menu layout. Both are v2rayN. Back up existing subscriptions and custom rules before migrating settings.

How can I tell whether my Mac uses Apple Silicon or Intel?

Open “About This Mac” from the system menu and check the chip or processor field. If it shows an Apple M-series chip, choose Apple Silicon; if it shows an Intel processor, choose Intel. The wrong architecture can prevent the installer from launching, so download the matching DMG again.

Should Android users choose arm64 or the universal build?

Most mainstream Android phones released after 2015 should use arm64 first because the file is smaller. Choose the universal build if the architecture is unknown, the device is older, or arm64 installation fails. The universal build includes resources for more architectures and is usually larger.

What is the difference between v2rayNG and v2flyNG?

Both are graphical Android clients. The main difference is their core family and the update path for some protocol features. v2rayNG uses the Xray core and is the usual default choice; v2flyNG uses the v2fly core and suits users with compatible configurations or a need to stay within the V2Fly ecosystem.

Should Linux users download deb or rpm?

Debian, Ubuntu, and derivatives typically use deb; Fedora, Rocky Linux, AlmaLinux, and RHEL-based distributions typically use rpm. Also verify the CPU architecture: choose amd64 or x86_64 for standard 64-bit PCs, and arm64 or aarch64 for ARM devices.

What should I do after downloading and installing the client?

Installing the client does not automatically create a usable server configuration. Next, import a subscription URL or individual configuration, update the server list, choose a server, and enable the system proxy or another connection mode for your use case. For first-time setup, continue with the quick-start guide.