Clients and Installers

V2Ray Client Download

Choose your operating system first, then check the processor architecture and package type. Use v2rayN on desktop platforms, v2rayNG on Android, or v2flyNG when you need the V2Fly configuration ecosystem.

Free forever Open source Install guides for four platforms

Choose by system

Platform Installers and Clients

The active platform label is added to the page URL. Copy the anchored link to return directly to that platform. Switching platforms does not start a download; confirm the package type before clicking a card button.

Windows

v2rayN Desktop Client

Windows offers the Desktop and classic WPF editions. Choose Desktop for a new installation; choose WPF if you know the traditional interface and want to keep its menu layout and workflow. Both options are x64 installers.

Windows · x64
Recommended

v2rayN

Current release 7.24.1

v2rayN is a graphical desktop client for managing subscriptions, switching nodes, configuring the system proxy, and setting routing rules. Desktop is recommended for a first installation because its layout is closer to the macOS and Linux versions, making cross-platform migration easier.

Preferred choice

Desktop edition

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

v2rayN-Desktop-Setup-x64-7.24.1.zip

Download Desktop edition
Classic interface

WPF edition

A familiar, stable interface for users who already know the classic menu structure and workflow.

v2rayN-Setup-x64-7.24.1.zip

Download WPF edition

Windows pre-installation checklist

Check Recommendation How to verify
Processor architecture x64 Check System Information for the system type. Most desktop PCs show x64-based processor.
Package choice Desktop first Choose Desktop for a first installation; choose WPF when you need the classic interface.
Installation directory Use a fixed directory Avoid moving the program directory repeatedly after installation, as shortcuts and configuration paths may stop working.

Post-install configuration order

From installation to connection check

Downloading is only the first step. Configure the client in a fixed order after installation to avoid misdiagnosing an outdated subscription, a disabled system proxy, or an unselected node.

  1. 01

    Finish installation and launch for the first time

    Open the client using the installation method for your system. After installing on Windows or Linux, confirm that the program directory is writable; on macOS, complete the first-launch authorization prompts; on Android, approve the system connection request. Check that the main interface loads correctly before configuring subscriptions.

  2. 02

    Import the complete subscription URL

    Add the URL under subscription management and manually run one update after saving it. The updated list should contain nodes or configurations. If it is empty, check that the URL is complete, contains no spaces, and is still valid before changing the local proxy port.

  3. 03

    Select a configuration and enable the system proxy

    Select a configuration as the active node, then enable the client's system proxy. Android routes traffic through the system VPN connection screen; on desktop systems, confirm that the system proxy status has changed. Set routing or per-app rules only after the basic connection works.

  4. 04

    Confirm connectivity

    Reopen a browser window and visit a test page while checking the client log for new connection entries. If the connection fails, check the subscription update, active node, system proxy, local port, and system time in that order. Change one thing at a time to identify the actual cause.

Read the complete user guide Open Troubleshooting

Package identification

How to read common installer filenames

Filenames usually include the client name, release number, architecture, and package type. Check the extension first, then look for architecture markers such as arm64, aarch64, x64, x86_64, or universal.

Desktop installer

zip and dmg

Windows downloads use a zip container; extract it and run the installer inside. macOS uses dmg; open it and follow the on-screen installation steps. Do not use a dmg package on Windows or identify a file's purpose solely by its icon.

Desktop-Setup-x64 · arm64.dmg

Android package

apk and universal

apk is the Android application package format. arm64-v8a targets mainstream 64-bit ARM devices, while universal packages support more architectures. Prefer a single-architecture package when the device details are known; otherwise choose universal.

arm64-v8a.apk · universal.apk

Linux package management

deb and rpm

deb and rpm belong to different distribution package systems. In architecture fields, amd64 and x86_64 generally refer to common Intel and AMD desktop devices; arm64 and aarch64 refer to ARM devices. The package type and architecture must both match.

amd64.deb · x86_64.rpm · aarch64.rpm

Download issues

Common installer selection questions

Confirm the platform, chip, and package type first, then configure the connection after installation. The questions below cover the most common choices on this page.

Should Windows users choose the v2rayN Desktop or WPF edition?

The Desktop edition is the preferred choice because it uses a modern cross-platform interface. Choose WPF if you already know the classic interface or need to keep the familiar workflow. Both target Windows x64, and there is no need to install both. Before switching editions, record the subscription URL and key settings to avoid configuring everything again.

How can macOS users tell whether they have Apple Silicon or an Intel processor?

Open About This Mac from the system menu and check the Chip or Processor field. Choose the Apple Silicon installer for Apple M-series chips and the Intel installer for Intel processors. Do not rely only on the device design, screen size, or purchase year, as similar product cycles may use different chips.

Should Android users download arm64 or the universal build?

Most mainstream Android phones released after 2015 should use arm64 first. Use the universal build when the processor architecture is unknown or the arm64 package cannot be parsed. Universal builds cover more devices but are usually larger; they do not add client features.

Should Linux users choose deb or rpm?

Choose deb for Debian, Ubuntu, and derivatives; rpm is generally used by Fedora, openSUSE, and RHEL-based distributions. After choosing the package type, check the device architecture: common Intel and AMD desktops use x64, while systems showing arm64 or aarch64 require the matching ARM package.

What should I do after downloading and installing the client?

Import the complete subscription URL and manually update the node list, select a working configuration, enable the system proxy, then visit a test page in your browser to confirm the connection. If the updated list is empty, check the URL; if the list is normal but the connection fails, check the active node, system proxy, and local port.