Installation options for four platforms

CLIENT PACKAGE INDEX

V2Ray Client Download

Choose a platform based on your operating system, then verify the processor architecture and package format. Use v2rayN on desktop, v2rayNG for standard Android setups, and v2flyNG when you need the V2Fly core ecosystem.

  • Packages grouped by system and architecture
  • Release details updated from the same-source manifest
  • Chinese configuration guidance available

PLATFORM PACKAGES

Choose an installer by platform

Platform switching is preserved in the address-bar anchor. Copy the current page URL so recipients can open the matching platform panel directly.

windows-packages
Windows x64

Windows:v2rayN

Windows offers Desktop and classic WPF interface versions. Choose Desktop for new installations; choose WPF if you are familiar with the traditional v2rayN interface or need to keep the existing workflow. Both packages target x64 desktop devices.

Windows system requirements and selection checklist

Check Recommendation How to check
Processor architecture x64 Open “Settings → System → About” and check the system type.
Disk permissions Use a directory with long-term read/write access Do not place the runtime directory in a temporary folder; exit the running client before updating.
Interface version Prefer Desktop for new installations Choose WPF if you depend on the traditional workflow; otherwise use Desktop.

AFTER DOWNLOAD

Installation order after download

Handle installation, importing, and connecting separately. Complete each step before moving to the next so permission, configuration-format, and routing issues are easier to locate.

  1. 01

    Verify the platform, architecture, and package format

    First confirm that the platform label on the download page matches the current device. On desktop, also check x64, Apple Silicon, or arm64; on Linux, confirm deb or rpm as well. Mainstream Android devices typically use arm64; use the universal version only when the architecture cannot be confirmed. A mismatched architecture or format can prevent installation or startup and trigger a system incompatibility warning.

  2. 02

    Complete installation and handle system permissions

    On Windows, follow the package workflow after extracting; on macOS, open the DMG and follow the system authorization prompts; when installing an APK on Android, check the installation-source permission for the current app; on Linux, use the package tool for the distribution. Limit permission changes to what this client needs to install and run, and do not alter unrelated system security settings.

  3. 03

    Import a subscription or share link

    Add a subscription URL under “Subscription Group” or “Subscription Settings”, save it, and run an update. For a single vmess, vless, or trojan share link, use the clipboard import entry point. After importing, check the configuration name, address, port, transport, and TLS-related fields; do not assume every entry suits the current network environment.

  4. 04

    Choose a routing mode and start the connection

    Select a valid configuration first, then set the system proxy or VPN mode. Use routing rules when traffic must be handled by domain and IP categories; read the TUN mode guidance when more application traffic needs to be intercepted. After connecting, review the client logs to confirm that configuration loading, DNS queries, and outbound establishment complete without errors.

PACKAGE REFERENCE

Client and package selection rules

Follow this order: “platform → client → architecture → package format”. Do not infer device compatibility from the version number.

Use v2rayN across desktop platforms

The GUI client entry point for Windows, macOS, and Linux is v2rayN. Feature names may vary slightly by platform, but the workflow is consistent: add a subscription, update the group, select a configuration, set routing, and start the connection. Windows also requires choosing between Desktop and classic WPF; macOS and Linux primarily require checking the processor architecture and package format.

Use v2rayNG first for standard Android setups

v2rayNG uses the Xray core and suits common VMess, VLESS, Trojan, and REALITY configurations. Packages are available in arm64 and universal versions. Prefer arm64 on mainstream phones; switch to the universal version when the architecture is unknown or compatibility warnings appear. v2flyNG is the alternative client for the V2Fly core ecosystem and should be chosen only when the configuration explicitly requires it.

Handle release updates and configuration retention separately

Exit the running program before updating the client, and note the subscription groups, routing rules, and custom DNS settings. Do not overwrite desktop program directories by mixing old and new files; before updating Android, confirm that the app identity matches the existing installation. After updating, launch it once, check the core status and configuration loading, then restore the system proxy or VPN mode.

VMess VLESS Trojan REALITY Routing DNS

DOWNLOAD FAQ

Frequently asked questions about downloading and installing

Check the package by platform first, then handle permissions and configuration. The answers below match the client list on this page.

Should you download v2rayN Desktop or the classic WPF version for Windows?

Choose Desktop first. It uses a next-generation cross-platform interface and is suited to new installations. Choose the classic WPF version if you already prefer WPF or need to keep the traditional desktop workflow. Both target Windows x64. Do not run both versions at the same time, as their system-proxy ports and configuration directories may interfere with each other.

How do you choose the Apple Silicon or Intel version for macOS?

Open “About This Mac” from the system menu and check the Chip or Processor field. If it shows an Apple M-series chip, download the Apple Silicon version; if it shows an Intel processor, download the Intel version. Do not rely only on the device name, as one product line may include different processor versions.

Should Android users download the arm64 or universal version?

Most mainstream Android phones released after 2015 use arm64, so start with the arm64 version. If you cannot confirm the processor architecture or installation reports incompatibility, use the universal version instead. The universal version supports more architectures and has broader compatibility, but its package is usually larger.

How should you choose between v2rayNG and v2flyNG?

For standard Android setups, use v2rayNG. Choose v2flyNG when you need the V2Fly core ecosystem or an existing configuration explicitly requires it. Switching clients does not automatically correct server parameters; before importing, still confirm the share-link format, transport, and encryption-related settings.

Should Linux users download a deb or rpm package?

Choose deb for Debian, Ubuntu, and derivatives; choose rpm for Fedora, RHEL, and related distributions. Then run uname -m to confirm the architecture: choose x64 for x86_64 and arm64 for aarch64. Do not convert package formats by changing the file extension.

How do you import a V2Ray subscription after installation?

Open the client’s subscription group or subscription settings, add the subscription URL provided by your service provider, and run an update. Then select a configuration, set the routing mode, and start the connection. Use the clipboard import entry point for a single share link. Subscription URLs may contain access credentials; do not publish them on public pages or shared documents.

V2Ray Client Download