Download Center · 3 Clients

V2Ray Client Download

Pick your installer by platform: v2rayN for Windows, macOS and Linux, v2rayNG for Android, and v2flyNG when you need v2fly core behavior. All three clients import VMess, VLESS, Trojan, SS and REALITY subscriptions; after installing, select a node, set the routing mode and verify the connection in the client.

Clientsv2rayN · v2rayNG · v2flyNG / CoresXray · V2Fly / ProtocolsVMess · VLESS · Trojan · SS · REALITY

Selection tips

Use v2rayN across all three desktop systems; on Android, v2rayNG is the default, and you only switch to v2flyNG when you need v2fly core behavior. All three clients share the same subscription format, so switching clients does not require a new subscription URL. For a full comparison, see the selection guide; for first-time setup, see Quick start.

Platform installers

Installers and system requirements for four platforms

Windows and Linux offer v2rayN, Android offers v2rayNG and v2flyNG, and macOS splits into arm64 and x64 by chip. Switch tabs to see the installers, system requirements table and setup steps for each platform; the file names and version numbers in the cards come from each project's release listings.

v2rayN

v2rayN

Recommended

Desktop client for Windows 10 / 11 with the Xray core, supporting subscription groups, real connection latency tests and routing rule editing.

Download Desktop version New cross-platform interface, recommended for new installs Download classic WPF version Classic stable interface, keep using it if you already run the WPF version
Version 7.24.1 Desktop file v2rayN-Desktop-Setup-x64-7.24.1.zip WPF file v2rayN-Setup-x64-7.24.1.zip

System requirements: Windows 10 or later, or Windows 11, 64-bit. On first launch you must allow access in the firewall prompt, otherwise the system will block the local listening port.

Windows system requirements

v2rayN · Windows
ItemDetails
OS versionWindows 10 or later, Windows 11 (64-bit)
Version choiceChoose Desktop for new installs; choose WPF to keep the classic interface
InstallationUnzip the archive and run the installer inside, then follow the wizard
First launchAllow the app through the firewall so the local listening port works

Install and first launch

  1. Download the Desktop zip and unzip it, then run the installer in the extracted folder.
  2. Launch v2rayN and allow the app network access in the Windows firewall prompt.
  3. Open Subscription groups, paste your subscription URL and update; once the node list appears, select a node.
  4. Choose a routing mode in the routing settings, then turn on the system proxy switch to connect.

Client comparison

How the three clients compare

This download page covers three graphical clients: v2rayN for all three desktop platforms, v2rayNG as the Android default, and v2flyNG when you prefer the v2fly core. All three share essentially the same subscription format and configuration options, so switching clients does not require a new subscription URL.

Client · Platforms · Core · Best for
ClientPlatformsCoreBest for
v2rayN Windows / macOS / Linux Xray First choice on desktop; subscription groups, real connection latency tests and routing rule editing
v2rayNG Android Xray First choice on Android; per-app proxy, routing modes and launch on boot
v2flyNG Android V2Fly Alternative when you need v2fly core behavior; the interface and workflow are close to v2rayNG

V2Ray is the collective name for the clients and cores in the open-source Project V ecosystem. At the core level there are currently two branches, V2Fly and Xray: both implement VMess, VLESS, Trojan, Shadowsocks and other protocols, and both support transports such as WebSocket, gRPC and HTTP/2, so subscription links work with either branch. A graphical client simply wraps a core and provides interfaces for subscription management, node lists and routing settings, so when choosing a client, focus on your platform and habits rather than which core it bundles.

The three clients have clear roles. v2rayN covers Windows, macOS and Linux and is the single entry point for desktops. v2rayNG targets Android and offers settings that matter more on mobile, such as per-app proxy, routing modes and launch on boot. v2flyNG shares its codebase with v2rayNG and differs in the core branch, making it a fit for scenarios that need v2fly core behavior. The same subscription can be imported into both the desktop and Android clients, and node order and groups are maintained independently in each client.

Versions and updates: the buttons on this page point to the current installers in each project's release listings, and the file names and version numbers shown in the cards come from those listings and match the files the links point to. Each client also has a built-in check for updates, and your subscriptions and node settings are preserved when you upgrade. If you want to pick a protocol for a specific scenario or compare the two core branches feature by feature, continue with the protocol and core comparisons in the technical reference.

Download FAQ

Download and installation FAQ

Below are the six most common questions about downloading and installing. For full answers on subscription import, connection checks and troubleshooting, see the FAQ page and the technical reference.

What is the difference between the v2rayN Desktop and WPF versions, and which one should I choose?

The Desktop version is the newer cross-platform interface: Windows, macOS and Linux share the same interaction model and configuration logic, so it is the recommended choice for new installs. The WPF version is the classic Windows interface, and long-time WPF users can simply keep using it when they upgrade.

Both versions use the same core and support the same protocols, and subscription links can be imported into either one; the main difference is the interface and the workflow you are used to.

How do I check whether to download arm64 or x64 on macOS?

Click the Apple menu in the top-left corner and open About This Mac: models that show Chip: Apple M... need arm64, and models that show Processor: Intel... need x64.

The two installers contain different builds, so check your chip before downloading; you do not need to install both.

Should I choose the arm64 or the universal APK for my Android phone?

Mainstream phones released after 2015 use the arm64-v8a architecture, and the arm64 package is smaller. For older devices, emulators or when you are unsure about the architecture, choose the universal build, which bundles libraries for several architectures and therefore has broader compatibility.

Both versions offer the same features; the difference is package size and compatibility range. After installing, you can check the architecture in use inside the client.

How do I choose between deb and rpm on Linux, and what about arm64 devices?

Use deb for Debian, Ubuntu, Linux Mint and similar distributions; use rpm for Fedora, RHEL, openSUSE and similar. If you are unsure, run cat /etc/os-release to see the distribution name and choose accordingly.

On x64 machines, use the two main links in the card; on arm64 devices such as Raspberry Pi boards and ARM servers, use the small link below the card to download the matching package.

The system says the app is blocked or will not open after downloading. What should I do?

On Windows, the first launch triggers a firewall prompt, so select Allow access. On macOS, if the first launch is blocked, go to System Settings → Privacy & Security and click Open Anyway.

On Android, allow installing apps from this source when prompted; once installed, you can turn that permission back off without affecting the client.

Do I need to download the core separately after installing the client?

No. All three clients bundle the core in the installer, so it works right after launch, and the core version is updated together with the client.

This download page only offers client installers, not standalone core files. The differences between core branches are a technical topic covered in the core family notes in the technical reference.

After downloading

Next steps after installation

The installers only provide the client itself; connecting still requires importing a subscription and verifying it. The three documents below are ordered by how you will use them: start with Quick start, then check the technical reference and FAQ as needed.

Quick start

Step-by-step instructions for importing subscriptions, choosing a routing mode and verifying the connection, with separate sequences and setting locations for desktop and Android.

View tutorial →

Technical reference

How VMess, VLESS, Trojan, SS and REALITY differ, plus a feature comparison of the V2Fly and Xray core branches with selection advice.

View reference →

FAQ

Troubleshooting guidance for failed connections, subscription updates, DNS resolution and routing settings, organized under Basics and Troubleshooting.

View FAQ →