Choose by operating system and processor architecture

V2Ray client downloads and installer selection

Use v2rayN on desktop systems and v2rayNG on Android devices by default. Select the current operating system first, then choose an installer for your processor architecture; each card lists the version, package format, and supported platform.

4 platform entry points 3 GUI clients Architecture and package format guidance
Platform downloads

Choose the operating system on this device

Switching platforms updates the URL anchor, so you can copy the current link and continue on another device of the same type. Each panel lists only GUI clients that can run directly on that system.

Windows

v2rayN desktop client

Windows offers Desktop and classic WPF interfaces. You do not need to install both; choose one based on your interface preference. Subscription imports, node selection, and system proxy setup are largely the same in either edition.

v2rayN

Recommended
Current version 7.24.1 · Windows x64

v2rayN is the primary desktop client for Windows, with subscription management, node speed tests, routing modes, system proxy controls, and TUN settings. The two entries use different interfaces for the same product; either one is sufficient for everyday configuration.

Modern cross-platform interface Desktop edition

Best for a fresh installation, with a layout close to the macOS and Linux editions. The download is a compressed archive; extract it and run the installer.

Download v2rayN Desktop
Classic Windows interface WPF edition

Best for users already familiar with the classic v2rayN layout. Common menus stay within the native Windows interface, making existing configuration workflows easier to follow.

Download v2rayN WPF

Windows system requirements and installation checks

Check Requirement How to verify
System architecture 64-bit Windows Open “Settings → System → About” and check that the system type reports an x64-based processor.
Write location A directory readable and writable by the current account Use a fixed application directory; do not launch the program from a compressed archive preview window.
Proxy permissions The client can modify the system proxy After launch, switch on the system proxy and return to the main window to confirm that the status bar has updated.
Configuration preparation A subscription URL or single-node details Import from a subscription group after installation; configuration is not required during the download stage.
What to do after downloading

From installation to the first connection

The installer provides the client program; it does not replace a subscription or node configuration. Following the sequence below helps distinguish installation, subscription, and connection issues.

  1. 1

    Install and launch once

    For Windows, fully extract the archive before running the installer from a fixed directory; on macOS, open the DMG and move the app to Applications; on Android, open the downloaded installer; on Linux, install with the package tool for your distribution. After the first launch, confirm that the main window opens normally before changing advanced settings.

  2. 2

    Import a subscription or single-node configuration

    With a subscription URL, create a subscription group, paste the complete URL, and update it. For a single-node link, use clipboard import or QR scanning. Check that entries appear after updating; if the list is empty, review the update error first instead of repeatedly toggling the system proxy.

  3. 3

    Choose a node and routing mode

    Select a node first, then choose a routing mode suited to your needs. A common starting point is to bypass the local network and mainland China addresses; use custom rules when you need per-domain or per-IP control. Routing determines which requests enter the proxy and does not indicate the node’s connection quality.

  4. 4

    Enable the system proxy and verify

    After enabling the system proxy on desktop, confirm that the status bar and system network settings are synchronized. On Android, allow the VPN connection when prompted during the first connection. Test with a familiar website, then check the client log for a connection record; if it fails, troubleshoot the subscription, node, routing, and local network in that order.

Need the complete setup steps?

The user guide covers the full sequence for importing subscriptions, choosing nodes, enabling the system proxy, selecting a routing mode, and verifying the connection.

View the user guide
Common download questions

Installer and architecture selection

Handle the system, architecture, and package format first, then move on to subscriptions and connectivity. The most common download-stage problem is choosing the wrong installer, not misconfiguring the client.

Should Windows users choose the v2rayN Desktop or WPF edition?

Choose Desktop for a modern cross-platform interface; choose WPF if you prefer the classic Windows layout or need to keep an existing workflow. Both are v2rayN editions, so install only one. Do not run both editions or let both control the system proxy, or it will be difficult to identify which process is active during troubleshooting.

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

Open About This Mac from the system menu in the upper-left corner and check the chip or processor field. Download Apple Silicon when it shows an Apple M-series chip, and Intel when it shows Intel. Do not guess from the product name or appearance; the same product line may have changed chip architectures.

How should I choose between the arm64 and universal Android versions?

Most mainstream Android phones released after 2015 should use arm64 first. If the device information shows arm64-v8a, that confirms the choice. If installation reports an incompatibility or the processor architecture cannot be confirmed, switch to the universal edition. Both installers provide the same core features; the difference is the range of architectures included.

Should I download deb or rpm for Linux?

Choose deb for Debian, Ubuntu, and derivatives; choose rpm for Fedora, RHEL-based systems, and distributions using RPM package management. After choosing the format, run uname -m to check the architecture: x86_64 maps to x64, while aarch64 or arm64 maps to arm64.

What else do I need after downloading the client?

Install or extract the client first, then prepare a working subscription URL or single-node configuration. Import it, update the node list, choose a node and suitable routing mode, enable the system proxy, and test connectivity. Completing the client installation does not provide node configuration; handle the two separately.

How do v2rayNG and v2flyNG differ?

Both are Android GUI clients. v2rayNG uses the Xray core and is the default choice for most users; v2flyNG uses the v2fly core and is intended when a subscription or configuration specifically requires it. Each client stores its own configuration, so record the subscription URL and custom rules before switching and import them again after installation.

V2Ray client download