CLIENT PACKAGES

V2Ray Client Downloads and Package Selection

Choose an operating system first, then download by CPU architecture and package format. Use v2rayN on desktop platforms; on Android, choose between v2rayNG and v2flyNG based on the required core.

Free forever Open source Four platforms GUI clients

Desktop client v2rayN

Primary Android choice v2rayNG

Alternative Android choice v2flyNG

Desktop edition 7.24.1

PLATFORM

Choose a client by operating system

Platform labels sync to the address bar. Copying a link with a platform anchor opens the corresponding package list directly.

Windows desktop

v2rayN: Desktop and Classic WPF Editions

Download the desktop edition first. It uses a new cross-platform interface for fresh installations and future moves between desktop systems. The classic WPF edition keeps the traditional Windows menus, tray, and window layout for users who want to preserve an existing workflow.

DESKTOP

Desktop edition

Preferred choice

A new cross-platform UI. Choose it for a first installation, a consistent settings layout, or future moves between desktop systems.

Download v2rayN desktop edition ZIP

WPF

Classic WPF edition

Classic Windows interface. Choose it when existing configuration steps rely on the older menus or when you prefer the traditional tray workflow.

Download classic WPF edition ZIP

Windows System Requirements and Installation

Windows pre-installation checklist
Check	Requirement	Selection guidance
CPU architecture	x64	For common 64-bit Intel and AMD Windows computers.
File format	ZIP archive	Fully extract the archive before running the installer from the extracted directory.
Upgrade handling	Exit the client first	After closing the main window, check the tray icon to confirm that the client has exited.
Configuration preparation	Subscription or individual node details	The installer does not include connection settings; import them manually after launch.

Extract the package. Do not run the program from the archive preview. Extract all files to a regular directory first.

Complete the first launch. Follow the system prompts, open v2rayN, and confirm the core type, language, and configuration directory.

Import connection settings. Open “Subscription Groups” to add a subscription URL, update it, select a node, and set the system proxy mode.

macOS desktop

v2rayN: Choose the DMG by chip

Open “About This Mac” from the system menu and check the chip or processor field. Choose Apple Silicon for an Apple M-series chip, or Intel for an Intel processor. Both packages provide the same client features; only the executable architecture differs.

ARM64

Apple Silicon

M-series chip

For computers showing an Apple M-series chip in “About This Mac.” Choose the native arm64 package to match the processor architecture directly.

Download Apple Silicon edition DMG

X64

Intel

For computers whose processor field in “About This Mac” shows Intel. Check the system information directly instead of relying on the device’s appearance or purchase year.

Download Intel edition DMG

macOS System Requirements and Installation

macOS pre-installation checklist
Check	Requirement	Selection guidance
Chip type	Apple Silicon or Intel	Check the chip or processor field in “About This Mac.”
File format	DMG disk image	Open the image and follow the window instructions to move the client to the Applications directory.
Network permissions	Allow system proxy operations	When enabling the system proxy or TUN for the first time, macOS may ask you to confirm permissions.
Upgrade handling	Back up custom settings	Keep subscription groups, routing rules, DNS, and local listening settings.

Check the chip. Read the chip name in system information and download the DMG matching the processor.

Move it to Applications. Open the disk image, follow the window instructions, and launch the client from Applications.

Configure proxy scope. After importing a subscription, verify the connection with the system proxy first; consider TUN mode only when more applications need proxy access.

Android mobile

v2rayNG as the primary choice, v2flyNG as the alternative core

For typical use, start with v2rayNG. It uses the Xray core and supports subscriptions, routing, per-app proxying, and VPN service mode. Choose v2flyNG only when the v2fly core is required. Most mainstream phones released after 2015 use arm64; download the universal edition when the architecture is unknown.

Suitable for standard Android configurations. Import an individual link from the clipboard or add a subscription URL under Subscription Groups; connections use the system VPN service to handle network requests from selected apps.

ARM64-V8A

arm64 edition

Mainstream phones

For most mainstream Android phones and tablets released after 2015. Choose this package when the device is confirmed to use a 64-bit ARM architecture.

Download v2rayNG arm64 APK

UNIVERSAL

Universal edition

Includes more CPU architectures and is usually a larger file. Choose it when the device architecture is unknown or the arm64 package reports incompatibility.

