Graphical client
Free to use
Open-source code

V2Ray Client Download

Choose a client by platform, then select the architecture and package format. For desktop, use v2rayN; for Android, v2rayNG is the recommended choice, with v2flyNG as an alternative.

Choose a platform Install a client Import a subscription

Desktop: v2rayN
Recommended for Android: v2rayNG · Xray
Android alternative: v2flyNG · V2Fly

Windows: v2rayN packages

This page provides x64 downloads. Check your system type under “Settings → System → About” before choosing an interface edition.

v2rayN

Recommended 7.24.1

The Desktop edition uses a newer cross-platform UI; WPF keeps the classic Windows interface. Both editions manage connection settings, subscriptions, and proxy options. Choose based on your preferences and system compatibility, not connection speed.

Desktop edition · x64

Download v2rayN Desktop

The Desktop edition is a good starting point for a first-time installation. The download is a ZIP archive: extract all files before running the installer inside.

Classic WPF edition · x64

Download v2rayN WPF

Choose this edition if you prefer the classic Windows layout. Exit any running client before installing to avoid listening-port conflicts.

Windows system and installation checklist

Check	What to look for
Processor architecture	Both packages on this page are x64 and won’t run directly on 32-bit systems. On ARM devices, first confirm that Windows can run x64 apps.
System requirements	Use a Windows version that still receives system updates. Check the installer’s prompts for specific operating system and runtime requirements.
Installation location	Choose a location you can access with your account. Extract the entire archive before running the app; don’t launch it from the ZIP preview window.
Permissions and proxy	System proxy and TUN have different permission requirements. Grant elevated permissions only when prompted for a feature that requires them.

After installation, open the main window, import a subscription, and select a server. To route browser traffic through the proxy, choose “Automatically configure system proxy” under “System Proxy,” then check the local mixed listening port under “Settings → Parameters.” Use the port shown in your client rather than copying a number from another guide. If your browser has its own proxy extension, check that it isn’t overriding the system settings.

Before migrating from an older version, back up your subscription groups and custom routing rules, then close the old process. Don’t run Desktop and WPF at the same time to test the same port; port conflicts and changes to system proxy settings can make troubleshooting confusing. Confirm the new version connects successfully before removing the old directory. For the next steps, see the system proxy guide.

macOS: choose v2rayN for your chip

Open “About This Mac” from the Apple menu. Choose Apple Silicon if it shows an Apple chip, or Intel if it shows an Intel processor.

v2rayN

7.24.1

v2rayN for macOS uses the desktop interface, with packages for different processor architectures. Subscription management and routing work much the same, but macOS handles system proxy settings and permission prompts differently. Don’t follow the Windows system settings steps on a Mac.

Apple Silicon · arm64

Download v2rayN · Apple Silicon

For Macs with Apple chips. Choose the native architecture that matches your processor; there’s no need to select the Intel package just to follow an older guide.

Intel · x64

Download v2rayN · Intel

For Macs with Intel processors. “64” in the package name identifies the architecture; it doesn’t indicate a different proxy protocol.

macOS system and installation checklist

Check	What to look for
Processor architecture	Choose arm64 for Apple silicon and x64 for Intel. Check “About This Mac” to confirm your processor.
System requirements	Use a macOS version that still receives system updates. Check the current installer or app launch prompt for the minimum supported version.
Package format	Open the DMG and follow its instructions to install the app in “Applications.” Don’t keep running it from the mounted disk image.
Network permissions	Respond to system prompts as needed for the features you use. Check system proxy settings first, and enable TUN only if needed.

If macOS blocks the app on first launch, check the app name, download source, and reason shown in the system alert. Then review the relevant message under “System Settings → Privacy & Security.” Don’t bypass the alert by disabling system security protections, and don’t paste terminal commands unless you understand what they do. A wrong architecture and missing permissions are separate issues; troubleshoot them separately.

After installation, import your existing settings and select a server. Some apps may continue using their own proxy settings even when the system proxy is enabled; terminal apps may not use it automatically either. For a first test, use a browser that follows system settings and check the client logs. Before closing the client, turn off the system proxy so it doesn’t keep pointing to a local port that is no longer listening.

Android: v2rayNG and v2flyNG

For most phones released since 2015, try arm64 first. If you’re unsure of the device architecture, choose the universal version. The architecture supported by the installed operating system is what matters.

v2rayNG

Recommended 2.2.6

v2rayNG is an Android graphical client that uses the Xray core. For your first setup, try v2rayNG and import the connection details provided with your subscription. Supported protocols and transport features depend on what both the current client and server configuration support.

arm64 · Recommended

Download v2rayNG · arm64

For devices that support arm64-v8a. If Android reports an architecture incompatibility, check your device information or try the universal version.

Universal · Multiple architectures

Download v2rayNG · Universal

For devices where the architecture is unclear. This package supports more architectures and is usually larger than a single-architecture package.

v2flyNG

Alternative · V2Fly core 1.10.31

An alternative Android client that uses the V2Fly core. A good fit if you already have compatible settings and want to use the V2Fly ecosystem. Don’t assume both apps support exactly the same options; check the subscription format and transport settings before switching.

arm64

Download v2flyNG · arm64

Recommended for devices that support arm64-v8a. Import your settings separately after installation; subscriptions aren’t shared automatically between apps.

Universal

Download v2flyNG · Universal

An alternative when you’re unsure of the device architecture. Disconnect the other client’s VPN before testing.

Android system and installation checklist

Check	What to look for
Processor and system architecture	arm64 corresponds to arm64-v8a. A 64-bit-capable processor doesn’t guarantee that the installed operating system provides a 64-bit app environment.
Android version	Check the APK installation prompt for the minimum supported Android version. The universal package won’t fix an operating system that’s too old.
Installation permissions	Allow APK installation only for the browser or file manager you use to open the file. You can revoke that source’s permission afterward.
VPN connection permission	When you start the proxy, approve the VPN connection request from Android. Typically, two apps can’t use the system VPN connection at the same time.

