Client installation packages

V2Ray client downloads and platform selection

Choose your operating system first, then download the package matching your processor architecture and interface version. Use v2rayN on desktop systems; on Android, choose between v2rayNG and v2flyNG.

Windows macOS Android Linux

Download by platform

Choose the client installation package for this device

The page reads the same-origin release manifest to update the version and download URL. If dynamic loading is temporarily unavailable, the button still keeps the complete download path for the current release.

Windows

v2rayN desktop client

Windows offers two installation paths: the Desktop version and the classic WPF version. Choose Desktop for a first installation; choose WPF if you already know the traditional interface or need to preserve an existing workflow.

Current release 7.24.1
v2rayN
Top pick Desktop client

v2rayN

Windows x64 · Desktop and classic WPF versions

Recommended

Desktop version

ZIP

Uses a newer cross-platform UI with a layout similar to the macOS and Linux desktop versions. Suitable for first-time installations and Windows users who want the newer interface.

Download v2rayN Desktop
Classic interface

WPF version

ZIP

The classic, stable Windows-only version, with menus organized around the traditional v2rayN workflow. Suitable for users who already have an established routine.

Download the classic WPF version

Windows system requirements and selection guide

Check Recommendation Reason
Processor architecture x64 The Windows packages on this page target common 64-bit desktop devices.
First installation Desktop version Uses the newer interface, making the workflow more familiar when switching between desktop platforms later.
Existing workflow Classic WPF version Keeps the traditional Windows menu structure for users who want to continue an existing configuration process.
Runtime dependencies Install the required runtime shown in the startup prompt If the app does not open normally after a double-click, first check the runtime environment, extraction path, and directory write permissions.

Before you install

The four checks that prevent package selection errors

Most installation issues are not caused by subscriptions or configuration, but by a mismatch in platform, architecture, package format, or runtime environment. Complete these four checks before downloading to shorten the troubleshooting path.

01

The operating system must match

Windows, macOS, Android, and Linux use different package formats and runtime mechanisms. Do not judge by similar-looking filenames or use a desktop client package on a mobile device. Confirm the platform name in System Settings or system information before opening the corresponding tab.

02

Check processor architecture in system information

x64, arm64, and universal describe the processor architectures targeted by the program. On macOS, check About This Mac directly; on Android, use the universal version when uncertain; on Linux, distinguish x86_64 from aarch64 through the system architecture information. The purchase year is only a clue, not a substitute for system information.

03

The package format must match the system

macOS uses DMG, Android uses APK, and Linux requires a choice between deb and rpm. The Windows page provides compressed packages that must be fully extracted first. With the wrong format, the system will usually refuse to open the file or the package manager will report incompatibility.

04

Check paths and permissions first when installation fails

If the program will not start, first check that the files were fully extracted, the directory is writable, the required runtime environment is installed, and security settings are not blocking the first launch. The subscription URL is only needed after the client starts successfully and should not be part of startup troubleshooting.

After downloading

From installation to subscription import

The installation package is only the first step. Once the client starts normally, complete subscription setup, configuration updates, configuration selection, and proxy mode settings in order.

View the complete tutorial Read the full manual
  1. 1

    Install and launch for the first time

    Install according to the current platform. Extract Windows archives first, follow the macOS installation prompts, open the appropriate APK on Android, and use the matching package tool on Linux.

  2. 2

    Add the complete subscription URL

    Open subscription management and add the complete URL provided by your service provider. Save it, run one manual subscription update, and confirm that the client has generated a configuration list.

  3. 3

    Choose a configuration and proxy mode

    Select a configuration from the updated list. For ordinary desktop apps, start with the system proxy; when more application traffic needs to be routed, configure TUN mode after reading the instructions.

  4. 4

    Check status and logs

    If the connection does not work as expected, first confirm that the intended configuration is selected and the proxy switch is in the correct state. Then check the client logs for port, subscription, and configuration-field messages.

Download FAQs

Package selection and first launch

These questions cover version selection, chip architecture, package formats, and what to do after installation.

Should Windows users download the v2rayN Desktop or WPF version?

Choose Desktop first for a new installation. It uses a newer cross-platform UI and follows a design direction closer to the macOS and Linux desktop versions. Choose WPF if you are familiar with the classic Windows menus and want to preserve your existing workflow. Both are v2rayN and support subscription import, configuration selection, system proxy, routing rules, and log viewing.

How do I know whether to choose the Apple Silicon or Intel macOS package?

Open About This Mac from the system menu and check the Chip or Processor field. Choose Apple Silicon for an Apple M-series chip and Intel for an Intel processor. Do not rely only on the device model or appearance. If the download reports an architecture mismatch, recheck this field and replace the package.

Should Android users download arm64 or the universal version?

Most mainstream Android phones released after 2015 should use arm64 first, which covers most modern mobile devices. If the architecture is unknown or the arm64 package reports incompatibility, download the universal version of the same client. Changing architecture builds does not change the subscription URL content.

Should Linux users choose deb or rpm?

Debian, Ubuntu, and their derivatives typically use deb; Fedora, Rocky Linux, AlmaLinux, and similar systems typically use rpm. After determining the format, confirm the processor architecture: choose x64 for x86_64 or amd64, and arm64 for aarch64 or arm64. Both format and architecture must match.

What should I do after the download finishes?

Install and launch the client, then open subscription management and add the complete subscription URL provided by your service provider. Save it, run an update, select the generated configuration, and enable system proxy or TUN mode for your use case. If the connection fails, check the client status and logs first; do not repeatedly edit the subscription before the client starts successfully.