Download v2rayNG universal edition APK

For configurations that specifically require the v2fly core. The client is similar to v2rayNG, but the core family differs; before importing a subscription, confirm that the server configuration matches the selected core’s protocol, transport, and security parameters.

ARM64-V8A

arm64 edition

64-bit ARM

For mainstream Android devices confirmed to use a 64-bit ARM processor. Download this version first when the architecture matches.

Download v2flyNG arm64 APK

UNIVERSAL

Universal edition

For devices with an unknown CPU type or cases where a dedicated architecture package cannot be installed. Client features match the arm64 edition.

Download v2flyNG universal edition APK

Android System Requirements and Installation

Android pre-installation checklist
Check	Requirement	Selection guidance
CPU architecture	arm64 or universal	Prefer arm64 for mainstream devices; choose the universal edition when the architecture is unknown.
File format	APK	After downloading, open the file in the system file manager and follow the installation prompts.
Connection permissions	Allow VPN service	The first connection displays a system confirmation dialog. The client can establish a local VPN service only after approval.
Background operation	Adjust battery settings as needed	If the connection stops after the screen locks, add the client to the system’s list of apps allowed to run in the background.

Choose the client. Use v2rayNG for standard configurations; choose v2flyNG when the service configuration explicitly requires the v2fly core.

Choose the architecture. Download arm64 when the device is known to use 64-bit ARM; otherwise choose the universal edition.

Import and connect. Add and update the subscription under Subscription Settings, select a configuration, tap Connect, and approve the system VPN service request.

Linux desktop

v2rayN: Choose a package by distribution and architecture

Choose deb for Ubuntu, Debian, and derivatives; choose rpm for Fedora, RHEL, and compatible distributions. Use x64 on standard 64-bit Intel or AMD computers, and arm64 on ARM boards and ARM desktop devices.

DEB · AMD64

Debian-based x64

Ubuntu / Debian

For common x64 Ubuntu, Debian, and desktop distributions using the deb package system.

Download x64 deb DEB

ARM device: Download arm64 deb

RPM · X86_64

RPM-based x64

Fedora / RHEL family

For common x64 Fedora, RHEL-family, and compatible distributions using the rpm package system.

Download x64 rpm RPM

ARM device: Download arm64 rpm

Linux System Requirements and Installation

Linux pre-installation checklist
Check	Requirement	Selection guidance
Distribution family	deb or rpm	Choose according to the distribution’s existing package-management system, not the desktop environment.
CPU architecture	x64 or arm64	Intel and AMD 64-bit devices generally use x64; ARM devices use arm64.
Desktop environment	GUI and tray support	If the tray icon is missing, check the desktop environment’s status-icon extension or tray implementation.
System proxy	Desktop network settings writable	After enabling the system proxy, confirm that the desktop environment is using the proxy address written by the client.

Confirm the package format. Choose deb or rpm by distribution, then x64 or arm64 by processor.

Install with the system package manager. This also handles desktop entries, dependencies, and uninstall records.

Check desktop integration. After launch, confirm that the window and tray entry work normally, then import a subscription and configure the system proxy.

PACKAGE DECISIONS

How to Choose the Package, Architecture, and Client

Before downloading, make three decisions: which operating system you use, which CPU architecture the device has, and which core family the configuration requires. The version number does not determine client selection; different architecture packages for the same client provide the same primary features.

Choose the platform by device OS

Choose v2rayN for Windows, macOS, and Linux desktops. They use similar structures for subscriptions, nodes, routing, and DNS, making menu mapping easier when migrating settings. On Android, start with v2rayNG and switch to v2flyNG only when the v2fly core is required.

Choose the architecture by processor

x64 is common on Intel and AMD desktop computers; arm64 is common on Apple M-series computers, mainstream Android devices, and ARM Linux devices. The package architecture must match the operating system and processor; similar names do not make packages interchangeable.

Confirm the package format last

The Windows page provides ZIP packages, while macOS uses DMG. Linux deb and rpm packages correspond to different distribution package systems. Android uses APK; choose arm64 when the architecture is known, or the universal edition when it is not.

Quick selection table

Match the device description to the corresponding download button on the page.

