CLIENT PACKAGES

V2Ray Client Downloads

v2rayN, v2rayNG, and v2flyNG
Choose by operating system, architecture, and interface.

Check your device details before choosing an installer. Connection settings and subscriptions are separate; follow the quick start guide to import them.

PACKAGE SELECTOR

Choose an operating system

Downloads are grouped by platform. Select a tab to see the clients, architecture details, and requirements for that system.

v2rayN

7.24.1

Recommended · Windows

One client, two desktop interfaces. Desktop is the newer cross-platform UI; WPF is the classic stable edition. Both downloads below are for x64.

Download Desktop · x64 Download classic WPF · x64

Desktop: a consistent workflow across platforms

Desktop uses the Avalonia UI and suits users who want a similar workflow across multiple desktop operating systems. Node management, subscription updates, and settings are organized around desktop use. Menu names may change between interface versions. If a setting has moved, search by its function rather than matching its location in a screenshot.

WPF: a traditional desktop layout

The WPF edition is for Windows and retains the classic lists, menus, and settings windows. It’s a good fit if you already know this interface. The choice of UI does not make a connection faster; results still depend on core support, server settings, and network conditions. Export your configuration before switching, and avoid editing the same subscription in both editions.

Windows installation requirements

Check	What to look for	Before installing
System and processor	Both packages on this page are x64. Check the relevant release notes for supported Windows versions.	Check System type under System Information or About in Windows Settings.
Runtime dependencies	Dependencies may change between client releases.	If startup reports a missing runtime, install the required component and try again.
Install location and permissions	Assess standard proxy use separately from features that require elevated permissions.	Choose a folder you can read and write to. Grant permission for virtual network adapter features only when prompted.

If your system isn’t x64, don’t install based on the word Windows in the filename alone. First check whether your system supports programs built for that architecture. Emulation support and client feature compatibility are separate considerations.

v2rayN

7.24.1

macOS desktop client

Choose the DMG for your processor: arm64 for Apple Silicon or x64 for Intel. Use the package that matches your Mac’s architecture.

Download Apple Silicon · arm64 Download Intel · x64

Check About This Mac first

Open About This Mac from the Apple menu and check Chip or Processor. Choose the Apple Silicon package if an Apple chip is listed, or the Intel package if it shows an Intel processor. Don’t guess based on the Mac’s appearance or purchase year: similar-looking models may use different processors. Package size isn’t a reliable way to tell them apart.

Launch from Applications

Open the DMG and follow the prompt to move the app to Applications, then launch it from that folder. If a security warning appears the first time you open it, confirm which app it refers to and where the download came from, then follow the steps in System Settings. Don’t disable system-wide security as a routine installation step, and don’t run the app from the mounted disk image long-term.

After importing your configuration, test a node connection in the client before enabling the system proxy. Apps must use the system proxy settings for their requests to pass through the client. If you need a virtual network adapter, read the permission prompts and relevant guides separately. A successful installation does not mean every app is routed through the client.

macOS installation requirements

Check	What to look for	Before installing
Chip architecture	Use arm64 for Apple Silicon and x64 for Intel.	Check Chip or Processor in About This Mac.
OS compatibility	Check the release notes for the minimum macOS version.	Note your current macOS version. On older systems, check support for the interface and its dependencies.
App and permissions	Install in an app folder you can write to. Features that route additional traffic may require permission.	Quit the existing app before updating, and review each system prompt on first launch.

v2rayNG

2.2.6

Recommended · Xray core

For Android, v2rayNG is the recommended choice. Most mainstream phones released after 2015 use arm64; choose the universal build if you’re unsure of your device’s architecture.

Download v2rayNG · arm64 Download universal

Current download: v2rayNG_2.3.11_arm64-v8a.apk. The version shown on the page and the filename are read separately. After installation, check About to confirm the installed version.

Architecture and installation permissions

The arm64 package targets the corresponding app runtime architecture; the universal build includes components for more architectures. A 64-bit-capable processor does not necessarily mean the system can run every 64-bit app. If you see an incompatibility warning, check your system details. When installing from a browser or file manager, grant install permission only to the source you’re using. You can revoke it afterward in your security settings.

Confirm VPN permission before connecting

After importing a usable configuration and selecting a node, the system will ask for VPN permission the first time you connect. This allows the client to handle app traffic; it is separate from your node account. Resolve any conflict with an existing VPN connection first. If the connection drops when the screen locks, check battery optimization and background restrictions before trying a different installer.

v2flyNG

1.10.31

Alternative · V2Fly core

Choose this if your configuration specifically requires a V2Fly core. Before downloading, check that the protocol, transport, and configuration fields are supported by this version.

Download v2flyNG · arm64 Download universal

v2flyNG and v2rayNG have similar interface concepts, but use different core families and release schedules. Support for the same share link doesn’t guarantee that every extended parameter will work the same way. For connections that rely on specific core features, check the configuration provider’s guidance before switching clients.

To compare the clients, back up your configuration and test them one at a time; don’t run both connections simultaneously. A universal package won’t add support for fields the core doesn’t recognize. Architecture affects installation compatibility; core features affect configuration compatibility. Check them separately.

Android installation requirements

Check	What to look for	Before installing
App runtime architecture	Use arm64 for most recent devices; choose universal if unsure.	Check your system or device specifications. If installation fails, note the full error message.
OS version	Minimum requirements vary by client release.	A universal package may not support older systems. Check the release requirements first.
System permissions	Grant install-source permission and VPN connection permission separately.	After installing, import your configuration and review the system prompts needed to connect.
Existing installation	An in-place update requires a matching app signature and compatible version.	If you see a signature mismatch warning, back up your data before deciding how to migrate.

v2rayN

7.24.1

