Choose by operating system and CPU architecture

V2Ray Client Downloads

Use v2rayN on Windows, macOS, and Linux; on Android, choose between v2rayNG and v2flyNG. Installers are grouped by platform, interface edition, and CPU architecture.

v2rayN 7.24.1 v2rayNG 2.2.6 v2flyNG 1.10.31

Platform packages

Open the installer list for your platform

The platform choice is saved in the page URL, so refreshing keeps you on the current option. Each panel lists only the graphical clients for that system, without mixing in unrelated files.

Windows packages

Windows: v2rayN Desktop and WPF editions

Both installers target x64 Windows. The Desktop edition uses a modern cross-platform UI and suits first-time installations; the classic WPF edition keeps the traditional Windows interface for users familiar with the older menus and system-tray workflow.

v2rayN

Recommended Current release 7.24.1

A Windows graphical client with subscription groups, node selection, system proxy, routing rules, logs, and core switching. After extracting and installing it, import your service URL from the Subscription menu on the main screen.

Desktop edition Modern cross-platform UI

Best for new installations, with an interface structure closer to the macOS and Linux versions. Choose it if you want a similar workflow across desktop operating systems.

Download the Desktop edition v2rayN-Desktop-Setup-x64-7.24.1.zip

Classic WPF edition Traditional Windows interface

Best for users familiar with the classic v2rayN menus, system-tray icon, and settings window. If you already rely on the older workflow, WPF reduces the adjustment required.

Download the classic WPF edition v2rayN-Setup-x64-7.24.1.zip

Windows requirements and selection guide

Check	Recommended condition	How to check
Windows version	A supported 64-bit Windows release	Open “Settings → System → About” and check the system type and version.
CPU architecture	x64	When the system type says “64-bit operating system, x64-based processor,” use the Windows installer provided on this page.
Interface edition	Desktop or WPF	Choose Desktop for a first installation; choose WPF to keep the classic workflow.
Upgrade method	Exit the running client before installing	Record subscription groups and custom routing settings before upgrading. After installation, confirm that the configuration loaded correctly.

macOS packages

macOS: choose v2rayN by chip

macOS installers come in Apple Silicon and Intel variants. Their capabilities are aligned, but each binary targets a different processor, so check the chip information in About This Mac before downloading.

v2rayN for macOS

Desktop client Current release 7.24.1

A v2rayN desktop client for macOS, with a layout close to the modern Desktop edition. After importing a subscription, manage groups, switch nodes, set routing modes, and review connection and configuration-loading details in the log window.

Apple Silicon M-series chip

Choose this package when the chip field in About This Mac shows an Apple M-series chip. Most current Mac devices use this architecture.

Download the Apple Silicon edition v2rayN-arm64.dmg

Intel x64 processor

Choose this package when the processor field in About This Mac shows Intel. Do not infer the architecture from the device’s appearance or purchase year alone.

Download the Intel edition v2rayN-64.dmg

macOS requirements and selection guide

Check	Available option	How to identify it
Chip architecture	Apple Silicon or Intel	Open About This Mac from the system menu and read the chip or processor field.
Installer format	DMG	After opening the disk image, follow the window instructions to move the app to the Applications folder.
System permissions	Permissions related to networking and the system proxy	On first launch, follow the system dialog to grant permission, then return to the client and check the system proxy status.
Before upgrading	Exit the old process	Quit the running client from the menu bar before replacing the old version in the Applications folder.

Android packages

Android: v2rayNG and v2flyNG

v2rayNG is the recommended Android choice, using the Xray core and covering common subscription and routing features. Choose v2flyNG when you need the V2Fly core. Each client offers arm64 and universal installers.

v2rayNG

Recommended Xray core Current release 2.2.6

An Android graphical client supporting QR-code scanning, clipboard import, subscription groups, routing modes, per-app proxying, and logs. Most mainstream phones released after 2015 can use arm64 directly; choose universal when the device architecture is unknown.

arm64 edition Preferred for mainstream phones

Built for arm64-v8a processors, with an installer focused on the architecture used by most current devices. Most Android phones released in recent years can use this edition.

Download v2rayNG arm64 v2rayNG_2.2.6_arm64-v8a.apk

Universal edition Broader architecture coverage

Use this edition when the processor type is unknown, the device is older, or the arm64 installer reports an incompatibility. The universal package includes files for more architectures.

Download the v2rayNG universal edition v2rayNG_2.2.6_universal.apk

v2flyNG

Alternative V2Fly core Current release 1.10.31

An Android client based on the V2Fly core for users who specifically need V2Fly configuration compatibility. Whether subscriptions and node parameters work depends on the server protocol, transport fields, and the client’s supported features.

arm64 edition For mainstream devices

Built for the arm64-v8a architecture. Choose this installer first when the device information identifies a 64-bit ARM processor.

Download v2flyNG arm64 v2flyNG_1.10.31-fdroid_arm64-v8a.apk

Universal edition Wider compatibility

Suitable for devices with an unknown processor architecture. If the arm64 package will not install, try the universal edition to test compatibility again.

Download the v2flyNG universal edition v2flyNG_1.10.31-fdroid_universal.apk

Android requirements and selection guide