Device situation	Client	Download	Why this choice
Standard 64-bit Windows computer	v2rayN	Desktop edition x64	Uses a new cross-platform interface and is suitable for first-time installations.
Need to keep the classic Windows menus	v2rayN	Classic WPF x64	Retains the traditional window and tray workflow.
Apple M-series computer	v2rayN	Apple Silicon DMG	Native match for the arm64 chip.
Mac with an Intel processor	v2rayN	Intel DMG	Matches the x64 processor architecture.
Mainstream Android phone	v2rayNG	arm64 APK	Common device architecture with a more focused package.
Android architecture unknown	v2rayNG	Universal APK	Includes compatibility targets for more architectures.
Ubuntu or Debian x64 desktop	v2rayN	amd64 deb	Matches the distribution’s package system and processor.
Fedora or RHEL-family x64 desktop	v2rayN	x86_64 rpm	Matches the rpm package system.

AFTER INSTALL

Configuration order after installation

Installing the client only deploys the program. To establish a connection, import a valid configuration, choose a proxy mode, and verify the routing result. Follow the order below to distinguish installation issues from configuration issues.

Import a subscription or individual node

On desktop, create a group under “Subscription Groups,” enter the subscription URL, and update it. On mobile, add the URL in Subscription Settings or import an individual configuration link from the clipboard. After importing, check that the protocol, address, port, and transport parameters are complete.

Choose a system proxy mode

For browsers and desktop apps that follow system proxy settings, start with “Set system proxy automatically.” Configure TUN mode only when more apps need coverage or when connections ignore the system proxy. Do not change routing, DNS, and TUN simultaneously during the first test; multiple changes expand the troubleshooting scope.

Configure routing and DNS

For standard traffic splitting, start with the “Bypass mainland China” preset rules, then add domain or process rules as needed. DNS settings must match the current proxy mode: system proxy mainly affects apps that honor proxy settings, while TUN also captures broader network traffic and DNS requests.

Verify the connection and routing

Open a website that requires a proxy to confirm the connection, then visit a site that should connect directly to check routing. If the connection fails, inspect the client log and distinguish subscription update failures, incorrect node parameters, inactive system proxy, DNS errors, and local security-software restrictions.

DOWNLOAD FAQ

Common Download and Installation Questions

These questions cover version selection, CPU architecture, upgrades, and first launch. Troubleshoot connection parameters, routing, and DNS separately after the client is installed.

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

Choose the desktop edition first. Its new cross-platform interface and settings structure are better suited to fresh installations and make it easier to keep the same workflow across desktop platforms. The classic WPF edition retains traditional Windows windows, menus, and tray behavior; choose it when you already rely on the older workflow or specifically need the classic interface.

Both editions are v2rayN; do not run them at the same time. Exit the client before switching and back up subscription groups, routing rules, DNS settings, and local listening ports.

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

Open “About This Mac” from the system menu and check the chip or processor field. Choose the Apple Silicon package for an Apple M-series chip, or the Intel package when Intel is shown. Do not rely only on the device model or purchase year; the same exterior series may use different processors.

Should Android users download arm64 or the universal edition?

Most mainstream Android phones released after 2015 use arm64. The arm64 package contains only the matching architecture and is more focused. If the processor is unknown or installation reports an architecture mismatch, switch to the universal edition, which supports more compatibility targets while providing the same primary features as arm64.

Should Linux users choose a deb or rpm package?

Choose deb for Ubuntu, Debian, and derivatives; choose rpm for Fedora, RHEL, and compatible distributions. The format follows the distribution’s package system. Confirm the architecture separately: use x64 for standard 64-bit Intel or AMD computers and arm64 for ARM devices.

If the client starts but the tray icon is missing, check whether the desktop environment provides a status-icon or tray extension. This issue is usually unrelated to the deb or rpm format itself.

Do I need to remove the existing client before installing a new version?

You can usually install the new version directly. Exit the running client first and back up subscription groups, routing rules, custom DNS, local listening ports, and per-app settings. When switching from classic WPF to the desktop edition on Windows, or upgrading across many versions, keep a copy of the original configuration directory and compare each field with the new interface.

Why can’t I connect immediately after installing the client?

The client manages settings and runs the proxy core, but the package does not include a ready-to-use server configuration. After launch, import a valid subscription or individual node, select a configuration, and set the system proxy or TUN mode. If it still cannot connect, check the subscription update time, node parameters, system time, proxy mode, DNS, and client log in order.