Linux desktop client

Choose deb or rpm for your distribution, then check your CPU architecture. The main downloads are x64; arm64 packages are listed below.

Download deb · x64 Download rpm · x64

arm64: Download deb · arm64 Download rpm · arm64

deb and rpm are package formats

Debian, Ubuntu, and related distributions typically use deb packages; Fedora and openSUSE typically use rpm. The same package format does not guarantee compatibility with every distribution release, so check package dependencies and build targets. In filenames, amd64 and x86_64 commonly indicate x64; arm64 and aarch64 indicate the corresponding 64-bit ARM architecture.

Install with a graphical package manager

Open the package in your file manager and use the system installer to review dependencies and the install location. If it reports missing dependencies or a version conflict, read the error details and check your distribution and software sources. Don’t force the installation by ignoring dependencies. Troubleshoot launch failures, missing tray icons, and connection problems separately.

This is a graphical desktop client and requires an active desktop session. Desktop environments may handle tray icons and autostart differently. After installation, launch it from the app menu and confirm that its configuration folder is writable before enabling autostart at login. Starting the app automatically is not the same as connecting to a node automatically.

Linux installation requirements

Check	What to look for	Before installing
Package format	Choose deb or rpm based on your distribution.	Check the distribution name and version in System Information.
CPU architecture	x64 uses amd64 / x86_64; arm64 uses aarch64.	Check your hardware details. Package format and architecture are not the same thing.
Desktop and dependencies	Requires a desktop session and the graphical dependencies for this release.	Let the system installer check dependencies; review any conflicts before proceeding.

BEFORE FIRST CONNECTION

Check installation and connection separately

The installer deploys the app. Subscriptions, nodes, and routing determine whether it can connect. Check them in order to avoid reinstalling unnecessarily.

Read the full quick start guide →

Before installing: back up your configuration

For a first-time setup, get a subscription URL or complete node settings you’re authorized to use. If you already have a client installed, use its export or backup feature to save your configuration and note the local ports, core selection, routing mode, and custom DNS settings. A subscription URL alone won’t preserve manually added nodes or local rules. Keep each of these settings in your backup, especially when switching interface editions.

Subscription URLs may contain access credentials, and share links may reveal connection details. Store backups somewhere access is controlled, and don’t post your full configuration when asking for help. Before sharing a screenshot, remove addresses, identifiers, and subscription details while keeping the fields relevant to the error.

First launch: import a configuration, then select a node

If the client opens, the app has started—but you still need to add a subscription or import nodes in its interface. Check that the expected entries appear, then select the connection you want to use. A subscription group is not the same as the active node, and updating a group won’t necessarily change the current connection. If importing fails, check the link format and whether the client supports it.

During testing, change one setting at a time. Keep the default listen address first, then check that the selected node has a complete address, port, protocol, and transport configuration before testing the connection. Don’t change DNS, sniffing, routing, and local ports all at once, or it’ll be hard to identify what affected the result.

After connecting: check how apps route traffic

System proxy settings affect apps that respect them; core routing handles requests that have already reached the client. These are separate layers. If a browser works but other apps don’t, first check whether those apps use the system proxy rather than immediately switching clients. On Android, also check the VPN connection status and which apps are included.

For more on how routing, DNS, and inbounds work together, see the JSON Configuration Handbook. Before editing configuration manually, check how the client generates its runtime config. Settings in the graphical interface may overwrite files at startup, so direct edits to generated files may not persist.

UPDATE / COMPATIBILITY

Version, architecture, and configuration compatibility

Project V is the open-source ecosystem behind V2Ray-related technologies; V2Fly and Xray are widely used core families. v2rayN, v2rayNG, and v2flyNG provide graphical management interfaces. Client and core version numbers follow separate schemes. Choose an installer based on your OS and architecture; check the actual core and its version to determine configuration support.

Downloads and displayed versions on this page come from separate manifest fields, so they may temporarily differ during an update. A filename may not include the version number. Don’t edit numbers in the URL yourself. After installation, confirm the actual version in the app’s About or information screen, and keep a backup of the configuration you used.

Before updating, quit the running client. If an in-place update fails with a signature, dependency, or permissions error, read the specific message instead of assuming it’s a network issue. After restoring your configuration, test a known connection before restoring subscription schedules, startup settings, and other customizations.

DOWNLOAD NOTES

Download and update FAQ

Five answers on choosing installers, checking versions, and migrating settings.

Can I connect right after downloading a client?

The client reads configuration, manages connections, and routes traffic. The installer does not include server connection details. First, get a subscription URL or node settings you’re authorized to use. Import them, select a node, then configure routing and how apps connect through the proxy.

Windows: Desktop or WPF?

Desktop uses a newer cross-platform interface, suited to users who want a similar workflow across desktop operating systems. WPF is the classic, stable edition for users familiar with the traditional Windows interface. Both must match your system architecture. Back up your configuration before switching, and avoid running both editions on the same ports.

Android: arm64 or universal?

Most mainstream phones released after 2015 should use arm64, but check that the system supports running apps built for that architecture. If you’re unsure of the architecture or the arm64 package reports an incompatibility, try the universal build. It supports more architectures but does not remove the client’s minimum OS requirements.

The version shown on the page differs from the installer filename. Which should I trust?

The displayed version and filename come from separate manifest fields, so they may differ during an update. Check the name of the downloaded file, then confirm the installed version in the client’s About screen. Don’t edit the download URL based on the version shown on the page.

What should I back up before updating?

Use the client’s export or backup feature to save nodes, subscriptions, routing, and custom settings. Note the current core selection and local ports. Exit the running client before updating. After restoring your settings, test one connection before enabling the system proxy or other traffic-routing options. Treat backup files as sensitive.