Choose an installerPick your platform, then check the architecture

V2Ray Download
Client Installers

Choose v2rayN for desktop. For Android, start with v2rayNG; consider v2flyNG if you need compatibility with V2Fly core configurations. Picks are based on platform and core compatibility, not ratings.

Windows installers

Choose an interface first: Desktop or classic WPF. Then check your system architecture. Both downloads below are x64 archives. Extract the files before running the installer.

v2rayN

Windows desktop client

Top pick

Optional Xray corex647.24.1

Download v2rayN Desktop

Desktop: a newer cross-platform UI and a good place to start for a fresh install.

Download the classic WPF edition

WPF: a tried-and-tested option for users who prefer the familiar Windows workflow.

What’s different: Desktop and WPF mainly differ in interface technology and interactions, not in the proxy protocols they use. Node compatibility still depends on subscription fields, the selected core, and server configuration. If your current setup works, back it up before switching editions so interface changes don’t get confused with connection issues.

View the installation and subscription import guide →

System requirements and installation

Check	What to look for
Processor	x64 system. Find your system type under Settings > About.
System compatibility	Follow the current installer’s prompts for Windows version and runtime requirements.
File permissions	You need appropriate read and write access to the install location and configuration folder.
TUN permissions	Virtual network adapter features may require administrator approval.

Install steps: Extract the entire archive to its own folder; don’t launch the app from inside the archive. If a runtime component is missing, install the one specified in the prompt and try again. Don’t keep switching installers to work around the same error.

Running both editions: Don’t run Desktop and WPF at the same time if they use the same local listening ports. Before testing a new version, quit the old process and check the system tray and system proxy settings. Closing the window may not quit the client.

macOS installers

Check your chip: Open the Apple menu and choose About This Mac to see whether your Mac has Apple silicon or an Intel processor. Prefer the installer built for your Mac’s native architecture.

v2rayN

macOS desktop client

Recommended for desktop

Cross-platform UIDMG7.24.1

Download for Apple silicon

arm64: for Macs with Apple silicon.

Download for Intel

x64: for Macs with an Intel processor.

Install: Open the DMG and follow the prompts to move the app into your Applications folder, then launch it from there. Avoid running it long-term from the mounted disk image; managing updates, permissions, and configuration can be less convenient. If you see a security warning on first launch, check the file’s source and the specific reason given by macOS, then follow the appropriate approval steps in System Settings.

View desktop client setup steps →

Check system requirements and chip

Check	What to look for
Apple silicon	Choose the arm64 Apple silicon installer.
Intel processor	Choose the x64 Intel installer.
macOS version	Check the minimum requirements shown by the installer and macOS.
Permissions	Grant system proxy and virtual network adapter permissions only if needed.

Test the proxy: After importing your configuration, test browser access through the system proxy before considering TUN. Some apps don’t use the system proxy setting. That’s separate from choosing the right installer, so one app failing to connect doesn’t necessarily mean the installation failed.

Before updating: Back up your existing settings and quit the running app before replacing it. After updating, check your subscription groups, local listening address, and routing mode. Menu names aren’t necessarily the same across platforms or as they are on Windows.

Android installers

Client choice: Start with v2rayNG, which uses the Xray core. Choose v2flyNG if you need compatibility with the V2Fly core. Most mainstream phones released since 2015 can use arm64, but check the app architectures your device supports.

v2rayNG

Android · Xray core

Top pick

APKSubscription import2.2.6

Download v2rayNG arm64

For most devices, check for arm64-v8a support first.

Download v2rayNG universal

For unknown architectures; includes components for multiple architectures.

Why choose it: v2rayNG suits Android setups built around the Xray configuration ecosystem. If your subscription uses settings such as VLESS and REALITY, check that the core version supports the fields you need rather than relying on the client name alone. On first connection, approve the system VPN request. This lets the client create a local traffic tunnel; it does not provide a working server.

See how to import an Android subscription and connect →

v2flyNG

Android · V2Fly core

Alternative core

APKV2Fly configuration support1.10.31

Download v2flyNG arm64

Choose this build if your device supports arm64.

Download v2flyNG universal

For devices that need components for multiple architectures.

Compatibility: v2flyNG is an alternative built around a different core family, not just a different skin for v2rayNG. Similar interfaces or subscription formats don’t guarantee identical features. Before switching, check the protocol, transport, security settings, and custom configuration. Don’t assume configurations that rely on Xray-specific fields will work with the V2Fly core.

Check core and configuration compatibility →

Android requirements and installation notes

Check	What to look for	After installation
Device architecture	Most mainstream devices use arm64. If you’re unsure, check your device specifications or choose the universal build.	If you see an incompatibility warning, check the system and app architectures.
System compatibility	Check the installer’s stated minimum Android version.	Save the full error message; don’t just download the file again.
Install permission	Follow Android’s prompts and allow installs only from the source you’re using for this file.	You can revoke temporary install permission once setup is complete.
Connection permission	Approve the system VPN request when connecting, and check for other VPN apps already in use.	Avoid having multiple apps compete for the same connection tunnel.