Installing the app doesn’t import a connection. Open the client, add a subscription group, paste an existing subscription URL, and update it. Then select a profile and start it. When Android first asks for VPN permission, confirm that the request comes from the client you’re using. A connection indicator only means Android established a local VPN tunnel; it doesn’t prove the remote server is working. Test an actual connection and check the logs.

If the connection drops after the screen locks, check battery optimization and background activity restrictions instead of repeatedly switching APKs. If installation reports a conflict with an existing app, the signing certificate or installation source may be different. Back up your settings before deciding whether to uninstall; uninstalling usually deletes app data. When comparing the two apps, use the same node and network conditions to distinguish client settings from server issues.

Linux: choose deb or rpm

First check your distribution’s package format, then confirm the CPU architecture. Both the file extension and architecture must match; don’t choose by client name alone.

v2rayN

7.24.1

The Linux desktop edition is available as deb and rpm packages. Use your distribution’s software installer to handle dependencies, then launch the app from the application menu. The two main downloads below are x64; arm64 devices can use the links in smaller text.

deb · x64 / amd64

Download v2rayN · deb

For compatible distributions that use deb packages, such as Debian and Ubuntu. The package’s dependencies must still be met.

rpm · x64 / x86_64

Download v2rayN · rpm

For distributions that use rpm and meet this package’s dependencies. The same file extension doesn’t guarantee compatibility with every system release.

For arm64 devices: Download arm64 deb Download arm64 rpm

Linux system and installation checklist

Check	What to look for
Desktop environment	This page provides a graphical client. You need a desktop session that can run GUI apps; this isn’t a command-line package for server deployment.
Architecture names	amd64 and x86_64 correspond to the x64 packages on this page; arm64 and aarch64 correspond to the arm64 packages.
Distribution and dependencies	deb and rpm identify package formats, not system library compatibility. Let your package manager check dependencies; don’t force an installation by ignoring them.
Proxy and permissions	The desktop system proxy affects only apps that follow that setting. TUN requires additional permissions and system support; it’s not the same as the system proxy.

If the installer reports missing dependencies, save the full error and check whether your distribution version meets the requirements. Don’t copy system libraries from another distribution or try to install an rpm as a deb by changing its extension. If the graphical app won’t launch, check the desktop session, file permissions, and existing processes before assuming the problem is your connection settings.

Start connection testing with the basics: import one working profile, confirm the core starts, then test with an app that explicitly uses the proxy. The desktop proxy, a browser’s own proxy settings, and terminal environment variables can all work independently; changing one doesn’t update the others. Verify the regular proxy before enabling TUN. If only one app can’t connect, check how it reads proxy settings before reinstalling the entire client.

After installation

First-run and update checklist

Back up before migrating

Before updating a device with existing settings, save your subscription groups, custom routing rules, DNS settings, and local port records. Backups may contain connection credentials, so store them somewhere you control and don’t share them in public forums. Don’t assume settings will migrate automatically when changing interface editions, installation sources, or client names. After importing, check each setting before removing the old version.

Test a node before enabling the proxy

The package provides a client, not a working subscription. Add an existing subscription, update it, and test a server. Tcping checks whether the target port is reachable; a real connection test more closely reflects an actual proxy request. Neither guarantees every site will always be available. If a test fails, first check the subscription’s validity, system time, and node settings rather than immediately changing routing or DNS.

Change one setting at a time

Confirm the regular system proxy works before configuring routing rules or TUN. Record each setting and its result as you go; changing the port, DNS, and routing at once makes it harder to find the cause of a problem. Before exiting the client, check that the system proxy has been restored. If websites suddenly stop loading, make sure the system isn’t still pointing to a local port that has been closed.

For setup steps, see the subscription import and first connection guide. If the client is installed but you can’t connect, visit v2rayN troubleshooting and follow the steps for your symptoms.

Download questions

Package selection FAQ

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

For a first-time installation, try the Desktop edition, which uses a newer cross-platform interface. Choose WPF if you prefer the classic Windows interface. Both require you to import connection settings. Back up your existing configuration before switching, and don’t enable system proxy or TUN mode in both clients at the same time.

Android: arm64 or universal?

For most phones released since 2015, try arm64 first, but check which architecture the device’s operating system actually supports. If you’re unsure or arm64 reports an incompatibility, choose the universal version. It includes more architectures and is usually a larger download. Check your Android version and available storage before switching packages.

Why might the version shown differ from the package filename?

The displayed version and package paths for each architecture come from different manifest fields, so they may not update at the same time. This page uses the filenames provided by the manifest rather than inferring download URLs from the version text. Check the client’s About page for the installed version; don’t change version numbers in download URLs manually.

Why can’t I connect right after installation?

The client package doesn’t include connection settings. Import an existing subscription or node, update the subscription, and select a server. Then enable system proxy or TUN mode as needed. Test one node first, then check the listening port, routing preset, and browser proxy settings.

What should you keep before updating the client?

Keep your subscription groups, custom routing rules, DNS settings, and local port records. Store backups somewhere you control. Exit the client before updating, then check that your settings migrated correctly. Don’t run the old and new versions at the same time, and never show subscription URLs or connection credentials in public screenshots.

What should you check if a download is interrupted or installation fails?

If a download is interrupted, check your browser’s download history, available disk space, and network connection, then download the package again. If installation fails, note the full error and confirm the operating system, processor architecture, and package format match. Don’t disable all security protections to troubleshoot; check for leftover proxy settings from another client separately.