Check	Recommended choice	Details
Client	v2rayNG first	Use v2rayNG for common subscriptions; choose v2flyNG when you specifically need the V2Fly core.
CPU architecture	Prefer arm64	Most mainstream phones released after 2015 use arm64; try the universal edition if installation fails.
Installer format	APK	Open the completed download from the system’s download history and grant permission for this installation when prompted.
Background operation	Adjust according to your device settings	If the connection is frequently stopped by the system, check battery optimization, background activity, and notification permissions.

Linux packages

Linux: v2rayN deb and rpm packages

Linux packages are divided by distribution package system and CPU architecture. Debian and Ubuntu-based systems generally use deb, while Fedora, Rocky Linux, AlmaLinux, and RHEL-based systems generally use rpm.

v2rayN for Linux

Desktop client Current release 7.24.1

A Linux graphical desktop client with subscription management, node switching, routing, and log inspection. Confirm both the distribution package format and CPU architecture; the file extension alone is not enough.

deb x64 Debian / Ubuntu family

For x64 desktop distributions using the deb package system. Most common Intel or AMD desktops and laptops should use this package.

Download deb x64 v2rayn_7.24.1_amd64.deb

ARM devices: Download deb arm64 v2rayn_7.24.1_arm64.deb

rpm x64 Fedora / RHEL family

For x64 distributions using the rpm package system. Before installing, confirm that the system can handle rpm packages and their dependencies.

Download rpm x64 v2rayN-7.24.1-1.el10.x86_64.rpm

ARM devices: Download rpm arm64 v2rayN-7.24.1-1.el10.aarch64.rpm

Linux requirements and selection guide

Distribution or device	Package format	Architecture choice
Debian, Ubuntu, and derivatives	deb	Choose x64 for standard Intel or AMD computers; choose arm64 for ARM devices.
Fedora, Rocky Linux, AlmaLinux, and RHEL family	rpm	Choose x64 for x86_64 devices; choose arm64 for aarch64 devices.
Desktop environment	Graphical desktop session	v2rayN is a graphical client and requires a working desktop environment to display its settings window and system-tray entry.
Before installation	Package manager and dependencies	Install with your distribution’s package tool and follow terminal prompts to add any missing runtime dependencies.

Before installation

Confirm these three things before downloading

The same client name does not mean every installer is interchangeable. Match the operating system, CPU architecture, and package format one by one before moving on to installation and subscription setup.

Confirm the operating system

Windows, macOS, Android, and Linux use different installation formats. Choose v2rayN for desktop systems, and select v2rayNG or v2flyNG on Android according to the core you need. Similar names do not make installation files interchangeable.

Confirm the CPU architecture

x64, arm64, and universal describe the processor coverage of an installer. Read the chip field in About This Mac for macOS, check system information on Linux, and try arm64 first on most Android devices.

Keep a record of your existing configuration

Before upgrading, record subscription groups, custom routing, DNS, and local port settings. After installation, confirm that the client starts, then import the subscription and check the logs. Avoid changing several settings at once so the cause of a problem remains clear.

Next step

Configuration order after installation

Start the client and check the logs
Once the client opens normally, check the log window for configuration parsing errors, port conflicts, or runtime-environment errors. Avoid changing complex routing rules during the first launch.
Import the subscription and update groups
Copy the complete subscription URL, add a group from the client’s Subscription menu, and run an update. If the list is empty, check the URL format and log messages first.
Choose a node and routing mode
Select an available node first, then configure the system proxy and routing mode for your use case. Add custom rules gradually, starting with entries whose scope is clear and easy to verify.
Verify the connection and save settings
Confirm that the client status, system proxy status, and log output agree. If you need startup launch, enable the corresponding option in the client settings afterward.

Read the subscription import guide Open the configuration file reference

Download FAQ

Common download and installation questions

These questions cover installer versions, CPU architectures, package formats, and subscription updates. A client that installs successfully may still have incorrect subscription parameters, so troubleshoot installation and configuration separately.

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

For a first installation, choose Desktop because its modern cross-platform interface has a workflow closer to Windows, macOS, and Linux. Choose WPF if you know the classic menus, system-tray entry, and settings window or want to preserve the old workflow. Both target Windows x64; the main difference is the interface technology and interaction layout, and there is no need to install both.

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. If it shows an Apple M-series chip, download Apple Silicon, whose filename includes arm64; if it shows an Intel processor, download Intel. The wrong architecture usually causes installation or startup failures or an incompatibility warning. Replace the installer rather than changing subscription content.

Should Android users choose arm64 or the universal edition?

Most mainstream Android phones released after 2015 use arm64, so try that edition first. Choose universal if the architecture is unknown, the device is older, or installation reports incompatibility. It includes more processor architectures and is usually larger, but the client features and subscription format remain the same.

Should Linux users download a deb or rpm package?

Choose deb for Debian, Ubuntu, and derivatives; choose rpm for Fedora, Rocky Linux, AlmaLinux, and RHEL-based distributions. Then check the architecture: standard Intel or AMD desktops generally use x64, while ARM boards or desktops use arm64. A correct package format with the wrong architecture still cannot be installed.

What should I do if subscription updates fail after installing the client?

Check that the subscription URL is complete and that copying did not add spaces or line breaks, then verify the system clock and network connection. Open the client log and address timeout, DNS resolution, certificate, or content-format errors one by one. Updating the client only replaces the local program; it does not repair an expired subscription URL or node configuration with missing fields.