Background activity: If the connection drops when the screen locks, check battery optimization, background activity, and app sleep settings before reviewing the client logs. A universal APK won’t bypass background restrictions, and switching architecture builds won’t fix an invalid subscription or an unreachable server.

Update limitations: If an app with the same name won’t install over the existing version because of a signing mismatch, back up your settings and check the source before taking action. Uninstalling may erase app data. Remove the old app only after confirming the migration steps.

Linux installers

Choose a package format: Check whether your distribution uses deb or rpm, then confirm x64 or arm64. The file extension reflects the package system; renaming a file won’t convert it to another format.

v2rayN

Linux desktop client

Recommended for desktop

deb / rpmDesktop session7.24.1

Download v2rayN · x64 deb

For x64 desktop systems that use deb packages.

Download v2rayN · x64 rpm

Check that the package meets your distribution’s requirements and dependency versions.

For arm64 devices arm64 deb arm64 rpm

Compatibility: A matching package format doesn’t guarantee that an installer will work on every distribution. System libraries, desktop components, and package dependencies must still meet the installer’s requirements. In particular, don’t force-install an rpm on another distribution just because the extension matches. Open the file with your system’s graphical software installer and review the dependency resolution before confirming.

View routing, DNS, and TUN setup →

System requirements and desktop environment

Check	What to look for
Package system	Choose deb or rpm for your distribution, then check compatibility with your system.
Processor architecture	amd64 and x86_64 correspond to x64; aarch64 corresponds to arm64.
Runtime environment	Requires a desktop session that can run graphical apps and their dependencies.
Network permissions	Features such as TUN require additional network permissions. Follow your system’s prompts.

System proxy: Desktop environments handle proxy settings differently. After starting the client, check the local listening port, then confirm whether the app you want to use reads the desktop proxy settings. Terminal apps and browsers may behave differently.

Installation failed: Start with the dependency and architecture errors shown by the software installer. Don’t force an installation to bypass dependency checks, and don’t run the entire client with elevated privileges as a routine fix.

Set up the client after installation

Before connecting: A successful installation only means the client can run. Confirm where your configuration comes from, then enable proxy features one at a time to make troubleshooting easier.

Configuration source

Import a subscription or node

Manage subscriptions: Add a valid link to a subscription group and check for recognized nodes after updating it. Expired links, unexpected responses, and unsupported fields require different fixes. Don’t share a full subscription link in public screenshots or forums.

Subscription import steps →

Basic connection test

Choose a proxy mode

Choose a mode: On desktop, start by testing the system proxy. On Android, follow the prompts to create a VPN tunnel. Enable TUN only if you need to route traffic from more apps, and check the required permissions and DNS settings. System proxy, routing rules, and TUN are separate settings.

Routing guide →

Troubleshooting

Test one node

Troubleshooting order: Check the local listener and proxy status first, then review your subscription settings, system time, and server reachability. Change one setting at a time and keep a record of errors. A single timeout can’t tell you whether the problem is the client configuration, network path, or server.

View common connection issues →

Download and update FAQs

What to troubleshoot: Start with installer, architecture, and update issues. For connection setup, see the guides and advanced options.

Desktop or classic WPF for Windows: which should you choose?

For a first install, start with Desktop, which uses a newer cross-platform interface. The classic WPF edition offers familiar Windows controls and a tried-and-tested experience. They do not use different proxy protocols. Back up your settings before switching editions, and avoid running both at once to prevent port conflicts.

Android: arm64 or universal?

Most mainstream phones released since 2015 can start with arm64, but check which app architectures your device supports. If you’re unsure or arm64 is reported as incompatible, choose the universal build. It includes components for multiple architectures and is usually larger; that does not mean it offers faster connections.

Why might the version shown on a card differ from the download filename?

The version shown on each card and the installer paths for each platform come from separate manifest fields and may be updated at different times. Don’t edit filenames or download URLs based on the card text. To confirm the installed version, check the installer details and the client’s About page.

Can I connect as soon as the client is installed?

The client reads your configuration and establishes a connection; the installer does not include a working server. Import a valid subscription or complete node configuration, select a node, choose a proxy mode, and test the connection. Subscription links are sensitive and should not be shared publicly.

What settings should I keep before updating the client?

Back up your subscription groups, node settings, routing and DNS options, and custom outbound settings before updating. Quit the running client first. On the first launch after updating, check that your settings are intact, then test a node you know works. Don’t change several settings at once while troubleshooting.

V2Ray DownloadClient Installers

Windows installers

v2rayN

macOS installers

v2rayN

Android installers

v2rayNG

v2flyNG

Android requirements and installation notes

Linux installers

v2rayN

Set up the client after installation

Import a subscription or node

Choose a proxy mode

Test one node

Download and update FAQs

V2Ray Download
Client Installers